langsmith-fetch

Name: langsmith-fetch
Availability: InStock
Author: Fancu

Fetch and analyze LangSmith Studio execution traces for LangChain and LangGraph agents.

Updated Dec 11, 2025

Search Tags:#debugging #troubleshooting #langchain #agent #traces #langsmith

Ready to run

npx skills add https://github.com/Fancu1/dotfile --skill langsmith-fetch-fancu1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: langsmith-fetch
Source: https://github.com/Fancu1/dotfile/tree/main/skills/langsmith-fetch
Command: npx skills add https://github.com/Fancu1/dotfile --skill langsmith-fetch-fancu1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers debug LangChain and LangGraph agents by fetching and analyzing execution traces directly from LangSmith Studio, streamlining the process of identifying and resolving issues.

Core Features & Use Cases

Fetch Recent Traces: Quickly review recent agent activity to spot errors or unexpected behavior.
Deep Dive Specific Traces: Investigate individual trace details to understand execution flow, tool calls, and errors.
Export Debug Sessions: Save traces and threads for later analysis or sharing with team members.
Error Detection: Automatically identify and report common error patterns and frequencies.
Use Case: When your LangChain agent is behaving unexpectedly, use this Skill to fetch the last 5 minutes of traces, identify any errors, and pinpoint the exact tool call that failed.

Quick Start

Debug your agent by fetching the last 5 minutes of traces and displaying them in a pretty format.

Frequently Asked Questions about langsmith-fetch

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

FAQPage Schema

How do I debug LangChain agents using LangSmith traces?▼

Fetch and analyze execution traces from LangSmith Studio to debug LangChain agents. This allows you to review recent activity, investigate specific tool calls, and automatically detect common error patterns within your workflows.

What is the best way to troubleshoot LangGraph agent errors?▼

Fetch recent execution traces to troubleshoot LangGraph agent errors and pinpoint exact failed tool calls. You can deep dive into individual trace details to understand the execution flow and export debug sessions for later team analysis.

Do I need a LangSmith API key to fetch execution traces?▼

Yes, fetching execution traces requires a configured LangSmith API key and project environment variables. The langsmith-fetch CLI uses these credentials to securely access and analyze your LangSmith Studio debug data.

Can I export LangSmith debug sessions for later analysis?▼

Yes, you can export debug sessions to save traces and threads for later analysis. This feature allows you to share fetched LangChain and LangGraph agent execution data with team members to collaboratively resolve issues.

Why does fetching LangSmith traces fail during agent debugging?▼

Fetching LangSmith traces fails if required environment variables are missing. You must ensure both the LangSmith API key and project environment variables are correctly configured before running the langsmith-fetch CLI to retrieve execution data.