Upgrade OpenCode to v1.18.26 and resume Claude 5 sessions after prompt or tool edits
OpenCode v1.18.26 lets Claude 5 sessions keep stale thinking blocks after prompt or tool changes, accepts Bedrock GPT-5.6 reasoning effortnone, prompts for the Azure CLI resource name directly, persists session renames, and omits empty apply_patch move paths.Why this loop
Claude 5 sessions used to fail after prompt or tool changes because of stale thinking blocks. v1.18.26 tolerates those blocks, so keep the existing session instead of starting over. Bedrock GPT-5.6 now accepts reasoning effort none, so you can configure non-reasoning turns. Azure CLI sign-in now asks for the resource name instead of querying Azure management APIs. Session names from the title editor and tab context menu now save. apply_patch no longer puts an empty move path in permission metadata, so treat remaining move paths as real. Tool-call timing also stays accurate when a tool updates metadata while still running.
Proposed actions
- Upgrade OpenCode to v1.18.26 from https://github.com/anomalyco/opencode/releases/tag/v1.18.26. Reopen any Claude 5 session that previously failed after a prompt or tool change and continue it; stale thinking blocks no longer abort the session.
- For Amazon Bedrock GPT-5.6 in OpenCode, set reasoning effort to
nonewhen you want a non-reasoning turn—that value is now accepted. - When OpenCode Azure CLI sign-in prompts you, type the resource name directly; v1.18.26 no longer queries Azure management APIs for it.
- Rename OpenCode sessions from the title editor or the tab context menu; those names now save reliably.
- On apply_patch permission prompts, do not expect an empty move path in metadata; if a move path is present, treat it as a real move.
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.26 and resume Claude 5 sessions after prompt or tool edits
Summary: OpenCode v1.18.26 lets Claude 5 sessions keep stale thinking blocks after prompt or tool changes, accepts Bedrock GPT-5.6 reasoning effort none, prompts for the Azure CLI resource name directly, persists session renames, and omits empty apply_patch move paths.
Primary source: https://github.com/anomalyco/opencode/releases/tag/v1.18.26
Why it matters
Claude 5 sessions used to fail after prompt or tool changes because of stale thinking blocks. v1.18.26 tolerates those blocks, so keep the existing session instead of starting over. Bedrock GPT-5.6 now accepts reasoning effort none, so you can configure non-reasoning turns. Azure CLI sign-in now asks for the resource name instead of querying Azure management APIs. Session names from the title editor and tab context menu now save. apply_patch no longer puts an empty move path in permission metadata, so treat remaining move paths as real. Tool-call timing also stays accurate when a tool updates metadata while still running.
Suggested actions
- Upgrade OpenCode to v1.18.26 from https://github.com/anomalyco/opencode/releases/tag/v1.18.26. Reopen any Claude 5 session that previously failed after a prompt or tool change and continue it; stale thinking blocks no longer abort the session.
- For Amazon Bedrock GPT-5.6 in OpenCode, set reasoning effort to
nonewhen you want a non-reasoning turn—that value is now accepted. - When OpenCode Azure CLI sign-in prompts you, type the resource name directly; v1.18.26 no longer queries Azure management APIs for it.
- Rename OpenCode sessions from the title editor or the tab context menu; those names now save reliably.
- On apply_patch permission prompts, do not expect an empty move path in metadata; if a move path is present, treat it as a real move.
Config surfaces this release may change
- permission rules (high confidence) — check your repo before applying
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-26-upgrade-opencode-to-v1-18-26-and-resume-claude-5-sessi and mark Applied, Skipped, or Failed. Proposal id: b3149def-4822-41fb-955e-48e7ba239248
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.