- Forward tunnel early data (workspace-ports.forward-tunnel.early-data.v1). It is negotiated on
each attach: the client asks for it and the host echoes it in `ready`. The client sends up to
64 KiB, its receive credit and a half-close right behind Open. The host holds those bytes
until the destination connects, writes them before Opened, and drops them if the connect
fails. Old hosts and old clients keep the strict ordering, and the browser tunnel is unchanged.
New-connection HTTP GET through a forward on a real VM: p50 127 -> 64 ms, p95 138 -> 70 ms.
- SSH and port-forward idle-sleep activity now use ForwardUseMeter instead of the
2 KiB/min byte threshold. An idle VS Code remote window sends 2.3-3.0 KB/min of
keepalives, so it kept the VM awake forever. The meter counts packet bursts and
payload-sized packets instead; the unit tests replay traces recorded on the real VM.
- Downloads: files.stat now goes out with the first pages instead of one round trip ahead
of them.
* feat(cloud): remote desktop single-use tickets, fit, clipboard and keyboard release
- VM: Xvnc on a 0600 socket with no VNC auth plus an X cookie; orca-desktop-proxy (websockify
subclass) admits one WebSocket per unused 60 s ticket from the same localhost origin, refuses
rebinding Hosts, scrubs tickets from logs, serves the page with connect-src 'self'.
- Worker: POST /desktop mints a fresh ticket per call (schemaVersion 2).
- Desktop: no secret in the tab URL; main hands the page tickets on load and reconnect (backoff,
floor, pause with Reconnect), only for the exact URL of a live forward it opened; keyboard stays
in the desktop until Ctrl+Cmd / Ctrl+Alt; a paste key pushes this computer's clipboard; sandbox
copies reach this computer after a copy gesture.
- UI: keyboard hint, asleep/starting neutral tone and mapping, persistent error toasts, Beta badge.
* fix(cloud): remote desktop review fixes
- Security review: noVNC host/port/encrypt pinned to the page's origin, CSP connect-src 'self',
exact-URL + live-forward trust, mint floor and per-minute cap, copy gate on copy gestures only,
X display cookie.
- Design review: archived is its own neutral state, starting covers waking, page messages say
"Wake it in Orca", pause overlay is a status for calm states and focuses Reconnect, hint wraps
and hides from assistive tech when faded.
- FE review: paste follows the keyboard layout, AltGr never releases, page calls settle on
navigation, state notices only on change, hint once per load/release, paste always pushes,
no committed bytecode, session tests.
* fix(cloud): remote desktop archived page message, hint layout, fixtures
* fix(cloud): remote desktop copy gate counts double-clicks (pointer events have no click count)
* chore(cloud): remote desktop lint (exhaustive pause reasons, no test casts or wall clock)
* Keep saved agent models searchable while catalogs refresh
- Load saved catalogs independently of pending refreshes.
- Preserve edited presets until a completed catalog confirms removal.
* wip
* wip
* Preserve model discovery status when a read times out
Keep catalog responses provisional while discovery continues, seed account
catalogs when late results arrive, and retire queued discovery on shutdown.
* Simplify model catalog deadlines and picker state
* fix(native-chat): bring back the chat an unsaved terminal fork came from on Continue in Chat UI
* fix(agent-hooks): name a forked Claude terminal's session from its fork SessionStart
* fix(native-chat): bind a fork's origin chat to the fork's own conversation
* fix(native-chat): bind a fork to its launched pane and keep the stand-in chat's draft
* Simplify Settings chrome and organize General into focused views
* Preserve search and skill actions across Settings views
* Correct Settings validation leftovers
* Keep skill conflict details visible in compact Settings rows
* Refresh Settings search and protected copy catalogs
* Use Settings design tokens and button variants
* Keep Settings test setup and translation catalogs current
* Keep Settings search metadata independent of display labels
* Build repository search groups only for the selected pane
* Keep pending skill installs and server menu labels accurate
* Use the supported role locator in the skill regression
* Keep absent skill installation actions on their supported path
* Restore the Settings sidebar to its existing appearance
* Restore shared navigation title keys in pane headings
* Preserve the Settings shell entry animation
* Drop unused Voice labels after the main sync
* Preserve main Voice translations and the moved skill module import
* feat(agent-session): keep the permission mode a Claude session reports
Claude names its live permission mode on prompt, tool and Stop hooks. Keep the
root agent's latest value on the provider session, next to effort, so a resume
without a recorded launch can tell whether the session ran in bypass.
Ports the capture from #36359 by Nelef.
* fix(agent-launch): resume an unrecorded launch bare unless it reported bypass
Without a recorded launch, every restart path now resumes with no settings
Arguments, env or permission default; the configured Command still runs. A
session whose root agent last reported bypassPermissions keeps its bypass flag,
so a hand-typed claude --dangerously-skip-permissions keeps it while a bare
hand-typed claude never gains one (#29898).
Account-switch restart used the shared rule only for Claude; it now uses it
for every agent. Thanks to JustinCMR (#37304) for finding the account-switch
and cold-restore gaps.
* fix(terminal): keep the launch recipe of a window-started agent in main
A window spawn hands main its recipe, but main kept only the token and agent,
so restarts that main runs (workspace sleep capture, closed-worker reopen)
found no recipe and resumed bare. Keep it with the launch authority, the same
gate that admits the token.
* fix(orchestration): reopen a closed worker with the recipe it launched with
A closed worker's pane record goes away with its tab, so orchestration send
reopened it bare (#37693). The worker row now keeps the recipe Orca launched
the agent with, keeps it when a later capture of the same launch arrives
without one (main loses it on a daemon reattach), and a reopen prefers it over
a pane record that may hold another launch of the conversation.
Adapted from #37757 by Pr1p, without a new column.
* fix(terminal): keep a slept pane's earlier recipe only for the same launch
A host sleep capture without a recipe reused the pane's earlier record for the
same conversation. That is right after a daemon reattach, when Orca's launch
still runs but main lost its recipe, and wrong for an agent typed into the
shell that resumed the conversation: it never ran that launch.
* fix(agent-session): restore a paired pane with the recipe its host recorded
A client restoring a pane on a paired host sends only its recorded Arguments,
and the host filled the rest from its current settings. A saved restore now
replays the host's own record for that pane, or, with none at all, resumes
bare and keeps a bypass only when this host's hooks saw it reported. History
and other user-chosen resumes keep current settings.
* fix(terminal): replay a saved note only for the launch main still holds
A note belongs to the agent in a pane only while main holds that launch's
token: main admits it at spawn and retires it when the launch command
finishes, and a daemon reattach restores neither. Worker, host sleep and
hook/quit captures now take a note only from that attested launch, and no
longer copy an earlier record's note by agent or conversation match, which a
typed resume in the same shell also satisfies. With no attested launch the
unrecorded rule applies.
Replaces the inferred orcaLaunched / recipeLostPaneKeys flags and drops the
mock-only reopen and fixture-echo worker tests.
* fix(agent-status): take a pane's note from the launch main attests
The window carried a pane's saved note into each new record by agent and
conversation match, so an agent typed into the shell that resumed the same
conversation inherited an earlier launch's bypass. Main now sends the note of
the launch it still holds with each status, and the window records only that,
its own launch registration, or, for a restored replay of the very status a
record was written from, that record's note. /clear and compact keep the note
because main still holds the same launch.
* fix(orchestration): reopen a worker with its own recipe or none
A worker without its own note took the note of whichever pane record held the
same conversation. Its reopen now always passes a complete recipe: its own
note, or the unrecorded rule. The unrecorded bypass is also scoped to Claude,
whose hooks are the ones that report a root agent's permission mode.
* fix(agent-session): restore a paired pane from its source pane, never current settings
A saved restore on a paired host looked up the destination pane, which a Wake
opens as a new tab, and fell back to the host's current settings whenever the
client sent its partial Arguments. The client now names the source pane (to
hosts advertising agent-session.restore-source-pane.v1), and the host replays
its note for that pane or, with none, resumes bare keeping only a bypass its
own hooks saw there. Older hosts keep today's behavior.
* fix(terminal): re-arm a launch across a main restart while its agent still runs
The daemon outlives main, so it now keeps main's admitted launch (token and
note) and drops it when that launch's command finishes. On reattach main
re-arms the launch only when the same agent still runs in the foreground:
nothing can be typed into a daemon PTY while main is down, so a running agent
there is the one the unretired note launched. A shell foreground clears the
daemon's note; an unknown read, including every Windows read, declines.
Older daemons keep no note, so restore declines there as before.
* fix(terminal): the daemon retires a launch note when its command finishes
A launch can finish while main is down, so main's own retirement never sees it and a
hand-typed agent in that pane would later pass the reattach foreground check.
* fix(agent-status): a fresh Claude start never inherits the last process's permission mode
A hand-typed resume of the same conversation may run without the bypass the previous
process had, so only /clear and compact carry the mode forward.
* fix(agent-session): name a restore's source pane in the host's own keys
A mirrored pane's key carries the desktop tab prefix, so the host's exact lookup missed
its saved note.
* fix(terminal): retire a daemon launch note by its token from the one retirement owner
A delayed reattach result or a late retire could clear a newer launch's note. Retires now
name the token they retire, the reattach checks its PTY before clearing, and re-arming the
same launch keeps the daemon's completion scanner.
* fix(agent-status): only the launch owner's statement changes a pane's note
Main now states the attested note, or null for none, on every hook status. An OSC or
display update makes no statement, so after a completed turn it no longer erases an Orca
launch's note; a typed resume still drops it through main's null.
* fix(terminal): an attach leaves alone a launch main already holds
The renderer attaches a pane the CLI just launched before its agent starts, so the
attach saw the shell and retired the new launch's daemon note.
* fix(agent-status): a paired client keeps a pane's note only on its host owner's word
The host's session-tabs frame now says whether the Orca launch it admitted still runs on
the published incarnation, and the client applies that fact whichever writer wins the
status. With an owner's word the conversation no longer decides; an older host that says
nothing keeps the same-conversation rule.
* refactor(agent-status): one decision picks a pane's note for every reader
The live entry, quit capture, provider-session updates, account restart and cold
restore now ask the same owner-aware decision. An owner's none is final and, when it
turns, ends the pane's registry entry and saved note, locally and from a paired host's
frame. Cold restore and account restart take that answer for a live invocation and read
the saved record only when none is live. Inlines single-use wrappers.
* refactor(agent-status): a paired retirement test reaches the cold-restore command; trim comments
Replaces the projection and continuity tests with one transition: host frame retires the
launch, the next OSC keeps no note, and the cold-restore command has no old bypass.
* fix(agent-status): an owner's none retires the pane's matched launch registry entry
* chore: satisfy changed-code gates (type guards, SAFETY notes, fixed test clock)
* fix(agent-launch): a teams launch keeps its note; a legacy leaf id restores without throwing
* refactor(daemon): keep the session launch note on the process base so session.ts stays in budget
* fix(agent-launch): a restarted terminal main can't vouch for keeps main's earlier launch rule
* fix(agent-launch): read the pane's current terminal; a finished launch settles an undecided pane
* fix(agent-launch): undecided and held launches end with their process
A finished command, a fresh launch or a replacement process settles an undecided pane;
a newer attach or finish supersedes a foreground read still in flight; a legacy relay
reattach without an incarnation stays undecided; a held launch applies only to the
process it was recorded for.
* refactor(terminal): watch and arm a created terminal's launch in one call
Keeps terminal-create.ts within the 300-line budget after main's growth.
* refactor(terminal): keep main's launch evidence in one immutable record
Replace the undecided flag, the reattach check map and the re-arm's writes
to main's orchestration launch fields with one launchEvidence object
(unknown, gone for an incarnation, or held with its recipe), owned by
launch-evidence.ts.
- A fresh admitted launch is held; any other fresh process is gone.
- A finished command or confirmed exit is gone, sticky for its process:
no reattach, legacy or noted, can revive it.
- A replacement retires its predecessor's evidence without deciding the
newcomer, which may still prove its own launch through a reattach.
- A reattach note is held only after a foreground read sees its agent;
the evidence object fences that read.
- A gone launch clears its recipe and blocks both refill sites; a
deliberate sleep snapshot keeps its recipe past the launch it captured.
- launchToken, launchIncarnationId and launchAgent writes match main.
* fix(terminal): keep launch evidence through a first incarnation and sleep snapshots
- Learning a process's first incarnation binds its held or gone evidence
to it, so a later attach can neither revive a finished launch nor drop
a running one; a known X->Y replacement is fenced as before and now also
clears the predecessor's recipe.
- A status from no Orca launch leaves a sleep snapshot of its session for
the wake and never takes that snapshot's recipe into a live or quit
record.
* fix(terminal): record a runtime split's fresh shell as running no launch
* chore: rerun CI on main with the typecheck fix
Extract shared state/helpers into leaf modules (pure moves, re-exports kept)
so import/no-cycle can run at full depth with type-only imports ignored.
120 src + 8 mobile cycles -> 0. 10 suppressions remain on the browserManager
singleton hub, which needs DI to break.
- loopback-callback-listener runs lsof through @orca/process-host
- MCP egress ledger read is async; cloud-mcp-sync's two memoized one-shot reads and the
loopback grant's liveness poll (a heartbeat with a stop) are baseline-listed
- auth-callback-forward under max-lines; VmBuildFailureActions uses Button variant quiet
- test casts replaced by typed fixtures (Translate, WorktreeCreationRequest builders,
typed HostedSandboxRequest, LegacyRenameRuntime); one SAFETY-annotated store stub
- runtime catalog + protected-copy keys synced
- workspace-resume lost-contact tests partially mock ssh-target-registry (new import chain)
Host archive: fd realpath must stay under the folder (Linux /proc/self/fd), O_NONBLOCK opens,
directories re-verified (realpath + dev/ino) before and after listing, reads capped at the walked
size, links that leave the folder dropped, case/NFC twins renamed, Windows-invalid and reserved
names and bidi/zero-width characters mapped, slots reserved before the walk and limited per client.
Desktop: hard byte caps against a host that keeps sending, executable types are never opened
(Download only) and every saved file gets the OS downloaded-file mark, open-locally cache under
userData, busy limit counts transfers not dialogs.
Toasts: InlineError layout=toast with one action, neutral tone for limits/refusals/no-app,
Refresh for moved files, errors stay until dismissed, ETA, zip size label, title-only live
region, stable store subscription, one transfer per path and intent, renderer tests.
A speed the chat reports that no model lists, in practice Flex from the
user's own Codex config, is no longer added to the Speed choices. It
still runs and is still sent. A chat with no model of its own keeps its
saved speed when some model lists it, so Standard can still turn it off.
Grab, Annotate and Draw become one Annotate split button. DevTools, open
in default browser, hard reload, find and extensions move into the menu,
with the profile list, new profile and cookie import under Profile. Zoom,
viewport size, password offers and file actions show as chips inside a
flat address field, and the Import hint moves to the new tab page. The row
drops from 50 to 40 px and the fold from nine stages to two.