You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OC can accumulate background processes that the agent can't see. Clicking 'x' does not kill them. Clicking on its title takes you to the cell that started it, but provides you no way to close it or process ID to pass to the agent.
Thanks for the report! To work out what's going on, could you share a few more details?
Which client were you using: the desktop app, the web app, or the TUI? Also, which OS are you on?
How the background process started: for example, the agent ran a shell command with background: true, or a background subagent. A rough example of the command would help.
Is the process actually still running? Check with ps, Activity Monitor or Task Manager. Or has the process already exited, and only the item in the UI still shows as running with an x that does nothing?
When it got stuck, if you know: for example, right away, or after the session had been idle for a while (about an hour or more).
You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.
These existing issues look related, ordered from most to least likely:
Activity
opencode-agent commentedon Oct 21, 2026
Thanks for the report! To work out what's going on, could you share a few more details?
background: true, or a background subagent. A rough example of the command would help.ps, Activity Monitor or Task Manager. Or has the process already exited, and only the item in the UI still shows as running with an x that does nothing?You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.
These existing issues look related, ordered from most to least likely:
opencode service restart. If your processes are no longer alive, this is probably the same problem.<defunct>) processes that are never reaped whenopencode serveruns as PID 1 in a container, leaving shells stuck "running".