Agent templates become agents
A Profile is an Agent template — SOUL.md, IDENTITY.md, tools, skills mode, and a default model. Spawning it creates a permanent live Agent.
Bazilion documentation
Bazilion is a personal, open-source, local-first multi-agent runtime built on Pi’s coding agent as its core engine. Pi runs the per-turn loop, stores the JSONL transcript, handles replay and compaction, executes providers and tools, and supplies the coding tools.
Bazilion wraps that engine with a small daemon on your own machine, a workspace
under ~/.bazilion, Agent templates, revisioned Team Templates, Teams, live
communication policy, shared files, memory, and messages — all under your own
control, with your own provider keys.
It is not a hosted platform. It is a daemon, a CLI, and a web UI you run yourself, published under the MIT license.
Bazilion 0.9.0 makes Teams canonical. Profile Groups, Groups, the Harness prototype, and all compatibility APIs/URLs are gone. Read what changed and how to reset an older alpha install.
Getting started Install the daemon, boot it, and finish first-run setup.
Core concepts Agent templates, Team Templates, Teams, policy, approvals, and memory.
Tools & integrations Browser automation, MCP servers, file handling, and built-in tools.
Configuration Providers, secrets, tokens, and the on-disk layout.
How the pieces fit
Section titled “How the pieces fit”Pi runs the agent loop
Bazilion is based on Pi’s coding agent for the session loop, transcript, compaction, provider/tool execution, and coding tools.
One reusable Team roster
A Team Template owns revisioned stable slots and directed communication edges. Spawning a reviewed revision materializes its Agents atomically.
One effective live policy
Every Team owns exactly one revisioned policy. Edges allow directly or hold one typed attempt for approval; a missing edge denies during enforcement.
A mailbox between them
Agents coordinate through a durable mailbox: send_message, read_inbox,
and wait_for_reply in the loop, plus CLI, API, and web surfaces.
Shared memory, indexed
Each Team has one memory rooted at <team>/memory, indexed with qmd
(BM25 over markdown) so every member can search it.