trace-claude-code skill
Automatically trace Claude Code conversations to Braintrust for observability. Captures sessions, conversation turns, and tool calls as hierarchical traces.
Is the trace-claude-code skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the trace-claude-code skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git /tmp/Continuous-Claude-v3 mkdir -p ~/.claude/skills cp -r /tmp/Continuous-Claude-v3/.claude/plugins/braintrust-tracing/skills/trace-claude-code ~/.claude/skills/trace-claude-code
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Trace Claude Code to Braintrust
Automatically send Claude Code conversations to Braintrust for tracing and observability. Get full visibility into your AI coding sessions with hierarchical traces showing sessions, turns, and every tool call.
What you get
Claude Code Session (root trace)
├── Turn 1: "Add error handling"
│ ├── Read: src/app.ts
│ ├── Edit: src/app.ts
│ └── Response: "I've added try-catch..."
├── Turn 2: "Now run the tests"
│ ├── Terminal: npm test
│ └── Response: "All tests pass..."
└── Turn 3: "Great, commit this"
├── Terminal: git add .
├── Terminal: git commit -m "..."
└── Response: "Changes committed..."How it works
Four hooks capture the complete workflow:
Quick setup
Run the setup script in any project directory where you want tracing:
bash /path/to/skills/trace-claude-code/setup.shThe script prompts for your API key and project name, then configures all hooks automatically.
Manual setup
Prerequisites
- Claude Code CLI installed
- Braintrust API key
- jq command-line tool (brew install jq on macOS)
Configuration
Create .claude/settings.local.json in your project directory:
{
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/session_start.sh"
}
]
}
],
"PostToolUse": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/post_tool_use.sh"
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/stop_hook.sh"
}
]
}
],
"SessionEnd": [
{
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/session_end.sh"
}
]
}
]
},
"env": {
"TRACE_TO_BRAINTRUST": "true",
"BRAINTRUST_API_KEY": "sk-...",
"BRAINTRUST_CC_PROJECT": "my-project"
}
}Replace /path/to/hooks/ with the actual path to this skill's hooks directory.
Environment variables
Viewing traces
After running Claude Code with tracing enabled:
- Go to braintrust.dev
- Navigate to your project (e.g., claude-code)
- Click Logs to see all traced sessions
Each trace shows:
- Session root: The overall Claude Code session
- Turns: Each conversation exchange (user input → assistant response)
- Tool calls: Individual operations (file reads, edits, terminal commands)
Trace structure
Traces are hierarchical:
- Session (root span)
- span_attributes.type: "task"
- metadata.session_id: Unique session identifier
- metadata.workspace: Project directory
- Turn (child of session)
- span_attributes.type: "llm"
- input: User message
- output: Assistant response
- metadata.turn_number: Sequential turn number
- Tool call (child of turn or session)
- span_attributes.type: "tool"
- input: Tool input (file path, command, etc.)
- output: Tool result
- metadata.tool_name: Name of the tool used
Troubleshooting
No traces appearing
- Check hooks are running:
tail -f ~/.claude/state/braintrust_hook.log- Verify environment variables in .claude/settings.local.json:
- TRACETOBRAINTRUST must be "true"
- BRAINTRUSTAPIKEY must be valid
- Enable debug mode:
{
"env": {
"BRAINTRUST_CC_DEBUG": "true"
}
}Permission errors
Make hook scripts executable:
chmod +x /path/to/hooks/*.shMissing jq command
Install jq:
- macOS: brew install jq
- Ubuntu/Debian: sudo apt-get install jq
State issues
Reset the tracing state:
rm ~/.claude/state/braintrust_state.jsonHook logs
View detailed hook execution logs:
# Follow logs in real-time
tail -f ~/.claude/state/braintrust_hook.log
# View last 50 lines
tail -50 ~/.claude/state/braintrust_hook.log
# Clear logs
> ~/.claude/state/braintrust_hook.logFile structure
hooks/
├── common.sh # Shared utilities (logging, API, state)
├── session_start.sh # Creates root trace span
├── post_tool_use.sh # Captures tool calls
├── stop_hook.sh # Captures conversation turns
└── session_end.sh # Finalizes traceAlternative: SDK integration
For programmatic use with the Claude Agent SDK, use the native Braintrust integration:
import { initLogger, wrapClaudeAgentSDK } from "braintrust";
import * as claudeSDK from "@anthropic-ai/claude-agent-sdk";
initLogger({
projectName: "my-project",
apiKey: process.env.BRAINTRUST_API_KEY,
});
const { query, tool } = wrapClaudeAgentSDK(claudeSDK);See Braintrust Claude Agent SDK docs for details.
More skills from parcadei/Continuous-Claude-v3
- Aagent-context-isolationAgent Context Isolation
- Aagent-orchestrationAgent Orchestration Rules
- Aagentic-workflowAgentic Workflow Pattern
- Aagentica-claude-proxyGuide for integrating Agentica SDK with Claude Code CLI proxy
- Aagentica-infrastructureReference guide for Agentica multi-agent infrastructure APIs
- Aagentica-promptsWrite reliable prompts for Agentica/REPL agents that avoid LLM instruction ambiguity
- Aagentica-sdkBuild Python agents with Agentica SDK - @agentic decorator, spawn(), persistence, MCP integration
- Aagentica-serverAgentica server + Claude proxy setup - architecture, startup sequence, debugging
- Aagentica-spawnSpawn Agentica multi-agent patterns
- Aanalytic-functionsProblem-solving strategies for analytic functions in complex analysis
- Aast-grep-findAST-based code search and refactoring via ast-grep MCP
- Aasync-repl-protocolAsync REPL Protocol