Early access · invites in small batches

Your agents work the night shift.

AI Workstation keeps your coding agents working around the clock on your own machines. Queue the backlog before bed, let schedules start the routine jobs, send a batch of tasks out as a swarm, and wake up to draft pull requests.

Tell us what you'd automateoptional
What do you build?

We use your address for the invite and nothing else.

Works with
  • Claude Code
  • Codex
  • Antigravity
  • OpenCode
  • Cursor
  • Grok
UsefulNote · tonight 02:14 Backlog sweep checked 6 items
Night shift Swarm You're around Event
Example board

02:14 on UsefulNote's board.

UsefulNote is our note-taking app. Mid-run, two items have landed, one is working, and a swarm plan waits for your approval. Go ahead and approve it.

Work / Night shift until 07:30 · now 02:14
2landed
1running
1queued
31%week used
Open tasks: read “next Mon” as a due date
night/1027-due-dates → dev · +48 −6
CI passedDraft PR
landed
Sync: retry a sealed upload after a timeout
night/1027-sync-retry → dev · +31 −9
CI fixedDraft PR
landed
Folders: keep a folder open after a sync
night/1027-folder-open · running e2e · turn 37
Working
12:40
Tidy: keep the dates in a pasted chat
priority p2 · tagged Tonight from a phone
Next
—
Report at 07:35 to Discord #hq
Swarm plan Waiting for you
  • Copy image in dark modeswarm/1027-copy-dark · design.js
  • Search folder namesswarm/1027-search · app.js
  • Pause a recordingswarm/1027-pause-rec · app.js
  • Export with photosswarm/1027-export · engine.js
4 worktrees · no shared files
Schedules tonightbrake 80%
  • Night shiftran
  • Backlog sweepran
  • Nightly e2enext
A day on the board

Two steps need you. The rest run on their own.

A day of UsefulNote's backlog, from one morning report to the next.

  1. Daily meeting

    The chair reads last night's results and brings in the agents it needs.

    auto

  2. Swarm approved

    You approve a plan for four backlog items. Each gets its own worktree, and no two touch the same files.

    you

  3. Swarm reviewed

    Every branch is reviewed, fixed up to twice, merged with the others and reviewed again.

    auto

  4. Tonight's queue

    You tag tonight's items from your phone.

    you

  5. Night shift starts

    A schedule starts it. A laptop that restarted at midnight still catches the slot.

    auto

  6. Backlog sweep

    A scheduled check looks at items nobody touched in two weeks and notes which look done.

    auto

  7. Nightly tests

    A scheduled job runs the end-to-end suite. If your usage is high, it waits for room.

    auto

  8. CI fix

    A night pull request's checks fail. A fix job reproduces the failure, fixes the cause and pushes.

    auto

  9. Night shift ends

    No new item starts after the end time. The one running finishes and lands first.

    auto

  10. Morning report

    What landed with its pull requests, what needs you and what it cost, posted to Discord.

    auto
Night shift

Tag it before bed. Review it at breakfast.

Items tagged Tonight are worked one at a time, highest priority first. In the morning each one is a draft pull request on its own branch, or a short note on what it needs from you.

  • Checked with the repo's own build and tests, then reviewed by your reviewer agent
  • The runner commits each item to its own night/ branch, never your checkout's
  • Stops at your end time, after twelve items, or before your weekly usage runs low
  • Keeps the laptop awake while it runs
Schedules

Routine jobs start on a clock.

Run any job template, a prompt, the night shift or a backlog check at a set time on the days you choose. Here is UsefulNote's week.

23:30Night shiftrun: night-shift
02:00Backlog sweeprun: active-sweep
03:00Nightly e2etemplate: e2e-check
08:00Progress digestdigest.at
09:30Daily meetingdaily.at
SunReconcilerun: reconcile
  • Each slot runs once, even with several laptops
  • A slot missed during a restart still starts within its window
  • Holds while usage is above the brake, so there's room for you
Swarm runs

Several tasks in parallel, one review at the end.

Pick up to six backlog items. One job plans them all, you approve the plan, and they're worked side by side, each in its own worktree. Nothing is pushed until you open the pull request.

  • The plan names the approach, the files, the checks and the best agent for each item
  • Up to four at once, never two on the same files
  • A reviewer checks every branch and sends findings back for up to two fix rounds
  • Passing branches are merged and reviewed together; a conflict is named, not forced
Unattended

Built to keep going without you.

The jobs that run while you sleep fix their own failed checks, pick themselves back up and stay inside two hard rules.

Failing checks get a fix

When a night pull request's checks fail, a fix job gets the failed logs, fixes the cause and pushes, without weakening a test. Small review comments are made and answered on the thread.

Stopped jobs pick back up

A job cut off by a reboot continues where it was. One stopped by a usage limit waits for the reset. One that ran out of turns while still making progress gets another run.

Unattended, never unguarded

Night and swarm jobs run without asking, with two rules that always hold: your credentials never leak, and no outside code gets onto the machine. They never commit or push; the runner does.

Approvals from anywhere

When a job does need you, answer it from the board, your phone or Discord.

Fewer questions each week

What you keep approving is suggested as an allow rule, and a job that was denied something shows the rule that would have let it through. Risky calls are never suggested.

Every laptop pitches in

Each laptop that's online runs jobs, and one web app reaches them all from your phone without opening a port.

The example

UsefulNote runs on it.

UsefulNote, our note-taking app, is the project on the board above: a web app with encrypted sync, AI that tidies a messy note, and a Playwright suite covering writing, sync and recordings.

workstation.config.json
"schedules": [
  { "name": "night-shift", "project": "usefulnote",
    "at": "23:30", "run": "night-shift", "catchUp": 60 },
  { "name": "active-sweep", "project": "usefulnote",
    "at": "02:00", "run": "active-sweep" },
  { "name": "e2e-nightly", "project": "usefulnote",
    "at": "03:00", "template": "e2e-check", "usageBrake": 0.7 },
  { "name": "weekly-reconcile", "project": "usefulnote",
    "at": "03:00", "days": ["sun"], "run": "reconcile" }
]
  • Your repo, your tests. Night jobs check their work with the app's own suite, and each pull request says which checks ran.
  • Your agents. Agents and job templates live in the repository, next to the rest of its agent setup, whichever coding agent you use.
  • A few lines of config. The workstation knows nothing about any one app. A project is a repository plus what runs when.
The same setup works for any repository
Requirements

What you need.

Windows 10 or 11PowerShell scripts
An always-on machinekept awake overnight
Node 22.12+node -v
A coding agentClaude Code · Codex · Antigravity · OpenCode · Cursor · Grok
git and ghgh auth status
Questions

Before you hand over the keys.

Will it push to my main branch?
No. Unattended jobs never commit or push. The runner puts their work on its own night/ or swarm/ branch as a draft pull request, and you decide what to merge.
Will it use up my plan's usage?
Only up to a limit you set. Schedules and the night shift hold off once usage passes the brake, so there's always room for your own sessions.
Where does my code run?
On your machines, in your checkouts. Syncing between laptops is optional and goes to a Supabase project you own.
When do invites go out?
In small batches. Tell us the first job you'd hand the night shift; it helps us choose who to start with.

Put your backlog on the night shift.

Get early access to AI Workstation and wake up to work that's already done.

Join the waitlist

Windows today · Invites in small batches