attach

crabbox attach follows recorded events for an active coordinator run.

crabbox attach run_abcdef123456
crabbox attach --id run_abcdef123456 --after 42
crabbox attach run_abcdef123456 --poll 500ms

Behavior

attach polls the coordinator for new run events on a fixed interval, prints them as they arrive, and exits when the run finishes.

stdout and stderr preview events are written back to stdout and stderr, preserving the stream split;
lifecycle events (lease, bootstrap, sync, command-start, finish, release) are printed to stderr with their sequence number, phase, timestamp, and message;
when the run has already finished, attach prints any remaining events and exits;
when the run is still active, attach polls until it sees a finish event.

attach is not detached command execution. It follows the events the original CLI is emitting; if that CLI process dies, the run state remains inspectable through history, events, and logs, but attach cannot resurrect it.

Bounded Output

Output events are a bounded preview. The coordinator caps stdout/stderr capture at 64 KiB per run and records an output.truncated marker when the cap is reached. Use logs for the larger retained command output after completion.

Flags

--id <run-id>       run id (also accepted as a positional argument)
--after <seq>       resume after this event sequence number
--poll <duration>   polling interval, default 1s

Use Cases

watch a long warmup or run from a second terminal without disturbing the original CLI;
monitor an agent-launched run while doing something else locally;
replay events from a known sequence (--after) when reconnecting after a network blip.

Direct Mode

Direct-provider mode does not record runs centrally, so attach has no event stream to follow. Use shell output from the original CLI instead.

Related docs:

2.0 KiB Raw Blame History