Session Replay

The suv replay command prints a chronological, plain-text timeline of recorded commands: what ran, where, whether it succeeded, and how long it took. Use it to retrace a shell session, a day, or a directory.

Looking for AI agent sessions? suv replay lists commands only. To read an agent's prompts, responses, models, reported tokens, and saved summaries, use Agent Sessions (suv sessions).

Basic Usage

Replay the commands from the current shell session:

suv replay

With no flags, suv replay uses the current session from $SUVADU_SESSION_ID. Outside a Suvadu shell, it shows the last 24 hours. Each line shows the time, directory, status (✓, ✗ with the exit code, or • when the exit code is unknown), duration, and command. A footer shows totals and the average duration:

── Replay: current session (4f2a9c1e) ─────────────────────────────────
   Session 4f2a9c1e  │  Host: laptop  │  3 commands

 10:41:52  ~/projects/app        ✓       1.2s  git pull
 10:42:10  ~/projects/app        ✗1      8.4s  npm test
 10:44:31  ~/projects/app        ✓       7.9s  npm test

── 3 commands  │  2 passed  │  1 failed  │  Avg 5.8s ──

The output is plain text, so it can be read in the terminal or piped to other tools.

Command-Line Flags

Filter the replay to focus on specific time ranges, directories, or executors:

Flag	Description	Example
`--session`	Replay a specific session by ID	`suv replay --session a1b2c3d4`
`--after`	Show commands on or after a date: `YYYY-MM-DD`, `today`, `yesterday`, or `"N days ago"`	`suv replay --after today`
`--before`	Show commands on or before a date (same formats as `--after`)	`suv replay --before yesterday`
`--tag`	Filter by session tag	`suv replay --tag deploy`
`--exit-code`	Filter by exit code	`suv replay --exit-code 1`
`--executor`	Filter by executor name or type (e.g., `claude-code`, `agent`, `human`)	`suv replay --executor claude-code`
`--here`	Only show commands run in the current directory	`suv replay --here`
`--cwd`	Filter by a specific working directory path	`suv replay --cwd ~/projects/myapp`

Examples

Replay today's commands

suv replay --after today

Shows every command you ran today in chronological order, across all sessions and directories.

Replay commands in the current directory

suv replay --here

Shows the timeline of commands that were run in your current working directory, regardless of when they happened. Useful for understanding the history of a specific project.

Find yesterday's failures

suv replay --after yesterday --exit-code 1

Shows commands from yesterday onward that exited with code 1. Helps you retrace debugging sessions.

Replay what an AI agent did

suv replay --executor claude-code --after today

Shows today's shell commands recorded from Claude Code. This includes only commands, not prompts or responses. For those, open the session in Agent Sessions.

Replay a specific session

suv replay --session a1b2c3d4

Replays all commands recorded under one session ID. Find IDs with suv sessions --list, or run suv status to see the current shell's ID.

Piping and Redirection

The output of suv replay is pipeable plain text. You can combine it with standard Unix tools:

# Search replay output for a specific pattern
suv replay --after today | grep "docker"

# Save a session replay to a file
suv replay --session a1b2c3d4 > session-log.txt

This makes suv replay useful for scripting, auditing, and generating reports.

Session Browser

To browse sessions interactively, including AI agent sessions with their prompts, responses, models, reported tokens, and saved summaries, use suv sessions. It is documented on its own page: Agent Sessions.

Session Command-Line Flags

Flag	Description	Example
`[SESSION_ID]`	Open a session by ID or unique prefix	`suv sessions a1b2c3d4`
`--list`	List sessions as plain text (non-interactive)	`suv sessions --list`
`--after`	Only sessions active after a date	`suv sessions --after "7 days ago"`
`--tag`	Filter sessions by tag	`suv sessions --tag deploy`
`-n` / `--limit`	Maximum sessions to load (`--list` defaults to 50)	`suv sessions -n 10`

Session Examples

# Find a session ID, then replay its commands as plain text
suv sessions --list -n 5
suv replay --session a1b2c3d4

For keyboard controls, AI timelines, and summary checkpoints, see Agent Sessions.

Tip: Each shell that loads Suvadu's hook gets a session ID in $SUVADU_SESSION_ID. A shell started from an existing Suvadu shell keeps the parent's ID. Tag the current session with suv tag associate <name> to make it easier to find later.