Agent sessions

An agent session is one conversation between you and a coding agent: your prompts, its answers and its tool calls. Pando records sessions of Claude Code, Codex, Pi and OpenCode (version 2) from your machine, links each one to the commits it made, and shows it to every member of the repository.

Turning it on

pando login asks once, at a terminal, whether this machine records sessions. Your answer is kept; it never asks again, and a login run by an agent or a script never asks.

pando session enable     record sessions on this machine
pando session disable    stop; sessions already recorded stay until deleted
pando session status     what this machine records, where it reads from, and what it skips

pando sync records them while it runs, apart from the shared files: a problem reading sessions never stops your files syncing.

What is recorded

• Only sessions inside a Pando folder on this machine: a project’s worktree, or the repository’s own folder. A session anywhere else is never read past the folder it names.
• Only new lines. pando sync reads what each agent wrote since last time and sends it. It keeps how far it got, never the session’s text.
• Only the conversation, never the agent’s own records about you (What is sent).
• Secrets are removed on your machine first: the Pando credential, the values of environment variables whose names look secret, the values in .env and .dev.vars files in the repository folder and its worktrees, everything betterleaks’ rules find, private keys, passwords in URLs, NAME=value pairs with a secret-looking name, and long random tokens. A removed value shows as redacted. If the check cannot run, nothing is sent. Pando checks again on the server for common token formats.
• Not kept: the agent’s reasoning, images (“Image, not kept”), and long encoded strings.

What is sent

Only the conversation. Each agent also writes its own records into a session (your account’s email, its system prompt, your instructions, the skills it has), and those stay on your machine. Pando sends these record types and nothing else; a type an agent adds later stays home until Pando lists it.

• Claude Code: user and assistant records (your prompts, its answers, tool calls and their results). Not sent: attachment records (the signed-in email, the system prompt, the skills list, the date), and its queue, cost and mode records.
• Codex: response_item records (prompts, answers, tool calls and their results), except developer and system messages and the <environment_context> and AGENTS.md instructions it adds to a turn; from session_meta, only its id, time, folder, version, branch and parent thread; from turn_context, only its model and folder. Not sent: world_state, event_msg, token counts, and the account ids and instructions in session_meta.
• Pi: the session header (its id and folder), message records, and model changes. Not sent: thinking-level changes and anything else.
• OpenCode 2: the session’s id, folder, parent and version, then user, assistant and shell rows. Not sent: idle and compaction rows, and every other table (OpenCode keeps instructions and accounts there).

Where agents keep sessions

Pando finds a moved folder when pando sync was started with that variable, when a commit is made in that agent’s shell, or when you add it:

pando session paths add ~/work/claude-b --program claude-code

Commits and sessions

A worktree’s commit hook adds a Pando-Session: s_… line to each commit an agent makes, naming its session. It reads the session from the nearest agent above the commit, so an agent started inside another names its own session. No line is written when recording is off, while git replays commits (a rebase or a cherry-pick), or for a commit typed in a plain terminal. Nothing is matched by time.

Once a commit is pushed, its session lists it; once it reaches main, the session says so. A commit’s model is the model the session was using when it was committed. A commit named by two sessions with different models shows no model.

Reading sessions

• A repository’s Sessions tab, beside Issues: one line per session under each day, newest activity first, with its agent, branch, issue, model, person, commits and time. Active means something was recorded in the last 30 minutes.
• A session’s page: its conversation from the first prompt, its commits with their own checks, and the files in its commits.
• A branch: each commit on its Overview shows its session’s number, and its Sessions tab lists those sessions.
• Your profile: your latest sessions, all of them at /<login>/sessions, and on the graph the agent behind most of each week’s (or day’s) commits on main.

Every member of a repository sees every session in it. A person sees your sessions only in repositories they can open.

Not recording a place

pando session exclude                              this whole repository, on every machine you sign in on
pando session exclude --project projects/web       one project
pando session include --project projects/web       record it again

A repository can also turn sessions off for everyone in .pando/pando.toml:

[sessions]
record = false               # no sessions at all
exclude = ["projects/web"]   # or not these projects

Settings, Sessions shows what each of your machines last reported, your list, the data folders found, and deletes sessions in bulk.

Deleting

• A session: on its page, Delete session, or pando session delete <id>. It is gone for everyone at once, with no undo. Its commits keep their line, and their rows say who deleted the session and when.
• One turn: Remove turn on a prompt. Its prompt, answers and tool calls are cut from the stored session; the prompt keeps its number, marked as removed.
• Many: Settings, Sessions, by repository, project and age.

Your own sessions are yours to delete; an owner of the repository can delete anyone’s.