DATABASES Signal 245
Agentic OS lets agents modify a running colony via HTTP mutations without restarting the binary
Developers run agent colonies from a single Rust binary, with each folder getting its own SQLite database and Linux sandbox for isolation.
Because the system’s topology is stored as files, changes can be made with standard tools like diff and git and applied at runtime without rebuilding or restarting. This removes the need for custom agent loops or SDKs, letting agents reshape their own harness while the colony runs. Operators gain auditable, reproducible agent systems that can be inspected and versioned like ordinary source code.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Each entity in the colony corresponds to a folder containing a config.json, a SQLite file, and a sandbox built from Landlock, network namespace, cgroup v2, and seccomp.
Agents and the overall colony are modified by posting a JSON diff to an HTTP endpoint, which validates and applies the change to a ledger without requiring a restart.
The binary ships no agent loop; loops are represented as edges that route messages back into an LLM entity, making the harness itself a mutable file system structure.
THE READ
What the cluster adds up to.
The Agentic OS replaces traditional agent frameworks with a single statically linked Rust binary that reads a directory tree as a running colony. Each folder in the tree becomes an entity, holding its own config.json, a private SQLite database, and a Linux sandbox constructed from Landlock, network namespace, cgroup v2, and seccomp. Message routes are defined by the folder hierarchy, and an LLM call is represented as an edge that routes back into the same entity. Because the binary contains no built-in agent loop, the loop itself is just another file-system edge.
Adopting the system requires running the binary, providing an LLM API key, and cloning the matching template repository. Changes to the colony are made by sending a JSON mutation over HTTP to the binary’s API endpoint; the mutation is validated, appended to a ledger, and applied instantly without restarting the process. Operators can use familiar tools such as ls, grep, diff, and git to inspect and version the colony’s topology since everything is stored as plain files. The only external dependency is the LLM service accessed through the API key.
The approach stops working on systems that lack the required Linux sandbox primitives; Landlock, cgroup v2, network namespaces, or seccomp are not available on macOS, Windows, or older kernels, so the binary cannot enforce per-entity isolation there. Performance is bounded by SQLite’s file-based storage and the overhead of spawning isolated namespaces for each folder, which may become costly with thousands of entities. Debugging agent behavior relies on tracing the HTTP-mutations ledger and the UI, which can be less intuitive than stepping through a conventional agent loop.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER