Docs navigation

Quick start

From zero to line-level AI attribution in about five minutes — trace your repo locally, then push to TracesHub and browse analytics and per-line blame.

Everything starts local and free: the agent-trace CLI is open source and records traces on your machine, with no account needed. TracesHub comes in when you want the record hosted, browsable, and shared. This page walks the whole loop.

Part 1 — Trace your repo locally

1. Install the CLI

One command, Python 3.9+, zero external dependencies. It installs the agent-trace CLI and the local file viewer.

curl -fsSL https://traceshub.com/install.sh | bash

Installer details, PATH notes, and uninstall are in the CLI docs: Installation.

2. Initialize your repo

Go to your project folder (it should be a git repo) and run init — zero prompts, just like git init. Hooks are wired up; nothing is written into your working tree.

cd your-project
agent-trace init

3. Keep coding with your agents

Work normally with Cursor, Claude Code, or Codex CLI. Hooks record traces locally under ~/.agent-trace as you go — nothing changes about how you work.

4. Commit and push as usual

On every commit, the post-commit hook links traces to the commit and builds the deterministic per-line attribution ledger. Push to GitHub like you always do.

git add -A && git commit -m "feat: …"
git push

5. Check attribution locally

Open the file viewer in your browser — per-line git blame overlaid with AI authorship — or ask about a single file straight from the terminal.

agent-trace viewer
# or, per file:
agent-trace blame src/app.py

Part 2 — Push it to TracesHub and share

6. Sign in to TracesHub

Go to app.traceshub.com and sign in with your GitHub account — that’s the whole signup. A personal organization is created for you automatically.

7. Connect GitHub and import your repo

Install the TracesHub GitHub App on your account or organization, then import the repo as a project from the dashboard and enable traces for it. Details: Connecting GitHub and Projects.

8. Mint a token and add the remote

Create a personal access token in the app (Settings → API tokens — it’s shown once, copy it). Tokens are scoped: a user token works across an org’s projects, a project token is limited to one project — so one user token can cover all your repos. See API tokens.

Your project’s Setup tab gives you the exact remote add command to paste, prefilled with your project’s remote URL:

agent-trace remote add origin \
  "https://api.traceshub.com/at/<org>/<repo>" --token <YOUR_TOKEN>

9. Push your traces

Push explicitly, git-style — nothing syncs until you say so. sync does push + pull in one go. Config toggles decide how much detail ships: full conversations, prompts and summaries, or attribution only — see Data & privacy.

agent-trace push
# or push + pull:
agent-trace sync

10. Browse it on TracesHub

Open your project: repo-wide analytics of what each model wrote, per-line file blame, and the conversation behind every AI-written line. Invite your team when you’re ready.

That’s the whole loop

Trace locally, push when you choose, browse and share on TracesHub. From here: