Install Saidran and check a session

Release binaries need Git. They do not need Go or Node. You can read existing logs without installing the agent. Reports are made locally without network or model calls. Installation downloads release files.

Install

On Linux or macOS, with amd64 or arm64:

curl -fsSL https://raw.githubusercontent.com/vincentsch/saidran/main/install.sh -o /tmp/saidran-install.sh
bash /tmp/saidran-install.sh

The installer verifies SHA-256 checksums and defaults to ~/.local/bin. It prints Installed: /absolute/path/to/saidran. Keep that path: if the folder is not on PATH, use the absolute binary path for the commands below.

You can change the install settings with environment variables:

For example:

INSTALL_DIR="$HOME/.local/bin" SAIDRAN_VERSION=v0.1.0 bash /tmp/saidran-install.sh

Windows

Download the matching saidran-windows-amd64.exe or saidran-windows-arm64.exe and checksums.txt from the same release. Before running the binary, use PowerShell to compute its checksum:

Get-FileHash .\saidran-windows-amd64.exe -Algorithm SHA256
Select-String -Path .\checksums.txt -Pattern 'saidran-windows-amd64.exe'

Use the arm64 filename in both commands on arm64. Compare the full hash with the matching entry, ignoring letter case. Stop if they differ. Rename the verified binary to saidran.exe and put it in a folder on PATH, or invoke its absolute path. Git must also be available on PATH.

Install with Go

With a Go toolchain, you can install from source:

go install github.com/vincentsch/saidran/cmd/saidran@latest

The binary goes into go env GOBIN, or $(go env GOPATH)/bin when GOBIN is empty. Go installation does not print the shell installer's Installed: line. Run go env GOBIN GOPATH to find the directory, then use the binary's absolute path if that directory is not on PATH.

Try the bundled demo

saidran demo

The demo needs no agent history. It extracts a sanitised Claude Code recording and repository into a temporary folder. Its test passed before a later edit, which gives the claim a Stale verdict. The terminal prints the HTML report path and the temporary folder. You can delete that folder after viewing the report. The README screenshots show this example.

Check your repository

Run inside the Git repository your agent changed. It must have at least one commit. For a new project, review and stage your files, then make the first commit with git commit before running Saidran. The tool compares against committed history and does not create that commit for you:

saidran

By default, Saidran picks the latest active session from the last seven days. Check its session ID and repository. The agent name and times should also match the conversation you intended. Read its command results and later edits even if no claims appear. When different agents finished less than ten minutes apart, interactive use asks which one to read. Scripts pick the newest and explain the choice.

List recordings or select one explicitly when the default is not yours:

saidran sessions
saidran --session claude:session-id
saidran --transcript /absolute/path/to/session.jsonl

Replace the example ID or path with your recording. Session references accept full IDs or unique prefixes; explicit transcripts bypass the seven-day limit. Do not combine --session and --transcript. See supported log locations and the selection flags. If logs are missing or unsupported, run:

saidran doctor

The doctor reference explains its diagnostics. Saidran never runs the agent or executes commands from its log.

Open the report

A successful check saves reports under <git dir>/saidran/<agent>-<full-session-id>/. The HTML file is report.html; Markdown and JSON versions are saved as report.md and report.json. Get the absolute Git directory with git rev-parse --absolute-git-dir; linked worktrees have separate reports. The terminal prints the saved HTML path. Open that file in your browser, or run:

saidran --open

Use the same explicit session flag again if you selected one earlier. JSON stdout does not include the HTML path. Use the report's session.agent and full session.id with the directory pattern above, and verify the file exists. Output flags let you choose another format or folder. They also support previews without saving files.

Verdicts explain coverage and later edits. The FAQ explains missing claims and unknown results. Reports summarize editable logs; they cannot establish whether a bug is fixed.