# Traces — AI Coding Tool Review & Pricing

> Traces is a hub for coding-agent sessions. Its CLI captures sessions from 16 agent ecosystems, normalizes them into one format and lets developers and teams share, search, resume and learn from them, with git hooks that link each commit back to the session that produced it. On November 16, 2026 Traces announced that it is joining Vercel.

Source: https://ai.dosa.dev/tools/traces · Updated Nov 17, 2026 · Category: Developer Productivity & Workflow · Published by dosa.dev

## At a glance

- **Tool**: Traces
- **Company**: Traces (Vercel)
- **Category**: [Developer Productivity & Workflow](https://ai.dosa.dev/category/productivity)
- **Pricing model**: Free
- **Official website**: https://traces.com

## Key features

- CLI install with npm i -g @traces-sh/traces or Homebrew
- Adapters for Claude Code, Cursor, Codex, OpenCode, Pi, Amp, Cline, Copilot, Gemini CLI and more
- Private, link-only and public trace visibility
- Organization namespaces for team history and activity by agent or person
- Git notes that link commits to the agent session behind them
- traces resume to continue a session in a different agent
- Agent skills, hooks and an MCP server
- Export a namespace as JSONL or push it to a Hugging Face dataset

## Pricing

**Model**: Free

The Core plan is free for individuals and small teams, with unlimited traces, unlimited teams and up to 50 seats. Larger organizations are asked to get in touch. New organization creation is paused while Traces joins Vercel.

## Who it is for

- **Best for**: Engineering teams that run several coding agents and want a shared, searchable record of agent sessions tied to the commits they produced.
- **Not ideal for**: Teams that want a new organization right now, since sign-ups for new orgs are paused during the Vercel transition, or teams that need fully self-hosted storage.

## Verdict

A useful cross-agent layer for keeping and sharing session history, though its future roadmap now sits with Vercel.

## Recent updates

Traces announced on November 16, 2026 that its team is joining Vercel; existing users can keep publishing and using the CLI, and new organization creation is paused. OpenCode 2.x support shipped on October 27, 2026.

## Frequently asked questions

### Is Traces free?

Yes - Traces is Free. The Core plan is free for individuals and small teams, with unlimited traces, unlimited teams and up to 50 seats. Larger organizations are asked to get in touch. New organization creation is paused while Traces joins Vercel.

### Is Traces open source?

Traces is not listed as open source on ai.dosa.dev - it is Free.

### Who is Traces best for?

Engineering teams that run several coding agents and want a shared, searchable record of agent sessions tied to the commits they produced.

### Who is Traces not ideal for?

Teams that want a new organization right now, since sign-ups for new orgs are paused during the Vercel transition, or teams that need fully self-hosted storage.

### What are the best Traces alternatives?

The closest Traces alternatives on ai.dosa.dev are Pieces for Developers, agenttrace, Vibe Kanban - all listed under Developer Productivity & Workflow.

### Who makes Traces?

Traces is developed by Traces (Vercel). It is listed in the Developer Productivity & Workflow category on ai.dosa.dev.

## Top alternatives

- [Pieces for Developers](https://ai.dosa.dev/tools/pieces-for-developers) (Paid) — Developers who work across multiple tools, IDEs, and environments and need to maintain a persistent, searchable history of code snippets, research, and workflow context.
- [agenttrace](https://ai.dosa.dev/tools/agenttrace) (Open Source) — Developers and teams needing to monitor and debug the efficiency, cost, and health of AI coding agents across multiple workflows.
- [Vibe Kanban](https://ai.dosa.dev/tools/vibe-kanban) (Open Source) — Software engineers who use multiple AI coding agents and need a structured environment to manage, plan, and review their output in parallel.
- [ai-memory](https://ai.dosa.dev/tools/ai-memory) (Open Source) — Developers or teams using multiple AI coding agents who need consistent context and project history persistence across different tools, machines, and sessions.
- [smolvm](https://ai.dosa.dev/tools/smolvm) (Open Source) — Running isolated coding agent sandboxes, untrusted code, and persistent local development environments that require a real Linux kernel boundary.
- [coop](https://ai.dosa.dev/tools/coop) (Open Source) — Running autonomous AI coding agents that require broad system access while maintaining a strong security boundary for the host machine.
- Full alternatives guide: https://ai.dosa.dev/tools/traces/alternatives
