Skip to main content
Output controls what agents print, how much detail they show, and whether they stream responses in real time.
The user runs the agent; output mode controls how much detail prints or streams during the run.

Quick Start

1

Level 1 — String (preset)

Pick a named output mode — the shortest way to control what the agent prints.
2

Level 2 — Config class (full control)

Use OutputConfig to combine formatting flags like streaming and markdown.

Output Presets

The default is output="silent" — agents return responses without printing anything. This is the fastest mode for programmatic use.

How It Works


Configuration Options

Full list of options, types, and defaults — OutputConfig
The most common options at a glance:

Common Patterns

Pattern 1 — Streaming for real-time UX

Pattern 2 — Save output to file

Pattern 3 — JSON output for pipelines


Best Practices

output="silent" (the default) adds zero overhead and returns the response as a Python string. Use it for APIs, background jobs, and any code that processes the response programmatically.
Set output="verbose" during development to see tool calls, agent reasoning, and formatted output. Switch back to silent before deploying.
Enable OutputConfig(stream=True) for chat interfaces and terminal apps where users expect to see the response appear word by word, not all at once.
Use output_file="path/to/file.md" to automatically save every response — useful for report generation, batch processing, and audit trails.

Caching — avoid redundant LLM calls

Execution — control iteration limits and rate limiting