Skip to main content
Runtime Config lets agents declare what capabilities they need — streaming, native hooks, MCP tools — and validates availability at startup.
The user enables runtime configuration on the agent; declared capabilities are validated at startup before the run proceeds.

Quick Start

1

Simple Usage

2

With Preferred Runtime


How It Works


Configuration Options

Full list of options, types, and defaults — RuntimeConfig

Common Patterns

Pattern 1 — Streaming-capable agent

Pattern 2 — MCP-tools agent with strict requirements


Best Practices

Keeping validate_on_creation=True (the default) surfaces capability mismatches immediately when the agent is created, not halfway through a task. This prevents silent degradation.
Set fallback_allowed=True unless your agent strictly requires a specific runtime. Fallback lets the agent work even in environments where the preferred runtime isn’t installed.
Capability names include streaming_deltas, tool_loop, mcp_tools, native_hooks. Use only documented capability names to ensure forward compatibility.

Runtime Capabilities — full capabilities reference

Execution — control iteration limits and budget