OpenAI shuts gpt-4o-transcribe and gpt-4o-mini-transcribe down on
2027-02-26. Offer GPT Transcribe instead, retire both old entries so a
saved choice loads as the new model, and send the language hint as
languages[], which gpt-transcribe takes in place of language.
"I think we should, uh, ship it" became "I think we should, ship it":
the filler's own comma went with it, but the one before it stayed. When a
pause follows the filler too, the comma before it now goes as well.
- Browser run Show button: keep the remembered page in state instead of reading a module Map during render, so a run keeps the page it drove.
- Linear description toolbar: subscribe to active formats with useEditorState; the editor mutates in place.
- Usage tooltip: recompute the 'Updated' and reset-credit expiry labels on each countdown clock tick.
* feat(cli): create workspaces on environment recipes
`orca worktree create --recipe <id>` creates the workspace on a new
environment from one of the repo's environment recipes, and
`orca vm recipe list` shows which recipes it accepts.
The desktop app on the provisioning computer runs the same main-side
provisioning the composer uses (write-ahead record, per-step timeouts,
cancellation), registers the project on the environment's Orca server,
then creates (orca-worktree) or adopts (provisioned-root) the
workspace there. Named progress steps ride on long-poll keepalive
frames, so the CLI prints them to stderr; older CLIs ignore them. A
failure after the VM exists destroys it through the shared cleanup and
returns recipe_workspace_create_failed with the failed step, the
recipe failure code and whether the destroy finished. Ctrl+C aborts
the request and destroys a started environment.
Paired devices cannot start a recipe create. Hosts advertise
worktree.recipe-create.v1 only when the desktop wires the recipe
service, so orcad and older hosts are refused before anything runs.
Based on #39228 by jutaz, a port of #28439.
Co-authored-by: Justas Brazauskas <brazauskasjustas@gmail.com>
* fix(cli): report the VM outcome when connecting fails; record no cross-host parent
* fix(vm-recipes): destroy the VM when recording its environment fails; reset exitCode in CLI tests
* perf(types): keep recipe orchestration out of the runtime's type graph
---------
Co-authored-by: Justas Brazauskas <brazauskasjustas@gmail.com>
* feat(dictation): add an Auto shortcut mode where holding records until release and a tap toggles
* fix(dictation): apply the terminal shortcut policy and the shortcut recorder to held dictation presses
* test(dictation): drop casts from the shortcut mode tests
* fix(dictation): time Auto holds by the key, not a Cmd release macOS reports alone
* fix(dictation): start an Auto hold pressed while the last dictation finishes
* refactor(dictation): simplify Auto hold timing and reuse the shared IME check
* wip
* rm execessive tooltip
* Clarify deletion options and improve resource popover layout
- Show the scope of persistent deletion choices directly in the menu
- Keep resource details accessible in short windows
- Style disabled dropdown actions consistently
* Clarify detached commits and deletion guidance
* Preserve translated tooltip guidance
* perf(sqlite): refresh the legacy profile copy hourly and recover crashed row caches
- The legacy whole-document refresh rewrote every changed split domain each 5 minutes
(~4-8 MB per cycle, ~200 MB/hour of WAL plus checkpoint on an active profile). Writer
start and graceful close already bring it current, so refresh at most hourly in between.
- Cap the profile-state WAL at 8 MB; without journal_size_limit it stayed at the size of
the largest transaction ever written.
- Row caches: a read-only startup read cannot roll back a hot journal (or recover a WAL
without -shm), so retry once on a writable connection instead of disabling the store
on every launch.
- Row caches: drop the saved baseline when a commit throws, since COMMIT may report an
error after the rows landed and our own commit does not move data_version.
* test(sqlite): accept Windows exit status for the crashed-writer fixture; document recovery cost
* docs(sqlite): state the crash-recovery cost without overstating its bound
* fix(sqlite): rebuild a row cache a crash left needing recovery instead of replaying it on main
* revert(sqlite): keep crash-recovery failures non-destructive; drop the rebuild fallback
* refactor: use concrete browser and input owners
* refactor: bind remote runtime callers to concrete transport owners
* Use checked subscription mock argument types
* Type browser lease mock with its subscription contract
* refactor: bind sleeping VM status probe test to socket owner
* feat(setup): import setup scripts from more workspace config formats
* fix(setup): isolate imported Copilot steps and harden config parsing
* chore(setup): drop type assertions flagged by the quality gate
* fix(setup): keep the orcad bundle ASCII and skip unrewritable dev container variables
* fix(runtime): a phone viewing a terminal on a headless runtime no longer resizes it for everyone
On orca serve / orcad, a phone that only opens a terminal now views it at the
current owner's size. It takes the size when it types or when the user taps
the phone-mode key; the desktop's take-back reclaims it. Desktop hosts keep
fitting phones on open.
* fix(runtime): keep phone claims across leave grace and held phone fit; pin the headless default for the process
A Codex chat launched codex app-server on the account home saved when the
chat was created, and nothing compared it with the selection, so after a
switch every message kept going to the old account. A chat that had hit
its usage limit kept failing with "Codex hit its usage limit" even though
the new account had quota.
Codex chats now follow the selection the way Claude chats do: the launch
prepares the selected account's home, the started process reports that
home, and the host replaces an idle chat whose account no longer matches
before its next message. Codex resumes a thread only from a rollout in its
own CODEX_HOME, so the launch links the thread's rollout into the new home
first. The chat's usage card reads the account its next turn runs on.
* fix(native-chat): clear /compact from the composer once it is sent
Conversation commands kept their draft until the host replied, while
messages release it as soon as they are on their way. Thread the
composer's onPending through the command dispatch so a sent /compact
or /clear leaves the input immediately; a refusal still hands it back.
Fixes#39122
* fix(native-chat): keep a command typed while a refused one was answering
A refused conversation command is handed back through the independent
draft merge, which replaces a lone command in the composer. With the
draft now released on send, a /clear typed while /compact was answering
was overwritten by the refused /compact. Return a refused command only
to an empty composer; anything typed since stays as typed, and the
refusal notice still says the command was not done.
* fix(native-chat): count images when a refused command checks for an empty composer
---------
Co-authored-by: mahedi-emon <113725370+mahedi-emon@users.noreply.github.com>
* feat(dictation): remove filler words from dictated text, per language
Spoken fillers (um, uh, äh, えーと, 음, 嗯 and their equivalents) are
dropped from dictated text before it is inserted, on desktop, the web
client and phones that dictate through the computer. The pass runs once
in the speech host's event sink, so every route shares it, and lives in
a new shared text pipeline that later passes join.
Only standalone sounds go, never words with meaning, and the comma after
a filler goes with it. The language comes from a single-language model
or the dictation language setting; an unknown language uses only
fillers that are no word in another language. Voice settings gain a
Remove Filler Words switch, on by default.
* fix(dictation): take the filler language from what the engine is told, and drop the comma before a final filler
* fix(dictation): keep 嗯 as a reply, clean all-caps transcripts, and read the sentence start in constant time
* refactor(dictation): one list of sentence-end marks in filler removal, and drop a duplicate off-switch test
* fix(dictation): write non-ASCII filler punctuation as escapes so the orcad bundle stays ASCII
ORCAD_CHILD_ENTRY_POINTS builds session-search-worker-entry.js, but
ORCAD_ARTIFACTS never listed it, so templates, the materializer, and the
remote installer dropped it and SSH-hosted session search failed with
'Session search worker entry not found'. Add the artifact and a test that
every built child entry is listed.
The legacy tool-row purge rescanned the whole messages table on every
writer open and foreign data_version change. Persist the scanned rowid in
meta, and install a trigger that records a floor whenever any writer
(including a downgraded build) inserts a tool row, so reused or later
rowids are still purged without full rescans.
* fix(sidebar): let the divider resize instead of scrolling the workspace list
The 4px scrollbar strip past the seam covered the visible divider pixel, so
grabbing the divider over a scrolling list dragged the scrollbar. Drop the
strip and start the resize handle on the divider; the native scrollbar inside
the sidebar is unchanged.
* fix(sidebar): trim the resize handle's outer reach by 1px
A suspended recipe VM kept getting reconnect attempts: shared-control
socket retries, health probes and SSH logins. Providers that resume a VM
on a new SSH login or connection woke it again, so suspend saved nothing
(#36363).
While a VM's record is suspended (or its resume failed) and no wake is
under way, Orca now makes no background dial to it:
- SSH: connect and the reconnect ladder refuse that VM's own SSH host,
which covers tunnels, managed-server checks, census and browser bridge.
- Shared control: no retry after close, and no socket open, including a
retry timer armed before the sleep.
- Status probe: answers asleep without dialing.
A wake (opening the workspace, Resume) is pending before it dials, so the
wake's own connect passes. Afterwards the server's control socket and
status are reopened.
A VM recorded as up whose SSH host Orca gave up reaching (the reconnect
ladder used every attempt) may have been stopped or reclaimed by its
provider. Before, opening the workspace did nothing for it (#34089). Now
it runs the recipe's resume and reconnects. If that fails, the record is
left as it was, so normal reconnects go on.
Fixes#36363
Refs #34089
The renderer's crew follow reconnect scheduler imported the shared-control
socket state module, which reaches the Node-only sealed-frame reader and
its node:zlib codec. Vite dev throws on that import in the web client,
the desktop renderer's crew panel chunk and the component fixtures.
Move the reconnect timer function next to the scheduler, its only user.
* Remove low-value ACP, hook and renderer test suites
* Remove low-value shared automation and agent test cases
* Remove low-value packaging and mobile probe test cases
---------
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
With a per-workspace VM workspace active, New workspace showed "Run on: Local
Mac" but created the workspace inside that VM. Seed the composer from the same
project on a visible host, hold Create when the resolved target is a
per-workspace VM (which Run on never lists), and show "Choose target" instead
of another host's name when the selection is not listed.
Fixes#38669
Co-authored-by: Neil <neil@stably.ai>
Drops the logo and duplicated shortcut list for a single list with key caps, a default-agent row with an agent picker, Go to file, Mobile emulator, Reopen closed tab and a quiet Close pane.
* feat(mobile): show folder workspace Source Control on the phone
A folder workspace now has Source Control on the phone: one row per attached
worktree (repo, name, branch, ahead/behind, change count), read from the host
list's own lineage projection and each worktree's git.status. Tapping a row
opens that worktree's existing Source Control in place; Back returns to the list.
* fix(mobile): folder Source Control routing, back, hidden reads and failure states
- A desktop worktree under a server's folder is listed and opens with desktop routing and gates.
- A child opened in the dock gets Back to the folder list beside Close.
- Rows and the catalog stop reading while the screen is covered, as the single-worktree screen does.
- Offline, failed and missing-folder states; rows whose status can't be read say Unavailable.
- Server rows poll like the host list; branch shown without refs/heads/.
- Perf contract: git.status reads per signal at N and 10N rows.
* perf(mobile): folder Source Control reads summaries and rebuilds only on lineage changes
- Rows read a status summary without per-file line stats; relayed servers' rows open no desktop event stream.
- Membership resolves over a projection of lineage and label fields, so agent and terminal churn rebuilds nothing.
- A row whose re-read failed or whose host reported readError shows Unavailable.
- A connection still coming up shows loading, not offline.
- Perf contracts at N/10N rows and H/10H catalog rows.
* perf(mobile): folder membership keys on lineage only; child status reads update the folder list
Membership resolves again only when a row's lineage fields change, keying
only rows the catalog replaced; labels come from the current rows. A child
Source Control's newer status read is handed to the folder list's summary,
so Back shows what an action did without another read.
* fix(mobile): folder summary takes child reads as they land and ignores server health
Membership depends only on each relayed server's installation, so health
and relay flips no longer resolve the folder again. A child Source
Control hands each status read to the folder summary as it is accepted,
so a summary read answering just after can't hide it, and an older read
never replaces a newer summary failure.
* fix(mobile): folder summary skips restored and cached reads that could undo newer ones
Persisted status is marked restored before anyone hears of it, so a
child screen never hands an earlier launch's status to the folder list.
A cached read caught up on opening writes only an idle summary and never
cancels one in flight. Perf contracts count real lineage serializations,
committed row renders and summary publications.
* fix(mobile): clear the restored mark on any answer but the restore's own
A live answer timed before the stored record, as after a clock
correction, is still this launch's, so its reads and the folder summary
treat it as confirmed.
* fix(mobile): the restore's own write skips clearing its mark only once
A listener replacing restored data as it hears of it writes this
launch's answer, so the mark clears for it too.
* test(mobile): type folder Source Control test fixtures without assertions
* test(mobile): name mocked modules with type-only namespace imports
* feat(mobile): show folder worktrees as cards on the sheet surface
Each attached worktree is its own grouped card on the grey sheet
surface, the look the phone's option sheets use, so rows read apart
from the page.
* fix(mobile): keep folder Source Control's states on the card surface
Loading, empty, error and the list now share the sheet surface, so the
screen no longer changes background between states.
Codex's Speed row used a segmented Standard | Fast switcher while Claude and
Cursor used a single Fast chip. Speed is now always one button: one faster
tier toggles it, several (Fast and Ultrafast, or a configured Flex) open a
list from the button.
A process in Claude's group that ignored SIGTERM held /clear for the full
3 s grace; on /clear the supervisor now reaps the group after 1 s.
Linear: STA-14361
A reset that reclaims a crashed run's lock now puts that record back on release,
without overwriting a lock another start took, so the next start still reports the
crash. Starts without a rotating marker delete leftover .next staged files (one holds
a secret key); an unreadable marker leaves them for recovery by hand.
Co-authored-by: Claude <noreply@anthropic.com>
Cloning always went into <parent>/<repo name>, so a same-named repository
from another owner (or any non-empty folder of that name) could not be
cloned into the same parent. Before cloning, Orca now checks the target
on the clone host. If it is taken, the clone forms show a Folder name
field with a free suggestion (<repo>-<owner>, then <repo>-2...) and clone
into that instead. RPC repo.clone and `orca project setup-clone` accept
the folder name too.
Review rebuilt only when a git.status read changed, so a base move that left this worktree's status as it was kept the old compare (also cached 30 s). The compare entries now take git.status's gitStatusChanged signal. A status read that lands after the signal marked the shown compare rebuilds Review without re-keying worktree diffs, and a compare read that lands marked is read again.
* fix(mobile): paint host labels and relay server rows from the phone's store on relaunch
* refactor(mobile): reuse the SSH target summary schema for stored host labels
* fix(browser): import the session registry from its new profiles folder
#40002 moved browser-session-registry into sessions/profiles, and #39613 landed after it with the old path, so main no longer typechecks or builds.
* fix(test): keep the popup Electron fixture in its own worker
#40067 lets unit files share a worker's module cache. The popup compatibility fixture keeps its Electron app, mock server and temp root at module level, so after the first file the others reuse a closed browser.
* fix(native-chat): show newly installed skills in the Codex $ menu before the first message
Resting Codex chats served the background probe's skills/list from a
5-minute cache, so a skill installed in that window showed "No matching
skills", even in a new chat. Each menu open now compares a cheap stamp
of Codex's skill folders and skill/plugin config with the one taken
before the last scan, and rescans only when it changed.
Probe requests always force a reload, and probe pools are keyed by the
catalog's launch generation instead of the whole env, whose 10 s refresh
started a second Codex on every rescan.
Fixes STA-14359
* fix(native-chat): keep the structured session hook within its line limit
* perf(mobile): answer a page's ready that arrived before its bridge host
A page's ready can reach the shell before the screen has built its bridge
host (the host waits on the client and the host profile read). It used to
be dropped, so init waited for the page's next retry, up to 2 s later.
Keep the latest ready per session and answer it once the host exists.
* perf(mobile): keep one prewarmed page document while Home is shown
While native Home is on screen, boot one page document for the most
recently connected host with a cached build, parked invisibly in the
window. Opening a page from that build adopts it instead of building a
WebView, which removes the WebView start and script parse from the tap.
The spare is dropped when Home is left without a claim (2 s grace), on
background, memory pressure, its own failure and before the cache deletes
its files. It is never kept beside a shown page, and only phones with
more than 3 GiB of RAM (4 GB phones) get one. A parked page is told to
stop asking for init; the adopting view answers the ready it sent.
Builds on Jinwoo's spare pool and replay work in #32203 and #32204.
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>
* fix(mobile): unregister the shell's memory callbacks from the context that registered them
---------
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>