multi-agent-mux

0 Fork 0

Files

T

GodopuandClaude Opus 5.5 ec7f5c4e57 fix(update): the legacy start_watchdog starts the monitor in its own process group; tests clean up only the processes they started (Issue #72 , review round 5)

With MAM_DELEGATION_PY=0 the monitor was left in the caller's process group
(decision 2), on every restart the update makes. The legacy body now spawns
it under job control (`set -m`, macOS has no setsid(1)) and restores the
caller's option. The update tests assert the restarted monitor's PGID in both
modes, and their teardown kills helper groups and this test's exact monitors
instead of `pkill -f <ws>`, then reports anything left that names the
workspace.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-28 05:18:04 +09:00

hooks

feat(mux-loop): redesign role CLI flags with --creator and --planner, drop --target-agent

2026-08-26 14:03:20 +09:00

references

docs: add PLAN_HERDR.md and herdr_docs.md reference file

2026-07-19 16:18:09 +09:00

reports

release(v4.11.0): attach uses the herdr-registered name; sessions start and stop only through the skills (Issue #71 ) - archive the review reports, bump the lockstep version

2026-10-27 07:28:47 +09:00

skills

fix(update): the legacy start_watchdog starts the monitor in its own process group; tests clean up only the processes they started (Issue #72 , review round 5)