Hacker News Reader

Comment by rnadomvirlabe | Hacker News Reader

I find copilot to be much more straightforward, and I can track per request against my credits. Here is the explanation of what a request is:

https://docs.github.com/en/copilot/concepts/billing/copilot-...

View on HN

> A request is any interaction where you ask Copilot to do something for you—whether it's generating code, answering a question, or helping you through an extension. Each time you send a prompt in a chat window or trigger a response from Copilot, you're making a request. For agentic features, only the prompts you send count as premium requests; actions Copilot takes autonomously to complete your task, such as tool calls, do not. For example, using /plan in Copilot CLI counts as one premium request, and any follow-up prompt you send counts as another.

This clearly isn't true for agentic mode though. This document is extremely misleading. VSCode has the `chat.agent.maxRequests` option which lets you define how many requests an agent can use before it asks if you want to continue iterating, and the default is not one. A long running session (say, implementing an openspec proposal) can easily eat through dozens of requests. I have a prompt that I use for security scanning and with a single input/request (`/prompt`) it will use anywhere between 17 and 25 premium requests without any user input.

Do you have any evidence to support your claims? I keep a pretty close eye on my usage and have never seen it deviate from "1x/3x requests per time I hit enter". Is there a reproducible scenario I can try that will charge multiple requests for a single prompt?

Reply on news.ycombinator.com