Why: tool scripts and a large MCP catalog should not block the first prompt or inflate the tool list.
Evidence: GOWORK=off go test of runtime/codeorch, runtime/tools, runtime/mcp, runtime/policy, and adapters/native.
Impact: deferred tools stay out of the declaration list. A server that is not already connected is dialed in the background.
Refs: feature/code-orchestration
Why: tool scripts and a large MCP catalog should not block the first prompt or inflate the tool list.
Evidence: GOWORK=off go test of runtime/codeorch, runtime/tools, runtime/mcp, runtime/policy, and adapters/native.
Impact: deferred tools stay out of the declaration list. A server that is not already connected is dialed in the background.
Refs: feature/code-orchestration
Why: models need a capped way to call several tools from one script, and a slow MCP server must not block the first prompt.
Evidence: GOWORK=off go test ./runtime/codeorch/ ./runtime/tools/ ./runtime/mcp/ ./runtime/policy/ ./adapters/native/
Impact: run_tool_script stays unregistered until the caller turns it on. Deferred tools stay out of the model list. An unready MCP server connects in the background.
Refs: feature/code-orchestration
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit ecca2d74b9 into main2026-10-03 18:07:11 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: tool scripts and a large MCP catalog should not block the first prompt or inflate the tool list.
Evidence: GOWORK=off go test of runtime/codeorch, runtime/tools, runtime/mcp, runtime/policy, and adapters/native.
Impact: deferred tools stay out of the declaration list. A server that is not already connected is dialed in the background.
Refs: feature/code-orchestration