Skip to content

fix(opencode): accumulate step tokens instead of overwriting - #42326

Closed
gold-beyond wants to merge 1 commit into
anomalyco:devfrom
gold-beyond:accumulate-step-tokens
Closed

gold-beyond wants to merge 1 commit into
anomalyco:devfrom
gold-beyond:accumulate-step-tokens

Conversation

@gold-beyond

@gold-beyond gold-beyond commented Aug 13, 2026

Copy link
Copy Markdown

Issue for this PR

Closes #42324

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

In multi-step tool-call messages, processor.ts overwrites assistantMessage.tokens on every step-finish event, so only the last step's output, reasoning, and cache.write survive — while cost already accumulates with +=.

This change accumulates the additive fields (output, reasoning, cache.write) across steps. input and cache.read keep the final step's values, because the final step's request already includes all prior steps and accumulating those would double-count. total keeps the final step's value as before.

This fixes under-reported context metrics and delayed auto-compaction for multi-step messages.

How did you verify your code works?

  • Added a two-step test in packages/opencode/test/session/processor-effect.test.ts with distinct per-step usage, asserting the accumulated message tokens.
  • bun typecheck passes.
  • bun test --timeout 30000 test/session/processor-effect.test.ts passes (one pre-existing failure unrelated to this change, reproducible on clean dev).
  • bun test --timeout 30000 test/session/compaction.test.ts passes.

Screenshots / recordings

This is not a UI change.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Multi-step tool-call messages overwrite assistantMessage.tokens on
each step-finish, keeping only the last step's output, reasoning,
and cache.write. Accumulate those fields like cost already does, and
keep the final step's input and cache.read since its request already
includes all prior steps.

Fixes anomalyco#42324
@github-actions github-actions Bot added needs:compliance This means the issue will auto-close after 2 hours. and removed needs:compliance This means the issue will auto-close after 2 hours. labels Aug 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for updating your PR! It now meets our contributing guidelines. 👍

@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Multi-step tool calls overwrite token counts instead of accumulating (output, reasoning, cache.write lost)

1 participant