mirror of
https://github.com/stablyai/orca.git
synced 2026-11-16 10:58:10 +00:00
mobile-diff-github-layout
14
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
2ceaff4869 |
refactor(renderer): group workspace creation and launch owners (#40688)
* refactor(renderer): group workspace creation and launch owners * refactor(renderer): combine concrete workspace naming imports |
||
|
|
ef27841e29 |
refactor: group agent launch, status, and messaging owners (#40313)
* refactor: group agent launch, status, and messaging owners * refactor: consolidate direct owner imports * refactor: import pane ownership directly in status listeners |
||
|
|
00e25b55b2 |
Show one actionable error when an agent launch cannot prepare its workspace (#37220)
* fix: report agent launch failures once with actionable recovery * fix: keep terminal launch controls shown but waiting while the host connects Replace per-row pending metadata with one derived terminal-readiness flag on the agent menu model, kept out of picker identity keys. Terminal buttons and rows stay mounted and disabled while SSH or a paired server is still connecting; chat and Configure stay usable, and the terminal default is not changed. Repo targets with no workspace yet read the repo host's facts. Invalid Source Control arguments keep their existing actionable message. * fix: keep launch readiness and failure ownership consistent across pickers and fallbacks A host that is still connecting now declines a terminal launch silently at the launcher, including shortcuts and fallbacks, instead of reporting a failure. A terminal fallback refused behind a visible chat reports through that chat's notice rather than a second toast. The agent picker stays usable while only a terminal waits; an armed terminal rechecks readiness on Enter; a configured chat option no longer inherits the terminal's waiting state; waiting terminal controls say why. Invalid CLI arguments name the actual problem for every caller, the no-agent shortcut message is restored, and prospective repo readiness no longer rescans repos on unrelated store writes. * fix: keep the handoff dialog open when a host-waiting launch opens nothing A session continuation launched through the host's admission now waits for that launch to settle before reporting the handoff. When the host declines the chat and its terminal fallback is declined while the host is still connecting, nothing opens, so the dialog stays open for a retry instead of closing with no session and no message. * fix: let the handoff dialog close while its session is starting Cancel, Escape and outside clicks now close the Hand Off dialog even while a start is in flight; Start stays disabled with its spinner. Closing aborts agent detection if it is still running, and a dialog closed during detection starts nothing. A launch already sent settles on its own and reports through its existing owners. The in-flight start belongs to the request it was made for, so a late finish never closes, completes or blocks a dialog reopened since. * test: replace type assertions in launch refusal tests with typed fixtures * refactor: name the setup panel's launch helper launchSurface * perf: resolve a picker's terminal host only when ownership changes The terminal readiness check rebuilt the target's ownership chain and ran the full OS resolver on every store write, for every mounted picker. Each picker now keeps its target host and re-resolves it only when an ownership slice changes; other writes read just that host's connection and contact facts. Local hosts read nothing. The launcher's own pending decline uses the same host pieces from execution-host-facts, so the rule has one copy. * perf: word a declined chat's fallback failure without re-saving launches Wording the failed chat's notice after its terminal fallback was refused re-saved every retained launch record, though the wording itself is never saved. Listeners now hear about it without a save; lifecycle changes still save. The refused-fallback test moves to its own file and counts saves at two sizes. * test: narrow refused launch outcomes where tests read the opened tab launchAgentInNewTab now returns a refusal instead of a tab when the launcher declines, so tests that read the opened tab's surface or completion narrow it first. Fixes the web typecheck. * fix: keep Configure usable and show one reason on a waiting agent row While the host connected, each New Chat agent row was marked aria-disabled, so its Configure button read as disabled to assistive tech and keyboard. The row now only blocks its launch and points to its "Connecting…" reason. A row shows one reason, the one that stops its launch now, and the agent name keeps its width so it is not cut to a single letter. * test: cover distinct repo targets and host freshness in the picker perf contract Pickers for workspaces not created yet now count repo reads cold and after another host's row is republished, at two scales with a repeated-target control, and assert no unaffected renders. Two freshness controls follow the cached host: an owner moving from local to a connecting SSH host and back, and a paired server that is still checking versus verified with its OS. * fix: mark a waiting agent launch unavailable while Configure and chat stay usable An agent row's launch item also held its Configure button (New Chat) or its start-in-chat button (the + menu). Disabling the row while the host connected disabled those too; leaving it enabled made the waiting launch read as available and then do nothing. The launch item and those controls are now siblings. While the host connects the launch item is marked unavailable, dimmed and described "Connecting…", and stays focusable so arrow keys still reach the controls beside it. Configure and chat keep their own state. A chat started from Configure or the chat button goes through the row's guarded launch and closes the menu, without choosing the waiting item. * fix: release the agent row button's press listeners when a press is cancelled Each press on the button beside an agent row added a window listener that only a pointerup removed, so cancelled touches and closed menus left them behind. A press now owns one handler that removes both listeners on release, cancel, the next press or the row closing; drag release onto the button still chooses it. * fix: give the agent launch row item its own menu item variant The launch item beside Configure or the chat button restyled the shared menu item (transparent focus, dimmed while unavailable), which the design system gate rejects. That treatment is now the menu item's launch-row variant; the rendered rows are unchanged. * fix: route the menu's terminal host by owner and repair the e2e and ja checks The menu's terminal readiness now reads workspace records through the workspace record selectors and picks a not-yet-created workspace's repo by the host it names, without the focused-host fallback; with no host named it settles only when the id has one row, which reads the same. Its cached host is re-checked when the settings slice changes instead of reading the focus setting. E2E unit tests narrow refused launch outcomes, and the two new ja strings write Agent as the rest of the catalog does. * test: count a launch as opened only when it returned a surface A refused launch now returns its refusal instead of null, so the parity check asks whether a surface opened. * perf: keep menu readiness on the workspace's owner and index the twin fallback Terminal readiness re-resolved every mounted menu's host on any settings write, and an unstamped worktree whose project is listed both here and by a paired server walked the whole repo catalog to resolve. Readiness now resolves an existing workspace's host from its resource owner only, never the focused default a row-less setup terminal is created on, so settings writes leave it alone. The shared-project check reads that project's rows from the existing per-snapshot repo index instead of the whole catalog. Setup terminals and every route keep their behavior. * test: assert which readiness pickers render on each detected-twin update The detected-twin perf contract now checks render deltas per update: a catalog republication renders no picker, and stamping the first workspace with a checking server, then that server reporting its OS, renders only that workspace's pickers. * test: give the structured chat fixture's owner stub the menu's resource host The fixture replaces the whole worktree owner module with a stub, so the menu readiness check's new resource-host export was missing and the picker path threw before launching. The stub now answers both exports with the scenario's owner host. * Keep launch failures with one action owner on current menus * Align Start work regression with its remote launch target * Narrow refused launch outcomes in current contract tests * Assert notified refusals in existing launch regressions * Assert the refused keyboard launch receipt * Narrow successful web runtime launches in tests * Keep agent menu labels left aligned * Keep merged launch reporting within existing checks * Keep direct launch argument reads within the file limit |
||
|
|
23808bb73f |
refactor(renderer): organize host and terminal owners and remove forwarding shells (#39320)
* refactor(renderer): organize host and terminal implementation owners * fix(refactor): align active adoption reliability references * refactor(terminal): remove forwarding shells and stale mocks * fix(renderer): consolidate direct owner imports * fix(refactor): route incoming issue trust type to its owner * test(runtime): give independent status viewers separate pairing tickets * style(refactor): normalize rebased terminal mock formatting |
||
|
|
f308486115 |
Show Source Control for folder workspaces (#38831)
* Separate editor tab placement from content ownership * Show scoped Source Control sections for attached worktrees * Preserve active diff refresh and validate section catalogs * Complete folder section test worktree metadata * Use contextual types for scoped Source Control actions * Preserve optional scoped action parameters * Preserve editor ownership through restore, mirroring and workspace removal * Retire Source Control drafts only after confirmed owner removal * Limit section work to visible expanded repositories * Keep editor follow-up actions and bulk closes in their invoking views * Track the consolidated editor order writer in its owning module * Use complete typed fixtures for repair contracts * Preserve live editor placement during layout readback * Pass projected editor placement directly to serialization * Read attached worktree lineage from shared graph module * Retain inferred owner checks and scope placement retirement * Preserve selection in untouched workspaces during purge * Exercise editor placements in existing launch and lifecycle fixtures * Preserve shared buffer prompts and editor strip order * Pause inactive section context subscriptions * Keep section recovery and file actions in the folder workspace * Describe attached Source Control in folder workspace CLI help * Attribute Git metadata signals once per dispatch * Watch mounted source control sections outside the warm budget * Resolve section watches only for served filesystem roots * Restore restart-stable editor identity across SSH opens * Apply section terminal routing to explicit Chat choices * Include cross-store descendants in folder workspace panels * Keep cross-host recovery on its existing workspace route * Start cross-host section agents in their workspace without navigation * Update memoized Source Control labels on language changes * Remove unused terminal close-to-right implementation * Suspend inactive Source Control body observers * Retain base ref query while section observation pauses * Cover retained base ref search across section visibility * Resolve note menu ownership from the retained snapshot * Preserve section agent working directories and background placement * Keep Source Control sections active while their overlays are open * Read current settings when Source Control commands execute * Adapt editor and browser test stores to view subscriptions * Preserve bound store hooks for ordinary app views * Trust agent starts outside the placement workspace * Trust the section worktree through transient launch ownership * Extract editor follow-up file actions from the panel * Fail section launches when trust capability lookup fails Preserve explicit unsupported-host fallback, propagate lookup failures to the existing launch error path, and let the existing transport retry refresh rejected capability probes. * Follow the moved pane launch test in web configs * Preserve section file ownership during refresh and close * Share tab order removal across editor close paths * Verify companion editor close through the real store * Close all workspace split copies for legacy mobile file requests * Keep unmatched mobile close requests within their workspace * Reuse the agent menu render snapshot * Keep attached folder roots scoped to their resolved host * Apply repository trust decisions to the launch trust owner |
||
|
|
3228095e97 |
refactor(renderer): organize launch, workspace, browser and search owners (#38845)
* refactor(renderer): group launch, workspace, and browser owners * fix(renderer): restore workspace name Enter focus to agent picker |
||
|
|
318f543293 |
fix(agents): paired-host agent tabs use the host's launch settings (#38301)
* fix(agents): paired-host agent tabs use the host's launch settings Agent tabs opened on a paired host were replacing that host's permissions and Arguments with the desktop's settings. Let the host plan fresh launches, carry the user's choices separately, and preserve existing prepared launches when an older host cannot express them. Action Arguments replace configured Arguments while inheriting the host's permission settings; resumed sessions keep their recorded recipe. * fix(agents): paired-host agent tabs use the host's launch settings Preserve per-launch permissions on older paired hosts by compiling picks they cannot apply from their own settings. Keep authored Arguments separate from saved model defaults so a command's pinned model wins. Use the host's reported shell and execution platform for argument quoting, and remove unused prompt-delivery wrappers. * fix(agents): paired-host agent tabs use the host's launch settings Replace recognized permission flags from older paired hosts when a launch picks another permission, while preserving unrelated Arguments and ambiguous prepared launches. Keep multiline drafts working on Command Prompt hosts and omit chat-only permissions from terminal requests. * fix(agents): paired-host agent tabs use the host's launch settings Preserve per-launch permission choices that suppress the paired host's Full access flag even when the choice emits no flag itself. Compile these choices from the host snapshot when older launch preferences cannot carry them, while keeping unsupported OpenCode terminal permissions filtered out. * test: merge duplicate imports in paired launch options test * test: drop type assertions in paired launch options test * chore: lower focus-read ratchet baseline after removing creation wrappers * fix(agents): paired-host agent tabs use the host's launch settings Keep accepted inline fork drafts delivered when their mirrored tab is unavailable, and cancel launches whose pairing changes during negotiation. Keep action Arguments metadata on the tab route so injected workspace launch callbacks retain their contract. Update consumer fixtures to run lazy compatibility preparation and verify the final launch inputs and cancellation boundary. * fix(agents): paired-host agent tabs use the host's launch settings Keep pairing changes during legacy launch preparation silent and preserve the prompt for retry. Make picker tests exercise structured model picks on modern hosts while retaining prepared-command coverage for older hosts. * fix(agents): paired-host agent tabs use the host's launch settings A permission pick on an older paired host could turn desktop-configured Arguments into a launch override, including the desktop's model. Keep settings-seeded text out of the paired picker request so the host snapshot supplies defaults, while preserving explicitly edited launch Arguments. * fix(agents): paired-host agent tabs use the host's launch settings Keep permission-control choices separate from Arguments the user edited. Fresh paired terminal launches now share that ownership projection in the new-tab picker and continuation dialog, so a control change preserves the host's executable and environment settings. Explicit Arguments edits, including clearing the field, keep their existing launch behavior. Cover old-host and modern requests, explicit terminal/chat edits, and the continuation Start handler. Workspace creation keeps its existing path. * fix(agents): paired-host agent tabs use the host's launch settings Older paired hosts could inherit the desktop's model and permission defaults when the launch picker was configured or reopened. Read picker defaults and prepared launch recipes from the executing host, and compile edited Arguments using its settings. Preserve explicit empty edits, narrower permissions and draft prompts. Keep inherited choices neutral while host settings are unavailable, retaining the existing compatibility launch when no usable host recipe exists. * chore: merge duplicate type import and drop dead test branch * fix(agents): paired-host agent tabs use the host's launch settings Actions with explicit permission choices could unnecessarily read host settings and fall back to desktop preparation when those reads failed. Keep representable action Arguments on the host's authoritative launch path, and read inherited permissions only when the action needs them. Cover an explicit empty Arguments override and Ask with unavailable settings, preserving the host executable and environment without a permission bypass. * fix(agents): paired-host agent tabs use the host's launch settings Supply the paired host's default agent in the shortcut test instead of assuming the desktop's default applies. Keep a conflicting desktop default so the shortcut continues to verify the paired host owns its selection. |
||
|
|
d5f2a17cd2 | refactor: group agent launch contracts under concrete owners (#37915) | ||
|
|
747acba743 |
test: remove 46 low-value client and benchmark tests (#37818)
* test: remove 16 low-value behavior and UI tests * test: remove 30 low-value client and benchmark tests * test: prune timeout ratchet after test removal * test: correct remaining split benchmark coverage claims |
||
|
|
76472f27ce | refactor(settings): group runtime and host owners (#37804) | ||
|
|
fe78cff1aa |
test: remove 20 low-value tests across 11 files (#37404)
* test: remove 20 low-value test declarations * test: prune allowances for removed Git profiling suite --------- Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com> |
||
|
|
89f9ce08de |
refactor(shared): organize session contracts and projections (#36979)
* refactor(shared): organize session contracts and projections * chore: tighten dropped-path flaky pattern allowance * docs: preserve current agent instructions with valid formatting |
||
|
|
76cf164cf9 |
Chat UI leaves Experimental: each agent's Chat or CLI choice decides what opens (#36110)
* Chat UI leaves Experimental: each agent's Chat | CLI choice decides launches Remove the experimentalNativeChat switch and every gate on it. The Chat settings page, Default Agent Chat | CLI choice, + menu Chat/CLI rows, source-control surface choice, Antigravity chat section and orchestration chat-error switch are always present. What a new launch opens comes only from the per-agent choice (no saved choice opens a chat) plus the existing support checks. - One lookup, nativeChatPreferenceFor, keyed by agent id so host-registered agents read the same way; unreadable settings still open a terminal. - A relayed desktop stamp (nativeChatDefault) maps onto the launched agent; an explicit surface still wins. Old phones' createSupport keeps admitting by the host's per-agent choice. - settings.get stops publishing the retired switch keys; nothing in the repo reads them from a host. - Startup chat sync and hydration run when some agent can open as a chat or the machine already holds chats. - The retired key is stripped on load. The one-time upgrade tip from the chat upgrade is retired with its audience record; a new record, captured once from the raw profile, marks which existing profiles had Chat UI off. - The window-side AI-button tab path, which only ran with the switch off, is deleted. * Keep profiles that had Chat UI off on the terminal Existing users who never turned Chat UI on would otherwise see new agent launches open as chats, since an agent without a saved choice now opens as a chat. The one-time load step that records the new audience also sets every known agent to CLI for those profiles, in the same save and only when the record was absent, overwriting saved chat choices the old switch masked. Profiles that had Chat UI on and new profiles are untouched. Browser profiles keep their own settings, so the web client does the same once: a stored switch that is not on seeds CLI choices, and dropping the key marks the step done. Agents first seen after this step open as chats. * Agents without a saved Chat | CLI choice open as their CLI An agent with no saved choice now opens in the terminal for everyone, including fresh installs and agents first seen later. The one-time load step carries what launches opened while Chat UI was experimental: with the switch on, every known agent without a saved choice is saved as chat; with it off, chat choices the switch masked are saved as CLI. Existing profiles join the launch tip audience whether the switch was on or off. Browser profiles get the same carry from their saved key. The startup chat restore and host agent list now run only when some agent is saved as chat or the runtime holds chats. * Preserve owned terminal launches and local chat choices * Clarify chat and terminal support * Explain worker CLI integration timeout budget * Use checked annotations for chat graduation test fixtures * Store agent surface default separately from per-agent overrides * Preserve explicit Chat intent across default changes * Preserve current browser settings during host replies * Correct browser settings factory and regression types * Name exported launch fixture mock types and clarify agent defaults * Preserve settings fallbacks and complete launch test lifecycles * Check allocated tab identity before launch fixture interpolation * Register combined integration project for compiler parity probes * Use checked settings in the launch test fixture * Preserve retired Chat preference data privately * Align chat E2E fixtures and capture pane lifecycle evidence * Use typed raw settings in retention contracts * Consolidate transcript diagnostic imports * test: align chat fixtures with live pane and native menu contracts * test: capture relay tab selection loss diagnostics * test: wait for owned shells before synthetic chat fixtures * test: preserve all-host visibility in SSH observer * test: bind synthetic transcript fixtures before provider seeding * test: assert selected chat owner after narrow image preview * ci: allow fifth compiler project to complete comparison * Type the web-terminal fixture's chat map without an assertion * Right-click the selection itself in the chat copy spec |
||
|
|
12edee3ac6 |
Choose default models and effort for agents (#36210)
* Add host-owned model and effort defaults to agent settings * Unify terminal defaults and raw argument precedence * Keep agent model defaults typed through creation * Preserve quick-create prompt through preparation * fix: complete execution-host preference boundary and CI contracts * Preserve raw options until a replacement is emitted * Complete launch choice ownership and consumer contracts * Align launch contracts with compiler boundaries and consolidate proof * Name exported fixture mocks and verify ordered chip removal * Preserve typed choices across compound legacy publication edits * Preserve non-emitted composed launch choices through legacy edits * Preserve rollback omissions and settle agent launches before success * Carry terminal draft ownership through launch completion * Keep inline draft delivery independent of terminal projection * test: consolidate launch ownership contracts * test: check web launch fixture array types * test: align launch fixtures and conformity records * test: import the shell-ready marker from its declaring module * test: give caller routing the web host tab's completion contract |