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
{{ message }}
Repository navigation
[FEATURE]: Capability of monitoring an ongoing process, it was possible on v1 #57713
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
On opencode v1, it was possible to ask for the ai to run a process, and monitor if it fails, fix it, re run it, etc.
It is not possible anymore on v2, it can't use sleep anymore to check on the ongoing process.
Thanks for the request! If I understand it right, you'd like the agent in v2 to keep an eye on a process it started: notice when it fails, fix the problem and rerun it, as it could in v1 by sleeping and checking the output.
Some context on how v2 works now: sleep isn't blocked. When a shell command runs in the background, the agent is told not to poll it with sleep/tail. It gets a notification with the command's output automatically when the command finishes, and can then fix and rerun. That covers commands that finish. It doesn't cover watching a process while it is still running (dev servers, watchers, long builds), which I think is the gap you're describing. The polling rule applies "unless the user explicitly asks otherwise", so for now you can tell the agent directly to check the process's output periodically.
Related issues and PRs:
feat: add monitor events #52569: open PR adding a monitor tool that streams a running process's output into the session and wakes the agent
I have managed to make it work, after using a smarter model, and insisting, and pasting this response.
Still feels like a regression, that it rejects to poll a process on first attempt.
Activity
opencode-agent commentedon Oct 21, 2026
Thanks for the request! If I understand it right, you'd like the agent in v2 to keep an eye on a process it started: notice when it fails, fix the problem and rerun it, as it could in v1 by sleeping and checking the output.
Some context on how v2 works now:
sleepisn't blocked. When a shell command runs in the background, the agent is told not to poll it withsleep/tail. It gets a notification with the command's output automatically when the command finishes, and can then fix and rerun. That covers commands that finish. It doesn't cover watching a process while it is still running (dev servers, watchers, long builds), which I think is the gap you're describing. The polling rule applies "unless the user explicitly asks otherwise", so for now you can tell the agent directly to check the process's output periodically.Related issues and PRs:
monitortool that streams a running process's output into the session and wakes the agentMaintainers will take a look and consider it.
borjaBruker commentedon Oct 21, 2026
I have managed to make it work, after using a smarter model, and insisting, and pasting this response.
Still feels like a regression, that it rejects to poll a process on first attempt.