The Flywheel,
native on Omarchy.
The same one-liner as on Ubuntu. The installer detects Arch and Omarchy, installs the system layer with pacman, keeps your starship prompt, and skips oh-my-zsh. All 74 modules, 6 agent CLIs, and the full tool stack.
curl -fsSL https://agent-flywheel.com/install | bashRun it as your own user; the installer calls sudo only for the steps that need it.
what arch users get
Native on Arch
pacman for the system layer
Base packages, CLI tools, Go, PostgreSQL, Vault, and Tailscale all come from the official Arch repos. The installer never adds apt or a third-party repo to your machine.
Your prompt stays yours
ACFS never replaces an existing ~/.zshrc; it appends one guarded loader line. If you use starship, the new shell initialises it and your starship.toml is left where it was.
oh-my-zsh & p10k skipped
On Arch the installer skips oh-my-zsh, powerlevel10k, and their plugins. You get zsh with history, completion, and the ACFS aliases, with nothing else layered onto your shell.
Doctor knows the difference
acfs doctor knows the Arch layout. The oh-my-zsh checks report SKIP rather than FAIL, so a clean Omarchy install passes instead of showing four false failures.
Prebuilt binaries, no source builds
The flywheel tools install from their checksum-verified upstream installers, which ship prebuilt Linux binaries. You get the same tools and versions as on Ubuntu without compiling anything.
Idempotent resume
If the install is interrupted, re-run the same command. Phases are checkpointed in ~/.acfs/state.json, and tools that are already installed are skipped.
the details
What changes on Arch
apt → pacman package sets
Each Ubuntu package batch has a hand-checked Arch equivalent (bind for dnsutils, github-cli for gh, fd for fd-find). The package database is synced once before any installs.
sudoers drop-in 90-acfs
Vibe mode writes passwordless sudo as a single drop-in file, validated with visudo. /etc/sudoers itself is never edited, so deleting the file reverts it.
wheel group, not a sudo group
Your user is added to wheel, as Arch expects. The installer configures the account you run it as and does not create an ubuntu user.
Postgres via pacman + initdb
Installed from the official repo, cluster initialised with initdb (UTF-8), service enabled with systemd. The PGDG apt repo is not used.
$ acfs doctor
- ✓ PASSzsh installed
- ○ SKIPOh My ZshNote: not used on Arch-family; existing prompt preserved
- ○ SKIPPowerlevel10kNote: not used on Arch-family
- ○ SKIPzsh-autosuggestionsNote: not used on Arch-family
- ○ SKIPzsh-syntax-highlightingNote: not used on Arch-family
- ✓ PASSacfs.zshrc sourced
- ✓ PASSbun 1.3.x
- ✓ PASSuv 0.9.x
- ✓ PASScargo 1.9x
- ✓ PASSgo 1.2x (pacman)
- ✓ PASSclaude / codex / agy
- ✓ PASSntm · am · bv · br · cass · cm · dcg · ru …
Summary: 8 passed, 0 warnings, 0 failed, 4 skipped
Representative output; versions and the exact check list depend on your install.
Full detail in the README's Omarchy (Arch) support section.
one system, not a pile of binaries
How the tools feed each other
The inner ring is the loop a working session runs through: ntm spawns the agents, am lets them message each other and reserve files, bv picks the next task from the Beads graph, ubs scans the diff before commit, and cass and cm turn every finished session into searchable history and procedural memory for the next one.
The outer ring is the support crew: guards (dcg, slb), repo sync (ru), account switching (caam), and the rest. Builds go through rch, which ships cargo work to remote workers so twenty agents compiling at once do not flatten the box. Each tool exists because running many agents at once exposed a specific problem.
Every line in the diagram is a real integration: shared IDs, MCP calls, or files one tool writes and another reads. Hover a node to see its connections.
Tap or hover a tool to see its connections
the storm, indexed
Every tool in the vortex
Every name in the storm above is a binary on your PATH after install. ACFS leaves your desktop, shell, and prompt alone; the first two tiers are the flywheel stack it installs, and the third is the agents, runtimes, and CLIs it sets up around them.
- CornerstoneThe tools the flywheel turns on. Learn these first.
- FlywheelThe rest of the Agent Flywheel stack; each one plugs into the cornerstones.
- Third-partyAgents, runtimes, and CLIs installed around the stack. On Arch, most come from pacman; optional modules are marked.
Cornerstone
10 toolsntmNamed Tmux Manager: spawn and monitor agent sessionsamMCP Agent Mail (Rust rewrite): messaging and file reservations between agentsbrbeads_rust: local-first issue tracking for agentsbvBeads Viewer: dependency-graph triage for taskscassCoding Agent Session Search (CASS): every past agent session, searchablecmCASS Memory System: procedural memory for agentsubsUltimate Bug Scanner: static checks before every commitdcgDestructive Command Guard: blocks rm -rf and git reset --hard in agentsruRepo Updater: multi-repo sync and AI-driven commitsrchRemote Compilation Helper: offload cargo builds to a worker fleet
Flywheel
28 toolsslbSimultaneous Launch Button: two-person rule for dangerous commandscaamCoding Agent Account Manager: switch agent accounts in under 100msfsfsFrankenSearch: hybrid lexical and semantic code searcheeEidetic Engine: durable local memory for agentsptProcess Triage: find and kill runaway processesmsMeta Skill: skill management with MCP integrationcasrCross-Agent Session Resumer: resume a Claude session in Codex, or vice versadsrDoodlestein Self-Releaser: local cross-platform release buildsasbAgent Settings Backup: git-versioned agent configspcrPost-Compact Reminder: re-inject instructions after context compactionpfrPower Failure Resumer: restart agent sessions after a rebootsbhStorage Ballast Helper: reserve disk to survive full-disk eventssysmoniSystem Resource Protection: deprioritizes background processes so the workstation stays responsivefmdFranken Markdown: one binary turns Markdown into HTML and PDFpiPi Agent: single-binary coding agent with local model supportgiilGet Image from Internet Link: pull iCloud and Dropbox shares into the terminalcsctfChat Shared Conversation to File: archive AI chat share links as MarkdownxfX Archive Search: fast search over X/Twitter data archivestoonToken-Optimized Notation: compress source code for LLM contextranoNetwork Observer: monitor AI CLI network trafficmdwbMarkdown Web Browser: fetch pages as Markdown for agentss2pSource to Prompt TUI: pack a repo into one promptaprAutomated Plan Reviser Pro: multi-pass plan refinementjfpJeffreysPrompts CLI: curated prompt librarybrennerBrenner Bot: hypothesis-driven research sessionsaadcASCII Art Diagram Corrector: fix malformed ASCII diagrams from AI outputcautCoding Agent Usage Tracker: LLM provider usage and costs across agentsrust_proxyRust Proxy: transparent proxy routing for network debugging
Third-party
17 toolsclaudeClaude Code (Anthropic)codexCodex CLI (OpenAI)agyAntigravity CLI (Google)opencodeOpenCode agent CLI (optional module)ompoh-my-pi: a coding agent with the IDE wired in (optional module)grokGrok CLI (xAI, optional module)bunJavaScript runtime and package manageruvPython package managercargoRust toolchain (rustup)goGo toolchain (pacman)ghGitHub CLI (pacman)tmuxTerminal multiplexer (pacman)rgripgrep (pacman)fzfFuzzy finder (pacman)atuinShell history with searchzoxideSmarter cdgumGlamorous shell scripts (pacman)
Want the long version of each one? Read the TL;DR
Get on the Flywheel!
One command sets up your Arch or Omarchy machine for agentic coding. Re-run it any time; it skips whatever is already installed.
curl -fsSL https://agent-flywheel.com/install | bash