Trace
Sign in Start free

Docs

Get started

From sign-up to your first verdict. The fastest way is to let your coding agent do it; every step also works by hand.

With Claude Code

/plugin marketplace add dobrinov/tracetells
/plugin install trace@tracetells
/trace:setup

Then run /mcp, choose plugin:trace:trace and Authenticate. Your browser opens Trace to approve it; there's no token to copy. /trace:setup adds the tag to your pages, writes trace.json from your code and pushes it.

By hand

  1. Sign up at app.tracetells.com. Your account comes with its first website.
  2. Add the tag to every page, before </head>. See Install the tag. The first visit ticks the step off.
  3. Say what success means in a trace.json in your repository: the events your app sends, your goals, funnels and product areas. See trace.json.
  4. Analyse once Pulse says it's time, with /trace:analyse or the analyse_website prompt in any MCP client. Pick the insights worth doing.
  5. Fix and release. Ship one with /trace:fix, mark it released with /trace:manage release insight 12, and Trace gives a verdict on its goal 14 days later.

The dashboard shows; your agent does

The dashboard at app.tracetells.com is for looking, in six places: Pulse, Journeys, Product map, Problems, Goals and Work. Changes happen in your coding agent, over MCP, with the model you choose. Wherever there's something to do, the dashboard shows the command to run.

Still stuck?

Write to hello@tracetells.com, or open an issue on GitHub.