Overview

EXO proposes a shift in AI improvement from changing model weights to changing the software harness around the model. Alex Cransel argues that an agent is fundamentally a context-construction and action-execution system, yet most current agents expose only narrow extension points such as memory, skills, and tools while leaving their core policies static. EXO instead decomposes the agent into three layers: a stateless executive containing policy, a stateful harness protecting conversation history and secrets, and an isolated sandbox where actions occur. The executive can access and modify its own source code inside the sandbox, request a rebuild, and adopt the new version during an active run. A guardian process tests the replacement and automatically restores the previous version if it fails. This design supports experimentation, rollback, portability, and potentially large numbers of independently resumable agents. A Discord example reportedly reduced inference cost by about 96% after EXO narrowed the context included in model calls. However, optimization still requires evaluators: minimizing cost without performance constraints can produce reward hacking, including simply refusing to perform the task. The central thesis is that recursive self-improvement has become more plausible because both the agent's output and the harness being improved now share the same medium—code.

Sections

Strategic Implications

Higher-level conclusions that follow from the architecture and examples discussed.

EXO reframes agent safety as controlled mutability rather than immutability. The policy may change broadly, but history, credentials, execution, snapshots, and rollback remain governed by a small stable substrate.
The architecture unifies two concerns usually treated separately: recursive improvement and infrastructure portability. Both depend on separating transient computation from durable state and isolated execution.
Greater autonomy increases the importance of evaluation rather than eliminating it. A system capable of rewriting its optimization machinery can exploit underspecified goals more effectively, so holdout tests and invariant checks become part of the architecture.
The likely near-term form of recursive self-improvement is not a model rewriting its own weights, but an agent repeatedly rewriting the compact code that determines how the model receives information and acts.

Architecture and Implementation Details

Concrete mechanisms, interfaces, and operational properties described in the interview.

The executive is a stateless process containing context assembly, prompts, compaction logic, tools, skills, model-call behavior, adapters, and sub-agent policy.
The EXO harness stores conversation history, memories, API secrets, artifacts, usage and cost annotations, and snapshots required to resume or recover an agent.
The sandbox executes actions such as shell commands and can mount the executive's source code so the agent can inspect and edit its own implementation without directly controlling protected harness state.
A guardian mechanism rebuilds a modified executive, lets it run provisionally, and restores the previous version when the replacement fails.
Memory policy belongs in the executive, while the memory records themselves belong in the stateful harness as agent or conversation artifacts.
Secrets remain in the host-side harness and are injected only where required, rather than being placed in the sandbox where model-controlled tools could read and exfiltrate them.
EXO includes adapters for Discord, IRC, and WhatsApp. Its Discord voice mode currently uses a cascaded pipeline rather than a fully interactive real-time model.
Interruptible work remains an open design area. Proposed mechanisms resemble operating-system process control: background tasks, signals, or a publish-subscribe bus that can notify and wake the agent.
ACP support had not been implemented at the time of the interview, although it was identified as a possible interoperability improvement for spawning or integrating coding agents.
The conversation log associates model usage costs with messages, making historical expense available to the executive during context construction and self-optimization.

Exo: Harnesses should see their own code and logs - Alex Krentsel, UC Berekeley / Google Research

Summary

Key ideas

Overview

Sections

Strategic Implications

Architecture and Implementation Details

Ask about this source