Doesn't LangSmith already do clustering with Insights Agent?

Yes. The wedge isn't whether clustering exists — it's the shape. Insights Agent clusters traces in response to a natural-language prompt, surfacing patterns the user asked about. Moda runs a fixed behavioral taxonomy across the population automatically on ingest, without prompting, and tags each conversation against the same categories every time.

How does Moda compare to the LangSmith Engine?

LangSmith Engine (public beta from May 2026) clusters explicit errors, evaluator failures, and negative feedback into named issues, runs RCA against your connected code repo, and proposes PRs and eval datasets. Moda focuses on the conversation-semantic layer rather than code RCA — named behavioral failures, frustration trajectories, and agent counterfactuals derived from the conversation itself, not the repo.

Can Moda and LangSmith coexist?

Yes. Many teams keep LangSmith for trace-level debugging and prompt experimentation and add Moda for conversation-semantic analytics on top. Both ingest OTLP, so the same span stream can feed both.

Moda vs LangSmith

LangSmith has expanded well beyond tracing. It now ships Insights Agent for auto-clustering of traces, Multi-turn Evals, and the LangSmith Engine — an autonomous issue-detection system that proposes PRs and online evaluators. The wedge against Moda is shape, not feature presence: LangSmith clusters trace summaries on prompt-driven exploration, with the analyses tied closely to the LangChain / LangGraph stack. Moda is self-improvement for AI agents on the harness layer — model-agnostic, with learnings that live in a latent space outside the model weights and apply across whichever model the harness mounts. Every failure and frustration event is attributed to a specific harness component (prompt, tool, workflow, context, memory, eval, or model).

When you want a prescriptive behavioral failure taxonomy applied automatically on ingest, frustration root cause with an agent counterfactual, and a stack that doesn't pull you toward a specific runtime.

Capability	Moda	LangSmith
Trace clustering	Automatic 3-level intent taxonomy on conversation segments, refreshed on ingest with no prompting.	Insights Agent clusters traces from a natural-language prompt; Plus or Enterprise plan.
Behavioral failure taxonomy	Named categories: tool misuse, context loss, agent laziness, hallucination, reasoning loops, goal drift.	Engine clusters errors, evaluator failures, anomalies, and negative feedback into named issues, but the taxonomy is discovered per project, not prescriptive.
Frustration root cause	Trigger turn, trajectory, affected goal, and agent counterfactual on every detected frustration event.	Negative user feedback feeds Engine's issue clustering; no first-class counterfactual framing.
Runtime coupling	Runtime-agnostic; OpenTelemetry / OpenLLMetry ingest from any agent stack.	Framework-agnostic per marketing, but most depth (Fleet, LangGraph Platform, Engine RCA) assumes LangChain or LangGraph.

Book a call Contact