OpenFang

OpenFang is where agent work actually runs. It is a native Rust daemon that hosts the agents, aggregates the tool servers, holds the messaging channel adapters and gives agents access to models. As of 27 October 2026 it is running version 0.6.9 with 43 agents.

The sandbox, and what actually uses it

OpenFang contains a WebAssembly sandbox with fuel metering, epoch interruption and a watchdog that enforces a wall-clock limit. Fuel is the important idea: a runaway module burns its allowance and halts, rather than consuming the host.

• ·Scoped tools — an agent definition names which tools it can reach
• ·Timeouts — subprocess agents are bounded by a timeout and a heartbeat
• ·Local records — sessions and an audit trail are kept on the machine that runs the daemon

Aggregating tools

OpenFang is also the hub that tool servers register into. Its configuration lists 43 of them — 42 spoken to over standard input and output, one over a streaming connection — covering containers, system and security proofs of concept, code search, the Brain itself and individual spaces. An agent definition names which of those it can reach.

In practice many of the generated space agents are bound only to memory tools, and work in those spaces is executed by the Brain’s own executors rather than by the agent. Scoping is real where it is configured; it is not yet configured everywhere.

Transports differ by direction: the Brain reaches OpenFang over HTTP, OpenFang reaches tool servers over standard input and output, and results can stream back over a server-sent event connection.

Channels

The channel adapters live here too: 42 of them in the code, of which one is configured: Telegram, which OpenFang both receives and answers. WhatsApp runs through OpenClaw, a separate messaging gateway. See Channels for the full picture.

Model access

Model calls go through a provider layer rather than being pinned to one vendor. The built-in catalogue knows 42 providers and 205 models; this site previously said 28 and 130+, which was out of date in the other direction. A local runner is available for work that should not leave the machine.

In practice almost everything takes one route: the default model is Claude through the Claude Code command line, and 37 of the 43 agents use it. Switching is a configuration change, but today an outage at that one provider would affect most agents. We no longer claim otherwise.