Upload from any agent
Publish traces from 10+ supported agents directly in the CLI.
Share and collaborate on your coding agent sessions. Made for teams, and free to get started.
Download the CLI to get started
Works with your favourite agents






Start sharing traces from any agent, in minutes.
Publish traces from 10+ supported agents directly in the CLI.
Copy the link & share your trace with your team or the world.
UserMenu because it uses imperative WAAPI and can re-measure on state changes. I'm reading that implementation next and then I'll verify smoothing techniques from current guidance.Download a full trace or continue working on someone else's.
Download a trace, or continue it in Claude Code. The open agent menu lists OpenCode, Pi, Claude Code, Codex, Cursor, Gemini CLI, Amp, Cline, OpenClaw, GitHub Copilot, Hermes, Droid, with Claude Code selected.
Traces for Teams
Traces gives teams one place to see work in progress, share context on finished work, and see which agents people are using.
Create your Team

“Github increasingly doesn't feel like the best place to understand the work done on a codebase. Agent traces provide a much more human-readable overview. Just started using traces.com. Feels quite nice.”
Millin Gabani, CEO of Worklayer
See original postShare agent conversations without worrying about sensitive data.
Share your traces privately, directly, or publicly, so only the right people see them.
maujim · 102 messages
Diagnose and Enhance Voltage Error Reporting
maujim · 102 messages
Diagnose and Enhance Voltage Error Reporting
maujim · 102 messages
Diagnose and Enhance Voltage Error Reporting
Set team-level policies to control how your team can share traces.
Traces can be published as:
We automatically strip sensitive data like API keys, emails & database credentials from traces on publish.
Shared the rollout trace after scrubbing [REDACTED], [REDACTED], and [REDACTED] from the assistant reply before sending the link to the team.
The published run keeps the reasoning intact while replacing keys, customer emails, and database URLs with clear [REDACTED] markers anyone can spot immediately.
Reviewers still understand what happened, but the sensitive values stay hidden behind [REDACTED] in every shared view.
Start simple & integrate more as you go.
Publish & manage traces directly from your terminal.
Let your agent share traces as you work.
Publish traces via API with your own tools, schedulers & workflows.
Automatically share traces on every commit from your CI/CD pipelines.
Free for individuals & small teams, flexible at scale.
Core
Free
Custom
Get in touch
See what ships, loop in the right agents, and share traces with git hooks & custom skills.
Team analytics preview showing Claude Code, Codex, Cursor, Gemini CLI, and Amp as the top agents, with an average session length of 47 minutes and 82.0 percent AI output.
A GitHub-style pull request timeline shows Maya Chen committing a docs update, a Traces bot comment with pull request trace links, two preview deployments, and a pull request mention.
Traces found for this PR:
Team member list showing Maya Chen as admin, Theo Brooks as member, Alice as the invited agent, Lina Park as member, and Ari Singh as member.

