agtrace 0.7.0

The official CLI for agtrace, built on top of agtrace-sdk. Visualize and analyze AI agent execution traces.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99

<div align="center">
  <img src="https://raw.githubusercontent.com/lanegrid/agtrace/main/docs/images/agtrace-icon.png" width="96" alt="agtrace logo">
  <h1>agtrace</h1>
  <p><strong>See What Your AI Agent Is Actually Doing</strong></p>

  [![npm](https://img.shields.io/npm/v/@lanegrid/agtrace.svg?style=flat&label=npm)](https://www.npmjs.com/package/@lanegrid/agtrace)
  [![crates.io](https://img.shields.io/crates/v/agtrace.svg?label=crates.io)](https://crates.io/crates/agtrace)
</div>

---

## The Problem I Had

When I started using AI coding agents (Claude Code, Codex, Gemini), I realized I was working with a **black box**. I couldn't see:

- How much of the context window was being consumed
- What the agent was actually doing between my prompts
- When the conversation was getting too long and performance would degrade

I found myself *guessing* the agent's internal state. That felt wrong.

## What Changed

Now I always run **agtrace** alongside my coding agent. It's become essential.

![agtrace with Claude Code](https://raw.githubusercontent.com/lanegrid/agtrace/main/docs/images/agtrace_live_use_screenshot.png)

What I see:
- **Context window usage** — A color-coded bar showing how full the conversation is
- **Token consumption trends** — How much context each task uses over time
- **Live activity** — Tool calls, file reads, reasoning traces as they happen

For the first time, I can make informed decisions about when to start a new session, how to scope my requests, and whether the agent is stuck in a loop.

---

![agtrace watch demo](https://raw.githubusercontent.com/lanegrid/agtrace/main/docs/assets/demo.gif)

## Try It

```bash
npm install -g @lanegrid/agtrace
cd my-project
agtrace init      # One-time setup
agtrace watch     # Launch dashboard in a separate terminal
```

Works with Claude Code, Codex (OpenAI), and Gemini. Zero config — just discovers existing logs.

## Give Your Agent Memory of Past Sessions

One thing I didn't expect: agents can also query their own execution history via [MCP](https://modelcontextprotocol.io):

```bash
# Claude Code
claude mcp add agtrace -- agtrace mcp serve

# Codex
codex mcp add agtrace -- agtrace mcp serve
```

Now your agent can search what it did yesterday, find past errors, and learn from previous sessions.

See the [MCP Integration Guide](docs/mcp-integration.md) for more.

## Other Commands

```bash
agtrace session list       # Browse past sessions
agtrace lab grep "error"   # Search across all sessions
```

## For Tool Builders

If you're building your own IDE plugin, dashboard, or observability tool:

```toml
[dependencies]
agtrace-sdk = "0.6"
```

See [SDK Documentation](https://docs.rs/agtrace-sdk) and [Examples](crates/agtrace-sdk/examples/).

## Documentation

- [Getting Started](docs/getting-started.md)
- [MCP Integration](docs/mcp-integration.md)
- [Architecture](docs/architecture.md)
- [Full Documentation](docs/README.md)

## Feedback

Have ideas?
- [RFC: Watch TUI Display](https://github.com/lanegrid/agtrace/discussions/36)
- [RFC: MCP Tools](https://github.com/lanegrid/agtrace/discussions/37)

## License

MIT / Apache 2.0