TracesDocs
DiscordHome
Git Integration

CLI Discovery

Browse traces from your repo's git history without manual imports.

When the TUI launches inside a git repo, it runs background discovery after the initial trace list loads. You can clone a repo, open Traces, and browse every trace attached to the repo's history -- including traces from other contributors.

How it works

Two sources are queried in parallel:

  1. Git notes -- reads trace IDs from refs/notes/traces on the last 20 commits
  2. API by repo -- queries the API with the repo's remote URL for all matching traces in your namespace

The results are deduplicated against the local SQLite store. Unknown traces are fetched as metadata-only entries (title, agent, git fields, shared URL). No message content is downloaded. The list refreshes automatically when new traces are found.

Syncing full content

traces sync <externalId>

Downloads messages and parts from the API and stores them locally. The trace then appears in the TUI with its complete conversation history.

Requirements

  • Git hooks installed in the repo (so notes are present) -- see Git Hooks
  • Traces have been shared (so the API can return them)

Git Hooks

Attach trace IDs to git commits automatically with a post-commit hook.

Account and Profile

Manage your personal account, profile settings, and identity details.

On this page

How it works
Syncing full content
Requirements