enjoy-the-silence
It stands itself up on a machine that isn't yours: a rented VPS, a spare box, a throwaway container. Your laptop is only a window. State the work in one sentence, then watch the floor live or walk away. The run is the same either way.
Inside that box the crew runs at full power because the machine is built to be thrown away: work order → plan → red-teams → build → review → visual approval → delivery → run report.
⚙Watch it work
Three short clips, filmed against the real control room with mocked model calls (no tokens spent). Station behaviour mirrors real factory runs. CI re-records them on every relevant push — the latest filming is always in the Record demos workflow artifacts.
1 · Create a feature from one sentence
The owner states the work; a planner drafts the plan, two red-teams attack it, a builder implements it in an isolated worktree, two reviewers check the diff, and it lands.
2 · Model presets: who builds, who checks
Settings groups models into unlimited presets. With muse and agy installed, the factory suggests cross-family presets — Gemini writes the code, Muse checks it. Each group has switch rules: quota, failure rate, or provider errors.
3 · Quota failover: swap the whole preset
The builder's preset runs on the Antigravity subscription, whose quota is exhausted (429). The factory marks that provider spent, swaps the entire active preset to the muse preset, and the feature lands.
Full walkthrough
The longer tour of the control room: floor, work orders, station detail, governance stop-points, run report.
⚙How a feature flows
⚙Ways to run it — pick where the mill stands
The wizard only ever generates configuration; applying it and logging in stay yours. You don't need to own hardware.
A · Silent PC: a rented box on Hetzner (recommended)
Spin up a 32 GB RAM VPS (e.g. a Hetzner Cloud or dedicated AX box), point the wizard at the cloud target, and the factory lives there — your laptop stays off and silent while the work is done. 32 GB comfortably funds a dozen parallel tasks plus the OS reserve; reach the control room over your VPN/tailnet or an SSH tunnel, and turn the login key (model auth) once, by hand.
bun run wizard -- --target cloud --out ./my-env # generates OpenTofu + factory config, never applies # apply on the box, start the dashboard, state tasks from anywhere
B · A spare box at home
An old mini-PC or retired laptop on your LAN becomes the mill floor. Run the wizard on that machine so it can tailor the config to the box itself.
bun run wizard -- --target clean --out ./my-env
C · Throwaway evaluation on your current machine
An Incus container you can delete afterwards — the honest way to watch a full unattended run before committing to anything.
bun run wizard -- --target incus --out ./my-env bun run demo # offline rehearsal of the whole pipeline, planted fault included
D · You already run NixOS
Take the factory as a module into your existing configuration; rollback is your previous NixOS generation.
bun run wizard -- --target existing --out ./my-env
⚙Why a factory instead of just a coding agent
- Agent- and model-agnostic. Stations are job cards, not a vendor's chat. Organise runners as ordered presets — one family writes, another checks — and when quota or a critical failure rate fires, the factory auto-selects the next preset. Trying a new agent is a settings change, not a migration.
- Workflows bigger than a prompt. A persisted pipeline with gates that can stop the line — plan approval, decisions conflicts, craft vetoes, screenshot approval — across sessions, restarts and parallel tasks.
- Isolated from your system. A reproducible NixOS base the wizard only generates, per-task worktrees, rollback via git revert or a previous OS generation. Because the box is built to be thrown away, the crew inside it runs at full power, no permission prompts, no babysitting. Nothing on the machine is precious, so nothing is protected by slowing the agents down. The gates decide what leaves the box and lands in your real projects.
- Context in files, not chats. Plans, decisions, red-team arguments, deliveries and token consumption live on disk. Kill any session; the next agent resumes from the record.
- Proof, not vibes. Done means the project's own checks passed — 386 automated tests in the verify suite today, reproducible by cloning and running
bun run verify— and for UI, that your eyes approved the screenshot diff. Screenshots live outside git, never committed.
⚙Start yours
git clone https://github.com/Dmytroportianka/enjoy-the-silence cd enjoy-the-silence bun install bun run wizard -- --target incus --brain muse --out ./my-env bun run dashboard # control room
Or paste the prompt in START_WITH_MUSE.md into a Muse session opened in the repo and let it commission the factory — it stops at every step that must stay human.