allow using /context command #268
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I experimented with https://agentclientprotocol.com/rfds/session-usage (see agentclientprotocol/agent-client-protocol#415), but the Claude Agent SDK does not seem to return the information we need for an accurate context indicator. For example, one request to explore a project returned 500k+ cached read tokens in Claude's
resultmessage, while the agent reported 64k tokens used. I can open a PR with those changes for reference once the Typescript SDK is updated.To allow users to still see the current context usage, allowing to run
/contextseems to be the second best option. This PR changes the code to handle the<local-command-stdout>message that the SDK generates when sending/contextand includes/contextas allowed command.Screenshot from Tidewave with this change: