Describe the process. Get the automation that runs it.

Describe the work, and an agent with its own computer builds it, runs it, and adapts when you correct it.

Join the waitlist
A desert labs workspace: the chat on the left, and on the right the pull request watcher it built, showing a finished summary of PR #8 with what changed and the files it touched.

From a sentence to something that does the work

  1. 01

    Say what you want done

    Explain it the way you would to a new hire. “Every morning, group yesterday's support tickets by cause and tell me what to fix first.”

  2. 02

    It builds it on its own computer

    An agent with a computer of its own does the work, using a browser and whatever else the job needs.

  3. 03

    It runs again whenever you need

    On a schedule, from a webhook, or through a page the agent builds for you.

  4. 04

    You fix it by telling it

    “That number comes from the invoice, not the email.” Correct it once and the agent adapts. No waiting on anyone else.

How the automation works

Every automation needs somewhere to run. Each workspace is one computer. Look around it below.

Inside a workspace
workspace/

One computer per workspace

Each workspace gets its own computer. That is where the agent works, and where your automation and your team's page run.

Built for the work nobody wants to do twice

Why this isn't Gumloop or n8n

Those are good tools, and they do what they set out to do. If you already know every step, they will run it. The gap is everything before that: working out the steps, keeping them up to date, and the jobs that never fit a box in the first place.

What you hand over

Canvas tools: A chart you draw yourself, every box and branch and field matched up by hand.

desert labs: A description of the work, the way you would explain it to someone joining your team.

Who builds it

Canvas tools: You, or someone you hire, once one of you has turned the work into boxes.

desert labs: The agent, on its own computer, and it runs the thing before handing it over.

When it gets it wrong

Canvas tools: Yours to find and yours to fix, by opening the chart and rewiring it.

desert labs: You say what was wrong, and it changes the automation and remembers.

What runs

Canvas tools: The chart exactly as drawn, so anything it can't express is a box someone has to build.

desert labs: Whatever the agent wrote for the job: plain code where the work is always the same, its own judgement where it isn't.

Odd jobs and one-offs

Canvas tools: You wait for them to add support for it.

desert labs: It has a browser and a computer, so if a person could do it at a desk, it can too.

What will you automate?

Start with one process. Describe it, watch it get built, and keep the thread open.

Join the waitlist

Already have an account? Log in