Use cases
What people build with it
Every workflow below ships inside AWO as a recipe you can open, fill in and run — these are not illustrations of what might be possible. Pick one in the Studio's template gallery and it arrives on the canvas with its steps already wired.
Watching things
For anyone who currently keeps a tab open and checks it.
Watch a page for changes
Checks a page on a schedule and tells you when something you care about changes — with an AI step in between deciding whether the change was worth a message.
schedule→fetch page→ask the AI→only if…→alert
Tell me when the price drops
Watches a product page and alerts you when the price falls below a number you set. The comparison is a real condition, so it does not message you about every reprice.
schedule→pull out price→only if…→alert
Watch a status page
Alerts you when a service you depend on posts an incident, so the first you hear of it is not a customer.
schedule→fetch page→ask the AI→alert
Chat that answers itself
Where AWO's graph earns its keep: a busy channel would bankrupt a one-run-per-message tool, and batching turns fifty messages into one model call.
Triage a Discord or Telegram channel
Reads a batch of messages, classifies what people are asking for, and routes each kind somewhere different — a branch per outcome rather than one catch-all reply.
discord · batched→ask the AI→only if…→reply / escalate
A digest on a schedule, alerts in real time
The same graph fed by two inputs: chat messages run the alert branch immediately, while an hourly schedule runs the summary branch. Neither triggers the other's work.
discord+schedule→one graph, two scopes
Development work
These need the code-writing capability, which is off until you turn it on and runs in a sandbox that opens a pull request rather than pushing to your branch. For work bigger than a single recipe, Project Autopilot takes a goal and a repository and plans the phases itself.
Plan → implement → test → fix
The full development loop: plan the work, build it, run the tests, and go back and fix what failed — up to a limit you set on attempts, time and spend.
issue→plan→implement→test↺fix
Code review pipeline
Reads a pull request's diff, reviews it against the standards you describe, and posts the findings where your team reads them.
PR webhook→read diff→review→comment
Reproduce → fix → verify
Turns a bug report into a failing test, fixes the code until that test passes, and refuses to open the pull request if it does not.
bug report→failing test→fix→gate
Refactor behind a test gate
Restructures code and holds the change to one rule: the suite that passed before has to pass after. Nothing ships if it does not.
target→refactor→suite→only if green
Docs from the code
Regenerates documentation from what the code actually does now, and opens a pull request with the difference.
schedule→read code→write docs→PR
All of these are in the template gallery
Open one, fill in three fields, press Test run.