by luoyuctl
Local-first TUI for AI coding-agent session history: trace cost, tokens, time, tool failures, latency, health, diffs, reports, and CI gates across local agent logs.
# Add to your Claude Code skills
git clone https://github.com/luoyuctl/agenttraceagenttrace is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by luoyuctl. Local-first TUI for AI coding-agent session history: trace cost, tokens, time, tool failures, latency, health, diffs, reports, and CI gates across local agent logs. It has 101 GitHub stars.
agenttrace's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/luoyuctl/agenttrace" and add it to your Claude Code skills directory (see the Installation section above).
agenttrace is primarily written in Go. It is open-source under luoyuctl on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh agenttrace against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
agenttrace is a local-first terminal TUI and report generator for AI coding-agent session history. It reads 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, and generic JSON/JSONL traces, then helps with two daily jobs: see what multiple agents spent across cost, tokens, and time; and diagnose why a task ran slowly.
AI coding agents now behave like small build systems: they call tools, retry, stall, and spend tokens while you only see the final answer.
agenttrace reads the logs your agents already write and puts cost-heavy or slow sessions first.
It helps you answer:
These screenshots were captured from a local run against real session logs. They are not --demo output and not test fixtures.
agenttrace
| Overview | Critical sessions |
|---|---|
| Session detail | Diagnostics |
|---|---|
That local run found:
AGENTTRACE v0.5.4
| Signal | What agenttrace found |
|---|---|
| Analyzed sessions | 1,761 |
| Total tokens | 9.13B |
| Estimated cost | $5,037.26 |
| Tool failure rate | 1.1% |
| Critical sessions | 16 |
| Average health | 91% |
curl -sL https://raw.githubusercontent.com/luoyuctl/agenttrace/master/install.sh | sh
Other install paths:
brew install luoyuctl/tap/agenttrace
go install github.com/luoyuctl/agenttrace/cmd/agenttrace@latest
Windows:
iwr -useb https://raw.githubusercontent.com/luoyuctl/agenttrace/master/install.ps1 | iex
# Open the local TUI
agenttrace
# Check detected agent directories and cache state
agenttrace --doctor
# Generate machine-readable evidence
agenttrace --overview -f json
# Search local session metadata without indexing prompt text
agenttrace --search billing
agenttrace --search internal/ws -f json
# Create a self-contained report for CI artifacts or issue links
agenttrace --overview -f html -o agenttrace-overview.html
# Save a local baseline, then compare a later run
agenttrace --overview -f json -o agenttrace-baseline.json
agenttrace --overview -f json \
--baseline agenttrace-baseline.json \
-o agenttrace-overview.json
# Fail CI on unhealthy agent runs
agenttrace --overview \
--fail-under-health 80 \
--fail-on-critical \
--max-tool-fail-rate 15
agenttrace supports local sessions from:
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, and generic JSON/JSONL traces.
| Need | agenttrace gives you |
|---|---|
| Historical spend review | Sessions grouped across agents with token totals, model pricing, estimated cost, and elapsed time |
| Slow-task diagnosis | Latency stats, long gaps, hanging sessions, retry loops, slow tools, large params, and context pressure |
| Regression evidence | Local baseline comparison when supplied, incident timelines, and conservative tool authority categories in reports |
| First-session triage | Sort and filter by cost, duration, health, failures, anomalies, model, source, or text search |
| Shareable evidence | JSON, Markdown, and self-contained HTML reports |
| Local-first inspection | No hosted backend required |
Listed in these open source projects:
Parser PRs are welcome. A good parser contribution usually includes:
DetectFormatRun before sending a PR:
go test ./...
go build -o agenttrace ./cmd/agenttrace/
./agenttrace --doctor
See CONTRIBUTING.md for the full contribution flow.
MIT © 2026 agenttrace contributors