Early access
Get the download
AWO is in early access: create a free account, ask for access, and a person turns it on for you — usually the same day. The account is also where your licence keys live.
Create a free account to download
No card, no subscription. The account is what download access and licence keys are attached to.
Getting started takes about a minute
Unpack the download
Double-click it. You get a folder — no installer, no admin password, and nothing is written anywhere else on your computer.
Open AWO
Double-click the AWO file inside that folder. Your browser opens with the builder. This is your own computer — nothing is hosted.
Start from a recipe
Press Start a workflow, pick something close to what you want, fill in the two or three boxes it asks for, and press Test run.
One thing worth knowing: a test run is a real run. The AI is really called and messages really send — only the triggering event is a stand-in. AWO says so on the button rather than letting you find out.
Your computer may ask if you are sure
AWO is not yet signed with an Apple or Microsoft certificate, so the first launch shows a warning. It is the standard warning for any unsigned download, and here is how to get past it — once, then never again.
On a Mac
You will see "cannot be opened because Apple cannot check it for
malicious software". Double-click AWO.command anyway, then open
System Settings → Privacy & Security, scroll down, and press
Open Anyway. Double-click AWO.command once more and it runs.
If that button is not there — or you would rather do it in one step — open Terminal, type the command below, then drag the AWO folder onto the Terminal window and press return:
xattr -dr com.apple.quarantine
Right-click → Open used to work and no longer does: Apple removed that shortcut in macOS 15. Either way it is once, not every time.
On Windows
You may see "Windows protected your PC". Click More info, then Run anyway. Only needed the first time.
We would rather say this here than have it surprise you. Signing certificates are on the list.
What you need
A computer, and somewhere for the AI to come from. That is it — the download already contains everything else it needs to run.
- An AI model. A free local one via Ollama works and keeps everything on your machine; OpenAI, Anthropic or your own endpoint work too. AWO ships no model and no keys, so the choice and the bill stay yours.
- Nothing else. No Node.js, no runtime, no dependencies — earlier versions asked you to install Node first, and the download now carries its own copy.
What happens after that
Build the thing you actually wanted
Add steps from the left, say what runs next on the right. The canvas is the same document the command line runs.
Set it watching
Press Start watching and the workflow runs on its own — on its schedule, or whenever its input fires.
Add a second input when you need one
That is the point where the free tier ends and a licence starts. Everything else stays as it is.
If something goes wrong
Nothing happens when I double-click it
Make sure you unpacked the download first — double-clicking the file inside the zip, without extracting it, does nothing on most systems. Drag the folder out to your Desktop, then open the AWO file inside it.
On a Mac, also check the unsigned-download step above: the very first launch needs a right-click → Open.
The Studio does not open, or the port is in use
Another program is already using that port. Open the folder in a terminal and run ./bin/awo studio --port 9000 — AWO reports a port clash in plain words rather than crashing.
It says permission denied (Linux or Mac)
Some unpacking tools drop the "this file may be run" flag. In a terminal, from inside the folder: chmod +x AWO.sh runtime/node, then try again.
An AI step fails with an authentication error
AWO ships no model keys, so the key has to come from you. Open Setup in the builder and choose a model. A local Ollama needs no key at all and costs nothing.
It was called Relay when I last used it
Same product, renamed. The relay command, RELAY_* variables and an existing .relay/ directory all still work — AWO reads the new names first and falls back to the old ones, and it uses an existing .relay/ where it is rather than moving your workflows.
Something else
AWO walks you through setup the first time you open it, and every step explains itself in the panel beside it. If something still does not do what you expect, email dlsneed1298@gmail.com — describe what you pressed and what happened.
Already bought a licence?
Your key is on your dashboard. Paste it into Setup once and it works offline from then on.