Skip to content

fix(core): clarify MCP timeout budgets - #35626

Merged
rekram1-node merged 4 commits into
v2from
mcp-timeout-config
Jul 6, 2026
Merged

rekram1-node merged 4 commits into
v2from
mcp-timeout-config

Conversation

@rekram1-node

Copy link
Copy Markdown
Collaborator

Summary

  • replace the ambiguous MCP request timeout with separate catalog and execution budgets
  • default execution requests to 100,000,000 ms and apply the budget explicitly to tool calls and prompt evaluation
  • preserve legacy timeout behavior during V1 migration and document the new configuration surface

Elicitation time remains part of the hard wall-clock execution budget because MCP does not guarantee an association between an elicitation and a specific request.

Closes #35275

Testing

  • bun typecheck from packages/core
  • bun test from packages/core (1,199 passed, 6 skipped)
  • bun test test/mcp.test.ts test/config/config.test.ts from packages/core

@rekram1-node
rekram1-node merged commit bfdbf43 into v2 Jul 6, 2026
8 checks passed
@rekram1-node
rekram1-node deleted the mcp-timeout-config branch July 6, 2026 22:47
jinhuang712 pushed a commit to jinhuang712/opencode that referenced this pull request Sep 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant