Flowlines
Start free

Integrations

Connect your production traces to Flowlines.

Bring OpenTelemetry, Langfuse, or LangSmith. Keep your current provider. MCP servers use a separate standards-based instrumentation path.

Book a setup meeting →Compare connection paths →

Application agent traces

Keep your telemetry stack. Add cross-session analysis.

If your traces already contain enough session, user, call, and outcome context, Flowlines can analyze them without a proprietary application SDK.

Connection studio

Choose your source. See the exact path.

Switch between the supported production paths and see what moves, what stays, and how Flowlines fits.

Connection studioChoose a source
No trace migration required
Live push

Send the traces you already emit.

Route standard OTLP traces to Flowlines while your current trace store stays in place.

  • OTLP/JSON or protobuf
  • Namespace API key
  • Existing semantic attributes
Book a setup meeting →
01Your agent02OTLP exporter03Flowlines analysisOTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://api.flowlines.ai/v1/tracesIllustrative connection path

MCP server setup

Add MCP observability from Claude Code or Codex.

The Flowlines skill reviews the server, asks what may be exported, then adds canonical tool-call telemetry with AGNTCY Observe or OpenTelemetry.

Choose your coding agent

Open the setup where you already work.

Open Claude CodeInstrumentation prompt includedOpen CodexInstrumentation prompt included
One click opens a guided instrumentation task. You approve every change.
01Review the server

The skill finds the framework, tool handlers, and existing telemetry.

02Set the boundary

You approve which arguments, results, and identities may leave the server.

03Add telemetry

The skill makes the smallest compatible OpenTelemetry integration.

04Verify a journey

Run one tool flow and confirm its intent, calls, and outcome in Flowlines.

Prefer the terminal?Show one-line commands
Claude Codeclaude plugin marketplace add flowlines-ai/plugins && claude plugin install flowlines@flowlines
Codexcodex plugin marketplace add flowlines-ai/plugins && codex plugin add flowlines@flowlines

Then use /flowlines:flowlines-mcp-observability in Claude Code or $flowlines-mcp-observability in Codex. Source and release history are in the official Flowlines plugin repository ↗.

How the layers fit

Debug individual runs. Monitor repeated behavior.

Langfuse and LangSmith remain useful for trace storage and call-level debugging. Flowlines adds cross-session behavioral analysis, user and intent rollups, recurring issue detection, and production outcomes.

Provider connections can remain read-only because Flowlines is the analysis layer.

Start free

Connect the traces already running in production.

Install with Claude CodeMCP setup prompt includedInstall with CodexMCP setup prompt included
Free plugin. Hosted service terms are separate.
Prefer a conversation? Book a meeting ›