* fix(native-chat): wrap long answers in a question card's answer field
The free-form answer field was a one-line input, so a long answer
scrolled sideways out of view. It is now a one-row textarea that grows
with its text (CSS field sizing, like the Linear title and agent-args
fields) up to six of its own lines, then scrolls. Enter still submits,
and a pasted line break becomes a space, so the answer stays one line.
The answer ref is typed for the textarea along the card chain.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(native-chat): keep Undo after a multi-line paste into the answer field
Rewriting the field value to strip pasted line breaks cleared the
textarea's undo history. A paste that holds line breaks now inserts the
one-line text with insertText right after the paste event, so it is one
undoable edit and the caret lands after it. The in-place cleanup in
onChange stays for dictation and drops.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(native-chat): keep caret-aware arrows on the wrapping answer field
* fix(native-chat): drop the answer field's paste-event path
Desktop Cmd+V and menu Paste reach the field through the paste bridge, not a paste event, so the field's onChange is the one place line breaks become spaces.
---------
Co-authored-by: Michael Schaecher <276865230+big-sheq@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(native-chat): run Codex /goal pause|resume|clear and /usage from chat
Codex app-server has no slash parser, so a chat's /goal pause set the goal's text to "pause" and /usage reached the model as prose. /goal pause|resume|clear now change the current goal through the host, and /usage opens the Codex usage section in Settings for the chat's host.
* fix(codex): say a chat has no goal when /goal pause or resume finds none
Codex rejects a status change without a goal in words naming the thread id; read the goal after that rejection and show Orca's copy instead.
* fix(native-chat): address review on Codex /goal controls and /usage
Look goal words up without inherited properties, keep text after a picked /usage, let Send run what Enter runs on a held host, name Codex when there is no goal (clear included), and drop the shared /goal hint that phones and goal-less hosts would show for words they send as text.
* fix(native-chat): keep the draft after a picked /usage and hold goal-mode Send
Picking /usage opens Settings and leaves the text typed after the command; Enter on the row no longer sends /usage to the agent. Goal mode submits its draft as an objective, so a held host keeps Send held there, and an enabled Send is not labelled with the hold.
* test(native-chat): build the picker state instead of casting it
* fix(native-chat): honor Stop before naming a missing goal, and own any Codex /usage row
A canceled pause or resume no longer reads the goal to word a refusal, and an agent-reported /usage row gives way to Orca's, as /resume already does.
* revert(native-chat): leave /usage for its own change
Brennan wants /usage to show the status bar's Codex usage panel for the chat's account, in a separate PR; this PR keeps the /goal controls and the held-chat Send fix.
* fix(native-chat): let arrow keys reach a question card's answer field
Up and Down cycled only the option rows and wrapped past the free-form
answer field, so only a mouse click could reach it. The field is now the
last stop in the loop. A one-line field always hands plain Up/Down back
to the options; a multiline field does so only from the very start or
end of its text, so caret moves inside a draft keep working. Arriving
by arrow focuses the field without choosing the typed answer and puts
the caret at the end.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor(native-chat): find the question answer field by its existing marker
Mark the multiline answer field with data-native-chat-answer-field like
the one-line field already is, and find it by that marker instead of a
deny-list selector that a markdown task-list checkbox could defeat.
Paste routing is unchanged: it only claims an input element. Trim the
tests to one case per behavior.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Michael Schaecher <276865230+big-sheq@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(browser): save and fill passwords in Orca's browser (experimental)
Off by default under Settings > Experimental > Saved passwords.
* fix(browser): secure saved passwords and fix login lifecycles
* fix(browser): keep the guest preload self-contained so saved passwords load
The shared uuid import split into a chunk the sandboxed preload can't require, so the
whole preload failed on every page. Element tokens now come from crypto.getRandomValues.
* fix(browser): fill a saved login on mouse press so clicking a row works
Pressing Orca's UI blurs the page field, which closed the list before the click landed.
* feat(browser): manage saved passwords from a Passwords section in Settings › Browser
Replaces the Manage passwords dialog with an inline section: save and Touch ID
switches, import menu, a searchable list grouped by site with last-used times and
hover actions in a capped scroll box, delete confirmations, and an Add/Edit dialog.
* feat(browser): turn saved passwords on for everyone instead of behind Experimental
Drops the experimental flag, its Experimental toggle and the badge; the Passwords section in
Settings › Browser now shows on desktop for the local host without opting in. With no toggle,
the guest disable message and the apply-to-open-pages step had nothing left to trigger them.
* fix(browser): refuse protected password actions when Touch ID is set up but unavailable, and keep fills on the matched page
Touch ID lockout or a closed lid made canPromptTouchID() false, which counted as a Mac without
Touch ID, so show, copy and protected fill went through unchecked. Enrollment from bioutil now
tells the two apart. A fill also kept no hold on the page across the Touch ID prompt, so a page
that navigated meanwhile got the password; it now goes only to the frame and origin it was matched for.
* fix(browser): keep a browser profile when its saved logins can't be deleted
Profile deletion removed the profile first and only logged a failed vault delete, so the
encrypted vault could stay on disk with nothing left to retry it. The vault now goes first,
and the profile stays (deletion reports failure) when it can't.
* New chats run the agent's configured model when no model was picked
A new chat with no model pick sent the default Orca had learned from an
earlier chat on its first message, so the agent ran that remembered model
instead of the one its own configuration now chooses (STA-13542: OMP chats
ignoring config.yml). Unpicked defaults are now shown but never sent, for
model as already for effort; the Claude create/send fallback no longer
turns a shown default or an agent report into the chat's own model.
* Phone declared-effort test: only saved models are sent
* Show changed files directly in chat turns
* Use the fixture frame for the diff interaction
* Keep changed filenames readable and preserve file actions
* Keep unconfirmed file changes in tool activity
* Capture changed files in completed transcript fixtures
* Preserve patch data with authoritative history status
* Keep mobile diff interaction coverage beside its card
* Assert the decoded patch line contract
* Exercise full returned history in catch-up coverage
* test(chat): target file summary when reopening patches
* fix(sidebar): extend the workspace list scrollbar hit area past the seam
Add a 4px strip just right of the sidebar seam that drives the list
scroll position like the native thumb (drag the thumb, or jump on track
click), and falls back to resizing where no list scrollbar is under it.
The resize handle starts past the strip; the divider line stays on the seam.
* fix(sidebar): keep seam scrollbar drags alive over native plugins
* Keep long chat turns alive past timeline entry limits
* Retire completed tool payloads and preserve late event ownership
* Use canonical payload metadata in the long-turn benchmark
* Explain the real-scale benchmark timeout
closeTerminalTab defaulted a missing reason to 'user', so programmatic
closes (a withdrawn launch pane, a host-retired pane) reached a paired host as session.tabs.close reason:'user' and
killed its live terminal. The reason is now required; only gestures
declare 'user', CLI/RPC/phone closes forwarded by main declare
'requested', and housekeeping declares 'cleanup', which never kills a
paired host's live terminal. A launch pane closed by housekeeping no
longer tells main the user stopped its launch.
Refs #37245
Headless orca serve (orcad and Electron --serve) was missing services that only
the desktop composition or a window attach started.
- orcad now wires the orchestration environment transport, so a headless Run
home can place workers on its paired servers again. The transport moves into
a shared factory both hosts use. Its routing graph broadcast to renderers
through BrowserWindow directly; that now goes through the desktop-surface
port, so the graph runs on plain Node.
- orcad also resolves paired-device names, which was a declared gap.
- Usage polling runs from the account composition every host builds. Polls
fire while someone watches: the focused desktop window, or a live
accounts.subscribe stream. A headless host's remote readers now get the polls
that stream promises, and unwatched hosts spend no usage budget.
- The composition parity test now accounts for every service a window attach
starts, so a new window-only start can't silently skip headless hosts.
Fixes#36853
Refs #37256
Co-authored-by: Brennan Benson <79079362+brennanb2025@users.noreply.github.com>
* fix(agent-state-rules): treat a 404 as nothing published, not a failure
No agent-state-rules release has been published yet, so every packaged
app logged a warning on each refresh. Log 404 at debug level; other HTTP
errors still warn.
Refs #37538
* test(agent-state-rules): drop the server-error case
Refs #37538
* fix(agent-state-rules): log nothing for a 404
orcad routes console.debug to stderr, so a debug line still reached
orcad.log on every refresh.
Refs #37538
* test(agent-state-rules): check the app fetches where the publisher uploads
A 404 is now silent, so a tag, engine-version or asset-name drift between
the publisher script and the app would go unnoticed.
Refs #37538
* fix(orcad): fit orcad inside a `ulimit -v` address-space limit
On hosts that cap virtual memory (ulimit -v 8 GiB on an HPC node), the
managed orcad crash-looped with "Failed to reserve virtual memory for
CodeRange" whenever it started a worker thread.
Two reservations used up the limit:
- undici's WASM HTTP parser, loaded by the first fetch, reserves a
trap-handler guard region (4-9 GiB). The pinned-Node orcad launch now
passes --disable-wasm-trap-handler --wasm-max-mem-pages=1024.
- each Worker isolate reserves V8's default CodeRange (512 MB on x64,
~600 MB of address space per worker). Main-process workers now go
through spawnWorkerThread(), which caps the code range at 64 MB, and
a lint rule keeps new sites on it.
Fixes#37538. Thanks to lin-tianyu for the report and logs.
* fix(orcad): keep the runtime selector one command; enforce spawnWorkerThread with ast-grep
Refs #37538
* test(orcad): run the address-space regression on Node
Refs #37538
* docs(orcad): note the WASM memory cap at the pinned-Node flags
Refs #37538
* fix(terminal): only resume a terminal stream where xterm is, so escape tails never print
After switching workspaces, Claude Code's prompt could show stray text such as
"43B": the tail of ESC[43B from a frame whose start was lost when output was
dropped (hidden panes, the pending cap, daemon background thinning, the
renderer backlog cap) and the stream resumed raw.
Main marks every delivery that cannot prove it starts at escape-parser ground
(midEscape: true, or 'unknown' after bytes it never saw), never batches bytes
across a gap, and routes salvaged query copies through the drop sentinel.
The renderer tracks where xterm's parser stands in the stream. Bytes enter
xterm only as an exact continuation of what it parsed, or from a boundary main
proves is ground (grounded with CAN); anything else is skipped whole, still
answers its queries, and is repainted by a restore. Snapshot and reattach
replays anchor the position; Orca's own CAN-led writes invalidate it. This
replaces the gap-label and seq-proof admission from #37269.
* refactor(terminal): tidy stream-boundary plumbing
Share the drop-sentinel check, build sentinel bytes once, name main's start field as a boundary, and drop unused test fixtures.
The remote host relays commands for desktop-hosted pages back to the
desktop, which ran every relayed command as the orca CLI. A terminal
link's follow-up browser.goto therefore marked the page agent-driven.
The host now tags relayed commands with whether its caller was an agent,
and the desktop only uses the agent identity for those.
* fix(chat): show running Codex image generation as generating
* fix(chat): settle an abandoned Codex image generation as not running
* refactor(chat): inline the running image status check
* fix(sidebar): show hidden discovered worktrees outside project grouping
* fix(sidebar): place hidden-worktree lines from the rendered rows in one pass
* fix(sidebar): keep shared-anchor hidden-worktree lines in row order
* fix(sidebar): count row visits without Reflect and drop a cast
* test(sidebar): build typed fixtures instead of casts
* fix(sidebar): show one hidden-worktrees line for all projects outside project grouping
relaunch() already lets a scenario declare terminalsRestart and passes it to
oracle.step, but compareRestart masked PTY ids only for coldDaemon, so
sleep-quit-resume reported its permitted terminal restart as a PTY id change.
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Say where to switch back from Chat UI wherever Orca turns it on
The Chat UI tip pointed to Settings → Agents, which users did not guess, and turning
Chat UI on from the tip or picking it in onboarding gave no reminder of where to undo it.
Point every surface at the Chat UI is on / Turn off switch in Settings → Chat UI, and
confirm the switch with a toast that names that path.
* Point browser and phone users at their own switch-back control, and word the toast as a default change
The browser client has no Chat UI launch switch, so its onboarding note names the
Onboarding checklist. Phone onboarding names Settings → Chat UI. The toast after Use
Chat UI says Chat UI became the default for new agents, since agents with their own
choice keep it.
* fix(mobile): send chat with the hardware keyboard modifier shortcut
Co-authored-by: James Hart <hjhart@gmail.com>
* test(mobile): provide attach icons for keyboard completion cases
* test(mobile): use a named native type import in keyboard coverage
---------
Co-authored-by: James Hart <hjhart@gmail.com>
* fix(chat): show the requested Codex wait duration
* test(chat): complete sleep activity test inputs
* test(chat): keep activity rendering within the web project
* test(chat): follow the translator module relocation
v1.4.249 is the first release with the reorganized src/shared layout, so the checkout wire-surface check rejected it and every baseline suite failed to extract. Module imports already resolve moved files by name.
Manual runs refused when a GitHub/GitLab-tagged automation's source tool or
auth was unavailable, while scheduled runs of the same automation ran. Drop the
source check and the per-row source-host probing that only fed it, so manual
runs match scheduled runs.
Fixes STA-13275
During creation the prior worktree stays active until handoff, and since #36920
the right sidebar stays open, so its panels showed the old worktree's files.
* fix(terminal): parse ligature fonts once and skip fonts whose rules explode
Since 1.4.247 the main window holds the local-fonts permission, so
@xterm/addon-ligatures reads and parses the whole font file once per
terminal. Fonts with large calt chained-context rules (Commit Mono: ~200MB
and ~1.7s per parse) then OOM the renderer when a session restores many
terminals, crash-looping Orca on every launch.
Share one parsed font per font stack across terminals, and estimate the
calt context expansion from raw GSUB bytes before parsing; over-budget,
oversized, or unreadable fonts keep the addon's common-ligature list, which
matches 1.4.246 behaviour.
* chore(terminal): document the ligature delegate terminal casts
* fix(terminal): keep the ligature addon from reading font files
Replace the shared-parse approach with the conservative fix. Since 1.4.247
the main window holds local-fonts, so @xterm/addon-ligatures read and parsed
the whole font file once per terminal; fonts like Commit Mono (~200MB per
parse) OOMed renderers on restore and crash-looped Orca.
Hide the terminal's font family from the addon so it never loads font files
and joins its common-ligature list, exactly as before 1.4.247. The settings
preview now uses the same wrapper. local-fonts stays granted for the font
picker.
---------
Co-authored-by: Orca Worker <orca-worker@localhost>
* Add Chat UI choice to onboarding and tailor agent tours
* Add setup guide controls for Chat UI and Yolo permissions
* Refresh native chat agents and improve surface radio controls
- Re-read the host inventory alongside workspace refreshes, including WSL
- Recognize downloaded, ready chat runtimes without a CLI on PATH
- Standardize onboarding and checklist surface choices on accessible radio variants
* Show full-access agent overrides in Yolo mode settings
* Polish Chat UI onboarding and clarify terminal fallbacks
- Group agents by launch surface and refresh selection previews
- Add scroll-edge fades to reveal clipped onboarding content
* Recognize ready custom Chat commands and nested scroll changes
* Advance agent tour after selecting a new tab type
* Install onboarding skills for selected chat providers
- Route Chat UI setup to local provider-specific skill roots
- Improve tour focus, Escape handling, and delayed target transitions
* Keep split lesson while a new pane mounts; update renamed skill in test
* Assert agentDefaultSurface in Chat UI onboarding e2e
* Open the chosen Chat UI agent when a new project's default checkout opens
* Make the onboarding chat preview match native chat
- Soften the selected preview tile styling.
- Accept a leading separator in dev:fresh arguments.
* Fix scrolling in the onboarding agent step
* Preserve initial working directory when opening empty workspaces
Also check only remaining tour steps for unfinished actions.
* Fix tour resumption after completed split steps
The floating panel has one tab row, and it shows only the focused split.
A browser in another split had no tab and no close button on screen, so
the terminal beside it could be closed but the browser could not.
Show an X in the browser toolbar when the page is in a floating split,
using the same close command as the tab row. The main window is unchanged
because each of its splits has its own tab row.
Fixes#38167
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(sidebar): keep discovered worktrees hidden when adding a project
Adding a project no longer switches it to show worktrees Orca didn't create
(Conductor workspaces and other tools' worktrees). They stay behind the
sidebar's "Hiding N discovered worktrees" line, the same as every other
way a project is added.
* fix(sidebar): open a picked linked worktree instead of revealing its siblings
When the folder added as a project is itself a linked worktree, its main
checkout is hidden. Open the picked worktree instead of switching the whole
project to show worktrees Orca didn't create.
* fix(repos): register clone and create paths with symlinks resolved
Git reports checkout paths with symlinks resolved. Clone and create saved the
typed path, so a project cloned under a symlinked folder (e.g. /tmp on macOS)
did not recognise its own checkout and hid it as a discovered worktree. Resolve
the existing part of the destination before registering, as adding an existing
folder already does.
* fix(repos): keep finding projects saved under a symlinked clone or create path
Projects cloned or created before paths were resolved keep the typed
spelling. Match both spellings so retrying the same clone or create reuses
the saved project instead of failing on its non-empty folder.
* fix(repos): keep Windows clone and create paths as typed
Windows Git reports the typed spelling, and resolving would turn mapped
drives into UNC paths. Runtime clone/create tests now use resolved temp
roots, matching what registration saves.
* fix(repos): register Git's checkout path for clone and create
Replace the parent-symlink resolution with the path Git reports after clone
or git init, as adding an existing folder already does. This also covers a
symlink at the target folder itself and WSL paths, leaves plain folders and
Windows spellings unchanged, and matches saved projects by both the typed and
the resolved spelling.
* fix(sidebar): keep opening projects whose own checkout isn't recognised
Projects saved through a symlinked path by older builds or paired hosts don't
recognise their own checkout. Keep main's behaviour for that case: show the
project so the add still opens it.
* fix(repos): match resolved paths when importing a folder of repos
Clone and create now save Git's resolved checkout path, so a nested import
through a symlinked folder must also match that spelling instead of
registering a duplicate project.
* fix(repos): find saved projects through a symlink before the clone target exists
Resolve a missing clone target through its existing ancestors, reusing the
worktree-create alias resolver, and read the lookup keys inside the clone
lock. Queued clones through a symlinked folder reuse the first clone, and a
different repository at a saved project whose folder is gone is refused
before cloning, as on main.
* fix(repos): match a folder import's resolved path only to local projects
The resolved spelling names this machine's folder, so a remote (SSH) project
at the same path string must not be treated as the import.
* fix(repos): limit a desktop folder import's resolved-path match to this machine
Runtime-owned and SSH projects can share the path string; only projects on
this machine may match the import's resolved folder.
* fix(repos): read a nested import row's connection through the host helper
* fix(repos): match only this machine's projects when creating a local project
* fix(mobile): address android auto quit
Android has no 'tabbar' accessibility role and throws when the Home tab bar mounts, killing the app on every launch of 0.0.63. Use 'tablist', which both platforms support.
* fix(mobile): keep the tab-bar accessibility trait on iOS
'tablist' maps to no trait on iOS, so VoiceOver stopped announcing the Home tabs as a tab bar. Only Android lacks 'tabbar'.
* perf(agent-hooks): start 5 processes per Claude hook event instead of 17
The managed Claude hook runs for every PreToolUse and PostToolUse. On macOS
each event started 17 processes; on Linux 17 (dash) or 19 (bash).
- Agent identity: Linux reads /proc/<pid>/stat and boot_id with `read`
builtins. macOS skips `uname` when OSTYPE is darwin and runs only
`exec /bin/ps`, without `sed` or `printf` subshells. The identity stays per
event: no shell builtin can tell a reused PID from the process that had it.
- Metadata header: packed once per pane into hook-metadata/pane-<id> beside
the endpoint file, and reused only while all six inputs match exactly.
- Payload: the capture subshell execs /bin/cat, curl reads the body from a
here-document, and the PreToolUse reply subshell execs curl.
Other agents keep their scripts byte for byte. Against a fake hook server,
the old and new scripts give the same server records, stdout, spool records
and time limits; the raw JSON body gains one trailing newline from the
here-document, which JSON parsing ignores.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(agent-hooks): keep the hook payload pipe off the exec path and prune metadata files
- Only the reply subshell that execs curl reads the body from a
here-document. The print-then-post path of Claude-compatible CLIs uses the
printf pipe again, so its body stays byte for byte and needs no TMPDIR.
- The spool drain removes hook-metadata files older than
AGENT_HOOK_SPOOL_MAX_AGE_MS, in main and in the WSL/remote guest.
- The Linux identity reads /proc/<pid>/stat to EOF, so a command name with
a newline keeps its start time.
- Comments are one line each, and the string-index stdin test is deleted;
the runtime stdin tests in the same file cover every generated script.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(agent-hooks): run the refresh locale test on the raw JSON exec-curl path
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(agent-hooks): keep the Claude hook body piped to curl
The here-document added a trailing newline to the raw JSON body and,
under macOS /bin/sh (bash 3.2), wrote every payload to a temp file.
Pipe the body again so the hook server gets the same bytes as before.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
* fix(mobile): re-read project catalog after the window publishes it
reposChanged went out before the window published the new project's
catalog, so the phone keyed a new project repo:<id> and its collapse
was lost when the catalog caught up.
Fixes#37067
* test(mobile): fold catalog re-announce check into the serve test
* fix(claude-accounts): keep /model and effort saved in a managed account across launches
Profile settings.json was overwritten from ~/.claude/settings.json on every
launch. Apply only the top-level keys the default home changed since the
last sync, tracked by per-key digests beside the profile marker, and keep
the rest of the profile copy.
* test(claude-accounts): fail hook install through a broken linked settings file
* fix(claude-accounts): leave an unreadable account settings file alone
* fix(claude-accounts): carry Orca hook changes in the default home to account copies
* refactor(claude-accounts): spell out the no-record case in the settings sync
* revert(mobile): drop the details card on session tab taps
Reverts 852391da0f (#36395). The card popped up on every tab switch.
Tapping a tab switches tabs again, and the session title card goes back
to its own owner from #30389. Keeps later changes to these files: tab
press feedback, the compact top bar's + button, and #36866's keyboard
keep-focus for title taps.
* fix(mobile): hide branch and folder when the setting is off
The phone's workspace row always printed the branch or folder path, so the
Branch name / Branch / folder path toggle under Card display did nothing.
The shared card details now carry that rule, and the row reads it.
* fix(mobile): centre the chevron on Home list rows
* fix(mobile): scroll sheets taller than the screen
Content-sized sheets ride the keyboard by translation, but their height cap ignored that lift, so a tall sheet pushed its top off screen with no way to scroll back to it. The cap now gives back the keyboard lift. Sheets that scroll their own list can now shrink to the cap instead of clipping it, and the GitHub Pages picker no longer nests its list inside the drawer's ScrollView.
* feat(mobile): show each desktop's machine kind and model
The desktop now reports whether it is a laptop, desktop or server, and its
model, on status.get. The phone stores it with the other last-known host
fields and turns it into a line like "MacBook Pro · macOS".
* feat(mobile): edit a host from its screen and align the Automations bar
The host screen's menu gains Edit host and Network diagnostics. Edit host moves
onto the standard bar and gains Remove host. Automations uses the standard bar
with its switcher pinned under it, as Source Control does.
* feat(mobile): arrange Home and bring back stats and account usage
Home drops the Jump back in times, names the repo on every Jump back in row
(#37642), shows each desktop's machine kind, and adds stats and account usage
at the bottom. A new Arrange button reorders and hides sections, saved on the
phone.
* fix(mobile): keep the page bundle within budget and show the machine on the host screen
The edit route gets a web stub so its native-only removal flow stays out of
the page's chunks, and Automations keeps its own segment style. The host
screen header shows the machine line like Home does.
* fix(mobile): give the edit route's page stub its own module
A bare re-export of the catch-all route compiled to the same asset as
[...page], so the page manifest listed it twice and the desktop template's
inventory check refused the build.
* feat(mobile): turn Home into Feed, Usage, Automations and Settings tabs
Feed keeps agents (needs-you first, five then Show all), desktops with a
needs-you count, and Tasks; New workspace moves to a floating button.
Usage shows stats and per-desktop account usage, Automations a per-desktop
summary with on/off switches that opens the page for editing (new=1 opens
its editor). Settings becomes a tab. Arrange Home is removed: tabs replace
the long scrolling Home it was for.
* style(mobile): darken the accent blue slightly
* style(mobile): give the Home Tasks row the desktop tile icon
* style(mobile): condense the Home Feed
Smaller tiles, type and gaps; a desktop is two lines with its needs-you
count as an amber pill; the Tasks row drops its duplicate heading.
* style(mobile): drop the Last known prefix on Home desktop rows
* chore(mobile): bump to 0.0.63 and Android versionCode 27
* test(mobile): re-record Linear task recordings for the darker accent blue
* test(mobile): check the page Back stack on Tasks now that Edit host is native
* fix(mobile): pass the Usage tab's limit window to the shared usage helpers
* fix(mobile): type the Usage tab test to the account-slot limits and keep the tab under 400 lines
Claude Code suggests allow rules with destination localSettings, and Orca
passed them back unchanged, so "Allow for this session" wrote a permanent
rule to the project's .claude/settings.local.json. Scope every suggested
update to the session, as the button says.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(projects): refuse project removal while a workspace is being created
Removing a project mid-create let the create land a workspace no project
owns, and its armed .orca-preparing checkouts outlived the project: a quit
inside their TTL leaked them locked, since crash reclaim only runs when the
same repo prepares again. Hold each create against its project row so
removal refuses until it settles, and release the repo's armed and
crash-left preparations when the project is removed.
* fix(projects): keep project removal working when its runtime needs repair
Resolving Git options for the dead-owner reclaim threw for a WSL runtime
needing repair, which blocked forgetting the project. Make the reclaim
best effort, and give host-setup deletion the same create fence and
preparation release as project removal.
* fix(projects): skip WSL boot and late prefetch arms on project removal
The removal-time reclaim no longer boots a stopped WSL distro, and a
prefetch that finishes after its project was removed no longer arms a
checkout nothing would reclaim.
* test(projects): assert the removal refusal by code, not copy
* refactor(projects): key the create hold by the shared repo host identity
* refactor(projects): keep workspace creation under the file line cap
Brennan Benson
Jinjing
OrcaWinandOrcaWin
Neil
Jinwoo Hong
Younghwan ChaeandClaude Opus 5.5
Jinlong LiuandClaude Opus 5.5