langsmith-fetch

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/javierbadapalacio6-beep/TACTIUM --skill langsmith-fetch-javierbadapalacio6-beep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/javierbadapalacio6-beep/TACTIUM/tree/main/TACTIUM/.agents/skills/langsmith-fetch
Command: npx skills add https://github.com/javierbadapalacio6-beep/TACTIUM --skill langsmith-fetch-javierbadapalacio6-beep

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 details. This Skill brings trace fetching and analysis directly into your terminal workflow so you can diagnose agent failures, memory issues, and performance bottlenecks without leaving your development environment. ## Core Features & Use Cases - Recent Trace Debugging: Fetch traces from the last N minutes and get a structured report of errors, tool calls, execution times, 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 across agents and tools, or export full debug sessions with traces and threads for sharing and archiving. - Use Case: Your agent suddenly stops responding. Run a quick trace fetch for the last 5 minutes, discover a Neo4j connection timeout in the search_nodes tool, and get a recommendation to add retry logic. ## Quick Start Ask the AI to debug your agent by fetching the last 5 minutes of LangSmith traces and summarizing any errors, tool calls, and token usage.

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, and durations. For a specific failure, fetch the individual trace by ID in JSON format to see the full execution flow and failure point.

How do I find errors in recent LangSmith traces?▼

Fetch recent traces in JSON or raw format and search for error, failed, or exception keywords. The Skill's error detection workflow groups failures by type, agent, and tool so you can spot recurring patterns like connection timeouts or rate limits.

What environment variables does langsmith-fetch require?▼

It requires LANGSMITH_API_KEY for authentication and LANGSMITH_PROJECT to target the correct project. Set both with export commands in your shell, and verify them with echo before running trace commands.

Why does langsmith-fetch return no traces found?▼

No traces usually means no agent activity in the timeframe, tracing disabled, or a wrong project name. Try a longer window, confirm LANGCHAIN_TRACING_V2=true is set in your agent code, and verify LANGSMITH_PROJECT matches your LangSmith project.

Can I export LangSmith traces for offline analysis?▼

Yes, use the traces command with an output directory to export traces with metadata, and the threads command to export conversations. This creates an organized session folder you can share with teammates or analyze with external tools.