alineo logs

bunx alineo-cli logs <name> [--json]

Arguments

Flags

What it does

Looks up the most recent sandbox for name in the ledger and prints every ledger event recorded against it — sandbox.created, exec.started/exec.output/exec.completed, sandbox.checkpoint_created, sandbox.closed, and so on.

Note this reads by name, unlike alineo prompt/alineo stop which read by sandbox ID — logs is a read-only audit trail, not a liveness-sensitive operation, so the staleness/non-uniqueness concerns that motivate ID-based addressing elsewhere don't apply the same way. If a name has multiple sandboxes in the ledger, the newest one is used.

Example

bunx alineo-cli logs my-session

14 events for 'my-session' (4af65c3b-24a2-4fd1-999d-918faa9b97fd):

2026-07-12T00:59:31.123Z  sandbox_created
2026-07-12T00:59:32.456Z  exec_start
  {"cmd":"apt-get update -qq && apt-get install -y --no-install-recommends git","seq":1}
2026-07-12T00:59:41.789Z  exec_complete
  {"exitCode":0,"seq":1}

Long payloads are truncated to 200 characters in text mode. Use --json for the full, untruncated payloads.

Notes

• Only shows what's in this CLI invocation's own ledger — a child sandbox forked via alineo spawn from inside another sandbox writes to that sandbox's own internal ledger, not this one. Use alineo agents from inside the child's own project context to inspect it, or connect to it directly.
• Errors with No session named '<name>' found in the ledger. if nothing matches.