* Show CI result lines on the phone, following the desktop setting
The host now sends nativeChatCiResultLines resolved in settings.get, the
ready snapshot and a nativeChatCiResultLinesChanged event, from one
publisher that tracks each pushed chat preference separately. The phone
keeps one store per desktop connection and preference, reads the CI value
only from the paired desktop, and hides the lines until that desktop
reports one. CI rows stay in the projection and are filtered after it, so
a flip rebuilds nothing. The phone draws the line with links to the pull
request and commit.
* Let the phone CI line wrap and select like other notices
Long repository names at large font scale no longer push the commit link
past an ellipsis: the line wraps, centered, with the icon on its first
line. Its text follows the system-notice selection policy, so iOS selects
natively and Android keeps the long-press actions sheet. The CI strings
are translated in every mobile locale, the filter copies only once it
meets a CI row, and the tests drop a token assertion and a duplicate case.
* Draw CI results as one-line cards on desktop and phone
The CI result line becomes a one-line card in the same frame as the
opened pull request card, with the Hide button inline at its right end
on desktop, and in the phone's chat card frame without one. Only the
lead and pull request name truncate, so the commit link and the Hide
button stay reachable on narrow widths. The fixture uses real
percent-encoded item ids so its links render.
* Make the CI card's whole lead open its pull request
A translated lead at large font scale can push the ellipsis before
repo#N, which left no visible way to open the pull request. The
truncating segment is now the pull request's target on desktop and
phone, named for it, while "at <sha>" stays the commit's own target.
The ja, zh and zh-Hant leads use a plain colon so the space after it
isn't doubled.
* Read the CI result lines setting only for structured chats
CI result lines come only from structured sessions' journals, so a
terminal chat no longer sends the setting read. The prompt-controller
fixture stubs the setting hook: its tests count only the chat's prompt
writes, and the structured chat's one read per desktop connection is
expected.
* refactor(mobile): give relay and encryption concrete owners
* refactor(mobile): organize session and review feature owners
* refactor(mobile): organize RPC and host ownership
* test(mobile): point render fixtures at concrete owners
* refactor(mobile): use explicit type-only owner imports
* refactor: import journal queue state from defining owners
* refactor(shared): organize execution and automation owners
* fix: retain type imports used by surviving test cases
* refactor: finish work item owners and refresh validation metadata
* test: infer reconnect status fixture type
* test(claude): resolve source files beside same-named directories
* test(runtime): group repository creation mock registrations
* perf(tasks): look up the GitLab comment viewer only on phone reads
The phone is the only reader of viewerDidAuthor, so GitLab detail reads
from desktop IPC and the Checks poll skip the `glab api user` lookup.
The phone sends markViewerComments on every GitLab detail read.
Ported from #39749 (GitLab part only); GitHub REST-fallback viewer
lookup is unchanged.
Co-authored-by: AmoabaKelvin <97001695+AmoabaKelvin@users.noreply.github.com>
* perf(tasks): keep GitLab viewer marks by default; desktop detail reads opt out
Older phones and callers that omit markViewerComments keep author marks.
Co-authored-by: AmoabaKelvin <97001695+AmoabaKelvin@users.noreply.github.com>
---------
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
Co-authored-by: AmoabaKelvin <97001695+AmoabaKelvin@users.noreply.github.com>
* chore(lint): bump oxlint to 1.91, add perf lint rules and perf audits
* fix(lint): await promises returned inside try/catch/finally for return-await
Prepare typescript/return-await with error-handling-correctness-only: await
returns whose catch or finally was meant to cover them, and suppress the eight
sites where the catch must not re-handle the returned promise.
* chore(lint): enable return-await (error-handling-correctness-only); exempt secondary-scan directives in the changed gate
* refactor(mobile): move file preview discard modal into its own module
Keeps MobileFilePreviewScreen under the 400-line limit after merging main.
---------
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
* fix(window): cancelling a quit prompt now cancels the quit
Renderer-owned quit prompts (running-work "Close Window?", Save dialog,
close-guard and shutdown-checkpoint vetoes) never reach
will-prevent-unload, so main kept isQuitting latched after Cancel. A later
plain close was treated as a quit and renderer crashes were not recovered.
Add a window:close-cancelled IPC (preload ui.cancelWindowClose; no-op in the
web client) that the renderer sends on each cancel path. Main accepts it only
from its own renderer, only while quitting, and only once that renderer has
acknowledged the newest close request, then runs the same abort path as a
beforeunload veto.
Fixes#39596
Co-authored-by: Neil <neil@stably.ai>
* test(window): expose webContents.send on the renderer recovery harness type
---------
Co-authored-by: tomarai85 <tomarai85@users.noreply.github.com>
Co-authored-by: Neil <neil@stably.ai>
When a link attempt finds the target taken, check what is there. A
dangling symlink another writer created after the directory listing is
not readable history, so the thread stays out of the bridged set, as
on main.
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
Co-authored-by: AmethystLiang <6427696+AmethystLiang@users.noreply.github.com>
On Windows, Hankaku/Zenkaku commits the Japanese composition as a
Process/229 keydown that may never send a keyup. The composer treated any
Process/229 keydown as an IME-confirm Enter and armed the carry, so the
user's next real Enter was swallowed. Only arm the carry when the
processed key's physical code is Enter (or unknown), sharing the code
check with the terminal IME path.
Fixes#39289
Hermes Kanban cleanup can remove a worker's cwd; os.getcwd() then raised
FileNotFoundError from the orca-status plugin and Hermes failed pre_tool_call
closed, blocking the tool. The payload now omits cwd when it can't be read.
Fixes#39736.
Account selection and every Codex launch walked all rollouts in every
source home and ran a synchronous existsSync per rollout on the main
process, then linked missing ones with sync mkdir/link/symlink. A CPU
profile of an installed build attributed ~6.4s of sampled existsSync time
to this bridge during typing lag.
The bridge now walks all source homes together and diffs directory
listings asynchronously, so a target directory is read once per pass and
history the target already holds costs no per-rollout synchronous call.
Small directories use per-path checks instead of listing a wide target.
Name matching yields every 256 entries.
Behavior matches the previous bridge:
- An existing target name is never overwritten.
- Earlier sources are tried first, and a later source still gets an
attempt when an earlier one cannot be linked.
- Hardlink-only targets skip and leave no folders behind.
- Readiness, index healing and quit handling are unchanged.
* perf(main): overlap independent fs probes on git status, agent detection and orcad startup
* perf: skip per-entry copies in git change list and tab hydration; drop unused activity barrel
* perf(mobile): warm WebKit's processes on iOS before the first page opens
Builds a blank, non-persistent WKWebView a second after Home has a paired
host, so the first page open starts against WebContent, GPU and Network
processes already running. A release before the delayed start now makes
the start a no-op.
Based on #32163 by Jinwoo-H.
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>
* fix(mobile): guard warmUp on older binaries and release the warm view on page failure
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>
---------
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
Co-authored-by: Jinwoo-H <73622457+Jinwoo-H@users.noreply.github.com>
* perf(skills): read skill folders ahead of the walk, three reads at a time
Port of #35220. findSkillFiles awaited realpath then readdir for every
folder, so a busy main process paid about two event-loop turns per folder.
A read-ahead now lists folders in walk order while the walk claims them
in its own depth-first order, so results, order, alias winners and the
cycle guard are unchanged.
Changes from #35220: up to 3 read-ahead reads (was 64) plus at most one
demand read from the serial walk, so at most 4 directory reads in flight
on libuv's 4-thread pool; a sorted array replaces the min-heap; tests
assert walk results only.
Co-authored-by: thefrikidude <100475418+thefrikidude@users.noreply.github.com>
* test(skills): drop walk tests that cannot detect the read-ahead
Both pass on the old walk, so they do not guard this perf-only change.
Note the in-flight bound applies per walk.
Co-authored-by: thefrikidude <100475418+thefrikidude@users.noreply.github.com>
---------
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
Co-authored-by: thefrikidude <100475418+thefrikidude@users.noreply.github.com>
Each federated dispatch relay now reschedules itself and doubles its wait
after consecutive failures (capped at 30 s) instead of syncing every second
forever. A server turning verified, or a sync completed by another caller,
returns the relay to the base cadence. A coordinator blocked in
`check --wait` re-arms its run's relays every 15 s, so a recovered worker is
seen within that window. Relays for a server removed from this host stop
instead of retrying; the next relay arm brings them back if it is re-added.
Stale in-flight syncs no longer record acknowledgments, epochs or home
auto-release after the relay stopped.
Replaces #39283.
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
Co-authored-by: brennanb2025 <79079362+brennanb2025@users.noreply.github.com>
* test: split GitHub and GitLab mocks out of runtime setup.spec
setup.spec.ts reached 801 counted lines after #39575, failing the root
oxlint max-lines rule on main. Move the GitHub/hosted-review and GitLab
mock functions and their vi.mock registrations into sibling modules that
setup.spec re-exports, so every consumer keeps the same imports and mocks.
* test: name split runtime mock modules as test harnesses
The module-mocking lint exempts *-test-harness.ts support modules shared by
split suites; the split-out GitHub and GitLab mock modules are exactly that.
---------
Co-authored-by: m4air <m4air@m4airs-MacBook-Air.local>
Native popups now hide the app menu bar like origin-bar popups, so the
Windows menu no longer eats into the 200px minimum content height.
The popup compatibility fixture keeps the first reported error across
later status writes, stops serializing the destroyed Event as an error,
and replaces its status file with the Windows retry helper. The native
resize check now compares against the native outer window size.
Fixes#39299
Co-authored-by: Neil <neil@stably.ai>
agy-acp-server 1.4.1 keeps the personal sign-in at
<GEMINI_HOME>/antigravity-acp/acp_token.json; nothing it writes ends in
oauth-token, so a signed-in Chat read as signed out and new chats could
move to the host's ~/.gemini account.
Fixes#39395
Co-authored-by: Neil <neil@stably.ai>
Adds commit actions to the Git Graph: check out a commit or branch, cherry-pick, revert, and create a branch from a commit. Conflicts hand off to Source Control with continue and abort. Works on local, WSL and remote hosts.
The packaged daemon PTY check types a POSIX arithmetic command and waits
for "OK 42". The daemon picked the PTY shell from the builder's $SHELL, so
a fish builder never printed it and Linux afterPack timed out. Pin the
probe daemon's SHELL to /bin/sh so the check exercises the packaged PTY,
not the builder's login shell.
Fixes#39591
Co-authored-by: Neil <neil@stably.ai>
A folder workspace with no worktrees now offers Create worktree for each repository, named after the folder workspace. If that branch name is already taken, the host refuses instead of picking another name, and the composer opens so you can choose.
With Hide sleeping on, deleting the active workspace activated the most
recently visited sibling (or main) and seeded it a terminal, so a hidden
sleeping row popped back into the sidebar. The removal successor now
skips siblings the sleeping sweep hides, using the same check the
sidebar's reveal path uses and honoring rows held through the PTY-rebind
grace window. With no eligible sibling the user lands on the start screen.
Fixes#39231
Co-authored-by: Neil <neil@stably.ai>
Command, Environment and Codex's session source home now use Input's
code variant, so they render at text-xs instead of md:text-sm above
768px. The Arguments label matches its siblings' text-xs style, and the
Arguments wrapper uses py-0.75 so its text is vertically centred.
Co-authored-by: Neil <neil@stably.ai>
List the Bitbucket API token scopes Orca needs (read:user, read:repository,
read:pullrequest, write:pullrequest) in the Email & API token form so users
configure a working token up front instead of hitting missing-permission
errors when creating a pull request. Strings are translated in every locale.
Fixes#38652
Co-authored-by: Neil <neil@stably.ai>
command -v prints a shell function's bare name, so a claude/codex directory
or executable in the cwd passed the -x check and Orca replaced the user's
function. Skip the wrapper when a function with that name is already defined.
STA-13246
* fix(agent-hooks): let the last-status throttle apply to routine hook events
Each hook event re-recorded the pane's authority evidence, which bumped the
revision counters behind the "urgent persist" fingerprint even when only
observedAt moved. Every event then skipped the 5s throttle and rewrote
last-status.json. Update the stored evidence without bumping the revision when
the authority itself (launch token, connection, tab, worktree) is unchanged.
* test(agent-hooks): remove timer-racy persistence count assertions
* Open the new-tab landing when splitting a Chat UI pane
Splitting a chat with Cmd+D opened a terminal nobody asked for. The split now
opens an empty pane that shows the home-screen landing (New agent, New
Terminal, New Browser Tab, plus shortcuts); Cmd+W closes it. Chats in the
floating panel and inside terminal tabs keep their terminal split.
* Split landing review fixes: agent launch cancellation, browser policy, labels
- New Agent on the landing cancels like the keyboard shortcut when the user leaves the workspace or host
- Hide New Browser Tab where the creation policy hides it (paired web without streaming)
- Chat split actions read Split Right / Split Down; New Agent gets its own key
- Tour visibility reads the projection's existing group subscriptions
* Show the split landing only in panes a chat split opened
Other flows reserve an empty split group for content they already chose
(remote terminal splits, AI Vault resume, browser and source-control
opens). The landing, its Close collapse and the tour now apply only to
groups the chat split marked, kept in window-only state and dropped when
the group goes away.
* Move split landing marks with their groups on worktree rename
* Keep the rename test's chooser mark out of the cast fixture
* Read the landing's browser policy by workspace; keep Agent in the Japanese label
* Keep the passed split lesson in the agent sessions tour count
* Keep the workspace open on a waiting split landing when its last tab closes
* Keep a waiting split landing when its workspace is reopened; drop its close row when it is the only pane
* Let a waiting split landing satisfy automatic default seeding, not recovery
Restores main's agent-activation inventory gate (a chooser never bypasses
ownership checks). Each automatic default-surface decision (shared seeder,
deferred reseed, startup watcher, paired wake, stream bootstrap) now leaves
a waiting chooser in place, and the paired mirror keeps a marked chooser when
the host reports no tabs. Explicit launches and requested default tabs are
unchanged.
* Fill an emptied paired workspace with its waiting landings, layout and focus together
* Read landing labels through useTranslate for main's render-path ratchet
* Drop the split landing's subtitle