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
v1.18.11 is the verification target for the two agent-breaking surfaces in this proposal: MCP SSE clients that stayed in reconnect loops after a server error response, and provider model configs that interleave reasoning in reasoning_text or a custom field name. Upgrade first so those paths are exercised on this tag, not an older build. The same release also opens external links in the system browser, starts the legacy directory picker at the home folder when no home path is loaded, and ships desktop fixes for stale session-tab title-bar state, file-tree clipping when shrunk, debug-gutter label/value misalignment, and related stale prompt-control reads (PRs #39767, #39770, #39842), plus Modal provider setup docs (#39710). Treat MCP SSE error recovery and interleaved-reasoning parsing as the required retests; use the UI/docs items only as a short smoke pass after those pass.
Proposed actions
- Pin this workspace to OpenCode v1.18.11 from https://github.com/anomalyco/opencode/releases/tag/v1.18.11 and do not start retests until the running app/version string is exactly v1.18.11.
- Connect an MCP server over SSE, force a server error response on that stream, and confirm the client does not remain stuck in a reconnect loop after the error.
- Load a provider model config that interleaves reasoning in the field
reasoning_text, then a second config that uses a custom reasoning field name; confirm both parse reasoning correctly and do not emit those fields as ordinary assistant text. - From the upgraded app, open an external URL and confirm it launches in the system browser (not an in-app view); then shrink the file tree tab and confirm it no longer clips.
- With no home path loaded, open the legacy directory picker and confirm it starts at the home folder; switch desktop session tabs and confirm the title bar no longer shows a stale session name, and that debug gutter labels stay aligned with their values.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costOpenCode session task
DevAgentRadar → OpenCode
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
v1.18.11 is the verification target for the two agent-breaking surfaces in this proposal: MCP SSE clients that stayed in reconnect loops after a server error response, and provider model configs that interleave reasoning in reasoning_text or a custom field name. Upgrade first so those paths are exercised on this tag, not an older build. The same release also opens external links in the system browser, starts the legacy directory picker at the home folder when no home path is loaded, and ships desktop fixes for stale session-tab title-bar state, file-tree clipping when shrunk, debug-gutter label/value misalignment, and related stale prompt-control reads (PRs #39767, #39770, #39842), plus Modal provider setup docs (#39710). Treat MCP SSE error recovery and interleaved-reasoning parsing as the required retests; use the UI/docs items only as a short smoke pass after those pass.
Suggested actions
- Pin this workspace to OpenCode v1.18.11 from https://github.com/anomalyco/opencode/releases/tag/v1.18.11 and do not start retests until the running app/version string is exactly v1.18.11.
- Connect an MCP server over SSE, force a server error response on that stream, and confirm the client does not remain stuck in a reconnect loop after the error.
- Load a provider model config that interleaves reasoning in the field
reasoning_text, then a second config that uses a custom reasoning field name; confirm both parse reasoning correctly and do not emit those fields as ordinary assistant text. - From the upgraded app, open an external URL and confirm it launches in the system browser (not an in-app view); then shrink the file tree tab and confirm it no longer clips.
- With no home path loaded, open the legacy directory picker and confirm it starts at the home folder; switch desktop session tabs and confirm the title bar no longer shows a stale session name, and that debug gutter labels stay aligned with their values.
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/opencode-v1-18-11-upgrade-opencode-to-v1-18-11-and-retest-mcp-sse-plus-i and mark Applied, Skipped, or Failed. Proposal id: 472869ed-a44b-461d-a67c-63ea22b205e2
Your job
- Restate the change in one sentence.
- Propose a minimal plan for my repo (or a throwaway pilot).
- Implement only what I approve; prefer small diffs and tests.
- 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”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.