MCP codemode: false is ignored: server tools stay behind execute (2.0.25–2.0.28, opencode acp) #55079

Activity

1. opencode-agent commented on Oct 13, 2026

   

   opencode-agentBot

   on Oct 13, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report. I wasn't able to reproduce this on 2.0.28 (Linux), but I found one setup that gives the same symptom.

   What I tried: I ran opencode acp with your config: the ollama provider pointed at a mock endpoint that records requests, a stdio MCP server myserver with one tool submit_result and codemode: false, the same permissions, OPENCODE_DISABLE_PROJECT_CONFIG=1, and session/new with mcpServers: []. Then I checked the tool list in the actual request sent to the model:

   • Server only in config: myserver_submit_result was sent as a direct tool, next to execute, and it was not in the Code Mode catalog. The request also included shell, edit, write and the other built-in tools, not just glob/grep/read/execute. So the list you got may be the model's own description of its tools, not what OpenCode sent.
   • The ACP client also sends a server named myserver in session/new: that entry replaces the one from config, and ACP's server format has no codemode field. The server then goes back to Code Mode and the tool is reachable only through execute. That is exactly what you describe. Could you check what your client actually sends in mcpServers? Some clients forward their own MCP servers even when you don't expect them to.
   • Prompt sent right after session/new: if the MCP server hasn't finished connecting, its tools are missing from the first request entirely (First prompt after start has no MCP tools: tool list does not wait for pending MCP connections #51812). In that case the tool isn't reachable through execute either.

   What would help:

   1. The raw session/new request your client sends, especially mcpServers.
   2. The tool names in the actual request to Ollama, not the model's description of them. For example, put a logging proxy between OpenCode and Ollama, or start opencode acp --print-logs.
   3. Whether the same thing happens with opencode run "..." using the same config, outside ACP.

   Related issues:

   • First prompt after start has no MCP tools: tool list does not wait for pending MCP connections #51812: first prompt after start has no MCP tools while servers are still connecting
   • mcp: codemode:false still folds server's execute tool into Code Mode execute instead of exposing it natively #53527: a codemode: false server's own execute tool gets folded into Code Mode
   • ACP resume sometimes marks a reattached MCP tool as removed #54794: ACP resume marks a reattached MCP tool as removed
2. rekram1-node commented on Oct 15, 2026

   

   rekram1-node

   on Oct 15, 2026

   Collaborator

   More actions

   codemode: false is honored, I'm unable to reproduce, if you can still reproduce plz provide more info, perhaps checking the outbound network requests to see what's actually happening, ex:

   proxy opencode --standalone

   Where proxy is something like:

   proxy () {
           if [[ -z "$1" ]]
           then
                   echo "Usage: proxy <command>"
                   return 1
           fi
           mitmweb --listen-host 127.0.0.1 --listen-port 58888 --web-open-browser &> /dev/null &
           local pid=$!
           echo -n "Waiting for mitmweb..."
           while ! nc -z 127.0.0.1 58888 2> /dev/null
           do
                   sleep 0.2
           done
           echo " ready"
           local cert="$HOME/.mitmproxy/mitmproxy-ca-cert.pem"
           local proxy_url="http://127.0.0.1:58888"
           export NODE_EXTRA_CA_CERTS="$cert"
           export NODE_USE_ENV_PROXY="1"
           export CODEX_CA_CERTIFICATE="$cert"
           export HTTPS_PROXY="$proxy_url"
           export HTTP_PROXY="$proxy_url"
           export ALL_PROXY="$proxy_url"
           export WS_PROXY="$proxy_url"
           export WSS_PROXY="$proxy_url"
           export NO_PROXY="localhost,127.0.0.1"
           "$@"
           local exit_status=$?
           kill "$pid" 2> /dev/null
           wait "$pid" 2> /dev/null
           unset NODE_EXTRA_CA_CERTS NODE_USE_ENV_PROXY CODEX_CA_CERTIFICATE
           unset HTTPS_PROXY HTTP_PROXY ALL_PROXY WS_PROXY WSS_PROXY NO_PROXY
           return "$exit_status"
   }
   

   (we rlly need better network debugging --- coming soon)
3. rekram1-node

   closed this as not plannedon Oct 15, 2026
4. opencode-agent commented on Oct 16, 2026

   

   opencode-agentBot

   on Oct 16, 2026 – with OpenCode Agent

   Contributor

   More actions

   Closing this for now since we haven't heard back. On 2.0.28, with myserver defined only in config and codemode: false, myserver_submit_result was sent to the model as a direct tool. I could only get the tool stuck behind execute when the ACP client also passed a server with the same name in session/new. That entry replaces the config one, and ACP has no way to carry codemode.

   If you're still seeing this, please reopen or comment with:

   • the raw mcpServers your client sends in session/new
   • the tool names in the actual request to Ollama

   That should be enough to tell which case it is. Thanks again for the detailed report.