GitHub Copilot

Copilot chat vs agent usage

Why Copilot agent runs consume far more credits than chat turns, how the two are metered, and how to choose between them.

Quick answer

A chat turn is one model call. An agent run is a loop of model calls plus tool use, so it can consume many times the credits. Use chat for questions and small edits, and agents for multi-step tasks where the loop saves you more time than it costs.

The cost difference

ModeModel callsTypical useCredit impact
Inline completionOneFinish a lineIncluded or minimal
ChatOne per messageExplain, draft, reviewLow
AgentOne per stepMulti-file taskHigh
Agent with retriesManyDebugging loopVery high

Choose the cheaper mode

  • Ask a question in chat before starting an agent.
  • Use an agent when the task needs file edits and test runs.
  • Stop the agent when the same error repeats.
  • Start a new agent session per task to avoid replaying context.
  • Use the default model for mechanical edits.

Measure the split

Organization metrics separate chat turns from agent activity, which is the first place to look when credits rise without more people. On a personal account, compare the balance before and after a session.

UsageAtlas keeps the reported Copilot balance over time so the jump is visible.

Chat and agent consume very differently

ModeModel callsAllowance impact
Inline completionOne short callMinimal
Chat questionOne call plus contextModerate
Agent taskMany calls plus toolsHigh
Agent loop on failureRepeated callsHighest

The same task can be cheap in chat and expensive in agent mode, because the agent reads files, runs commands, and revises. That is a fair trade when it finishes the task; it is pure cost when it loops.

Set a stop condition before starting an agent run, and see limits by plan for what each tier allows.

Questions, answered

Does an agent run count as one premium request?

No. An agent run can make many model calls, and each one can consume credits.

Is chat cheaper than inline completion?

Inline completion is usually included on the default model. Chat and agent calls are the metered part.

Can I limit agent steps?

Some clients allow a step or time limit. Where they do not, stop the run manually when it loops.

Browse by topic