Terminal Session Replay
ReviewAudited by ClawScan on May 1, 2026.
Overview
This appears to be a coherent local terminal-recording tool, but recorded sessions persist on disk and may include sensitive terminal output.
This skill looks purpose-aligned for local terminal session recording. Before installing or using it, remember that recordings can capture anything displayed or typed in the recorded shell, including secrets; review exports before sharing and delete sensitive sessions when finished.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a recorded session contains passwords, tokens, private data, or sensitive command output, that information may remain on disk and could be included in exported markdown.
The skill intentionally records terminal activity and stores it persistently, which can include secrets, credentials shown in output, private paths, or other sensitive context.
Captures commands, outputs, and timing for later review, documentation, or sharing with teammates... Sessions are stored in `~/.terminal-sessions/` by default
Record only when needed, avoid entering secrets while recording, review and redact recordings before sharing, and delete sessions that are no longer needed.
When recording is started, a local terminal recording process runs and saves what happens in that session.
The tool invokes the local `script` command to start an interactive terminal recording. This is central to the stated purpose and uses argument lists rather than shell string execution.
cmd = ['script', '--quiet', '--timing', str(paths['timing']), str(paths['typescript'])] ... result = subprocess.run(cmd)
Only start recording in response to an explicit user request, and make sure the user knows how to stop the recording with exit or Ctrl+D.
Replay may fail or behave differently on systems where `scriptreplay` is not installed, even if the declared requirements pass.
The replay path relies on local binaries beyond the declared `python3` and `script` requirements, so installation checks may not fully capture all runtime dependencies.
cmd = ['scriptreplay', '--timing', str(paths['timing']), str(paths['typescript'])] ... cmd = ['cat', str(paths['typescript'])]
Confirm required local tools are available before relying on replay, and update the skill metadata to declare all needed binaries.