Description
OpenCode trajectories include token usage in raw events under tokens.input, tokens.output, tokens.reasoning, and tokens.cache, but the current parser only reads SDK-style fields like input_tokens and output_tokens.
Because of this, OpenCode reports show Tokens In = 0 and Tokens Out = 0, making aggregate comparisons with other CLI agents inaccurate.
Expected Behavior
OpenCode token usage should be parsed from raw OpenCode events and included in evaluation metrics.
Acceptance Criteria
- OpenCode runner records nonzero token counts from OpenCode
tokens events.
- Evaluation metrics can recover token usage from existing OpenCode trajectories.
- Aggregate reports show correct OpenCode token totals.
Description
OpenCode trajectories include token usage in raw events under
tokens.input,tokens.output,tokens.reasoning, andtokens.cache, but the current parser only reads SDK-style fields likeinput_tokensandoutput_tokens.Because of this, OpenCode reports show
Tokens In = 0andTokens Out = 0, making aggregate comparisons with other CLI agents inaccurate.Expected Behavior
OpenCode token usage should be parsed from raw OpenCode events and included in evaluation metrics.
Acceptance Criteria
tokensevents.