In Claude Code Mode’s documented Jira example, full issue records stay inside a JavaScript sandbox. Claude receives only the keys and titles of issues that pass a date filter, rather than reading every field returned by the connector.
That is the central idea behind Claude Code Mode, an MIT-licensed plugin that lets Claude write one JavaScript program to call MCP tools, filter their responses, and join results before returning a final value to the model. It changes where intermediate data gets processed, without claiming to eliminate the underlying connector calls.
The project, published by GitHub user gabe4coding and introduced through a Show HN submission, is a third-party addition to Anthropic’s Claude Code, not an Anthropic product announcement. Its appeal is an immediately testable workflow for tool-heavy sessions. Its limits are equally important: the token-saving and isolation claims are project claims, not independently validated findings.
One Program Changes What Claude Has to Read
MCP, short for Model Context Protocol, provides the connector interface used here to reach external tools. The plugin targets workflows where those tools return more information than the model needs for its answer.
The project’s README describes the conventional sequence as individual tool calls whose full results enter the model’s context. Code Mode instead asks Claude to express the task as a program. That program can make tool calls, retain intermediate responses, perform transformations, and return a smaller result.
The documented Jira example searches for the user’s open issues, computes a cutoff of 14 days, filters on each issue’s update timestamp, and returns just its key and title. The model gets the shortlist, not the complete records used to produce it.
For a multi-step task, the same approach can combine results before exposing them to Claude. A program can retrieve records, call another tool using selected identifiers, and join the responses inside the sandbox. The model writes the processing logic without having to read every intermediate record.
This is a context-management strategy, not data compression in the usual sense. The source records still exist, and the tools still return them. The plugin keeps that intermediate material outside the model’s conversational context.
There is a corresponding loss of visibility. If the program returns an incomplete or incorrectly filtered answer, Claude cannot inspect omitted records from that return value alone. Developers should make the output sufficiently informative to check, perhaps including source identifiers, relevant timestamps, or counts alongside the answer.
