Upgrade OpenCode to v1.18.11 and retest MCP SSE plus interleaved-reasoning models
v1.18.11 stops MCP SSE reconnect loops after server errors and fixes provider configs that use interleaved reasoning fields like reasoning_text. Upgrade, then verify MCP stability and reasoning-model output.
Why this loop
This release directly unblocks two coding-assistant failure modes: MCP SSE clients that spun forever after error responses, and provider model configs whose interleaved reasoning fields (e.g. reasoning_text or custom names) were mishandled. Teams using MCP servers or reasoning-capable models should upgrade promptly and confirm those paths work, rather than keeping workarounds for stuck reconnects or broken reasoning field parsing. Desktop fixes (system-browser external links, session tab state, file tree clipping, debug gutter alignment) improve day-to-day reliability but the MCP and model-config fixes are the highest-leverage workflow wins.
Proposed actions
- Upgrade OpenCode to v1.18.11 (or later) on every machine that runs MCP servers or reasoning-capable provider models.
- For each configured MCP server over SSE: restart OpenCode, trigger a deliberate server error response once, confirm the client does not stay in a reconnect loop, then verify normal tool calls succeed again.
- For any provider model config that uses interleaved reasoning fields (reasoning_text or a custom field name): send a short multi-step reasoning prompt and confirm reasoning and final answer both render correctly with no missing or concatenated fields.
- If you use the Modal provider, follow the new Modal provider setup docs added in this release and save a working provider config in your OpenCode settings.
- On OpenCode Desktop after upgrade: open an external docs link (should launch the system browser), resize the file tree smaller (should not clip), and confirm the title-bar session tab matches the active session.
Agent prompt
Paste into your agent or query via MCP (`get_agent_prompt`) — free, no extra AI costPaste into Claude Code / CLAUDE.md task
# DevAgentRadar → Claude Code You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features. ## Context Assistant: OpenCode Proposal: Upgrade OpenCode to v1.18.11 and retest MCP SSE plus interleaved-reasoning models Summary: v1.18.11 stops MCP SSE reconnect loops after server errors and fixes provider configs that use interleaved reasoning fields like reasoning_text. Upgrade, then verify MCP stability and reasoning-model output. Primary source: https://github.com/anomalyco/opencode/releases/tag/v1.18.11 ## Why it matters This release directly unblocks two coding-assistant failure modes: MCP SSE clients that spun forever after error responses, and provider model configs whose interleaved reasoning fields (e.g. reasoning_text or custom names) were mishandled. Teams using MCP servers or reasoning-capable models should upgrade promptly and confirm those paths work, rather than keeping workarounds for stuck reconnects or broken reasoning field parsing. Desktop fixes (system-browser external links, session tab state, file tree clipping, debug gutter alignment) improve day-to-day reliability but the MCP and model-config fixes are the highest-leverage workflow wins. ## Suggested actions 1. Upgrade OpenCode to v1.18.11 (or later) on every machine that runs MCP servers or reasoning-capable provider models. 2. For each configured MCP server over SSE: restart OpenCode, trigger a deliberate server error response once, confirm the client does not stay in a reconnect loop, then verify normal tool calls succeed again. 3. For any provider model config that uses interleaved reasoning fields (reasoning_text or a custom field name): send a short multi-step reasoning prompt and confirm reasoning and final answer both render correctly with no missing or concatenated fields. 4. If you use the Modal provider, follow the new Modal provider setup docs added in this release and save a working provider config in your OpenCode settings. 5. On OpenCode Desktop after upgrade: open an external docs link (should launch the system browser), resize the file tree smaller (should not clip), and confirm the title-bar session tab matches the active session. ## Your job 1. Restate the change in one sentence. 2. Propose a minimal plan for my repo (or a throwaway pilot). 3. Implement only what I approve; prefer small diffs and tests. 4. Call out risks (permissions, breaking APIs, cost). Start by confirming you understood the proposal.
Your loop
This browser · no sign-in · not shared as “you”Your decision stays on this device. A public tally appears after a few votes.