Skip to main content

Replay

Nimbus records every task session automatically. You can replay any session to see exactly what happened, step by step.

Basic usage​

nimbus replay

Shows the most recent session for the current repository.

Speed control​

nimbus replay --speed 2    # 2× speed
nimbus replay --speed 5    # 5× speed
nimbus replay --speed 10   # 10× speed

The default speed is 1× (real time). The delay between events is capped at 2 seconds regardless of speed.

Select a specific session​

nimbus replay --session-id 1714123456

Session IDs are Unix timestamps. Use ls ~/.nimbus/sessions/<repo>/ to see available sessions.

Where sessions are stored​

~/.nimbus/sessions/
  acme-api/
    1714123456.json
    1714045123.json
    ...

Nimbus keeps the last 10 sessions per repository. Older sessions are removed automatically.

Session format​

Each session file is JSON:

{
  "id": "1714123456",
  "repo_name": "acme/api",
  "task": "add input validation to registration endpoint",
  "started_at": 1714123456.123,
  "completed_at": 1714123466.789,
  "pr_url": "https://github.com/acme/api/pull/142",
  "events": [
    {
      "timestamp": 1714123456.5,
      "event_type": "phase",
      "data": {"phase": "planning"}
    },
    {
      "timestamp": 1714123458.2,
      "event_type": "file_write",
      "data": {"path": "api/routes/auth.py", "diff": "..."}
    }
  ]
}

Use cases​

Debugging — something went wrong in a task. Replay it at 1× speed to see exactly which file was written incorrectly.

Auditing — review what Nimbus changed and when, without using git log.

Demos — replay a complex task at full speed to show what Nimbus did.