About langsmith-fetch
langsmith-fetch is a command-line skill for saving LangSmith traces locally, aimed at developers investigating agent runs. It supports fetching recent traces or a trace by ID and inspecting execution details.
Key features
- 01Fetch recent traces
- 02Fetch a trace by ID
- 03Save traces as JSON or readable text
- 04Inspect called tools and their results
Use cases
- 01Debugging unexpected agent behavior
- 02Reviewing tool calls and returned data
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ langchain-ai/ lca-skills --skill langsmith-fetchAfter installing, type/langsmith-fetchin Claude Code to confirm it loaded.
Details
From the project READMEFetching LangSmith Traces
Requires langsmith-fetch in project dependencies and LANGSMITH_API_KEY in a .env file.
Setup
First, find the .env file containing LANGSMITH_API_KEY:
find . -name ".env" -type f 2>/dev/null | head -5
Commands
Use --env-file <path-to-.env> with all commands:
# Fetch recent traces (uses LANGSMITH_PROJECT from .env, or specify --project-uuid)
uv run --env-file <path> langsmith-fetch traces ./traces --limit 10
uv run --env-file <path> langsmith-fetch traces ./traces --project-uuid <uuid> --limit 10
# Fetch single trace by ID
uv run --env-file <path> langsmith-fetch trace <trace-id>
# Include metadata (timing, tokens, costs)
uv run --env-file <path> langsmith-fetch trace <trace-id> --include-metadata
Output Formats
--format pretty- Human-readable (default)--format json- Pretty-printed JSON--format raw- Compact JSON for piping
Troubleshooting Workflow
- Find
.env:find . -name ".env" -type f 2>/dev/null - Fetch recent traces:
uv run --env-file <path> langsmith-fetch traces ./debug --limit 10 - Find relevant trace in saved JSON files
- Check: What tools were called? What did they return? Was it correct/expected?
Comments
Markdown supported