* fix(contextual-tours): don't restart the agent sessions tour for existing users
v1.4.249 prepended a "New agents start here" step to the workspace agent
sessions tour. No earlier action completes it, so long-time users who never
closed the old tour (usually because they had already split panes) now see
it from step 1. Mark it seen at startup for profiles that finished
onboarding before that release; new users still get the full tour.
* test(contextual-tours): cover which profiles skip the agent sessions tour
Profiles still in onboarding, or onboarded at or after the v1.4.249 release,
keep the tour; earlier profiles get it marked seen without losing other seen tours.
* fix(contextual-tours): don't reopen the agent sessions tour for users who already split
Replace the startup cutoff backfill with a rule derived from what the user did:
a tour never auto-starts after one of its actions is already done (unless it is
already running this session or replayed), and a start never lands before the
latest done step, so steps added ahead of the user's progress can't rewind it.
* perf(contextual-tours): stop watching the page for a tour progress already blocks
* fix(contextual-tours): decide the progress block inside the tour effect
Selecting the derived flag ran it against partial test stores during render; read
the raw fields and decide in the effect, like the session-consumed check.
---------
Co-authored-by: m4air <m4air@Mac.localdomain>
Co-authored-by: Brennan Benson <79079362+brennanb2025@users.noreply.github.com>
On a host whose temp directory is full or unwritable, every worker_done
failed and the task never settled (#38123). The settlement runs inside
savepoints, and SQLite keeps savepoint journals in a temp file by default.
When that file cannot be written, SQLite rolls back the whole transaction
itself, so our own rollback then failed with 'cannot rollback - no
transaction is active' and hid the real error. Heartbeats and questions
use no savepoints, which is why they kept working.
The orchestration database now keeps temp storage in memory, and the
lifecycle rollback skips when SQLite already ended the transaction so any
remaining failure of this kind reports its own error.
#38325 made the question card's answer field a textarea, so
findNativeChatAnswerField (HTMLInputElement-only) can no longer match.
The bridge's 'origin instanceof HTMLInputElement' branch was already
unreachable since #32035 stopped the context menu passing a paste origin;
the only remaining origin caller (app-menu paste) passes the queued-editor
textarea from findNativeChatPasteField. Remove the branch, the helper, and
the test that only exercised it by calling the bridge directly.
* Highlight the first agent search match that Enter picks
Co-Authored-By: Claude <noreply@anthropic.com>
* Move the search-default highlight into the dropdown menu primitive
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
* test: trim redundant notebook and editor tests
* test: remove implementation-budget notebook and PDF tests
---------
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>
Tokenize visible diff-pane lines when a diff editor's model, hidden areas or layout change, so outer-scrolled combined-diff sections paint coloured (STA-12770).
Use the shared agent picker for Source Control Customize and AI-author setup. Preserve existing Arguments, templates, Custom commands, model/effort choices and settings ownership; keep nested menus and tooltips within their dialog portal.
Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: Courtenay <1909814+hdsheena@users.noreply.github.com>
Co-authored-by: Andy Zhang <hiandyzhang@gmail.com>
* fix(pi): keep a native chat awake while its background subagents run
The idle sweep stopped a Pi chat 30 quiet minutes after its last turn even
while pi-subagents workers it had started in the background were still
running. On Windows those workers are children of Pi and died with it, so
the coordinator never got their results.
Pi extensions with detached work already declare it through the shared
session-liveness registry that Pi hosts read before idle eviction, and
pi-subagents registers there. Native chat runs Pi as a child process, so
Orca now loads a small bridge extension into native-chat Pi launches that
installs that registry at load and reports, over Pi's RPC stdout, whether
the session has active providers. The Pi adapter keeps the last report and
the idle sweep treats it like provider-held sends: the chat is not stopped
while work is declared, and idles a full window after it ends. Nothing else
reads it, so clear and compaction are unchanged.
Tracked in #28710.
* fix(pi): harden the background-work bridge after review
Keep the bridge ticking after a failed report so the next answer is
re-derived, validate registrations the same way the reference host does,
log a bridge that could not be written, and use type guards in its test.
* fix(pi): confirm Pi background work at idle-stop time
A cached report could be stale when work starts between samples, so the
idle sweep now asks a running child's provider right before stopping it
and stops only on a fresh idle answer. Pi's bridge answers requests that
Orca drops into a private per-child folder, replying on its status line,
so the probe never becomes a dialog or a prompt other extensions or the
model would see. A child launched without the bridge stops as before;
one with the bridge but no ready instance is left for the next sweep.
* test(pi): replay the bridge's recorded probe answers
Recorded on Windows from Pi 1.5.0 with pi-subagents 0.84.0 and the bridge:
ready, active while a worker ran, idle after its wake turn, and shutdown.
* fix(pi): let the Pi child own its probe folder and reject malformed answers
A launch abandoned before Pi started left its prepared folder behind, so
the bridge now creates the folder itself. An answer with no probe pending
could throw while reading Pi's output; replies are now matched exactly and
anything else times out as unknown. Leftover folders are reclaimed only
when their Orca process is proven gone.
* test(pi): reproduce an unasked-for answer from the ready bridge
* fix(native-chat): apply an idle window changed while a provider answered
The idle stop now re-reads the chat idle setting after the provider's
answer, so switching a chat to Never during the probe keeps its agent.
Normalize each Pi launch's private probe folder in the launch parity
snapshots, which now include the background-work bridge.
* fix(session-tabs): send per-client frames without projecting them twice
A frame sent to one client (a tab it opened, picked or reopened) was already
that client's projection, but delivery projected it again. That stacked the
:client-navigation epoch suffix and the selection revision, so the client
treated it as another publication and fenced it. A link clicked in a server
browser page then only brought its new tab forward the first time.
* test(session-tabs): fold the per-client frame publication check into the caller-selection test
* fix(mobile): the chat Send button keeps desktop's arrow while the agent works
#36588 swapped the phone's send icon and label for Queue or Steer while
a turn ran; desktop keeps the plain Send arrow and offers the other way
through Cmd/Ctrl+Enter. The phone now matches, with hold as its
alternate.
* test(mobile): the send button keeps its arrow while the agent works
Use the shared searchable agent picker in Quick Commands while preserving the full catalog, disabled-agent explanations, independent form drafts and saved commands.
Keep dialog search focused through opening and host-preference reloads, and avoid setup-only cleanup for agent-only menus.
The @ and / suggestion list lifts itself to the menu layer only inside a
popover. Since #37576 the new-tab agent setup is a dropdown submenu on the
same z-[70] layer, so the list stayed at z-50 and drew behind it.
The @ file and slash suggestion list was placed once from the composer's
viewport rect and only re-measured on composer resize, ancestor scroll or
window resize. Dragging the floating panel or resizing it from its bottom
edge moved the composer without any of those, so the list stayed behind,
over the transcript or the message box. Near the top of the window it also
ran off-screen.
Position it with floating-ui's autoUpdate and computePosition, which follow
any anchor movement and cap the height to the space above the composer.
Rows show their project, two-line layout with fixed time/size columns and hover actions; Ignore can be undone per row; delete confirmation reads 'Delete N workspaces?'. Fixes Ignore/Stop ignoring being reverted by streamed scan frames or scan settlement, and the git-unknown flash on open/close.
Co-authored-by: Jingyue-Wu <75918217+Jingyue-Wu@users.noreply.github.com>
* fix(dictation): keep the transcript when the composer's stop button ends dictation
* fix(dictation): leave focus where the user moved it when late text lands
* fix(native-chat): don't double the space before text that brings its own
* refactor(native-chat): name the draft-only insert for what it does
* 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.