Describe the process. Get the automation that runs it.

Get startedFree to start. No card required.
See how it works
A desert labs workspace: the chat thread on the left, and on the right the underwriting app it built — an investment memo for a Savannah industrial-outdoor-storage deal, carrying a “Pursue with conditions” verdict with Excel, CSV and PDF exports.
One workspace: the thread on the left, and the underwriting tool it built — memo, verdict, and exports — running on the right.

From a sentence to something that does the work

  1. 01

    Describe it in plain English

    “Every morning, go through yesterday's support tickets, group the ones with the same root cause, and tell me what to fix first.” Explain it the way you would to a new hire — no spec, no schema, no connectors to wire up.

  2. 02

    Get an automation in its own sandbox

    desert labs runs it on a cloud machine with Claude Code inside, so it can read documents, drive a browser and produce real files. No infrastructure for you to touch.

  3. 03

    Steer it, then build the next one

    Keep talking to it — tighten the policy, change the output, add a page. The thread that built it improves it, and the next process you automate starts alongside.

How the automation works

A generated automation needs somewhere to run. Every workspace is one machine — move through it below.

One Sandbox Per Workspace
workspace/

One sandbox per workspace

Every workspace gets a cloud machine of its own — isolated from everyone else's, and permanent. The automation and the UI your team uses are both served from inside it.

Built for the work nobody wants to do twice

What will you automate?

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

Get started

Already have an account? Log in