You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]:MCP was interrupted during runtime by a timeout warning from OpenCode. #8212
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
I have an MCP tool that needs to run for a long time, and I've confirmed that the MCP tool is working correctly in GitHub Copilot within VS Code. However, OpenCode throws a timeout warning after about 1 minute of running (MCP error -32001, request timeout). Is there a configuration option that allows users to configure the MCP timeout duration? This would allow me to run the MCP tool completely.
This issue might be a duplicate of existing issues. Please check:
MCP timeout not respected #8121: MCP timeout not respected - A closed bug report where the user configured a 30-second timeout but the MCP server was disabled after 15 seconds, suggesting timeout configuration issues.
Feel free to ignore if your specific case is different from these issues.
I referred to the configuration in https://github.com/anomalyco/opencode/issues/8121 and set "timeout": 600000, but my problem was still not solved. I asked OpenCode about it. Their answer was, "No, the timeout limit in the OpenCode system is hardcoded and cannot be modified through the configuration file. This is a built-in mechanism designed for system stability and resource management."
Activity
github-actions commentedon Jan 13, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if your specific case is different from these issues.
AfraBertha commentedon Jan 13, 2026
I referred to the configuration in https://github.com/anomalyco/opencode/issues/8121 and set "timeout": 600000, but my problem was still not solved. I asked OpenCode about it. Their answer was, "No, the timeout limit in the OpenCode system is hardcoded and cannot be modified through the configuration file. This is a built-in mechanism designed for system stability and resource management."
AfraBertha commentedon Jan 21, 2026
{ "experimental": { "mcp_timeout": 3600 } }this can be used