LLM provider SDKs
Auto-instrumented provider clients. Initialize Laminar and every model call is traced.OpenAI
Trace the OpenAI SDK in JavaScript and Python.
Anthropic
Trace the Anthropic SDK in JavaScript and Python.
Gemini
Trace the Google Gemini SDK.
Cohere
Trace the Cohere SDK.
LiteLLM
Trace calls routed through LiteLLM.
OpenRouter
Trace any model called through OpenRouter.
Agent frameworks
Multi-step agents, tool calls, and subagents render as a transcript instead of a raw span tree.Vercel AI SDK
Trace
generateText and streamText in Next.js and Node.js.LangChain / LangGraph
Trace LangChain chains and LangGraph graphs.
deepagents
Trace LangChain deepagents and their subagents.
Mastra
Trace Mastra agents and workflows in TypeScript.
Pydantic AI
Trace Pydantic AI agents and tool calls.
OpenAI Agents SDK
Trace OpenAI Agents, handoffs, and tools.
OpenHands SDK
Trace OpenHands software agents.
Temporal
Trace agent activities across Temporal workflows.
Coding agents
Claude Agent SDK
Trace Claude Agent SDK runs and subagents.
OpenCode
Trace OpenCode coding agent sessions.
Browser and computer-use agents
Browser session recordings sync with the trace: scrub the video and the trace scrolls with it.Browser Use
Trace Browser Use agents with synced session recordings.
Stagehand
Trace Stagehand browser automation.
Skyvern
Trace Skyvern browser agents.
Kernel
Trace computer-using agents running on Kernel.
Playwright
Trace Playwright browser sessions.
Puppeteer
Trace Puppeteer browser sessions.
Don’t see your SDK?
Laminar is OpenTelemetry-native, so it traces any LLM call or function you wrap yourself. Use the@observe decorator or create manual spans, and point any OTel-emitting code at Laminar. See Tracing Structure or jump to observe usage.
Once your traces land
View traces
Laminar extracts inputs, LLM outputs, and tool calls into a transcript view, so you read the conversation instead of a span tree.
Track outcomes with Signals
Define signals in plain language to track the outcomes and failures you care about across every run.
Query across traces
Run read-only SQL over your traces in the editor, the SQL API, the CLI, or the MCP server.
Tracing structure
Use
observe, sessions, metadata, and tags for deeper control over what gets captured.