{"version":"2.1.273","anchor":"synthetic-mcp-bridge-tool-context-gains-a-runquery-function","canonical_anchor":"synthetic-mcp-bridge-tool-context-gains-a-runquery-function","heading":"runQuery hook threaded through tool-execution contexts","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/synthetic-mcp-bridge-tool-context-gains-a-runquery-function","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### runQuery hook threaded through tool-execution contexts\n\nClaude Code's MCP bridge, non-interactive query, and interactive REPL tool contexts all now carry a runQuery hook\n\n**Unclear.** What runQuery is actually used for and what capability it unlocks is not stated in the finding.\n\n**What**\n\n- 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.\n\n- 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`.\n\n- The interactive REPL's tool-use context now also includes a `runQuery` entry, alongside existing options like `resolveCommandDialog` and `renderDebugControls`.\n\n**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.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}