mirror of
https://github.com/stablyai/orca.git
synced 2026-11-19 04:23:57 +00:00
87fdb249648ce0796e5191a3022c8d3199eeae7b
6
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
533a31b742 |
fix(agent-launch): restarted agents keep the launch they ran with (#38998)
* feat(agent-session): keep the permission mode a Claude session reports Claude names its live permission mode on prompt, tool and Stop hooks. Keep the root agent's latest value on the provider session, next to effort, so a resume without a recorded launch can tell whether the session ran in bypass. Ports the capture from #36359 by Nelef. * fix(agent-launch): resume an unrecorded launch bare unless it reported bypass Without a recorded launch, every restart path now resumes with no settings Arguments, env or permission default; the configured Command still runs. A session whose root agent last reported bypassPermissions keeps its bypass flag, so a hand-typed claude --dangerously-skip-permissions keeps it while a bare hand-typed claude never gains one (#29898). Account-switch restart used the shared rule only for Claude; it now uses it for every agent. Thanks to JustinCMR (#37304) for finding the account-switch and cold-restore gaps. * fix(terminal): keep the launch recipe of a window-started agent in main A window spawn hands main its recipe, but main kept only the token and agent, so restarts that main runs (workspace sleep capture, closed-worker reopen) found no recipe and resumed bare. Keep it with the launch authority, the same gate that admits the token. * fix(orchestration): reopen a closed worker with the recipe it launched with A closed worker's pane record goes away with its tab, so orchestration send reopened it bare (#37693). The worker row now keeps the recipe Orca launched the agent with, keeps it when a later capture of the same launch arrives without one (main loses it on a daemon reattach), and a reopen prefers it over a pane record that may hold another launch of the conversation. Adapted from #37757 by Pr1p, without a new column. * fix(terminal): keep a slept pane's earlier recipe only for the same launch A host sleep capture without a recipe reused the pane's earlier record for the same conversation. That is right after a daemon reattach, when Orca's launch still runs but main lost its recipe, and wrong for an agent typed into the shell that resumed the conversation: it never ran that launch. * fix(agent-session): restore a paired pane with the recipe its host recorded A client restoring a pane on a paired host sends only its recorded Arguments, and the host filled the rest from its current settings. A saved restore now replays the host's own record for that pane, or, with none at all, resumes bare and keeps a bypass only when this host's hooks saw it reported. History and other user-chosen resumes keep current settings. * fix(terminal): replay a saved note only for the launch main still holds A note belongs to the agent in a pane only while main holds that launch's token: main admits it at spawn and retires it when the launch command finishes, and a daemon reattach restores neither. Worker, host sleep and hook/quit captures now take a note only from that attested launch, and no longer copy an earlier record's note by agent or conversation match, which a typed resume in the same shell also satisfies. With no attested launch the unrecorded rule applies. Replaces the inferred orcaLaunched / recipeLostPaneKeys flags and drops the mock-only reopen and fixture-echo worker tests. * fix(agent-status): take a pane's note from the launch main attests The window carried a pane's saved note into each new record by agent and conversation match, so an agent typed into the shell that resumed the same conversation inherited an earlier launch's bypass. Main now sends the note of the launch it still holds with each status, and the window records only that, its own launch registration, or, for a restored replay of the very status a record was written from, that record's note. /clear and compact keep the note because main still holds the same launch. * fix(orchestration): reopen a worker with its own recipe or none A worker without its own note took the note of whichever pane record held the same conversation. Its reopen now always passes a complete recipe: its own note, or the unrecorded rule. The unrecorded bypass is also scoped to Claude, whose hooks are the ones that report a root agent's permission mode. * fix(agent-session): restore a paired pane from its source pane, never current settings A saved restore on a paired host looked up the destination pane, which a Wake opens as a new tab, and fell back to the host's current settings whenever the client sent its partial Arguments. The client now names the source pane (to hosts advertising agent-session.restore-source-pane.v1), and the host replays its note for that pane or, with none, resumes bare keeping only a bypass its own hooks saw there. Older hosts keep today's behavior. * fix(terminal): re-arm a launch across a main restart while its agent still runs The daemon outlives main, so it now keeps main's admitted launch (token and note) and drops it when that launch's command finishes. On reattach main re-arms the launch only when the same agent still runs in the foreground: nothing can be typed into a daemon PTY while main is down, so a running agent there is the one the unretired note launched. A shell foreground clears the daemon's note; an unknown read, including every Windows read, declines. Older daemons keep no note, so restore declines there as before. * fix(terminal): the daemon retires a launch note when its command finishes A launch can finish while main is down, so main's own retirement never sees it and a hand-typed agent in that pane would later pass the reattach foreground check. * fix(agent-status): a fresh Claude start never inherits the last process's permission mode A hand-typed resume of the same conversation may run without the bypass the previous process had, so only /clear and compact carry the mode forward. * fix(agent-session): name a restore's source pane in the host's own keys A mirrored pane's key carries the desktop tab prefix, so the host's exact lookup missed its saved note. * fix(terminal): retire a daemon launch note by its token from the one retirement owner A delayed reattach result or a late retire could clear a newer launch's note. Retires now name the token they retire, the reattach checks its PTY before clearing, and re-arming the same launch keeps the daemon's completion scanner. * fix(agent-status): only the launch owner's statement changes a pane's note Main now states the attested note, or null for none, on every hook status. An OSC or display update makes no statement, so after a completed turn it no longer erases an Orca launch's note; a typed resume still drops it through main's null. * fix(terminal): an attach leaves alone a launch main already holds The renderer attaches a pane the CLI just launched before its agent starts, so the attach saw the shell and retired the new launch's daemon note. * fix(agent-status): a paired client keeps a pane's note only on its host owner's word The host's session-tabs frame now says whether the Orca launch it admitted still runs on the published incarnation, and the client applies that fact whichever writer wins the status. With an owner's word the conversation no longer decides; an older host that says nothing keeps the same-conversation rule. * refactor(agent-status): one decision picks a pane's note for every reader The live entry, quit capture, provider-session updates, account restart and cold restore now ask the same owner-aware decision. An owner's none is final and, when it turns, ends the pane's registry entry and saved note, locally and from a paired host's frame. Cold restore and account restart take that answer for a live invocation and read the saved record only when none is live. Inlines single-use wrappers. * refactor(agent-status): a paired retirement test reaches the cold-restore command; trim comments Replaces the projection and continuity tests with one transition: host frame retires the launch, the next OSC keeps no note, and the cold-restore command has no old bypass. * fix(agent-status): an owner's none retires the pane's matched launch registry entry * chore: satisfy changed-code gates (type guards, SAFETY notes, fixed test clock) * fix(agent-launch): a teams launch keeps its note; a legacy leaf id restores without throwing * refactor(daemon): keep the session launch note on the process base so session.ts stays in budget * fix(agent-launch): a restarted terminal main can't vouch for keeps main's earlier launch rule * fix(agent-launch): read the pane's current terminal; a finished launch settles an undecided pane * fix(agent-launch): undecided and held launches end with their process A finished command, a fresh launch or a replacement process settles an undecided pane; a newer attach or finish supersedes a foreground read still in flight; a legacy relay reattach without an incarnation stays undecided; a held launch applies only to the process it was recorded for. * refactor(terminal): watch and arm a created terminal's launch in one call Keeps terminal-create.ts within the 300-line budget after main's growth. * refactor(terminal): keep main's launch evidence in one immutable record Replace the undecided flag, the reattach check map and the re-arm's writes to main's orchestration launch fields with one launchEvidence object (unknown, gone for an incarnation, or held with its recipe), owned by launch-evidence.ts. - A fresh admitted launch is held; any other fresh process is gone. - A finished command or confirmed exit is gone, sticky for its process: no reattach, legacy or noted, can revive it. - A replacement retires its predecessor's evidence without deciding the newcomer, which may still prove its own launch through a reattach. - A reattach note is held only after a foreground read sees its agent; the evidence object fences that read. - A gone launch clears its recipe and blocks both refill sites; a deliberate sleep snapshot keeps its recipe past the launch it captured. - launchToken, launchIncarnationId and launchAgent writes match main. * fix(terminal): keep launch evidence through a first incarnation and sleep snapshots - Learning a process's first incarnation binds its held or gone evidence to it, so a later attach can neither revive a finished launch nor drop a running one; a known X->Y replacement is fenced as before and now also clears the predecessor's recipe. - A status from no Orca launch leaves a sleep snapshot of its session for the wake and never takes that snapshot's recipe into a live or quit record. * fix(terminal): record a runtime split's fresh shell as running no launch * chore: rerun CI on main with the typecheck fix |
||
|
|
83f8e6340d | refactor(shared): organize file operations and storage owners (#39746) | ||
|
|
e97b290cb8 |
test: remove 835 low-value tests (#39558)
Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com> |
||
|
|
193dd5726f |
Git Graph tab: all branches, commit details and file changes (#6746)
* Add Git Graph view showing all branches and commit history Adds a full-pane Git Graph tab that visualizes the whole repository — all local branches, remote-tracking branches, tags, merges, and HEAD — instead of only the current branch's linear history shown in the Source Control sidebar today. - Add an opt-in allRefs scope to the shared git-history loader so the graph query enumerates --branches --remotes --tags HEAD; the default current-branch path is unchanged. The flag is forwarded through the local IPC, SSH provider, and runtime RPC boundaries so it works in all environments. - New git-graph tab content type with a full-pane GitGraphPane that reuses the existing graph SVG/row components, virtualizes rows, and opens a commit's combined diff on click. Wired into the tab strip as a chip (activate/close/keyboard-cycle) mirroring the simulator pattern. - Entry point: an Open Git Graph button in the Source Control commits header (Cmd/Ctrl-click opens in a split). Closes #4521 Co-authored-by: Orca <help@stably.ai> * Address review: virtual-tab guards, nav-order, truncation copy - Treat the Git Graph (and mobile emulator) tab chip as a virtual tab: add an isVirtual contract to EditorFileTab/EditorFileTabContextMenu so rename, copy-path, copy-relative-path, and reveal-in-finder are disabled for tabs whose filePath is a display label, not an on-disk path. Prevents a rename on the synthetic 'Git Graph' path running a real file operation. - Forward gitGraphIds through the legacy reconcileTabOrder fallback in getActiveTabNavOrder so keyboard tab navigation does not drop git-graph tabs when no split-group layout exists yet. - Make the truncation banner explicit: 'Showing first N commits across all branches' (was 'of many'), across all locales. - Tests: virtual-tab hides path actions; git-graph survives the legacy nav-order fallback. Co-authored-by: Orca <help@stably.ai> * Forward allRefs over SSH relay and web runtime paths Two boundaries re-destructured git.history params and dropped the new allRefs flag, leaving the repo-wide Git Graph inert (linear default-branch history) for SSH and web-runtime worktrees: - src/relay/git-handler.ts: the relay host's git.history handler forwarded only { limit, baseRef }. Add allRefs so the SSH host enumerates all refs. Adds an end-to-end relay test (a feature-branch commit absent from linear history appears only when allRefs is forwarded). - src/renderer/src/web/web-preload-api.ts: the web preload history shim destructured only { worktreePath, limit, baseRef }. Forward allRefs. Also fix a request-id race in useGitGraphHistory: bump requestIdRef before the null-context early return so an in-flight fetch from a prior worktree can't resolve and overwrite the 'idle' state after the worktree clears. Co-authored-by: Orca <help@stably.ai> * Support filtered and pinned Git history Resolve branch and tag roots on the host, keep paging tied to the chosen revision set, and echo the applied filter across Git transports. Co-authored-by: Matheus Breguêz <matbrgz@gmail.com> * Add the Git Graph tab and commit details Open the all-branch view from Source Control or the command palette, preserve older clients' layouts, and keep the sidebar HEAD-only. * Restore files the main merge left at stale versions The earlier merge of origin/main kept older or missing copies of 61 files unrelated to the Git Graph (CI script tests, reliability gates, shard timings and five terminal runtime files). Take main's version of each so the PR changes only its own files. * Limit pinned history to explicit graph scopes Keep All and HEAD snapshots free of redundant ref names, and filter ref searches before nested-tag peeling. Default history requests retain unpinned paging without evicting graph tokens. Co-authored-by: Matheus Breguêz <matbrgz@gmail.com> * Preserve canonical placement for older graph clients Pass graph-free record deltas through without rebuilding layouts, retain existing empty groups, and translate content creation into canonical groups while preserving hidden graph tabs. * Retain Git Graph browsing state for the tab lifetime Own history retrieval, selection and scroll in one renderer controller that retires on close or owner/filter changes. Accumulate parent pages before publishing, share action-time workspace navigation, serialize ref searches, and scope refreshes to the workspace. * Apply Git Graph branch selections on picker close Keep checkbox changes local until dismissal, then normalize and apply one chosen ref set. Allow picker reads to use a qualified host scope. * Keep Git Graph navigation bound to its tab owner Retain the tab's qualified owner and Git connection across workspace focus changes. Newer selections and refreshes supersede pending parent navigation without losing fetched pages. Report stale workspace switches and let the commit menu handle empty space in the Branch / Tag cell. Cover twin-owner retention, superseded navigation and picker apply-on-close with renderer regressions. * Translate desktop layout commands against canonical state Resolve older desktops' visible groups, tab gaps and split paths inside the canonical mutation, including detach and cross-partition moves. Keep initial admission visibility-aware and cache graph presence for binding-only frames. * Refine Git Graph picker and owner transitions Discard branch drafts on Escape or owner changes, follow updated tab ownership, and report workspace lookup failures for the current owner. Keep parent navigation queued behind pending history loads. * Drop the redundant default from the exhaustive layout command switch * Align Git Graph with changed-code quality rules Use typed fixtures and an event guard, keep primitive styling on content wrappers, and prune loaded-commit bookkeeping after render. * Route Git Graph opening through the existing editor action Use workspace record selectors for stable owner inputs and remove two loading labels orphaned by the graph changes from all locale catalogs. * Preserve Git Graph selection and keep row content visible Refresh and token recovery retain loaded depth and selection in one accumulating operation. Keep the published view until it settles, and only fall back to the first commit after history is exhausted. Prioritize current and open-workspace refs, reserve their markers, clip wide graphs and retain filenames when long paths need truncation. * Bound Git Graph refresh and allow graph column resizing Restore the loaded depth without searching for vanished selections, retain the published result on retrieval errors, and keep newer selections visible. Allow the bounded graph column to expand to every lane through the existing resize mechanism. * Retain Git Graph history for errors without a message Detect failed retrieval independently of its message and cover an empty-message rejection in the existing partial-failure regression. * Retain Git Graph widths and preserve shifted selections Separate committed and live resize widths, retaining the chosen width for the graph tab lifetime. Allow one bounded extra history page for selections shifted by new commits, and give the resize separator a translated label. * Preserve nullable Git Graph owner fallback * Fix Git Graph layout imports after the RPC method move * Route the Git Graph owner connection through the source-control connection helper * Keep the Git Graph button idle in hidden Source Control sections * Re-probe Git Graph support when the owner's runtime status changes --------- Co-authored-by: Orca <help@stably.ai> Co-authored-by: Matheus Breguêz <matbrgz@gmail.com> |
||
|
|
c7eae748d8 |
fix(tabs): a session's own name replaces a quick-command tab name (#38677)
* fix(tabs): a session's own name replaces a quick-command tab name * fix(tabs): only a session's own name replaces a quick-command tab name Session titles now say whether they are the session's own name (a rename or a provider-generated name) or a stand-in such as the first prompt. A quick-command tab keeps its label until the session has a name; a name typed on the tab still wins. Titles from older hosts and saved tabs with no kind keep the label; old saved titles are asked for once. * fix(tabs): classify History-cached titles for session-id-only title requests * fix(tabs): keep a cached session title when its transcript cannot be reread * fix(tabs): keep a session title when its classification reread fails * fix(tabs): keep the transcript for an unclassified cached session title * test(tabs): keep the cached-title fixture's agent literal |
||
|
|
7bf0377072 | refactor: place terminal and workspace contracts with concrete owners (#38061) |