Repository navigation
docs(acpmux): background-process registry design (list, tail, kill) - #20550
Conversation
…urvive the turn)
The design from cmuxterm-hq#2014: an acpmux-owned process record fed by
Claude Code's task events and Codex's backgroundTerminals, the
_acpmux/process/{list,tail,watch,kill} wire and process_update
notification, lifetime rules, and the client contract op-next-launch
builds the GUI on.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Bead |
- regenerated schemas/defaults/cmux-next.json Autofix-Run: https://github.com/manaflow-ai/cmux/actions/runs/38546250979
…/process-registry-design
The resource budget never landed (it scanned processes); the valve is cx-v9s8g without scanning. The registry is local like _acpmux/kill (coordinator), and the fallback signals a process group, not a tree walk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
|
Found 1 test failure on Blacksmith runners: Failure
|
Summary
Design for first-class background processes in acpmux: list, tail and kill the dev servers, watchers and long test runs an agent starts, and keep them running past the turn and past a closed chat. The NEXT GUI (op-next-launch) builds on the wire contract here.
ACP has nothing for this. Its client-side
terminal/*methods are going away in v2, and no RFD or PR covers listing or killing processes, so it's an_acpmux/*extension that we'll offer upstream as an RFD once it works for us. The decision to stay on ACP rather than fork it is in cmuxterm-hq#2014.Doc:
cmux-tui/crates/acpmux/docs/background-processes.md. It covers:commandExecutionitems andthread/backgroundTerminals/*._acpmux/process/{list,tail,watch,kill}and aprocess_updatenotification that replacesbackground_task_update.Part of it is built: #20585 (lifted limits,
runningupdates, the idle reaper fix) and #20724 (the registry for Claude Code's shells:process/list,process/kill,process_update). The doc marks what is built. Still to build: tail/watch, Codex, and the per-session resource valve, which comes back without process scanning in cx-v9s8g.Testing
Docs only; nothing to run.
Changelog
none
Proof
Docs only.
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Adds a design doc for first-class background processes in acpmux: listing, tailing, and killing the dev servers, watchers, and long test runs an agent starts, and keeping them running past the turn and past a closed chat.
_acpmux/process/{list,tail,watch,kill}wire contract and aprocess_updatenotification replacing the non-specbackground_task_update;list,kill, andprocess_updateare built, the rest is pending.ps//procscans, and the client contract for the NEXT GUI is included.schemas/defaults/cmux-next.json, which addssetting.freeModel.enabled; unrelated to the doc.Docs only; nothing to run.
Written for commit 9440442. Summary will update on new commits.