Supervising Child Tabs

Use Maxx supervision when one agent should coordinate several visible child tabs. The parent agent can open child sessions, group them, prompt them, and watch explicit events without hiding work in detached background processes.

Workflow

Start the parent agent in a normal Maxx tab.
Ask the parent to create child tabs for distinct tasks.
Keep each child tab visible in the sidebar with a clear title and declared metadata.
Keep the session_id returned by maxx-agent new-tab or maxx +control sessions create, and use it to prompt, interrupt, restart, inspect, retrieve declared results, or close child tabs when needed.
Treat completion or blockage as explicit agent-declared state, not inferred terminal output.

To read a child’s explicit answer, call `maxx +control sessions get

` and inspect `result`, `result_source`, and `result_at`. If `result` is null, the child has not declared an answer yet; wait for a `kind: result` event or ask it to call `sessions set-result`. ## Useful References - [Control API](/control-api.html) - [Automation runner](/automation-runner.html) - [No-inference rule](/no-inference.html) ## Operational Notes Each drive or automation flow should use its own control directory when parallel sessions must not share a socket: ```sh MAXX_CONTROL_DIR=/tmp/maxx-control-my-task ./tools/zig build run ``` Pass the same `MAXX_CONTROL_DIR` to any control or runner commands for that session.