Integrations

Integrations

Framework adapters, managed runtime integrations, and shared primitives for capturing agent evidence and enabling replay-aware analysis.

Integrations map framework-specific model, tool, state, and hook surfaces onto the isplay evidence model. Choose the integration that sees the earliest safe boundary in your runtime.

Integration Selection

If your runtime...Prefer
Is custom and you own the model/tool calls@isplay/adapter-kit
Uses Vercel AI SDK@isplay/adapter-ai-sdk
Uses Mastra agents or workflows@isplay/adapter-mastra plus explicit SDK calls
Uses LangGraph nodes or streams@isplay/adapter-langgraph
Runs inside Codex@isplay/adapter-codex
Runs inside Claude Code@isplay/adapter-claude-code
Runs inside OpenClaw plugin hooks@isplay/adapter-openclaw

Capability Matrix

IntegrationContext inventoryModel captureTool captureFixture replayCheckpoints
Kitexplicitexplicitexplicitapp-ownedexplicit
AI SDKrequest-derived plus annotationsmiddlewaretool execute wrappersapp-ownedSDK checkpoints
Mastraannotations and snapshotsmanualhelper methodsapp-ownedworkflow snapshots
LangGraphnode state, messages, stream updatesmodel wrapperstream/tool wrapperapp-ownedbefore/after nodes
Codexhooks and JSONLJSONL/proxy-dependenthooks and JSONLmanaged, often post-resultapp/worktree-dependent
Claude Codehooks and stream-jsonobservability-orientedhooksmanaged, post-tool contextapp/worktree-dependent
OpenClawnative hooksnative input/output hooksnative before/after tool hooksnative synthetic when supportedsession/checkpoint hooks

Shared Advice

  • Pass client or projectId into adapters explicitly.
  • Put capture inside a run context unless the adapter uses RuntimeRunRegistry.
  • Capture tool schemas and side-effect classes, not just tool outputs.
  • Drain streams so capture can finish model calls.
  • Do not claim deterministic replay for an adapter that only observes events after execution.

On this page