Follow Discord
Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.273 ·

runQuery hook threaded through tool-execution contexts

← All of v2.1.273 Home All releases

Claude Code's MCP bridge, non-interactive query, and interactive REPL tool contexts all now carry a runQuery hook

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaMCPwhat it touches
KindInternal Changesin v2.1.273,
Group of 3 Under the hood

Claude Code's MCP bridge, non-interactive query, and interactive REPL tool contexts all now carry a runQuery hook

What

  • The isolated tool-execution context used to expose Claude Code's tools over an MCP server connection now includes a runQuery function in its options.
  • The function that builds options for a non-interactive/analysis query now accepts a runQuery parameter from its caller and passes it into the agent context options, alongside existing options like commands, tools, and mcpClients.
  • The interactive REPL's tool-use context now also includes a runQuery entry, alongside existing options like resolveCommandDialog and renderDebugControls.

Why Giving all three tool-execution contexts (MCP bridge, non-interactive queries, and the interactive REPL) the same runQuery hook lets them share a consistent way to run queries, rather than each context wiring this up separately or lacking the capability.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat runQuery is actually used for and what capability it unlocks is not stated in the finding.

See this entry in the whole of v2.1.273 →