Integrations
Organized by execution boundary, not by logo wall.
Nondeterminism enters an agent at specific boundaries. Ontral instruments each supported one, records what crossed it, and serves it back on replay.
Model providers
the largest source of nondeterminismOpenAI
core technologyCaptures — Requests, responses, streamed chunks, and tool calls at the client boundary.
Why it matters — Replay serves the recorded response instead of sampling a new one, even after the model version changes.
Anthropic
core technologyCaptures — Messages, streaming, and tool use.
Why it matters — The same guarantee across providers: the output your agent saw is the output replay returns.
Network and APIs
external services change and disappearHTTPX
core technologyCaptures — Sync and async requests, responses, and failures.
Why it matters — The capsule preserves what an API returned at execution time, not what it returns today.
Requests
core technologyCaptures — Request and response pairs, including status and errors.
Why it matters — Legacy call sites become replayable without code changes.
Agent protocols
protocol mutations are real side effectsMCP
core technologyCaptures — Protocol traffic between your agent and MCP servers: calls, results, and attempted mutations.
Why it matters — On replay, MCP responses are served from the capsule and mutations are never re-sent.
Runtime nondeterminism
the runtime itself is an inputtime
core technologyCaptures — Clock reads.
Why it matters — Time-dependent branches replay on the recorded instant.
randomness
core technologyCaptures — Draws and seeds.
Why it matters — Stochastic code paths repeat deterministically.
UUIDs
core technologyCaptures — Generated identifiers.
Why it matters — Downstream references stay stable across replay.
async ordering
core technologyCaptures — Task interleaving as lanes.
Why it matters — Concurrency races replay in recorded order.
thread ordering
core technologyCaptures — Cross-thread sequencing.
Why it matters — Deterministic ordering even under contention.
streaming
core technologyCaptures — Chunk arrival order.
Why it matters — Partial outputs and pacing replay exactly.
Custom boundaries
your stack is part of the executiontool wrappers
core technologyCaptures — Internal functions and proprietary tools wrapped as explicit captured boundaries.
Why it matters — Internal services become replayable.
application metadata
core technologyCaptures — App-defined context attached to the capsule.
Why it matters — Search and slice capsules by what matters to your team.
outcome labels
core technologyCaptures — Optional business outcomes (incorrect refund, resolved).
Why it matters — Curate regression corpora by real-world results.
Agent frameworks
design partnerFrameworks that execute through supported provider, network, protocol, and runtime boundaries may already be capturable without a dedicated adapter. First-class adapters — LangGraph, CrewAI, OpenAI Agents SDK, internal frameworks — are prioritized with design partners.
Need another boundary?
A native extension, an unusual client, an internal protocol — coverage is driven by what early teams actually run.