Docs

​

Changelog

• Platform: The platform changelog lists user-facing product changes by day.
• SDKs: The TypeScript SDK and Python SDK changelogs list changes by version.
• Docs: This page lists documentation changes by day.

​

Reference

• Ingest status: The trace contract says ingest keeps exact OK and ERROR, ignores every other value, and lets a non-empty error force ERROR.

​

Getting started

• Page titles: Page titles name the task. The introduction title is “Production monitoring for AI agents.”

​

Integrations

• LangChain: The LangChain guide documents that an idle open trace is finalized and sent after the open-trace TTL.

​

Guides

• From issue to fix: Turning issues into fixes walks one production issue from the evidence through a code change and a check that it does not recur.

​

Platform

• Issues: The issues and overview pages link that guide.

​

Guides

• Runnable examples: Runnable examples points at one docs-chat agent implemented for each first-party stack, plus a direct SDK path.

​

Integrations

• Wiring: The LangChain, LangGraph, Mastra, OpenAI Agents, and Vercel AI SDK pages show the handler, exporter, or telemetry helper for that example.

​

Tracing

• Cross-process turns: Cross-process turns explains how a host and a sandbox record one trace.
• Fail open: The traces page says automatic SDK delivery catches network errors, and ingest() still raises.

​

Platform

• Product pages: Platform and connection pages match the public product: workspace sequence, ready traces, and the coding-agent setup path.

​

Connections

• Webhooks and MCP: Webhook and MCP pages replace the previous incident and monitor copy.

​

Navigation

• Page menu: Each page can be copied, opened as markdown, sent to the docs MCP, or opened in Cursor or Claude Code.
• Introduction: The introduction screenshot sits under the opening paragraph.

​

Platform

• Platform guides: Pages for overview, concepts, traces, issues, Inspect, artifacts, and analytics describe the dashboard.

​

Connections

• Connections: Pages for overview, Slack, Linear, MCP, and webhooks describe how Lemma connects to your tools.

​

Integrations

• Vercel AI SDK: The integration page says a generation records the provider system when the call sets messages.

​

Navigation

• Setup path: Instrumentation setup is the getting-started path for the SDK. The standalone quickstart and tracing overview pages were folded into that guide.
• Platform group: Platform pages have their own nav group, separate from tracing.

​

Tracing

• Release: Setup explains how to set release, including identifiers produced in CI.

​

Getting started

• Trace quality: Getting started documents the diagnostics skill for reviewing trace quality.

​

Tracing

• Metadata: The context page says any metadata key is searchable.

​

Integrations

• Token usage: LangChain, LangGraph, Mastra, OpenAI Agents, and Vercel AI SDK pages document generation token usage.

​

Tracing

• Release: Setup, the trace contract, and the integration pages document the client release field.

​

Tracing

• Inputs and outputs: Integration pages and the trace contract say prompts, tool payloads, model output, and error messages are always recorded.

​

Reference

• Analytics attributes: Analytics telemetry lists the generation attributes the SDK emits, and the generations page documents them.

​

Tracing

• Tool messages: Tool calls documents userFacingMessage and user_facing_message.

​

Integrations

• Mastra: The Mastra page says the trace name comes from the agent entity.

​

Integrations

• Trace contract: The Vercel AI SDK, OpenAI Agents, LangChain, and LangGraph pages describe current-turn input and output, thread and user, and nested tool calls.

​

Integrations

• Mastra: A Mastra page documents LemmaMastraExporter.

​

Tracing

• One delivery: Traces, context, and troubleshooting say each execution sends one complete trace. TraceHandle.flush is no longer documented.
• Second delivery: Troubleshooting describes a root whose input and output are null after a second delivery.

​

Guides

• Quality guide: Building high-quality traces lives under Guides.

​

Reference

• Trace contract: The trace contract specifies what clients send and which fields unlock product behavior. The undocumented environment field is gone from the contract.

​

Guides

• Quality: A guide covers what makes a trace useful to Lemma.
• Migrations: Guides cover moving from Raindrop, Langfuse, and OpenTelemetry.

​

Tracing

• Debug verify: The debug mode page says verification reads per-trace ingest status.

​

Tracing

• Debug mode: The debug mode page documents delivery logs and the smoke test.
• Debug flag: LEMMA_DEBUG=1 is documented as the preferred value. true still works.

​

Getting started

• Skill install: Getting started shortens the tracing skill install path.

​

Getting started

• Public docs: The docs site opens with an introduction and the tracing skill install path.

​

Tracing

• Instrumentation: Tracing pages cover setup, traces, generations, tool calls, spans, and context.

​

Integrations

• First-party stacks: Pages cover LangChain, OpenAI Agents, and the Vercel AI SDK.