General
Do I need a TracesHub account to use agent-trace?
No. The CLI is open source and fully functional locally — recording, blame, context, the viewer, git notes — with no account. TracesHub comes in when you want the record hosted, browsable in a web UI, and shared with a team. See the CLI documentation for everything the CLI does on its own.
Is attribution guessed or measured?
Measured. The ledger is built at commit time from per-line SHA-256 hashes; a line is AI-written (by a specific model and tool) or it has no attribution. There’s no scoring, no heuristics, no “probably AI”. See How TracesHub works.
Which coding agents are supported?
Cursor, Claude Code, and Codex CLI — one attribution ledger regardless of which wrote the code. The CLI docs track harness support in detail.
Does TracesHub upload anything automatically?
No. Recording is local and continuous; uploading only happens when someone runs agent-trace push or sync with a write token. There’s no background sync and no upload-on-commit.
Can I self-host?
The storage engine (agent-trace-service) and the CLI are standalone open source, so a team can run its own remote. The hosted application adds GitHub-linked orgs, access control, tokens, and the web views.
Does TracesHub store a copy of my source code?
No — the Files and Analytics views read your repo live from GitHub via the App. The trace store holds trace records, ledgers, commit links, and whatever conversational detail your push settings include. See Data & privacy.
Setup & pushing
My push fails with 401
The token is missing, revoked, or expired. Mint a new one in Settings → API tokens and rebind it (agent-trace remote set-token, or update your --token-env variable). More cases: Pushing traces.
My push fails with 403
Your token lacks traces:write, or your effective access on the project is read-only. Tokens are capped by your access at use time — check the project’s Share tab / your org membership, then the token’s scopes.
My push is rejected with a “traces disabled” conflict
The project’s traces toggle is off. An org owner or admin can enable it from the project header. See Projects.
I pushed, but Analytics shows zero AI lines
The Analytics and Files tabs are computed at the default branch’s HEAD. If your traced commits aren’t on the default branch on GitHub yet (unpushed, or on a feature branch), they won’t show there — but the Raw trace store tab will show them, which is the quickest way to confirm the push arrived. See Analytics.
The Files tab says the codebase view is unavailable
TracesHub can’t read the repo via the GitHub App — the App was uninstalled, suspended, or the repo was removed from its repository selection. Fix the installation under Settings → Connected GitHub. See Connecting GitHub.
The repo I want to import isn’t listed
The GitHub App installation can’t see it. If the installation uses only select repositories, add the repo to the selection on GitHub (or via Settings → Connected GitHub → Connect another).
Two of us push to the same project — does that work?
Yes, that’s the intended model. Each of you adds the same remote URL with your own token; local project ids differ, but the hosted store is shared. After pull/sync, each of you can blame and context lines the other wrote. See How TracesHub works.
Team & data
I invited someone but they can’t accept
Invitations expire, and each link is single-use per outcome (accepted / declined / revoked). Check the pending list on the project’s Share tab and create a fresh invite if needed. The invitee must sign in with GitHub to accept.
Why can’t I add a collaborator by GitHub login?
Direct collaborator grants require the person to have signed in to TracesHub at least once. Until then, send them an invitation link instead — same tab. See Teams & access.
How do I get all our data out?
Org owners/admins: Settings → Data export downloads a ZIP with the org’s trace data, metadata, and audit log. See Data & privacy.
What exactly does deleting a project remove?
All hosted trace data for that project — traces, ledgers, conversations, summaries — permanently. The GitHub repo and everyone’s local ~/.agent-trace data are untouched, and the repo can be reimported fresh. See Projects.
Still stuck?
- CLI-side issues (hooks, recording, blame, local data): the CLI docs’ Troubleshooting page and
agent-trace doctor. - Application issues (sign-in, GitHub connection, projects, sharing, the web UI): email support@traceshub.com.