
langsmith-fetch
โ 2by langchain-ai ยท part of langchain-ai/lca-skills
Fetches LangSmith traces for debugging agent behavior. Use when troubleshooting agent issues, reviewing conversation history, or investigating tool calls.
๐ฅ๐ฅ๐ฅโ VerifiedAccount requiredNeeds API keys
๐งฉ One of 2 skills in the langchain-ai/lca-skills package โ works on its own, and pairs well with its siblings.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
Fetching LangSmith Traces
Requires langsmith-fetch in project dependencies and LANGSMITH_API_KEY in a .env file.
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-metadataOutput Formats
--format pretty- Human-readable (default)--format json- Pretty-printed JSON--format raw- Compact JSON for piping
Copy & paste โ that's it
npx skills add langchain-ai/lca-skills --skill "langsmith-fetch" --full-depthRun this in your project โ your agent picks the skill up automatically.
Setup
First, find the .env file containing LANGSMITH_API_KEY:
find . -name ".env" -type f 2>/dev/null | head -5Troubleshooting 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?