A project is one GitHub repository imported into a TracesHub org. It holds the hosted trace store for that repo and everything around it: access, tokens’ target, analytics, file blame, and sharing.
Importing a repository
From the dashboard, click Import repository (or go to /new):
- Pick the installation — the GitHub account or organization where the repo lives. If nothing is listed, connect GitHub first.
- Pick the repository — search the list and click Import. Repos already imported are marked. Private repos work exactly like public ones.
The project is created under the matching TracesHub org with the same <org>/<repo> naming as GitHub, and you land on its page.
Enabling traces
A fresh project starts with traces disabled — nothing can be pushed into it and there is nothing to browse. The Enable traces button sits in the project header; org owners and admins can toggle it, everyone else sees a status badge.
While disabled, pushes from the CLI are rejected and the Analytics / Files / Raw trace store tabs show a “not enabled” notice. Disabling later doesn’t delete anything — it just closes the doors until re-enabled.
The project page
The project header shows the <org>/<repo> name, a link to the GitHub repo, the default branch, and the latest known commit. Below it, six tabs:
| Tab | What it’s for |
|---|---|
| Analytics | Whole-codebase AI attribution at the default branch’s HEAD — each model’s share of every line. See Analytics. |
| Raw trace store | Counts and breakdowns computed straight from everything pushed — all branches and commits. See Analytics. |
| Files | The repo tree at HEAD with per-line AI attribution; click a line for its model, trace, and conversation. See Files & line blame. |
| Setup | Copy-paste instructions to connect a local clone — install, token, the exact remote add command prefilled with this project’s URL, and the first push. See Pushing traces. |
| Share | Collaborators and invitations for this project. See Teams & access. |
| Settings | Project lifecycle — deleting the project and its trace data. |
Who can do what
Project access is governed by the access model: your effective traces access (read / write / admin) decides whether you can view and push, while org owners and admins manage the project itself — enabling/disabling traces, sharing, and deletion.
Deleting a project
Project → Settings → Delete project (org owners/admins only; you type <org>/<repo> to confirm). This permanently removes the project and all of its hosted trace data — traces, attribution ledgers, conversations, and summaries. It cannot be undone.
Two things it does not touch:
- The GitHub repository — completely unaffected. You can reimport it later as a fresh project under the same name.
- Local trace data on contributors’ machines — the local-first record under
~/.agent-tracestays; only the hosted copy is gone.