# Async by Default (Orbs and Proof)

#concept

## Summary

If agent work takes sixteen minutes and you are doing something else, latency stops being a cost. [[thorsten-ball]]'s working mode: delegate into a **remote sandbox**, walk away, run several in parallel, and — since you are waiting anyway — **ask the agent for proof** rather than a claim of success.

## Current Understanding

**The orb.** [[amp]]'s unit of work is a remote sandbox tied to one conversation. It sleeps when idle and wakes on typing; it streams to phone, laptop and TUI as the same conversation; and **one URL packages the thread + the agent + the computation + the diff**. Share the URL and a teammate opens the orb and takes over. Agent-to-agent messaging turns this multiplayer: "I found another bug" → "launch another orb to fix it" → new checkout, new branch, new agent, in parallel.

**The old objections collapsed.** Cloud IDEs (Cloud9 and friends) died on latency, key bindings, "I can't SSH in," and missing language servers. Thorsten's rebuttal: *who cares about latency when you're waiting for tokens per second anyway?* — and nobody uses editors, key bindings or language servers the way they did when those objections were formed. The objection stack was about a workflow that no longer exists.

**Ask for proof.** Quinn (AMP's CEO): *"You're async anyway — so ask the agent to give you proof."* Screenshots, benchmarks, dark-mode *and* light-mode variants, fifty tests in parallel. This is the delegation-side counterpart to [[make-more-cheap-code]]: cheap generated artifacts exist to make a claim checkable, and asking for three of them costs you nothing when you are not sitting there watching. In practice at AMP: screenshot a bug → send it → an orb returns a fix → spot check → merge; the designer "never fixed so many paper cuts."

**The prediction.** Local dev effort goes away, replaced by remote sandboxes — with the caveat that 15+ sandbox providers are already racing margins to zero, which Thorsten himself calls unsustainable.

## Evidence

- Orbs, sleep/wake, one-URL packaging, multiplayer handoff, the 16-minute live demo, the collapsed cloud-IDE objections, Quinn's proof line, paper-cut velocity, local-dev prediction, infra-margin prediction — [[2026-07-28-agentic-engineering-10x-developer]].
- Fire-and-forget as a native harness mode; completion notifications as what makes background agents usable — [[2026-07-14-skills-based-on-git]], [[harness]].
- The same mode as a job description: the AI-developer is IO-bound, runs tasks in parallel, and "if you launched Claude Code and sit watching it work — you're a bad employee" — [[2026-07-30-rakes-in-ai-sdlc-adoption]] (the role-shift side lives at [[developer-as-agent-manager]]).
- Scheduled agents producing while you sleep (the non-engineer version) — [[personal-ai-operating-system]].

## Related Pages

- Concepts: [[harness]] (async is one of its two modes), [[agentic-loops]], [[make-more-cheap-code]] (proof artifacts are throwaway code with a job), [[shedding-weight]] (async is what makes killing the backlog possible — parked agents replace queued tickets), [[personal-ai-operating-system]], [[context-as-scarce-resource]], [[developer-as-agent-manager]] (the human role this mode implies), [[review-is-the-new-bottleneck]] (where the parallel diffs pile up)
- Entities: [[thorsten-ball]], [[amp]], [[claude-code]]

## Contradictions / Uncertainty

- **Attention, not latency, is the real budget.** Five parallel orbs produce five diffs that a human must still review; [[make-more-cheap-code]] argues reading is the scarce resource. Async multiplies generation without multiplying review capacity, and the source does not address the pile-up. Status: tentative — this is the same open question logged on [[make-more-cheap-code]] about reviewing *agent behaviour* becoming the new attention sink.
- **Proof is produced by the thing being checked.** A screenshot from the agent that made the change is evidence, not verification; the failure mode where an agent produces a convincing artifact of work it did not do is unaddressed.
- **Remote sandboxes vs compliance.** Code and conversation in a vendor's cloud is exactly what [[enterprise-ai-reality|locked-down enterprises]] forbid. Also sits against [[eugene]]'s consolidated *local* workspace pitch ([[harness]]) — though the two are compatible if the consolidation point is the interface rather than the compute.
- "Local dev is going away" comes from a company selling remote sandboxes. Status: tentative.

## Next Questions

- What is the non-engineer's orb? The corpus has scheduled workflows (Allie) and completion notifications (Eugene) but nothing that packages a resumable, shareable unit of work for a non-technical user.
- Which proofs actually catch drift? If [[leave-less-room-for-imagination|the damage is what you don't notice]], a screenshot proves the happy path and nothing else — the proof list needs a design, not just a habit.