The experience
- Conversation and task UI
- Permission prompts
- Session controls
- Streaming presentation
Anvil by Brokk
One agent engine.
Your interface.
Anvil packages model routing, tools, permissions, and durable sessions into one replaceable process. Clients shape the experience; operators choose the executable.
- SwappableProcess, not library
- PortableOne executable
- OpenLGPL-3.0-only
A deliberate boundary
Build the experience. Keep the runtime independent.
ACP keeps the client experience independent from the runtime implementation. Editors and bots stay focused on interaction while Anvil provides consistent execution semantics behind a separate process.
The agent runtime
- Model routing and tool loop
- Permission enforcement
- Sessions and context compaction
- Sandboxing and MCP servers
Runtime capabilities
Serious infrastructure, behind a clean protocol.
01 / ROUTE
Model routing
Connect Codex, Bedrock, hosted providers, or local models through stable wire IDs.
02 / EXTENDTools + MCP
Ship built-in file and shell tools, skills, subagents, and managed MCP servers.
03 / CONTROLPermission gates
Keep attended and unattended workflows explicit at the protocol boundary.
04 / REMEMBERPersistent sessions
Resume work with durable history, context reporting, and automatic compaction.
Replaceable by design
Change the engine without rebuilding the cockpit.
Because Anvil is an ACP subprocess, a client can point at an official release, a locally built fork, or another compatible executable. Runtime and interface can evolve on separate release cycles while the process boundary stays explicit.
Try it in ten minutes
Verify the whole path.
Install a released binary, connect an ACP client, and verify model routing, Bifrost tools, permissions, and session context in one bounded journey.