Ultron’s execution engine is a custom-built sandboxed runtime that runs in isolated cloud environments. It’s what makes long, complex, multi-step tasks possible — not a 3-minute timeout, but a 50-minute window with a full toolchain available from the start.
What the sandbox provides
Tool execution pipeline
Every tool call follows the same pipeline:
Parallel tool execution
When Kimi K2 returns multiple tool calls in a single turn, they execute concurrently. Independent operations don’t wait for each other:
This is what makes research tasks run in minutes instead of sequentially chaining one search after another.
Budget control
Large tool outputs are handled gracefully:
- Results exceeding 30,000 characters are persisted to disk; the file path is returned instead
- The engine tracks token accumulation across all turns
- Compression triggers automatically before context limits are hit
- Sandbox sessions with heavy output (browser screenshots, large scraped pages) manage their own storage
Sandbox vs API mode
Complex multi-step tasks — building a full competitive report, running a lead enrichment batch, generating a content calendar with research — run in sandbox mode to take advantage of the extended runtime.
