anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

feat: add 'never' option for mcp_timeout to disable timeout #6109

New Issue
Open
opened 2026-02-16 18:00:35 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:00:35 -05:00
Owner
Copy Link
Copy Source

Originally created by @Skyline-23 on GitHub (Jan 15, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

Currently, mcp_timeout in experimental config only accepts positive integers (milliseconds). There's no way to completely disable timeout for MCP tool calls.

Some MCP tools may take a long time to execute (e.g., long-running browser automation, complex code analysis), and users need an option to disable the timeout entirely.

Proposed Solution

Allow mcp_timeout to accept "never" as a value to disable timeout:

{
  "experimental": {
    "mcp_timeout": "never"
  }
}

Alternatives Considered

  • Using a very large number (e.g., 999999999) - not intuitive
  • A separate boolean flag - adds complexity
Originally created by @Skyline-23 on GitHub (Jan 15, 2026). Originally assigned to: @thdxr on GitHub. ## Problem Currently, `mcp_timeout` in experimental config only accepts positive integers (milliseconds). There's no way to completely disable timeout for MCP tool calls. Some MCP tools may take a long time to execute (e.g., long-running browser automation, complex code analysis), and users need an option to disable the timeout entirely. ## Proposed Solution Allow `mcp_timeout` to accept `"never"` as a value to disable timeout: ```json { "experimental": { "mcp_timeout": "never" } } ``` ## Alternatives Considered - Using a very large number (e.g., `999999999`) - not intuitive - A separate boolean flag - adds complexity
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6109
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?