A terminal conversation showing a request to share a trace, the Traces skill that ran, and the private share link confirmation.
Great, I added back the function.
Share this trace
Skill Traces
Ran traces share --trace-id w9g0svsjx839ngt --json
Shared your trace to https://traces.com/s/w9g0svsjx839ngt as private.
Supported agents include Claude Code, Cursor, OpenCode, Codex, Gemini CLI, Pi, Amp, Cline, OpenClaw, GitHub Copilot, Hermes, Droid.
Install the CLI to get started or make an account first.
Download the CLI to get started
or Create an account
Create your accountBrowse traces & learn how people are using agents. Contribute by sharing your own traces.
Browse public tracesThe user reported a UI issue where a connection appeared "working" despite the OAuth handshake never completing. The assistant investigated the backend and UI logic, identified a false-positive in the UI status interpretation, implemented a comprehensive fix including UI and backend reconciliation, added tests, and pushed the changes to a branch. The fix is already included in an open PR (#23) with additional follow-up commits.
The user reported that the Today page reloads data from scratch on every visit, causing a poor user experience. The assistant investigated and identified two main issues: the client refetches data on every mount without caching, and the server runs an expensive retrieval pipeline on every request without caching. The assistant implemented a two-part fix involving a server-side Redis cache and a client-side stale-while-revalidate cache keyed by user ID to prevent cross-tenant data leaks.
The session addressed fixing and improving the relationship graph to eliminate false relationships, duplicates, and junk entities. The assistant investigated root causes, implemented extraction and filtering fixes, enhanced the strength model, updated the UI to present a you-centered view, and ensured the feature was verified with live data. Later, the assistant identified that the branch containing the relationship-intelligence work was merged but the commits were pushed afterward without an open PR, leading to a cleanup and rebasing effort to create a clean, mergeable PR.
The user requested to replace bare numeric citations in answers with Perplexity-style source pills showing proper icons and references. The assistant mapped the citation flow, confirmed the structured citation data was already available on the frontend but ignored by the UI, then built and verified the new citation pill UI. The user also asked to improve the meeting-prep answer, which was diagnosed as too narrow due to filtering logic.
The user requested enhancements to the connected sections UI to make them interactive, display real-time status, and support disconnecting or reconnecting accounts. The assistant explored the current UI and API, mapped the relevant data and components, then implemented a disconnect endpoint, a connections management page, and made the sidebar section clickable with icons and status indicators. After thorough testing and code review, the assistant fixed an authentication middleware gap to secure the new page and finalized the changes.
The user requested a progress assessment against spec. md and architecture. md.
The trace involved cleaning up git worktrees and branches to ensure the local main branch was up to date and clean, without touching closed or merged branches. The assistant then proceeded to share all relevant session traces for the day, carefully verifying the correct project association and adjusting visibility settings to revoke access to mistakenly shared non-project traces.
The trace involves planning and refining the implementation of Phase 4 — Layer 3 personalization (Supermemory) based on the current codebase. The assistant thoroughly reviewed relevant files, architecture docs, and dependencies, then drafted a detailed plan which was iteratively improved based on user feedback, including concrete timeout patterns, idempotency fixes, and acceptance criteria.
The user reported a UI issue where a connection appeared "working" despite the OAuth handshake never completing. The assistant investigated the backend and UI logic, identified a false-positive in the UI status interpretation, implemented a comprehensive fix including UI and backend reconciliation, added tests, and pushed the changes to a branch. The fix is already included in an open PR (#23) with additional follow-up commits.
The user reported that the Today page reloads data from scratch on every visit, causing a poor user experience. The assistant investigated and identified two main issues: the client refetches data on every mount without caching, and the server runs an expensive retrieval pipeline on every request without caching. The assistant implemented a two-part fix involving a server-side Redis cache and a client-side stale-while-revalidate cache keyed by user ID to prevent cross-tenant data leaks.
The session addressed fixing and improving the relationship graph to eliminate false relationships, duplicates, and junk entities. The assistant investigated root causes, implemented extraction and filtering fixes, enhanced the strength model, updated the UI to present a you-centered view, and ensured the feature was verified with live data. Later, the assistant identified that the branch containing the relationship-intelligence work was merged but the commits were pushed afterward without an open PR, leading to a cleanup and rebasing effort to create a clean, mergeable PR.
The user requested to replace bare numeric citations in answers with Perplexity-style source pills showing proper icons and references. The assistant mapped the citation flow, confirmed the structured citation data was already available on the frontend but ignored by the UI, then built and verified the new citation pill UI. The user also asked to improve the meeting-prep answer, which was diagnosed as too narrow due to filtering logic.
The user requested enhancements to the connected sections UI to make them interactive, display real-time status, and support disconnecting or reconnecting accounts. The assistant explored the current UI and API, mapped the relevant data and components, then implemented a disconnect endpoint, a connections management page, and made the sidebar section clickable with icons and status indicators. After thorough testing and code review, the assistant fixed an authentication middleware gap to secure the new page and finalized the changes.
The user requested a progress assessment against spec. md and architecture. md.
The trace involved cleaning up git worktrees and branches to ensure the local main branch was up to date and clean, without touching closed or merged branches. The assistant then proceeded to share all relevant session traces for the day, carefully verifying the correct project association and adjusting visibility settings to revoke access to mistakenly shared non-project traces.
The trace involves planning and refining the implementation of Phase 4 — Layer 3 personalization (Supermemory) based on the current codebase. The assistant thoroughly reviewed relevant files, architecture docs, and dependencies, then drafted a detailed plan which was iteratively improved based on user feedback, including concrete timeout patterns, idempotency fixes, and acceptance criteria.