Session Recording

nono run --record --profile my-agent -- my-agent

​

Watching and reading recordings

nono replay my-session                    # play it back in the terminal
nono replay --speed 2 --idle-limit 2 my-session
nono replay --from 1:30 my-session        # or --from suspended, --from resize
nono transcript my-session                # readable text
nono transcript --format json my-session  # structured entries
nono audit verify <audit-session>         # check the recording against the audit log
nono inspect my-session                   # recording state, copies and any loss

• Replay draws the recorded terminal through a terminal model. Sequences an agent printed that act on your terminal itself, such as clipboard writes, window titles or mode changes, are not passed on. A session recorded in a larger terminal than yours is shown from its top-left corner, cut to fit your terminal; enlarge the terminal, even during the replay, or use nono transcript to see all of it. Press Ctrl-C to stop.
• Transcript prints text that scrolled by once, in order. A screen that was redrawn in place, such as a full-screen interface, is shown as it stood at pauses. It also notes when the session was suspended or ended, when password input was not recorded, and which credentials were too short to remove.
• Both refuse a recording that does not match the audit log. nono audit verify reports missing or altered chunks, and gaps in the recording that no recorded loss explains.

​

What is protected

• Known credentials are removed. Credential values nono resolved for the session are replaced with [redacted:credential:<name>] in both output and input. This covers proxy-injected credentials, credentials loaded into the environment from keyrings or providers, and credential capture outputs, as well as tokens nono refreshes during the session. Values are also matched base64-encoded and percent-encoded, and when they are split across reads, however long the pause between the pieces. Values shorter than 8 bytes are not matched; their names (never their values) are listed in the recording so the gap is visible.
• Password input is never recorded. While the terminal is in canonical mode with echo off, which is how sudo, ssh and getpass(3) read passwords, nono records only that input was typed, not what or how much. Full-screen agent interfaces also turn echo off, but in raw mode, so their input is recorded normally.

​

Where recordings are stored

​

Profile settings

{
  "session_recording": {
    "enabled": true,
    "required": false,
    "input": "on",
    "max_bytes": 268435456,
    "file": "./artifacts/session.cast"
  }
}

​

Launch flags

​

Required recording

• If recording cannot start, the agent does not run.
• If recording fails while the session is running, for example because the disk is full or the recording reached max_bytes, nono stops the session.
• If the recording is incomplete when the session ends, nono exits with status 74, even if the agent succeeded, so a pipeline sees the failure.

​

Writing a copy for artifact collection

• Relative paths resolve against the directory nono was launched from. $WORKDIR and ~ are expanded in profile paths.
• Both files are created when the session starts and must not already exist. nono never overwrites a file or writes through a symlink.
• file is honoured only in the profile you select, and only when you authored it (a user profile or a profile given by path). A file inherited through extends is ignored, as is one in a package, registry or built-in profile; recording stays on without the copy.
• A profile can set one file, and --record-file adds another.

​

Delivering recordings to the platform

{
  "session_recording": {
    "delivery": { "receiver": "platform", "required": false, "flush_timeout_secs": 30 }
  }
}

• Each chunk is uploaded when it closes, signed with the host’s enrollment key, so the platform can show a running session about 10 seconds behind.
• Upload never slows the session down. Failed uploads are retried, and at session end nono waits up to flush_timeout_secs for what is left.
• With required: true, the session does not start unless the host is enrolled, and nono exits with status 74 if any chunk could not be delivered. It also makes the recording itself required.
• The platform treats uploaded chunks as unverified until the session’s audit log arrives and matches them.
• The only receiver so far is platform. Chunks that were not delivered stay in the local recording.

​

Current limits

• Only sessions with a terminal are recorded.
• Input from nono attach clients is attributed as attach:<n>.