Timeline

The timeline is your organization's record of agent work. It shows every session you recorded on this machine and every session your teammates synced to the organization's cloud projects, including the ones running right now. Each session keeps its prompts, responses, tool calls and the checkpoints that tie it to commits, and anyone on the team can comment on any step.

Open it from Timeline at the bottom of the sidebar. It covers every project in the active organization, so you don't need a project open. Timeline opens as a full page while your session keeps running; press Esc, select the back arrow in the bar, or select Timeline again to return to the session. The web app has the same timeline in the browser.

Get sessions onto the timeline

The timeline shows projects with session capture turned on, whether in the desktop app or with the Atlas CLI from a terminal.

• A project stored Local shows only your own sessions, and only on this machine.
• A project stored Cloud sends its sessions to the organization. They appear on your teammates' timelines, and theirs appear on yours.

To share a project's history, see Put a project's sessions in the cloud.

Read the board

The board lists sessions newest first, grouped by day. The date at the top stays in view as you scroll and changes when you reach the next day. Each day shows who worked that day.

Each row has three lines:

• the session title (the first line of its first prompt), with the model on the right
• the branch, the tokens it used or how full its context window got, and the project
• the person who ran it, with its checkpoints and lines added and removed on the right

The mark beside each row says what state the session is in: live (written to within the last minute and a half), needs attention (capture hit a problem recording it), finished, or imported from an earlier Claude Code transcript.

The board refreshes on its own: every 15 seconds for the whole organization, and in real time for cloud projects bound on this machine. Your local sessions show even with no connection.

The board holds the newest 500 sessions. Filter by project to see a project's full history.

Filter and search

The Project, Agent and People filters sit in the bar at the top of the page, beside Timeline. Each option shows how many sessions it matches.

Type in Search sessions… at the bottom of the board to search it. It matches session titles, project names, agents, models and branches. To search inside prompts, responses, tool calls and checkpoints, use the timeline in the web app.

Follow a commit back to its work

Start from a commit in Source Control, which shows the sessions that contributed to it.

Read a session

Select a session to open it. The header shows how long it was active, its tokens, an estimated cost and the token mix. Below that is the transcript, in order:

• Prompt and Response for each turn, and Thinking where the agent recorded it
• tool calls, folded into groups; select Show tool calls to see each call, then a call to see its Arguments and Result
• Checkpoint rows, one per commit the session produced, with the commit subject and lines added and removed

If a commit was later rewritten or squashed away, its checkpoint says Commit no longer reachable. The session record is kept.

Use Filters at the bottom of the session to show only some kinds of entry, or only failed tool calls, and Search this session… to find text in it. Maximize session hides the list so the session fills the page.

Comment on a session

Comments work on any session in a cloud project, yours or a teammate's. A local session has no one to discuss it with, so it shows no comment controls.

Comment on the whole session with the comment button (speech bubble) beside its title, or on one step: a prompt, a response, a thinking block, a tool call or a checkpoint. Each step's row has its own comment button, which shows when you hover the row. Once a thread has comments, the button shows the commenters' faces and a count instead.

In a thread you can:

• mention a teammate with @, which notifies them
• Reply, Resolve a thread, or Reopen it
• delete your own comment
• Reference in agent chat, to bring the comment into a session with your agent

Select the comments button (speech bubble) in the bar at the bottom of a session to open the comments panel. It lists every thread in the session; search them, sort Newest first or Oldest first, filter by person, and turn on Show resolved. Selecting a thread jumps to the step it is on.

Comments reach people outside the timeline too:

• When your own live session is in a cloud project, its header shows a comments badge, and teammates' comments appear next to the messages they are about.
• Mentions, replies and comments on your sessions land in your inbox in the web app, and by email if you have email notifications on.

Ask about a session

Select Ask about this session to ask questions about a recorded session. Answers come from what the session actually recorded. Starter questions include "What changed in this session?" and "Review this session like a PR".

You choose which checkpoints it reads, or keep Full timeline. Asking uses your own API key: add one in Settings → Agents → Provider keys. The session is read from your machine, and the question goes to the provider you choose.

Export and share a session

While a session is open, select Export session to save it as Markdown or JSON.

Select the session's name in the breadcrumb (Sessions / …) to copy it. A shared session copies as a link a teammate can open in the web app. A local session copies its ID. Pasted into team chat, the link stays a plain link, not a session card. See Session references.

To share a session with someone outside the organization, create a public share link in the web app. See Share a session publicly.

Ask Atlas Agent what someone is working on

Atlas Agent reads the same record. In a cloud project, ask it things like:

• "What is Sam working on?"
• "Which sessions are live right now?"
• "What did the team do on the billing project this week?"
• "Summarize the open comments on yesterday's parser session."

It lists the matching sessions, flags the live ones, and can open one and read it. By default it looks back 14 days.

Admins can also ask for one member's recorded activity: their sessions, checkpoints, lines added and removed, and tokens. This counts only work recorded in Atlas, so it is not a measure of anyone's performance.

Atlas Agent can also reply to and resolve comments. Anything that reaches another person, such as posting a reply or sending a message, asks you first. This needs Let Atlas Agent act in your organization, which is on by default in Settings.

How sessions link to commits

The desktop app watches repository history without installing git hooks, changing git configuration, or writing refs. It can therefore connect work committed from Atlas, another editor, or a terminal. The Atlas CLI installs a git post-commit hook instead, and links by the same rules.

For existing files, Atlas links a session when the commit includes a path the agent touched. For new files, the committed content must match the agent's output. This keeps normal follow-up edits linked while avoiding credit for files you replaced yourself.

Once Atlas settles a touched path, it stops using that touch to nominate future commits. Merge commits do not create checkpoints, and a purely human commit stays unlinked. A link survives an amend or a rebase; when a squash makes it ambiguous, Atlas drops the link rather than guess.

Atlas records a session even when it never produces a commit. Folders without git still keep sessions, but can't produce checkpoints.

What syncs and what doesn't

A project stored Local sends nothing. A project stored Cloud sends this, for every session recorded in it:

• Session details: its title, agent, model, token totals and start time.
• Messages: the full text of every prompt and response. Thinking is sent as a short preview only.
• Tool calls: each call's name, status, the paths it touched, and its full arguments and results. That includes command output and file contents the agent read or wrote.
• Checkpoints: commit SHA, branch, the git author's name and email, the files touched and line counts.
• The project: its name, slug, the repository's root commit and its origin URL.

These never leave your machine through the timeline: your source tree, git history, diffs, shared memory and the knowledge base.

Redaction happens on your machine. Atlas scrubs secrets such as API keys, tokens, credentialed URLs and KEY=value pairs before a session is stored locally, so what syncs is the already-redacted record. The server does not redact anything further. Before you publish a project's history, Atlas tells you how many secrets were redacted.

Who can read it. Everyone in the organization, admins included, can read every session in a cloud project that isn't restricted. A restricted project is readable only by the members named on it. A public share link extends one session or project to anyone who has the link. When someone leaves, their sessions stay and show as Former member.

Only the organization's owner can delete recorded sessions. A deleted session is erased for everyone, and a desktop that still has it won't upload it again.

Next

• Session capture: turn recording on for a project
• Organizations: put a project in the cloud
• Web app: the timeline in a browser, with full-text search and share links
• Atlas CLI: put sessions from your terminal on the timeline