Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-04 · high
Developers pick the reasoning level per task, but separate research says effort cues can cost up to 7.4x with no success gain.
Why now: GitHub posted the reasoning dial and comment-triggered automations together in its August 3 changelog entry.
GitHub gave developers a per-task dial for Copilot cloud agent reasoning level, with higher settings burning more credits, per its August 3 changelog.
That choice now sits with whoever kicks off the task, across Pro, Pro+, Business, Enterprise, and Max tiers, turning compute spend into a per-developer bet. Separate research on prompt waste found that effort cues like this one can cost 1.6 to 7.4 times more in compute without improving success rates.
Comment-triggered Copilot automations shipped in the same changelog entry, another way to start agent work without anyone at the keyboard.
The changelog doesn't say if GitHub tested its own reasoning levels against the waste finding. It also doesn't say whether the top setting actually closes more tasks than the lowest one on the same repo.
Exposing the dial is the right instinct. Credits are real money, and a default nobody can see or adjust is worse than one you can tune. But a knob without data on what it buys isn't much better than a guess with a price tag.
Whether GitHub, or anyone else, publishes task-completion rates broken out by reasoning level. Until that shows up, "customize your reasoning level" reads as "customize how much you overpay."
Each link below shares sources, entities, or timing with this story.
VS Code uses Copilot / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (VS Code uses Copilot); both cover Business, Copilot, Enterprise, Same; reported by the same outlet (github.blog).
Microsoft released Copilot / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft released Copilot); both cover Business, Copilot, Enterprise, GitHub; reported by the same outlet (github.blog).
VS Code uses Copilot / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (VS Code uses Copilot); both cover Business, Copilot, Enterprise, GitHub; reported by the same outlet (github.blog).
VS Code uses Copilot / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (VS Code uses Copilot); both cover Business, Enterprise, GitHub; reported by the same outlet (github.blog).
Microsoft released Copilot / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Microsoft released Copilot); both cover Copilot, Enterprise, GitHub, Same; reported by the same outlet (github.blog).
Microsoft released Copilot / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Microsoft released Copilot); both cover Copilot, GitHub; reported by the same outlet (github.blog).
Copilot uses GPT / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Copilot uses GPT); both cover Copilot, GitHub; reported by the same outlet (github.blog).
Copilot supports Visual Studio / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (Copilot supports Visual Studio); both cover Copilot, GitHub; reported by the same outlet (github.blog).