Using Atoo

Atoo is said “A-two”: your A2, the second engineer at the desk.

Atoo turns an input list and your own written conventions into a complete show setup for a Behringer WING, writes it to the desk, validates every value, and watches the desk for mistakes. A full browser UI is included or use it on the command line.

Start here

In this order, the first time:

Page	For
Why Atoo?	Whether Atoo is worth your time against what you already do
Installing Atoo	Install on a Mac or Linux with uv, step by step, then open atoo ui; Homebrew and pipx, and Windows, too
Try the Demo show	Build, Apply and Watch on a simulated desk, in five minutes
How Atoo works	The three files you write, the plan, and build, verify, apply and watch
Set up Atoo	Your Atoo folder with atoo init, your desk with a2 ping, your presets, and the config file
Setting up an AI provider	The model that writes your plans, and its API key
Build your first show	Your copy of the Demo show: change it with or without a model, apply it, watch it and undo
Patch a show	A change typed in plain English, onto a show already on the desk
Capture a desk you didn’t build	A desk that is already set up, as a show you can watch and edit
The command line	One show from files to desk with atoo commands, then useful things to try

Using Atoo in the browser

Page	For
Build a show	Show bundle files: the input list, your show-specific instructions, the Build plan, and the watch list
Apply a plan to the desk	The four steps: the pre-flight, Preview (the desk as tiles, each tile’s changes in Detail), writing, undo
Watch the desk during a show	Live findings, and setting watch conditions

The files you write

Page	For
Writing an input list	what is plugged in: columns, sockets, stereo pairs
Writing conventions	how you set up a desk, in your own words, and how it is read
Channels that are not on the input list	talkback, playback and the strips you want at every show, asked for in a sentence
Conventions reference	the levels vocabulary, the desk’s eighteen colors, and the resolved file Atoo writes beside yours
Using channel presets	your own .chn presets, and what they are called
Bus presets: mix and FX busses	a mix bus’s compressor, or an FX bus’s reverb or delay, from your own .bus export
Show bundles	one show’s folder, and what each file in it is
Watch conditions	your own alerts for Watch: the Kick stays on LCL 5, the PA never mutes

When something goes wrong

Page	For
Reading findings	what ERROR, WARNING and INFO mean, the verdicts, and the codes
Troubleshooting	can’t reach the desk, a build that fails, a refused plan, the UI not starting
Words Atoo uses	one name for each thing: Choices, Arm, History, the journal, a show bundle
Questions	is it AI slop, will it touch my desk mid-show, what if it goes wrong

From the command line

Page	For
How a show gets built	the stages, which one gates, and resolve
Capturing a desk	capture: a desk or a .snap as a show you can watch, with no model and nothing written
Learning from a batch of builds	lessons: the questions your builds keep asking, as candidate lines for your conventions
Applying a plan	apply: preview, reading the result, flags, exit codes
What a full apply changes on the desk	the reset to initialized, unpatching unbuilt strips, Main routes, talkback, alternate inputs, expansion bays
The journal	what every write leaves behind, and how far back undo reaches
Undoing a write	undo: step back one write, keeping everything changed since
Patching a running show	patch: a typed change onto a desk already in use
Patching from a rebuilt plan	amend, from the command line: the difference between two plans, onto a desk already in use
One plan, two desks	a primary and a backup, or a plan for a different WING
Checking a desk	audit: one read, signal tracing, and checking a desk against its plan
Watching from the command line	watch: the same rules on a loop, reporting what changed
Command reference	every command and flag (generated from the code)
Rules reference	every rule audit and Watch can report (generated from the code)
AI provider reference	Prompt caching on Claude, and what an OpenAI-compatible host is sent
Reporting a problem	what to send when something is wrong, and which files help
Installing from a checkout	running Atoo from a clone of its repository, in a virtualenv