Traces

At a glance

Traces stores and shares coding-agent sessions, including messages, tool calls and results. It is worth considering when a code diff leaves teammates asking how an agent reached the change. The key tradeoff is that sharing the explanation also uploads the session content; visibility and redaction need a deliberate choice before automation.

Good fit

Teams that want a reviewable history of agent work across coding tools. A shared session can preserve the attempted commands, intermediate results and conversation that a final commit omits. Manual sharing, agent hooks and Git hooks serve different levels of automation, and documented JSONL export offers an exit for analysis or archiving.

Consider something else when

Your sessions contain material you cannot send to a hosted service, or a PR description already supplies enough context. Link-only sharing is not member-only access: the documented direct mode permits anyone with the link. Automatic hooks can also share more continuously than a one-off handoff requires.

Start here

After reviewing the installation and authentication requirements, begin with a disposable session and the documented traces share --list command to identify the exact candidate. Check its content, choose visibility explicitly and only then consider sharing. The documented default is direct for individual namespaces and private for organisations. A successful share returns a URL; that upload was not performed for this guide.

Cost and requirements

The public Core tier is free for individuals and small teams, with unlimited traces and teams and up to 50 seats. Larger teams, self-hosting/on-premises deployment and priority support require a custom arrangement. Synced content is stored by Traces; the privacy policy allows deleted data to remain in backups for up to 90 days.

Limits to know

Secret redaction is a provider claim and should not replace inspection of a session that may include source, paths and tool outputs. Public documentation describes exports as a ZIP of JSONL files, with a 50 MB limit per file that may require narrower date ranges. No upload, resume, export or team access-control workflow was tested; the recommendation rests on the documented mechanism and public interface.

Related work

• BetterHub: a repository collaboration interface; Traces preserves the agent session behind a code change (complement)