Repository navigation
Proposal: background subagents, monitors, cron, worktree isolation #49842
Description
Activity
The
monitorpart is the one I would use immediately. I built opencode-perk for V1 because I wanted a running job to send progress back to an idle agent, without blocking the conversation or waiting for the job to finish. A CI watcher, for example, should be able to report a failing step while the run is still going, and I should still be able to talk to the agent in the same session. Claude Code’s Monitor tool captures the workflow well.V2 already owns background shell jobs, so I’d rather see progress events attached to those jobs than another job runner. Perk used an append-only drip stream with quiet-gap coalescing; stdout lines might be simpler here. I’m likely to prototype a V2 monitor plugin in the meantime to learn what works. The earlier #33806 looks like useful prior art.
I kinda needed the background tasks without waiting on V2, so thought about sharing here so somebody could benefit if they're looking for it
Hi team, I built a set of agent-orchestration features in my fork for my own work. Sharing in case it helps someone. Happy to split into PRs if anything looks interesting upstream, no pressure either way.
Fork (branch
better): https://github.com/KapilSareen/opencode-extendedI checked each item against current upstream
devbefore posting; none of these exist there (upstream still injects background results via a freshprompt(), has no background/monitor/sleep/cron/notify_parent tools, no per-agent isolation flag, bare cancel on abort, and hides completed tool blocks including diffs).What is in it:
prompt()(fixes model-reset, cache-bust and parked-injection races), plus a timeout that upgrades stuck foreground tasks to background instead of hanging the parent.backgroundtool (status with spend/tokens/recent activity, send, kill, list, tail, detach, by task_id or spawn name) andnotify_parentso running children can push milestones to their parent.monitortool/service: watch a process, stream matching lines into a session, process-group kill. Pluscronscheduling andsleepkeep-alive with early wake on new input.Everything is in separated commits with integration tests. Let me know if any of it would help upstream and how you would like it shaped. Thanks for opencode!