v0.1 · prototype

Chaossynergy

The OS is the agent interface.

immutable · agent-native · atomic

latest

Read the full story in Chapter 25 of The Philosophical Developer . The philosophy, the architecture decisions, and what comes next.

philosophy

Chaossynergy is an operating system shaped around one purpose: being the substrate that an AI agent lives in and operates through. Not Linux with an assistant installed. Not a CLI tool that talks to an LLM. An entire OS designed for human-AI collaboration.

The name is a contradiction made real. Chaos — the unpredictable, emergent behaviour of multiple agents, containers, and runtimes working in parallel. Synergy — the whole working together as one system, directed by a single conductor.

The substrate is sacred and dumb

Immutable, atomic, minimal. An appliance that exists only to boot the agent. If the agent breaks, delete the container. The host is untouched.

The agent is disposable

Hermes runs in a distrobox container with its own state. Break it? distrobox rm agent. Fresh runtime in 30 seconds.

Safety by construction

bootc provides atomic OS updates at the kernel level. Distrobox isolates the agent at the user level. One layer can fail and the other still holds.

architecture

Four integrated layers, one unified system. Everything the agent needs lives in a disposable distrobox container. The host OS stays minimal.

L0

Host OS (minimal)

Bluefin LTS (CentOS Stream 10) — just herdr, systemd services, GDM auto-login. No browsers. No Node.js. No Hermes. An appliance.

L1

herdr Multiplexer

Fullscreen Ptyxis terminal on boot. Agent-aware sidebar. Every shell auto-enters the distrobox via the chaossynergy-shell wrapper.

L2

Agent Container

Fedora distrobox with Chromium, Node.js, Hermes, pass. Shared home directory so the agent sees your projects and configs.

L3

Recovery Shell

Shift-at-boot emergency root shell. If the agent or multiplexer fails, you always have a way back in.

data flow (planned)
Hermes ◄──► npx @browsermcp/mcp ──WebSocket──► Chromium Extension
  │                                               │
  └──► pass show hermes/openrouter      browserpass fills login forms
       ~/.password-store/ ◄──── browserpass-native ◄──── browserpass ext

quick start

~ $
$ just build
$ just build-qcow2
$ just run-vm-qcow2

Or deploy from the registry:

~ $
$ sudo bootc switch ghcr.io/dark5un/chaossynergy:latest
$ sudo systemctl reboot

On first boot, press n in herdr to create a workspace, then type distrobox enter agent.

architecture decisions

roadmap

Chaossynergy is in alpha. The foundation works. It boots, builds, and connects. Here is where we are heading:

done

Alpha prototype

Bootable image boots into GNOME, launches herdr, connects to agent container. CI builds pass. Images published to GHCR.

next

Bootable disk images

qcow2 and ISO builds via bootc-image-builder. Install on bare metal or VM without needing an existing Bluefin install.

next

Browser MCP + pass

Wire Browser MCP Chrome extension to Hermes. Integrate browserpass for shared secrets between the agent and the browser.

later

Multi-agent architecture

Multiple distrobox containers (Hermes, Claude Code, Codex) orchestrated through herdr. Agents spawning agents via socket API.

later

Voice dictation

Whisper.cpp push-to-talk. Press a key, speak, text appears in the active application. Fully local, no cloud.

later

Presence-aware pairing

Opt-in camera sensing. Tiered: presence safety gate, gaze attention awareness, expression interaction dynamics. Fully local, no recording, no cloud.

links

see it in action

First boot
First boot — pulling the agent container
Hermes setup
Hermes wizard — configuring a local LLM
Setup complete
Setup complete — ready to go

built with

Chaossynergy stands on the shoulders of giants. Our thanks to: