OpenCode v2.3.1
Timed-Out Shell Commands Keep Running: A shell command still running when its timeout expires now moves to the background instead of being killed, so long builds and test runs finish and report back. · A foregroundtimeout: 0 now means the default 120 seconds. ([#63699](httWhy this loop
Release: OpenCode v2.3.1
Detail: Timed-Out Shell Commands Keep Running: A shell command still running when its timeout expires now moves to the background instead of being killed, so long builds and test runs finish and report back. · A foreground timeout: 0 now means the default 120 seconds. (#63699) · Compaction Without the Wait: As a session nears automatic compacti
Themes: agent, mcp, model, pricing, security, ide, cli, breaking Config surfaces changed: skills and plugins, permission rules Developer angle: Try in a throwaway repo before changing daily workflow. Team angle: Pilot / sandbox / policy review before org rollout. Source: https://github.com/anomalyco/opencode/releases/tag/v2.3.1
Proposed actions
- Review the skills and plugins and permission rules config for OpenCode to verify the changes don't break your workflow.
- Read the release notes for OpenCode v2.3.1 to understand the full scope of the update.
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: OpenCode v2.3.1
Summary: Timed-Out Shell Commands Keep Running: A shell command still running when its timeout expires now moves to the background instead of being killed, so long builds and test runs finish and report back. · A foreground timeout: 0 now means the default 120 seconds. ([#63699](htt
Primary source: https://github.com/anomalyco/opencode/releases/tag/v2.3.1
Why it matters
Release: OpenCode v2.3.1
Detail: Timed-Out Shell Commands Keep Running: A shell command still running when its timeout expires now moves to the background instead of being killed, so long builds and test runs finish and report back. · A foreground timeout: 0 now means the default 120 seconds. (#63699) · Compaction Without the Wait: As a session nears automatic compacti
Themes: agent, mcp, model, pricing, security, ide, cli, breaking Config surfaces changed: skills and plugins, permission rules Developer angle: Try in a throwaway repo before changing daily workflow. Team angle: Pilot / sandbox / policy review before org rollout. Source: https://github.com/anomalyco/opencode/releases/tag/v2.3.1
Suggested actions
- Review the skills and plugins and permission rules config for OpenCode to verify the changes don't break your workflow.
- Read the release notes for OpenCode v2.3.1 to understand the full scope of the update.
Config surfaces this release may change
- permission rules (high confidence) — check your repo before applying
- skills (high confidence) — check your repo before applying
- background and headless runs — check your repo before applying
- context and compaction settings — check your repo before applying
- agent context files — check your repo before applying
- settings files — check your repo before applying
- subagent definitions — 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-v2-3-1-opencode-v2-3-1 and mark Applied, Skipped, or Failed. Proposal id: 95f8de29-4504-46aa-9133-0b387acc2453
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.