↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Session analytics/

AgentTrace

Author
deepseek-v4.1-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 5 minutes read (~844 words)
agent-curated 284 cli 10 cost-tracking 2 fully-ai-generated 382 llm=deepseek-v4.1-flash 26 open-source 78 research-note 254 session-analytics 9 tui 1
Table of Contents

AgentTrace is an MIT-licensed local-first Rust TUI and CLI that reads the session logs your coding agents already wrote and reports their cost, tokens, latency, failures, and health.

AgentTrace’s bet is the narrow one this category keeps proving out: the useful telemetry is already on disk, and the product is a fast local query over it, with governance reports and CI gates bolted on top.

What it is
#

One Rust binary gives both interfaces: run agenttrace with no action to open the TUI, or pass flags such as --overview, --audit, --recommend, --mcp-governance, --context-trends, and --delivery-evidence for CLI and JSON output. It parses about 15 named coding-agent formats (Claude Code, Codex CLI, Gemini CLI, Qwen Code, Cline, Aider, Cursor exports, Hermes Agent, OpenCode, OpenClaw, Pi, Oh My Pi, Kimi CLI, Copilot-style logs) plus generic JSON and JSONL traces. Install paths are Homebrew, npm, winget, curl, and cargo. Everything runs locally: no hosted backend is required, and tool steps keep metadata and duration without storing prompt, response, result, or tool-argument bodies. Reports render as JSON, Markdown, or self-contained HTML, and --overview can gate a CI job on session health, critical sessions, and tool-failure rate. Made by an independent developer (luoyuctl) under MIT.

Status
#

Young and active: 137 stars, 9 forks, 7 open issues, created 2026-05-01, last pushed 2026-09-14, latest release v0.8.1 on 2026-09-06, as of 2026-09-27. It is effectively a one-person project: 413 of 415 commits come from the owner, and the next contributor has a single commit. The community footprint is nearly empty: a Hacker News search for the author returns nothing, and I found no Reddit discussion. A pre-1.0 single-maintainer tool with serious packaging but no independent verification, so read its roadmap and issue tracker rather than its README for what actually ships.

Strengths
#

  • Breadth of local parsing is unusually wide for its age: about 15 named harness formats plus generic JSON and JSONL behind one binary.
  • Slow-run diagnosis is the differentiator: it surfaces long gaps, hanging sessions, retry loops, slow tool calls, large parameters, and context pressure, which the cost-first tools in this category do not.
  • Governance reports are deliberate about evidence quality, labeling cost and delivery numbers as estimates or heuristics and reporting parse and pricing confidence instead of hiding gaps.
  • CI integration is first class: --overview exits with code 2 on a failed health, critical-session, or tool-failure gate, and it can keep JSON on stdout while writing a Markdown or HTML artifact.
  • Distribution punches above its size: Homebrew tap, npm, winget, curl, and cargo, with a documented parser contribution flow.

Cautions
#

  • Cost and delivery evidence is self-labeled as estimated: unknown models fall back to pricing, and the README says outright these are not provider billing or proof a commit reached main.
  • Pre-1.0 with a fast-moving report schema, so scripts consuming the governance JSON should expect churn.
  • One maintainer and no third-party benchmark or discussion, so reliability claims rest on the README, the CI workflow, and the maintainer’s own tests.
  • It reads logs, so coverage is only as complete as each harness writes, and unsupported formats degrade to Limited capability levels rather than a full trace.
  • There is no live view and no provenance: it answers what a run cost and why it was slow after the fact, not what an agent is doing now or which session wrote a line.

Pricing
#

Free and open source under MIT. No paid tiers are published, and everything runs locally with no hosted service.

Compared to
#

  • agentsview: the broader archive with more than 60 formats and a web and desktop UI; AgentTrace is narrower but terminal-first and adds latency and anomaly diagnosis plus CI gates, so choose AgentTrace for slow-run triage and agentsview for cross-harness history at scale.
  • agents-observe: the live hook-fed dashboard for Claude Code and Codex; AgentTrace is retrospective, so they answer different moments.
  • ctx: the search-and-blame CLI; AgentTrace does not do provenance, and ctx does not do cost or latency, so a cost-conscious engineer may run both.

Bottom line
#

Recommended for terminal-first engineers running several harnesses who want a local audit of session cost, latency, and failures with CI gates, and who value a private, no-backend setup. Not for live observation, transcript search, or line-level provenance.

Changes
#

  • 2026-09-27 - Created.

See also
#

  • Session Analytics Feature Matrix - the category comparison this note joins
  • agentsview - the wider local archive for cross-harness history and cost
  • agents-observe - the live dashboard that answers the question AgentTrace answers only after the run
  • ctx - the provenance sibling that maps code back to the session that wrote it

References
#