Agent cost comparisons need work ownership as well as timing
By OnTheRice · Sources and limitations · Report a correction
One VS Code report found that a workflow total missed late subagent work and a separate follow-up. Teams comparing agent costs should reconcile the whole task before calling a setup cheaper.
Source confidenceNot assessed
What’s changing?
The reported gap included late subagent calls and a follow-up outside the workflow by design. The reporter also warns that time windows can include unrelated work.
Key points
- One VS Code report found that a workflow total missed late subagent work and a separate follow-up.
- Teams comparing agent costs should reconcile the whole task before calling a setup cheaper.
What could change this view?
- This is one public analytics report, not independent reproduction or evidence of incorrect customer billing. No universal undercount is established.
Bottom line
Evaluation teams: reconcile workflow, full-turn and per-call records, including delayed work, before comparing costs.
This is based on the information recorded with this signal.
How likely is this call? · Three frameworks
This signal has no investible bullish or bearish call. A market-direction percentage does not apply.
Evidence behind this view
Checks whether separate pieces of evidence support the same view.
Recorded connection
The reported gap included late subagent calls and a follow-up outside the workflow by design. The reporter also warns that time windows can include unrelated work.
We have not established a separate count of independent evidence clusters for this card. Several reports may rely on the same event or data provider.
What past price moves show
Compares today’s price moves with recorded past patterns.
This card has no recorded investible call. A price-pattern comparison is not applicable unless a specific asset is added with evidence.
Evidence against this view
Shows evidence and risks that could challenge this view.
Recorded opposing evidence and risks
This is one public analytics report, not independent reproduction or evidence of incorrect customer billing. No universal undercount is established.
Why the direction changed
Explains recorded changes from expecting a rise to expecting a fall, or the reverse.
No documented bullish-to-bearish or bearish-to-bullish change is available for this card. We keep the original call and its time unchanged.
What people say vs the facts
Compares recorded public discussion with checked market facts.
No separate Reddit or public-discussion comparison with verified market data is recorded for this card. We cannot treat social attention as proof of a market move.
How past forecasts performed
Shows recorded forecast results and what they can teach us.
This card has no recorded investible forecast to score.
No tested mapping from evidence combinations to future success is recorded for this card. Confidence in sources and past outcomes do not establish a calibrated probability.
Sources, original wording and price checks
Original research record
A Code OSS HydraFusion report recorded 1,917,421,000 nano-AIU for a full turn, versus 1,314,302,000 in the workflow total. These are usage units, not a verified cash bill.
The reported gap included late subagent calls and a follow-up outside the workflow by design. The reporter also warns that time windows can include unrelated work.
OTR’s view: timing alone can assign usage to the wrong task. Cost comparisons need a clear boundary and a record of which task started each call.
Evaluation teams: reconcile workflow, full-turn and per-call records, including delayed work, before comparing costs.
This is one public analytics report, not independent reproduction or evidence of incorrect customer billing. No universal undercount is established.
A matched test should reconcile task-linked totals after background work finishes.
The concern falls away if the chosen metric already covers the intended work or the gap cannot be reproduced.
Check the next matched evaluation or accounting fix. No asset direction or trade entry.
Published
First published through Sites 06 Oct 2026, 12:18:23 SGT
No explicit investible BULLISH or BEARISH call on this card.
What changed
Recorded public historyOne VS Code report found that a workflow total missed late subagent work and a separate follow-up. Teams comparing agent costs should…
This is the first recorded public view. Further public updates will appear here.
- Agent cost comparisons need work ownership as well as timing
One VS Code report found that a workflow total missed late subagent work and a separate follow-up. Teams comparing agent costs should reconcile the whole task before calling a setup cheaper.
First published by OTR: 6 Oct, 12:18 SGTPublished by OTR: 6 Oct 2026, 12:18 SGT
Why the view changed
This is the first recorded view. Future source-backed updates will appear here.
Evidence, memory & review 1 linked source
What changed: A Code OSS HydraFusion report recorded 1,917,421,000 nano-AIU for a full turn, versus 1,314,302,000 in the workflow total. These are usage units, not a verified cash bill.
Directional takeaway: UNASSIGNED / NO ENTRY
OTR reasoning: The reported gap included late subagent calls and a follow-up outside the workflow by design. The reporter also warns that time windows can include unrelated work.
Counterpoint: This is one public analytics report, not independent reproduction or evidence of incorrect customer billing. No universal undercount is established.
Source trail
- HydraFusion total_nano_aiu misses background subagent spend after a phase ends ↗microsoft/vscode public issue2026-10-05T22:26:25Z · published (UTC)
Review status: APPROVED
No score or probability is presented.