v1 · design partnersoc · console
managed agent + pledge
§ integrations / langgraph

LangGraph · node-level scope enforcement, graph replay.

LangGraph's stateful graphs deserve the same audit posture as their stateless cousins. Console's adapter scope-checks every tool node and emits agent-action envelopes per execution — plus a graph-replay tool that re-derives the full audit trail from the persisted graph state.

· planned· prioritization tied to design-partner demand

What it does

LangGraph composes long-running stateful agents from typed nodes. The adapter touches three places:

  • Tool nodes — scope check before the node runs; envelope emission after. Same agent-action envelope shape as every other adapter.
  • Graph state checkpoints — checkpoint hashes are folded into the audit bundle so a verifier can prove which graph state the agent was operating from when an action fired.
  • Replay tool — given a persisted graph state and the audit bundle, re-derive every action receipt and confirm the bundle's claimed history matches what the graph would have produced.

Why this is harder than a stateless adapter

LangGraph agents persist state across many turns. The compliance question becomes: at what graph state did this agent take this action? The adapter has to bind action envelopes not just to the input arguments but to the graph state hash. This is a real engineering surface, which is why it sits below MCP / Anthropic / OpenAI / Vercel AI in priority order.

Status

Adapter package: planned in oc-packages. Targeted post-Q3 2026 unless a named design partner pulls it forward.

Want this adapter sooner?

Adapter prioritization is design-partner-driven. Tell us your stack, the volume, and the compliance bar — adapters that named partners need move from "planned" to "shipping" inside a quarter.