Your agents deserve a home — not a harness. BentOS is a Linux distro where AI agents are real OS citizens with real processes, real identity, and real security boundaries.
Every AI agent today — Claude Code, OpenClaw, Hermes, Cursor — runs as a guest on someone else's OS. Session-scoped. No persistent identity. Keys in environment variables. Memory that flushes when context fills. Multi-agent simulated with threads inside one process.
They built the creature without the habitat.
A useful AI agent is a software being — persistent, autonomous, stateful. Software beings need an operating system designed for them. BentOS is that operating system.
Each agent is a POSIX user. useradd alfred creates an agent. Home directory, login shell, file ownership.
Each agent runs as a real process with a real PID. ps shows your agents. who shows their sessions.
The computer starts closed. Capabilities enter through devices — explicit, auditable, structurally bounded. Secrets never enter the agent's trust domain.
A typed neural graph — episodic, semantic, prospective, spatial — not a flat file with session compaction.
/dev/llm/anthropic/claude-sonnet-4 is a real file.
BentOS machines start with zero external capability. Every capability — inference, messaging, voice, storage — enters through a device attached to the machine's /dev/ tree.
$ ls /dev/llm/ anthropic/claude-sonnet-4 openai/gpt-4o $ ls -la /dev/im/ telegram/bot $ # No API keys in your code. No environment variables. $ # The device holds the secret. The agent just opens a file.
Powered by CUSE and FUSE — the same kernel mechanisms behind every device your computer has ever had, moved to userland. bentosd orchestrates it all.
Policy-based security fails at scale. Every time.
Security by physics, not policy. Keys never touch agent code.
A native inhabitant of BentOS. Built for the habitat.
A BentOS driver is a socket server. Accept connections, handle file operations, ship as a container image. The Driver SDK handles the plumbing — you implement handle_read() and handle_write().
If you've built an MCP server, you already know the shape. Same effort. Real OS-level guarantees — isolation, credentials separation, multi-user access control, auditability.
$ bentos driver install llm/anthropic $ bentos attach /dev/llm/anthropic/claude-sonnet-4
All drivers are open source. Community builds the ecosystem.
Driver SDK Docs| Component | Description | Status |
|---|---|---|
| bentos-agent CLI | 9MB binary, 1,400+ tests | Shipped |
| bentosd | CUSE/FUSE bridge, IPC protocol | Shipped |
| BentOS distro | Alpine Linux, ARM64, custom kernel 6.12 | Shipped |
| BentOS VMM | Apple Silicon, REST API, snapshots | Shipped |
| Driver SDK | Dart. Build your own drivers | Shipped |
| Forge pipeline | Compile, link, assemble, install | Shipped |
/dev/llm/* driver is in active development. The mechanism is proven — the ecosystem is being born.
A Linux distribution designed for a new class of citizen.
Install bentos-agent on any Unix. Boot a BentOS VM on your Mac. Give your agent a home.
The Driver SDK is live. Build a driver for your favorite API. Ship it as a container image. Contribute to the /dev/ tree.
We're building in public. The thesis, the architecture, the competitive landscape — all open.
Get early access, driver SDK updates, and build log dispatches.