Dev Agent Lens

Dev-Agent-Lens

Capture and query the work of Claude Code, Codex, and the people reviewing it.
DAL stores traces as Parquet and exposes them through DuckDB. Use a directory for
one developer, or an S3-compatible object store for a team. Phoenix is an optional
source for existing history, not a requirement for new session capture.

Start with local sessions

Requires Python 3.12 and uv.

Choose the repository scope before importing. Session logs contain prompts,
source code, and tool results. For Claude sessions, use --agent claude-code and a
separate project name. Capture setup covers both agents,
identity, scheduled uploads, and persistence checks.

Typed queries

The raw layout preserves producer data. The typed layout extracts frequently
queried fields such as model, tokens, person, session, agent, ticket, and tool
kind, while retaining other attributes. Build it explicitly:

A rebuild is a maintenance operation: it replaces the derived layout. Coordinate
writers and readers before rebuilding a shared store. It is not an incremental
streaming index. Storage formats explains the raw,
typed, and blob datasets; the cookbook supplies
queries you can run against them.

Run for a team

- Self-hosted deployment: Docker Compose, local MinIO, receiver,
  source sync, identity mapping, and verification.
- External S3 or Cloudflare R2: separate object storage,
  credentials, migration gates, and hosting requirements.
- Historical import: Phoenix/Arize sources and resumable
  sync. The Oxen import script is provided for migration of existing archives.
- Git events: signed GitHub and Forgejo webhooks and
  historical pull-request backfill.
- Proxy setup: live LLM tracing with LiteLLM.
- Capture by surface: which path (proxy, hooks, session
  files) reaches each Claude Code and…