Cloud machine

Keeps working while your laptop sleeps

Connect an always-on machine, write what you want done in plain words, and hand it off: no terminal, no SSH. It keeps running while your Mac is closed, and when it is finished the work lands back in your queue, tied to the commit and the proof that delivered it.

No terminal, no SSH, just plain wordsRuns on while your laptop is closedResults come back proven, in your queue
Compare Aura
Projects
main
exponential backoff#816
oauth refresh
Claude
retry.ts

Your always-on machine

Hand off a job and keep working: a machine that stays awake picks it up, and you bring the finished work back with one click.

Connected as mhask

Send a job to the cloud

It runs on the cloud machine and lands back in your queue.

Bring results back

Pull anything the cloud machine has finished into your queue: each result keeps the commit and proof that delivered it.

01

Hand it off in plain words

Write what you want done, pick a brain, press Send. There is no command line: the machine picks it up and works it on its own.

Projects
main
exponential backoff#816
oauth refresh
Claude
retry.ts
Our API client hammers the server on 429s: add exponential backoff to the retry path.

Done. retry_with_backoff now waits 1s → 2s → 4s (capped at 30s) with a little random jitter, so a burst of 429s backs off instead of retrying instantly.

All 12 tests pass.

41sClaude
Switch to Gemini for a second opinion: any edge cases I'm missing here?

Two edge cases worth fixing.

The cap runs before jitter: backoff.min(MAX_DELAY) + jitter() can still land past 30s once jitter is added. Clamp after the jitter.

No ceiling on attempts: a permanently-429ing endpoint retries forever. Add a max of ~6 tries so it gives up cleanly.

18sGemini
Good catches. Codex: apply both and prove it.

Applied. Jitter is now clamped under the 30s ceiling, and MAX_ATTEMPTS = 6 stops the infinite-retry case.

Proven: 14/14 tests pass. It backs off, caps at 30s, and gives up after 6 attempts.

27sCodex
⌘L to focus
02

On while you are off

The machine keeps running when your Mac sleeps, so a long job finishes overnight instead of pinning your laptop open.

Mission Control
A-N220
Add rate-limit headers to the public API
?Queued
A-N223
Backfill missing changeset rows from git
Queued
A-N230
Ship the billing webhook handler
waiting on: Wire OAuth token refresh on 401
A-N231
Dashboard usage charts (per-agent tokens)
?waiting on: Migrate user table to UUID primary keys
A-N204
Refactor retry_logic to exponential backoff
7m
A-N198
Wire OAuth token refresh on 401
22m
A-N211
Migrate user table to UUID primary keys
3m
A-N371
Per-arch + beta-channel update manifests
ed8b9791h ago
PR #24
A-N109
Full Linux release channel (AppImage + auto-update)
c32e0f41h ago
PR #21
A-N212
Cache intent-recent + commit index for fast load
a14f58912m ago
Proven · 3/3 checks
A-N373
Fix Gemini model-switch no-op (brain_override)
593781040m ago
Proven · 4/4 checks
A-N365
Parallelize crew with git-worktree --jobs
1h ago
Couldn't finish
A-N324
Auto-prove on every build
2h ago
Couldn't finish
03

Bring the result back proven

When it lands, pull it into your queue: tied to the exact commit and the proof it delivered, not a wall of log output.

Semantic review
Reworked 3 functions (retry with backoff, compute delay, sleep fixed).
Used to
Every retry waited the same flat half-second, so a service that was already rate-limiting us kept getting hit at a fixed pace.
Now
Retries now wait a delay that doubles each attempt (100 ms, then 200, 400, 800…) capped at 30 seconds, so a struggling endpoint gets progressively more room to recover.

Why & how · A flat delay ignores how overloaded the other side is. Exponential backoff is the standard way to behave under rate limits, and the cap keeps the wait from growing without bound.

src/retry.rs
Previous was this
  • ~
    Retry With Backoffchanged
    This function was reworked.
    Why: Each retry now sleeps for an exponential delay instead of a flat 500 ms, and takes the operation by FnMut so callers can retry stateful closures.
    retry_with_backofffn
  • −
    Sleep Fixedremoved
    This function was removed.
    Why: Removed: the constant half-second sleep is replaced by the exponential compute_delay path.
    sleep_fixedfn
New is this
  • ~
    Retry With Backoffchanged
    This function was reworked.
    Why: Each retry now sleeps for an exponential delay instead of a flat 500 ms, and takes the operation by FnMut so callers can retry stateful closures.
    retry_with_backofffn
  • +
    Compute Delayadded
    A new function.
    Why: New helper that computes the backoff window: base 100 ms doubled per attempt, capped at 30 s so the wait can never run away.
    compute_delayfn
Proven · 3/3 checkschecked against the goal, and it passed
More of the platform
Mission Control
Every agent, task and PR in one window
Crew
The autonomous work-loop that ships proven fixes
Source control
Semantic diff, intent on every commit, PRs
Trace & proof
Every change tied to the goal it delivered
Memory
Recall an agent can query before it edits
Team radar
A live awareness plane so agents never collide

Ship with proof, not hope

Free public beta for macOS and Linux. Point it at a repo and drive every agent you already use.