AGENTIC WORKFLOW ORCHESTRATOR

Download

Get AWO

One archive with everything in it. No installer, no account, no sign-up step. Free to run with one workflow and one input — a licence key lifts the limits whenever you want it to.

Linux · macOS · Windows (Node.js)

awo-0.0.1.tar.gz

8.4 MB · v0.0.1 · requires Node.js 22 or newer

Download AWO 0.0.1

Nothing is sent anywhere when you run it. What that means exactly →

What runs it

The same archive on all three. AWO is JavaScript, not a per-platform binary.

Linux

Any distribution with Node.js 22+. Tested on Ubuntu and Debian.

macOS

Apple silicon and Intel. Node.js 22+ from nodejs.org or Homebrew.

Windows

Node.js 22+. Use WSL or Git Bash for the launcher script.

Three steps to a running workflow

Unpack it

No installer and no admin rights. Everything stays in the folder you unpack, plus a .awo/ for your workflows.

Start the Studio

It opens at http://127.0.0.1:8788 in your browser. This is your machine — nothing is hosted.

Open a recipe

Press Templates, pick something close to what you want, fill in the two or three fields it asks for, and press Test run.

tar -xzf awo-0.0.1.tar.gz
cd awo-0.0.1
./bin/awo studio

A test run is a real run. The model is called and Discord, email and webhook actions fire for real — only the triggering event is a stand-in. AWO says so on the button rather than letting you find out.

What you need first

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

node: command not found, or a version below 22

Node.js is not installed, or an old one is first on your PATH. Install version 22 or newer from nodejs.org and check with node --version. On macOS with Homebrew: brew install node.

The Studio does not open, or the port is in use

Something else is already on port 8788. Start it elsewhere with ./bin/awo studio --port 9000. AWO reports a port clash in plain words rather than crashing.

permission denied running ./bin/awo

The executable bit was lost in transit — some unzip tools do that. Restore it with chmod +x bin/awo, or run it directly as node dist/cli.js studio.

An AI step fails with an authentication error

AWO ships no model keys, so the key has to come from you. Open Setup and choose a model, or set the provider's environment variable before starting. A local Ollama needs no key at all.

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

The documentation covers setup and every node type. If that does not do it, email hello@example.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.