Recordings

Everything in a session goes through Tandem’s service, so every session is recorded. The files stay on your PC.

Files

Documents\SSH Recordings\<date>\<session>__<id>\
  session.cast     the terminal recording (asciicast v2)
  events.jsonl     the audit log, one JSON object per line
  meta.json        details about the session

session.cast plays in any asciicast player, and events.jsonl is easy to search with grep or load into a script.

The audit log

Each entry in events.jsonl has a timestamp and says who it came from: a viewer (human:viewer-1), an agent (agent:claude-code, named after the MCP client), or Tandem itself. Entries cover:

keystrokes, and commands with their exit codes (see command tracking)
terminal resizes
SFTP transfers and file changes
a session being made private or public
guardrail decisions: blocked, approval requested, approved, denied
password prompts being answered (never the answers themselves)

Replaying

Recordings in the viewer lists every session. Choose one to play it back, with a timeline you can click to jump around.

Exporting a transcript

Any recording can be copied to the clipboard as plain text: a short header, a list of the commands that ran and who ran them, then the terminal output with the colour codes stripped out. It’s meant for pasting into another agent so it can see what happened.

Deleting

You can delete recordings from the viewer, except for sessions that are still open.

Agents can’t read recordings. That part of Tandem needs the viewer’s token.

Next: Guardrails