deepagents-trace (Python server + CLI)

PyPI distribution name: deepagents-trace (the agenttrace name is already taken on PyPI by an unrelated project — TensorStax's own agent-tracing tool — so this package is published under a different name; the importable module, the CLI command, and the product itself are still called agenttrace/AgentTrace).

pip install deepagents-trace && agenttrace ui — starts the AgentTrace web API (and a /ws live-stream) with zero Node/Bun process, mlflow ui-style. For local development against this checkout: pip install -e python-server.

This is Phase 1 + 3 of the Python migration plan: a FastAPI backend that is a 1:1 contract port of the Next.js API (src/app/api/* in the main repo), plus the CLI. Phase 2 is not done yet — there is no bundled frontend, so / currently serves a placeholder page confirming the API is up; use the API directly (/api/*) or the existing Next.js dashboard against this backend's data once Phase 2 lands.

Install & run

pip install deepagents-trace       # or `pip install -e python-server` against this checkout
agenttrace ui                      # http://127.0.0.1:3000, SQLite by default (./agenttrace.db)
agenttrace ui --database-url postgresql://user:pass@localhost:5432/agenttrace
agenttrace ui --port 8080 --host 0.0.0.0

agenttrace db init creates the schema explicitly (also runs automatically on agenttrace ui startup) — schema-push style (Base.metadata.create_all), matching how this repo already runs prisma db push rather than migrations.

What's ported

The POST /api/events contract (the one integrations/agenttrace-langchain depends on) is unchanged: same fields, same atr_ key auth, same event types.

Tests

pip install -e "python-server[dev]"
pytest python-server/tests

Releasing a new version

Published: pypi.org/project/deepagents-trace — Trusted Publishing (OIDC) is set up, no API token stored as a GitHub secret.

To ship a new version:

1. Bump version in pyproject.toml.
2. Commit, then push a tag matching python-server-v* (e.g. python-server-v0.1.2) — .github/workflows/publish-pypi.yml builds and publishes automatically. A GitHub Release (published event) also triggers it, or run the workflow manually (workflow_dispatch).
3. Locally, verify before tagging: python -m build && twine check dist/* in this directory.

Trusted publisher config on pypi.org (Publishing → Trusted publishers), for reference/if it ever needs re-registering: project deepagents-trace, owner CouLiBaLy-B, repo agenttrace, workflow publish-pypi.yml, environment pypi.

Known gaps vs. the Next.js backend (tracked for later phases)

• No frontend bundle yet (Phase 2).
• No demo-account seeding on signup (the Next.js version seeds 3 sample projects — intentionally skipped here to keep this phase scoped to the API contract).
• Realtime wire protocol is plain JSON over /ws, not the Socket.IO protocol — the current React frontend's socket.io-client won't talk to it until Phase 2 adapts it.