@tracebird/cli
v0.1.1
Published
tracebird CLI — a local OTLP receiver and time-travel UI for AI agent runs.
Maintainers
Readme
@tracebird/cli
The public face of tracebird. A single npx away from a
local, time-travel debugger for your AI agent runs.
npx @tracebird/cli # start the OTLP receiver (+ UI, from Stage 3)Then point any OpenTelemetry-instrumented agent at it:
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318Commands
| Command | Description |
| --- | --- |
| tracebird / tracebird live | Start the OTLP receiver, capture spans, and serve the UI. |
| tracebird demo | Serve the UI with bundled sample runs — no agent needed. |
| tracebird open <file.jsonl> | Load a saved session and serve the UI (no receiver). |
JSON API
The UI reads a small read-only API (everything delegates to @tracebird/core):
| Route | Returns |
| --- | --- |
| GET /api/session | { live, filePath, count } |
| GET /api/runs | run summaries, newest first |
| GET /api/runs/:id | a full reconstructed Run |
Options
| Flag | Default | Description |
| --- | --- | --- |
| --port <n> | 4318 | Port for the receiver / UI server. |
| --host <addr> | 127.0.0.1 | Address to bind. |
| --out <dir> | ./.tracebird | Where captured sessions are written. |
| --no-open | — | Don't open the browser on start. |
How it works
- A tiny
node:httpserver acceptsPOST /v1/tracesin both OTLP/JSON and OTLP/protobuf (the SDK default). Protobuf is decoded with a vendored descriptor — no codegen step. - Parsing and reconstruction are delegated entirely to
@tracebird/core; the CLI only does I/O.
npx nx test cli