You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PyPI name 'agent-trace' conflicts with existing 'agenttrace' package
(PEP 503 normalization). CLI command is now 'agent-strace'.
GitHub repo, Python module (agent_trace), and trace directory
(.agent-traces/) are unchanged.
Co-authored-by: Ona <no-reply@ona.com>
Copy file name to clipboardExpand all lines: README.md
+28-28Lines changed: 28 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,19 +10,19 @@ We have `strace` for syscalls. We have `tcpdump` for packets. We have nothing fo
10
10
11
11
When a coding agent rewrites 20 files in a background session, you get a pull request. You don't get the story of how it got there. Which files did it read first? What context was in the window when it decided to change the approach? Why did it call the same tool three times?
12
12
13
-
LangSmith traces LLM calls. That's one layer. The gap is everything around it: tool calls, file operations, decision points, error recovery. `agent-trace` captures the full picture.
13
+
LangSmith traces LLM calls. That's one layer. The gap is everything around it: tool calls, file operations, decision points, error recovery. `agent-strace` captures the full picture.
14
14
15
15
## Install
16
16
17
17
```bash
18
18
# With uv (recommended)
19
-
uv tool install agent-trace
19
+
uv tool install agent-strace
20
20
21
21
# Or with pip
22
-
pip install agent-trace
22
+
pip install agent-strace
23
23
24
24
# Or run without installing
25
-
uvx agent-trace replay
25
+
uvx agent-strace replay
26
26
```
27
27
28
28
**Zero dependencies.** Python 3.10+ standard library only.
@@ -35,16 +35,16 @@ Wrap any MCP server. Every message between agent and server is captured.
35
35
36
36
```bash
37
37
# Record a session
38
-
agent-trace record -- npx -y @modelcontextprotocol/server-filesystem /tmp
38
+
agent-strace record -- npx -y @modelcontextprotocol/server-filesystem /tmp
agent-trace record -- <command> Record an MCP server session
85
-
agent-trace replay [session-id] Replay a session (default: latest)
86
-
agent-trace list List all sessions
87
-
agent-trace stats [session-id] Show tool call frequency and timing
88
-
agent-trace inspect <session-id> Dump full session as JSON
89
-
agent-trace export <session-id> Export as JSON, CSV, or NDJSON
84
+
agent-strace record -- <command> Record an MCP server session
85
+
agent-strace replay [session-id] Replay a session (default: latest)
86
+
agent-strace list List all sessions
87
+
agent-strace stats [session-id] Show tool call frequency and timing
88
+
agent-strace inspect <session-id> Dump full session as JSON
89
+
agent-strace export <session-id> Export as JSON, CSV, or NDJSON
90
90
```
91
91
92
92
### Replay output
@@ -146,23 +146,23 @@ Session Summary
146
146
147
147
```bash
148
148
# Show only tool calls and errors
149
-
agent-trace replay --filter tool_call,error
149
+
agent-strace replay --filter tool_call,error
150
150
151
151
# Replay with timing (watch it unfold)
152
-
agent-trace replay --live --speed 2
152
+
agent-strace replay --live --speed 2
153
153
```
154
154
155
155
### Export
156
156
157
157
```bash
158
158
# JSON array
159
-
agent-traceexport a84664 --format json
159
+
agent-straceexport a84664 --format json
160
160
161
161
# CSV (for spreadsheets)
162
-
agent-traceexport a84664 --format csv
162
+
agent-straceexport a84664 --format csv
163
163
164
164
# NDJSON (for streaming pipelines)
165
-
agent-traceexport a84664 --format ndjson
165
+
agent-straceexport a84664 --format ndjson
166
166
```
167
167
168
168
## Trace format
@@ -210,7 +210,7 @@ Events link to each other. A `tool_result` has a `parent_id` pointing to its `to
210
210
211
211
## Use with Claude Code, Cursor, Windsurf
212
212
213
-
agent-trace works with any tool that launches MCP servers. The idea is simple: instead of launching the MCP server directly, launch it through `agent-trace record`. The agent and server don't know the proxy exists.
213
+
agent-strace works with any tool that launches MCP servers. The idea is simple: instead of launching the MCP server directly, launch it through `agent-strace record`. The agent and server don't know the proxy exists.
214
214
215
215
### Claude Code
216
216
@@ -219,7 +219,7 @@ agent-trace works with any tool that launches MCP servers. The idea is simple: i
219
219
claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem /tmp
220
220
221
221
# Use:
222
-
claude mcp add filesystem -- agent-trace record --name filesystem -- npx -y @modelcontextprotocol/server-filesystem /tmp
222
+
claude mcp add filesystem -- agent-strace record --name filesystem -- npx -y @modelcontextprotocol/server-filesystem /tmp
0 commit comments