langsmith-fetch

Fetch and analyze LangSmith execution traces to debug LangChain and LangGraph agents.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Cramer-69/skills-repository-3af2d1c7 --skill langsmith-fetch-cramer-69
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/Cramer-69/skills-repository-3af2d1c7/tree/main/packages/awesome-claude-skills/langsmith-fetch
Command: npx skills add https://github.com/Cramer-69/skills-repository-3af2d1c7 --skill langsmith-fetch-cramer-69

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires langsmith-fetch.

What problem does it solve? Debugging LangChain and LangGraph agents requires digging through LangSmith Studio manually to find traces, errors, and tool call failures. This Skill brings trace fetching and analysis directly into the terminal so you can diagnose agent behavior, errors, memory operations, and performance without leaving your workflow. ## Core Features & Use Cases - Recent Trace Debugging: Fetch traces from the last N minutes and get a structured report of successes, failures, tool calls, durations, and token usage. - Deep Trace Analysis: Investigate a specific trace ID to see the full execution flow, identify the exact failure point, and receive root cause analysis with suggested fixes. - Error Detection & Session Export: Scan recent traces for error patterns and export organized debug sessions with traces and threads for sharing or archiving. - Use Case: Your agent suddenly stops responding. Ask the assistant to check recent traces; it runs langsmith-fetch, finds a Neo4j connection timeout in the failing trace, and recommends adding retry logic. ## Quick Start Ask the assistant to debug your agent by fetching and analyzing the LangSmith traces from the last five minutes.

Frequently Asked Questions about langsmith-fetch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a LangChain agent using LangSmith traces?▼

Run langsmith-fetch traces with a time filter like --last-n-minutes 5 to pull recent executions, then review errors, tool calls, durations, and token usage. For a specific failure, fetch the trace by ID in JSON format for full execution flow analysis.

How to fetch LangSmith traces from the command line?▼

Install the CLI with pip install langsmith-fetch, set LANGSMITH_API_KEY and LANGSMITH_PROJECT environment variables, then run langsmith-fetch traces with options like --limit, --format pretty, or --include-metadata.

Why does langsmith-fetch return no traces found?▼

No traces usually means no agent activity in the timeframe, tracing is disabled, or the project name is wrong. Verify LANGCHAIN_TRACING_V2=true is set, check your environment variables, and try a longer timeframe like --last-n-minutes 1440.

Can I export LangSmith debug sessions to share with my team?▼

Yes, run langsmith-fetch traces with an output directory to export traces with metadata, and use langsmith-fetch threads to export conversations. Organize exports into timestamped session folders for archiving or sharing.

What output formats does langsmith-fetch support?▼

The CLI supports three formats: pretty for human-readable inspection, json for detailed parsing and analysis, and raw for piping into other commands like grep to search for errors.