Settings → Orca Cloud → Team renders the Team page body in place instead of one row that opens a
dialog. Inline, the plan block is replaced by a link to Plan & billing (seats and invoices stay there,
JA-18). The Team dialog stays for its other callers (checkout landing, plans).
Terminal prompts read ubuntu@<random VM id> and changed after every wake. Each start (create and wake)
now sets the hostname to the workspace's title (else its repo's name) as a hostname label, plus an
/etc/hosts entry, inline before orcad starts: no image change. Verified on a dev VM: hostname ja-hello,
127.0.1.1 ja-hello, no sudo warnings.
The control plane sends a run's triggerDetail as an object ({requestedBy}, {event, target}, {scheduledFor}); the desktop schema wanted a string, so POST /run and run history failed to parse although the run had started, inviting a duplicate run. Accept the object and show one short label.
- Set up once: Settings actually opens (the target alone did nothing); the post-create prompt now runs the
agent sign-in inline (Claude setup-token, Codex device code) with progress and Try again, and stays
until acted on or dismissed (PC-3 interim)
- PC-1: the Agent step is never a setup-page step and never gates a start
- PC-8: one Create press is one intent, single-flight across the setup page, its auto-start, reveal,
Exit and Back; nothing creates while the setup page is open; the intent is the create's
Idempotency-Key (preload → IPC → recipe context, create-speed's #345)
- PC-5: no 'Using sandbox hours' start toast
- setup page: fixed top offset, header line instead of the prompt card, right-aligned actions, Back walks
the steps, × Exit keeps the draft without ever auto-running, done steps clickable
The hint used the control plane's create_ms (row to orcad ready, ~2-3 s) for a step the sheet measures
end to end (~6 s), so every normal start read as 'Taking longer than usual'. The sheet now records its own
'Start sandbox' durations (local, durations only, last 40), hints from their p50 once there are 5, and
warns past their p95; with no measurement yet, only past 30 s.
design-squad P3 on #336: aria-disabled with the muted look (still focusable), a tooltip and
aria-describedby with the footer sentence, and clicks do nothing.
Vercel's sandbox-init listens on 23456 as root (pid invisible to the user); the
VM declares it via ORCA_HOST_MANAGED_UNOWNED_PORTS. Any other pid-less
listener (root-run postgres, Docker-published ports) stays under External.
- POST /v1/sandboxes takes an Idempotency-Key (api_idempotency, 24 h, scoped per account and member):
the same key and body return the first create's sandbox instead of starting another; same key with a
different body is a 422. The desktop sends context.idempotencyKey when its caller provides one.
- The desktop sends the workspace name as the create's title, so lists show it, not an untitled row.
- GET /v1/sandboxes/boot-plan?repo= says whether a create would clone or update (environment build);
the driver asks in parallel with the create, so the build sheet names 'Clone repository' or 'Update
repository' once, with a placeholder until it knows, and never relabels mid-run.
Neil
Neil