Context length issue / better context inspector #2841

Activity

1. github-actions commented on Sep 28, 2025

   

   github-actionsBot

   on Sep 28, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [Question] detailed per-interaction telemetry (token counts and input composition) for opencode-model communications #2666: [Question] detailed per-interaction telemetry (token counts and input composition) for opencode-model communications - discusses detailed token tracking and visibility into what's sent to the model
   • [Feature Request] Configuration to Limit Input Tokens per Request #2637: [Feature Request] Configuration to Limit Input Tokens per Request - specifically addresses context length management and control over token consumption

   Feel free to ignore if none of these address your specific case.
2. rekram1-node commented on Sep 28, 2025

   

   rekram1-node

   on Sep 28, 2025

   Collaborator

   More actions

   @geril07 what is likely causing extra context that isn't necessarily in the session.json is the tool definitions (along with mcp server tools if you have any).

   opencode ships with a variety of tools by default, each one has a JSON input schema, a name, a description, and then often a description for the different fields that can be passed to it.

   Due to that these do require additional tokens / cost and wouldn't be present when interacting just directly with llm without any tools. So that probably explains the context difference.
3. geril07 commented on Sep 28, 2025

   

   geril07

   on Sep 28, 2025

   ContributorAuthor

   More actions

   Yeah, that's logical. It would be nice to have an option to inspect the entire context, which was requested in #2666.
   Closing as a duplicate then, thanks.
4. geril07

   closed this as a duplicateof [Question] detailed per-interaction telemetry (token counts and input composition) for opencode-model communications #2666 on Sep 28, 2025