Community PR triage
Repository: stablyai/orca
Four-week range: August 1, 2026 2:15 PM through August 29, 2026 2:15 PM (America/Phoenix, MST, UTC−07:00)
Generated: 2026-08-29T21:31:51.438Z
Limitations: 1486/1486 PR descriptions and recent discussions were available at generation time; missing evidence is marked Low confidence. Files are capped at 20 per PR in the inventory. Check rollups are summarized, not a substitute for inspecting every job. Mergeability Unknown is not treated as safe. Older-overlap search is complete only for deep-reviewed clusters.
Find and filter
Showing 1486 PRs in 1402 clusters
Cluster decision queue
| Priority | Cluster | PRs | Combined outcome | Relationship | Recommended decision | Confidence |
|---|---|---|---|---|---|---|
| P1 | 1Password agent-skill setup panel in the integration card (stacked on #12947) | #13042 | 1Password agent-skill setup panel in the integration card (stacked on #12947) | Standalone | Request changes | Medium |
| P1 | add --kind folder to repo add | #13359 | add --kind folder to repo add | Standalone | Request changes | Medium |
| P1 | add "Open With" submenu listing OS-registered apps | #13994 | add "Open With" submenu listing OS-registered apps | Standalone | Review soon | Medium |
| P1 | add `orca linear project create` (3/4) | #15042 | add `orca linear project create` (3/4) | Standalone | Defer | Medium |
| P1 | add `orca linear project edit` (4/4) | #15126 | add `orca linear project edit` (4/4) | Standalone | Request changes | Medium |
| P1 | add `orca linear project update add` (2/4) | #15034 | add `orca linear project update add` (2/4) | Standalone | Defer | Medium |
| P1 | add a native Plane (plane.so) task provider | #15329 | add a native Plane (plane.so) task provider | Standalone | Review soon | Medium |
| P1 | add a session-safe shared MCP tools bridge runtime | #16221 | add a session-safe shared MCP tools bridge runtime | Standalone | Review soon | Medium |
| P1 | add active pane border for the focused split pane | #16735 | add active pane border for the focused split pane | Standalone | Review soon | Medium |
| P1 | add agent health and CLI updates | #13009 | add agent health and CLI updates | Standalone | Review soon | Medium |
| P1 | add agent project read commands (1/4) | #15024 | add agent project read commands (1/4) | Standalone | Defer | Medium |
| P1 | add API-key-based ClinePass usage tracking | #13827 | add API-key-based ClinePass usage tracking | Standalone | Review soon | Medium |
| P1 | add Auggie status hooks | #16287 | add Auggie status hooks | Standalone | Review soon | Medium |
| P1 | add automation model options and launch at login | #16405 | add automation model options and launch at login | Standalone | Review soon | Medium |
| P1 | add Brazilian Portuguese (pt-BR) as a supported UI language | #15629 | add Brazilian Portuguese (pt-BR) as a supported UI language | Standalone | Review soon | Medium |
| P1 | add CLI import/unimport for existing worktrees | #13733 | add CLI import/unimport for existing worktrees | Standalone | Review soon | Medium |
| P1 | add collapsible folder groups for tabs and sidebar agents | #15109 | add collapsible folder groups for tabs and sidebar agents | Standalone | Review soon | Medium |
| P1 | Add command palette shortcut keybinding | #16793 | Add command palette shortcut keybinding | Standalone | Review soon | Medium |
| P1 | add curated appearance packs | #17214 | add curated appearance packs | Standalone | Defer | Medium |
| P1 | add default worker, model, and effort UI | #12431 | add default worker, model, and effort UI | Standalone | Review soon | Medium |
| P1 | add Droid agent support and composer-on-top layout | #13625 | add Droid agent support and composer-on-top layout | Standalone | Request changes | Medium |
| P1 | add durable Run capacity targets | #16852 | add durable Run capacity targets | Standalone | Review soon | Medium |
| P1 | add forge provider plugin extension point | #15315 | add forge provider plugin extension point | Standalone | Review soon | Medium |
| P1 | add Freebuff as a first-class CLI agent | #17065 | add Freebuff as a first-class CLI agent | Standalone | Review soon | Medium |
| P1 | add French UI locale | #16455 | add French UI locale | Standalone | Review soon | Medium |
| P1 | add Gajae Code as a supported TUI agent | #13952 | add Gajae Code as a supported TUI agent | Standalone | Review soon | Medium |
| P1 | add Gajae Code to the built-in agent registry | #15025 | add Gajae Code to the built-in agent registry | Standalone | Review soon | Medium |
| P1 | add generic Custom AI Provider usage tracking | #16224 | add generic Custom AI Provider usage tracking | Standalone | Review soon | Medium |
| P1 | add Google Gemini & Antigravity token and cost usage tracking | #16647 | add Google Gemini & Antigravity token and cost usage tracking | Standalone | Request changes | Medium |
| P1 | add graph cost report | #12125 | add graph cost report | Standalone | Request changes | Medium |
| P1 | add Huly task provider integration | #14054 | add Huly task provider integration | Standalone | Defer | Medium |
| P1 | add IBM Bob agent support (Bob Shell 2.x) | #14895 | add IBM Bob agent support (Bob Shell 2.x) | Standalone | Review soon | Medium |
| P1 | add inline text color formatting | #16250 | add inline text color formatting | Standalone | Review soon | Medium |
| P1 | add intermediate Auto permission mode across supported harnesses | #13348 | add intermediate Auto permission mode across supported harnesses | Standalone | Request changes | Medium |
| P1 | add JetBrains Junie as a supported agent | #16472 | add JetBrains Junie as a supported agent | Standalone | Review soon | Medium |
| P1 | add Jira as a mobile task provider | #13126 | add Jira as a mobile task provider | Standalone | Request changes | Medium |
| P1 | add Kimchi agent support | #15922 | add Kimchi agent support | Standalone | Review soon | Medium |
| P1 | add live appearance previews and backgrounds | #15525 | add live appearance previews and backgrounds | Standalone | Review soon | Medium |
| P1 | add local Paperclip task source | #17251 | add local Paperclip task source | Standalone | Defer | Medium |
| P1 | add local terminal bridge stream | #13127 | add local terminal bridge stream | Standalone | Request changes | Medium |
| P1 | add managed credential profiles | #13275 | add managed credential profiles | Standalone | Request changes | Medium |
| P1 | add managed Grok and Gemini homes | #13276 | add managed Grok and Gemini homes | Standalone | Request changes | Medium |
| P1 | add MiniMax Code as a supported TUI agent | #14886 | add MiniMax Code as a supported TUI agent | Standalone | Review soon | Medium |
| P1 | add Monokai and explicit light/dark color theme options | #14038 | add Monokai and explicit light/dark color theme options | Standalone | Review soon | Medium |
| P1 | add My GitHub panel — sign in, browse, clone, and clean up your own repos | #17190 | add My GitHub panel — sign in, browse, clone, and clean up your own repos | Standalone | Defer | Medium |
| P1 | add New Group button and group selector in add-project dialog | #15765 | add New Group button and group selector in add-project dialog | Standalone | Review soon | Medium |
| P1 | add OCaml and MLX syntax highlighting | #16421 | add OCaml and MLX syntax highlighting | Standalone | Review soon | Medium |
| P1 | add OpenCode native chat support | #13287 | add OpenCode native chat support | Standalone | Request changes | Medium |
| P1 | add opencode2 (v2 beta) support | #14053 | add opencode2 (v2 beta) support | Standalone | Review soon | Medium |
| P1 | add opt-in auto-submit for work item Start | #16864 | add opt-in auto-submit for work item Start | Standalone | Review soon | Medium |
| P1 | add orca skills remove for headless uninstall | #13170 | add orca skills remove for headless uninstall | Standalone | Request changes | Medium |
| P1 | add pure black dark variant | #16727 | add pure black dark variant | Standalone | Review soon | Medium |
| P1 | add Qoder CLI (qodercli) as a supported TuiAgent | #15291 | add Qoder CLI (qodercli) as a supported TuiAgent | Standalone | Review soon | Medium |
| P1 | add Qoder CLI (qodercli/qoderclicn) agents and supervised-hook registration for Qwen Code | #12910 | add Qoder CLI (qodercli/qoderclicn) agents and supervised-hook registration for Qwen Code | Standalone | Request changes | Medium |
| P1 | add Qoder CLI as a supported TUI agent | #13311 | add Qoder CLI as a supported TUI agent | Standalone | Request changes | Medium |
| P1 | add read-only Amphetamine session integration on macOS | #15932 | add read-only Amphetamine session integration on macOS | Standalone | Review soon | Medium |
| P1 | add reasonix TUI agent provider | #12330 | add reasonix TUI agent provider | Standalone | Request changes | Medium |
| P1 | add rich input composer | #12932 | add rich input composer | Standalone | Request changes | Medium |
| P1 | add Russian (ru) UI language support | #16736 | add Russian (ru) UI language support | Standalone | Review soon | Medium |
| P1 | Add sequencer continue/skip actions and branch identity display | #15382 | Add sequencer continue/skip actions and branch identity display | Standalone | Request changes | Medium |
| P1 | add setting to skip WSL distros in session history scan | #16961 #17072 | Coordinate 2 proposals for add setting to skip WSL distros in session history scan. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | add shell history opt-out | #16071 | add shell history opt-out | Standalone | Review soon | Medium |
| P1 | add Shortcut task provider | #16249 | add Shortcut task provider | Standalone | Review soon | Medium |
| P1 | add Show Whitespace toggle option in diff viewer | #15120 | add Show Whitespace toggle option in diff viewer | Standalone | Review soon | Medium |
| P1 | add spatial pane focus | #15068 | add spatial pane focus | Standalone | Review soon | Medium |
| P1 | add worker-start --spec to create and dispatch in one call | #13540 | add worker-start --spec to create and dispatch in one call | Standalone | Request changes | Medium |
| P1 | add ZCode as a first-class supported agent | #13965 | add ZCode as a first-class supported agent | Standalone | Review soon | Medium |
| P1 | add ZeroClaw agent connector and AI Vault scanner | #16597 | add ZeroClaw agent connector and AI Vault scanner | Standalone | Review soon | Medium |
| P1 | address-bar convergence — previews and browser tabs convert in place (STA-5681) | #16998 | address-bar convergence — previews and browser tabs convert in place (STA-5681) | Standalone | Review soon | Medium |
| P1 | agent context panel — instruction files, skills, MCP, hooks and plugins per workspace | #14875 | agent context panel — instruction files, skills, MCP, hooks and plugins per workspace | Standalone | Review soon | Medium |
| P1 | allow language packs to declare a native display name | #13140 | allow language packs to declare a native display name | Standalone | Review soon | Medium |
| P1 | app chrome can match terminal theme; configurable status-bar usage format | #16768 | app chrome can match terminal theme; configurable status-bar usage format | Standalone | Request changes | Medium |
| P1 | apply client page reconciliation | #14763 | apply client page reconciliation | Standalone | Defer | Medium |
| P1 | auto-generate titles for the panes in a split tab | #15781 | auto-generate titles for the panes in a split tab | Standalone | Review soon | Medium |
| P1 | background image behind terminal panes (#7714) | #15836 | background image behind terminal panes (#7714) | Standalone | Review soon | Medium |
| P1 | block-clone shared paths on ReFS | #16619 | block-clone shared paths on ReFS | Standalone | Review soon | Medium |
| P1 | bound page reconciliation execution | #14756 | bound page reconciliation execution | Standalone | Defer | Medium |
| P1 | bound producer pause so a lost renderer ACK cannot wedge a PTY | #17216 | bound producer pause so a lost renderer ACK cannot wedge a PTY | Standalone | Review soon | Medium |
| P1 | bound the custom sound's dedupe window so a stalled element cannot silence every later notif | #15938 #15940 | Coordinate 2 proposals for bound the custom sound's dedupe window so a stalled element cannot silence every later notif. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | bounded host-aware Cursor sidecar history | #14582 | bounded host-aware Cursor sidecar history | Standalone | Review soon | Medium |
| P1 | carry sender liveness evidence in every Delivery | #15272 | carry sender liveness evidence in every Delivery | Standalone | Review soon | Medium |
| P1 | Claude permission mode picker in the composer, and fix fast mode | #14745 #15681 | Coordinate 2 proposals for Claude permission mode picker in the composer, and fix fast mode. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | Codex structured chat — full migration (host runtime, journal, wire, desktop + mobile client | #13438 | Codex structured chat — full migration (host runtime, journal, wire, desktop + mobile client | Standalone | Request changes | Medium |
| P1 | Codex structured chat without TUI toggle | #14600 | Codex structured chat without TUI toggle | Standalone | Review soon | Medium |
| P1 | copy unresolved PR/MR comments prompt to clipboard | #13701 | copy unresolved PR/MR comments prompt to clipboard | Standalone | Review soon | Medium |
| P1 | create subgroups and move groups from the group menu | #15802 | create subgroups and move groups from the group menu | Standalone | Review soon | Medium |
| P1 | create worktrees on a per-workspace environment recipe | #17026 | create worktrees on a per-workspace environment recipe | Standalone | Review soon | Medium |
| P1 | detach a terminal tab group into its own window | #14997 | detach a terminal tab group into its own window | Standalone | Review soon | Medium |
| P1 | detach live tabs into secondary windows | #16203 | detach live tabs into secondary windows | Standalone | Review soon | Medium |
| P1 | detect a wedged supervised worker and surface it as a signal | #15273 | detect a wedged supervised worker and surface it as a signal | Standalone | Review soon | Medium |
| P1 | durable session records and persisted single-writer lease (native-chat phase 1a) | #13084 | durable session records and persisted single-writer lease (native-chat phase 1a) | Standalone | Request changes | Medium |
| P1 | enforce finite worker lifecycles | #13337 | enforce finite worker lifecycles | Standalone | Request changes | Medium |
| P1 | enforce isolated worker authority | #16827 | enforce isolated worker authority | Standalone | Review soon | Medium |
| P1 | expose deterministic manual queue rank | #16080 | expose deterministic manual queue rank | Standalone | Defer | Medium |
| P1 | expose HTML browser action | #15839 | expose HTML browser action | Standalone | Review soon | Medium |
| P1 | expose nested repository scan and import | #14514 | expose nested repository scan and import | Standalone | Review soon | Medium |
| P1 | expose workspace notes panel | #13045 | expose workspace notes panel | Standalone | Request changes | Medium |
| P1 | expose worktree --pr for linked GitHub pull requests | #14908 | expose worktree --pr for linked GitHub pull requests | Standalone | Review soon | Medium |
| P1 | Feat multi agent collabofeat(orchestration): migrate multi-agent collaboration to current ru | #16515 | Feat multi agent collabofeat(orchestration): migrate multi-agent collaboration to current ru | Standalone | Review soon | Medium |
| P1 | Feat/orca canvas view and control room | #16872 | Feat/orca canvas view and control room | Standalone | Review soon | Medium |
| P1 | filter workspaces by card status | #13999 #14633 | Coordinate 2 proposals for filter workspaces by card status. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | GLM Coding Plan usage visibility | #16772 | GLM Coding Plan usage visibility | Standalone | Review soon | Medium |
| P1 | Improved markdown rendering in editor and preview | #13535 | Improved markdown rendering in editor and preview | Standalone | Request changes | Medium |
| P1 | in-app audio/video preview from the file explorer | #15733 | in-app audio/video preview from the file explorer | Standalone | Review soon | Medium |
| P1 | Keep the SSH connection alive when a terminal outruns a slow link | #12220 | Keep the SSH connection alive when a terminal outruns a slow link | Standalone | Defer | Medium |
| P1 | keep unstamped local git worktrees routable when a runtime is saved | #16829 | keep unstamped local git worktrees routable when a runtime is saved | Standalone | Review soon | Medium |
| P1 | let orchestration-dispatched workers stay silent | #15153 | let orchestration-dispatched workers stay silent | Standalone | Review soon | Medium |
| P1 | let plugin keybindings opt into terminal focus | #15725 | let plugin keybindings opt into terminal focus | Standalone | Review soon | Medium |
| P1 | let the screen sleep in Keep-computer-awake mode (option A: 1-line) | #17183 #17184 | Coordinate 2 proposals for let the screen sleep in Keep-computer-awake mode (option A: 1-line). | Competing | Choose one preferred solution | Medium |
| P1 | let users remove the Computer Use skill | #13163 | let users remove the Computer Use skill | Standalone | Review soon | Medium |
| P1 | link worktrees to pull requests | #13129 | link worktrees to pull requests | Standalone | Request changes | Medium |
| P1 | load more commits in the git history panel | #14305 #14405 | Coordinate 2 proposals for load more commits in the git history panel. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | make Close Others / To The Right / To The Left bindable (#16614) | #17053 | make Close Others / To The Right / To The Left bindable (#16614) | Standalone | Review soon | Medium |
| P1 | make Move Tab to Split keybindable | #16324 | make Move Tab to Split keybindable | Standalone | Review soon | Medium |
| P1 | make multi-agent workflows durable | #16904 | make multi-agent workflows durable | Standalone | Review soon | Medium |
| P1 | make the heartbeat state a coordinator reads, not mail that wakes it | #15173 | make the heartbeat state a coordinator reads, not mail that wakes it | Standalone | Review soon | Medium |
| P1 | make workspace split divider color configurable | #14893 | make workspace split divider color configurable | Standalone | Review soon | Medium |
| P1 | manage current issue cycles | #16082 | manage current issue cycles | Standalone | Defer | Medium |
| P1 | managed-account failover and acceptance receipts for supervised workers（受監督工人多帳號遞補與驗收回執） | #14290 | managed-account failover and acceptance receipts for supervised workers（受監督工人多帳號遞補與驗收回執） | Standalone | Review soon | Medium |
| P1 | Merge codex-structured-core into Claude lane | #15356 | Merge codex-structured-core into Claude lane | Standalone | Request changes | Medium |
| P1 | move a live terminal tab to another worktree | #15108 | move a live terminal tab to another worktree | Standalone | Review soon | Medium |
| P1 | name the driver of store write chains before React #185 throws | #15076 | name the driver of store write chains before React #185 throws | Standalone | Review soon | Medium |
| P1 | named command profiles to launch an agent under a second CLI command | #16798 | named command profiles to launch an agent under a second CLI command | Standalone | Defer | Medium |
| P1 | negotiate page reconciliation commands | #14759 | negotiate page reconciliation commands | Standalone | Defer | Medium |
| P1 | open a folder passed as a launch argument as a project | #16476 | open a folder passed as a launch argument as a project | Standalone | Review soon | Medium |
| P1 | open clicked links in the pane to the side | #13392 | open clicked links in the pane to the side | Standalone | Review soon | Medium |
| P1 | open files and links from the agent preview terminal | #16787 | open files and links from the agent preview terminal | Standalone | Review soon | Medium |
| P1 | open sibling files from the path header | #16758 | open sibling files from the path header | Standalone | Review soon | Medium |
| P1 | open the originating session on click | #15957 | open the originating session on click | Standalone | Review soon | Medium |
| P1 | opt-in 1Password op:// secret resolution for tabs + bundled onepassword agent skill | #12947 | opt-in 1Password op:// secret resolution for tabs + bundled onepassword agent skill | Standalone | Request changes | Medium |
| P1 | opt-in zmx-backed durable SSH terminals | #12798 | opt-in zmx-backed durable SSH terminals | Standalone | Request changes | Medium |
| P1 | optional agent-state emoji in tab titles | #15794 | optional agent-state emoji in tab titles | Standalone | Defer | Medium |
| P1 | pick a base branch when creating a workspace from a task | #15748 #17250 | Coordinate 2 proposals for pick a base branch when creating a workspace from a task. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | point a Design Mode annotation at a second element or spot | #12141 | point a Design Mode annotation at a second element or spot | Standalone | Request changes | Medium |
| P1 | preview videos in the file viewer | #12570 | preview videos in the file viewer | Standalone | Request changes | Medium |
| P1 | Prime native cache before E2E fanout | #17280 | Prime native cache before E2E fanout | Standalone | Review soon | Medium |
| P1 | profile-driven output status scrape, with IBM Bob | #15936 | profile-driven output status scrape, with IBM Bob | Standalone | Review soon | Medium |
| P1 | prove Bun runtime path | #16741 | prove Bun runtime path | Standalone | Request changes | Medium |
| P1 | prune expired Codex runtime session logs (#16776) | #16990 | prune expired Codex runtime session logs (#16776) | Standalone | Review soon | Medium |
| P1 | put the daemon in a kill-on-close job so a crash cannot orphan its PTY tree on Windows | #16895 | put the daemon in a kill-on-close job so a crash cannot orphan its PTY tree on Windows | Standalone | Review soon | Medium |
| P1 | read Antigravity quota from local runtime | #14571 #15948 #16653 #16710 | Coordinate 4 proposals for read Antigravity quota from local runtime. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | read submodule changes when .gitmodules hides them | #15428 | read submodule changes when .gitmodules hides them | Standalone | Review soon | Medium |
| P1 | reap zombie worktrees & stale daemon generations | #12740 | reap zombie worktrees & stale daemon generations | Standalone | Defer | Medium |
| P1 | rebase #9495 onto current main and fix task-reference parsing | #15788 | rebase #9495 onto current main and fix task-reference parsing | Standalone | Defer | Medium |
| P1 | recommend merged workspaces instead of protecting them | #13930 | recommend merged workspaces instead of protecting them | Standalone | Review soon | Medium |
| P1 | record the iOS simulator screen to a video file | #16624 | record the iOS simulator screen to a video file | Standalone | Review soon | Medium |
| P1 | render PlantUML diagrams in preview and rich editor | #15043 | render PlantUML diagrams in preview and rich editor | Standalone | Review soon | Medium |
| P1 | report an honest submit verdict from terminal send | #15274 | report an honest submit verdict from terminal send | Standalone | Review soon | Medium |
| P1 | report guest renderer deaths and key renderer dedupe by webContents identity | #15063 | report guest renderer deaths and key renderer dedupe by webContents identity | Standalone | Review soon | Medium |
| P1 | report heartbeat freshness on worker-list | #15963 | report heartbeat freshness on worker-list | Standalone | Review soon | Medium |
| P1 | resume closed worker provider sessions | #14389 | resume closed worker provider sessions | Standalone | Defer | Medium |
| P1 | resume Hermes TUI sessions after crash | #15809 | resume Hermes TUI sessions after crash | Standalone | Request changes | Medium |
| P1 | RTL text-direction toggle for the built-in editor | #16291 | RTL text-direction toggle for the built-in editor | Standalone | Review soon | Medium |
| P1 | run native teammate panes on Windows | #15753 | run native teammate panes on Windows | Standalone | Review soon | Medium |
| P1 | seed the default agent when activating an empty worktree | #15912 | seed the default agent when activating an empty worktree | Standalone | Review soon | Medium |
| P1 | sender-set message delivery class and a count-only check | #15264 | sender-set message delivery class and a count-only check | Standalone | Review soon | Medium |
| P1 | serve Cursor sidecar scans on the relay and unblock #11525 CI | #12891 | serve Cursor sidecar scans on the relay and unblock #11525 CI | Standalone | Review soon | Medium |
| P1 | set a default session profile per project | #13152 | set a default session profile per project | Standalone | Request changes | Medium |
| P1 | settle exited worker release when tab is absent | #16927 | settle exited worker release when tab is absent | Standalone | Review soon | Medium |
| P1 | ship browserless npm runtime | #13452 | ship browserless npm runtime | Standalone | Request changes | Medium |
| P1 | show Cmd/Ctrl+1-9 index badges on workspace cards | #16083 | show Cmd/Ctrl+1-9 index badges on workspace cards | Standalone | Review soon | Medium |
| P1 | show commit files as a directory tree | #13942 | show commit files as a directory tree | Standalone | Review soon | Medium |
| P1 | show Cursor monthly usage on the status bar | #16815 | show Cursor monthly usage on the status bar | Standalone | Review soon | Medium |
| P1 | show host-side gh/glab status on Integrations cards | #12028 | show host-side gh/glab status on Integrations cards | Standalone | Review soon | Medium |
| P1 | show live Codex subagent progress | #12311 | show live Codex subagent progress | Standalone | Request changes | Medium |
| P1 | show pace reserve/deficit on the provider usage bars | #15596 | show pace reserve/deficit on the provider usage bars | Standalone | Review soon | Medium |
| P1 | show PR review comments in the local branch diff (read-only) | #16236 | show PR review comments in the local branch diff (read-only) | Standalone | Review soon | Medium |
| P1 | show provider subscription plan labels | #16297 | show provider subscription plan labels | Standalone | Review soon | Medium |
| P1 | show the active workspace's linked task in a Task panel | #15330 | show the active workspace's linked task in a Task panel | Standalone | Review soon | Medium |
| P1 | start argv workers with bound authority | #16548 #16664 #16715 | Coordinate 3 proposals for start argv workers with bound authority. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | stop an agent from the board without opening its worktree | #16788 | stop an agent from the board without opening its worktree | Standalone | Review soon | Medium |
| P1 | stop list/ps crashing on corrupt workspace layout paths | #14019 | stop list/ps crashing on corrupt workspace layout paths | Standalone | Review soon | Medium |
| P1 | stop macOS serve crash-looping in _RegisterApplication | #14542 #14768 | Coordinate 2 proposals for stop macOS serve crash-looping in _RegisterApplication. | Duplicate | Supersede redundant work | Medium |
| P1 | stop the Help menu funnelling ordinary bug reports into the crash channel | #12493 | stop the Help menu funnelling ordinary bug reports into the crash channel | Standalone | Request changes | Medium |
| P1 | supervise an adopted dispatch with --supervise | #15270 | supervise an adopted dispatch with --supervise | Standalone | Review soon | Medium |
| P1 | support Cursor Agent conversations | #16796 | support Cursor Agent conversations | Standalone | Review soon | Medium |
| P1 | support Fast Mono (bionic-reading) fonts | #14950 | support Fast Mono (bionic-reading) fonts | Standalone | Request changes | Medium |
| P1 | support keyboard-interactive authentication (MFA) | #15588 | support keyboard-interactive authentication (MFA) | Standalone | Review soon | Medium |
| P1 | support PowerShell setup scripts on Windows (#16611) | #16616 | support PowerShell setup scripts on Windows (#16611) | Standalone | Request changes | Medium |
| P1 | surface Codex startup dialogs and update flow in chat view | #15600 #15632 | Coordinate 2 proposals for surface Codex startup dialogs and update flow in chat view. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | surface merge-queue state as a distinct queued PR state | #16658 | surface merge-queue state as a distinct queued PR state | Standalone | Review soon | Medium |
| P1 | switch and create branches from the sidepanel | #16403 | switch and create branches from the sidepanel | Standalone | Review soon | Medium |
| P1 | track Nous Portal usage with credit balances | #15121 | track Nous Portal usage with credit balances | Standalone | Review soon | Medium |
| P1 | unblock pnpm lint and a source assertion on a CRLF checkout | #14481 | unblock pnpm lint and a source assertion on a CRLF checkout | Standalone | Review soon | Medium |
| P1 | wait out live OpenCode sqlite locks | #14134 #15671 | Coordinate 2 proposals for wait out live OpenCode sqlite locks. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | [leas code] Remove expired OMP overlay migration | #13455 | [leas code] Remove expired OMP overlay migration | Standalone | Request changes | Medium |
| P1 | accept pty:<ptyId> as a terminal selector | #13219 | accept pty:<ptyId> as a terminal selector | Standalone | Request changes | Medium |
| P1 | add --no-rotate-pairing flag for a static pairing URL | #13712 | add --no-rotate-pairing flag for a static pairing URL | Standalone | Review soon | Medium |
| P1 | add a Linear panel for the workspace's linked issue | #12698 | add a Linear panel for the workspace's linked issue | Standalone | Request changes | Medium |
| P1 | add a provider-agnostic --needs-attention hook with push notifications | #12199 | add a provider-agnostic --needs-attention hook with push notifications | Standalone | Request changes | Medium |
| P1 | add account-scoped launch selectors | #13272 | add account-scoped launch selectors | Standalone | Request changes | Medium |
| P1 | add an Android emulator harness for device-only repros | #13366 | add an Android emulator harness for device-only repros | Standalone | Review soon | Medium |
| P1 | add Aside as a Chromium cookie-import source | #12035 | add Aside as a Chromium cookie-import source | Standalone | Request changes | Medium |
| P1 | add board view, drag-drop, project fields in dialog | #12302 | add board view, drag-drop, project fields in dialog | Standalone | Review soon | Medium |
| P1 | add Cloudflare Tunnel pairing intent | #14040 | add Cloudflare Tunnel pairing intent | Standalone | Review soon | Medium |
| P1 | add Cursor usage tracking | #13837 | add Cursor usage tracking | Standalone | Review soon | Medium |
| P1 | add DAP spine — transport, session lifecycle, and host-aware adapter spawn | #13281 | add DAP spine — transport, session lifecycle, and host-aware adapter spawn | Standalone | Request changes | Medium |
| P1 | add Deepgram Nova-3 dictation | #12529 | add Deepgram Nova-3 dictation | Standalone | Request changes | Medium |
| P1 | add DeepSeek status bar usage provider | #12873 | add DeepSeek status bar usage provider | Standalone | Request changes | Medium |
| P1 | add detached Markdown editor windows | #13441 | add detached Markdown editor windows | Standalone | Request changes | Medium |
| P1 | add durable conversation wake foundation | #12033 | add durable conversation wake foundation | Standalone | Request changes | Medium |
| P1 | add fork and child creation actions | #12858 | add fork and child creation actions | Standalone | Request changes | Medium |
| P1 | add GDScript syntax highlighting | #12549 | add GDScript syntax highlighting | Standalone | Review soon | Medium |
| P1 | add Group by Issue workspace organization | #12567 | add Group by Issue workspace organization | Standalone | Request changes | Medium |
| P1 | add inline git blame and file history | #13338 | add inline git blame and file history | Standalone | Request changes | Medium |
| P1 | add keyboard shortcuts to switch AI provider account | #12792 | add keyboard shortcuts to switch AI provider account | Standalone | Request changes | Medium |
| P1 | add managed accounts | #13274 | add managed accounts | Standalone | Request changes | Medium |
| P1 | add Odoo as a task provider with ticket panel, chatter and workspace sync | #14499 | add Odoo as a task provider with ticket panel, chatter and workspace sync | Standalone | Review soon | Medium |
| P1 | add one-tap collapse/expand for all workspace groups | #12411 | add one-tap collapse/expand for all workspace groups | Standalone | Request changes | Medium |
| P1 | add Project/Current view toggle and polish card styling | #15156 | add Project/Current view toggle and polish card styling | Standalone | Review soon | Medium |
| P1 | add standalone terminal workspace | #12887 | add standalone terminal workspace | Standalone | Request changes | Medium |
| P1 | add terminal shortcut capture notification toggle | #14483 | add terminal shortcut capture notification toggle | Standalone | Review soon | Medium |
| P1 | add zh-TW (Traditional Chinese) locale | #14223 | add zh-TW (Traditional Chinese) locale | Standalone | Defer | Medium |
| P1 | answer an over-capacity response instead of closing the client | #12068 | answer an over-capacity response instead of closing the client | Standalone | Request changes | Medium |
| P1 | ask before bulk-closing tabs with running work | #16406 | ask before bulk-closing tabs with running work | Standalone | Request changes | Medium |
| P1 | attach extra reviews and track sibling branches on the worktree card (#9213) | #13374 | attach extra reviews and track sibling branches on the worktree card (#9213) | Standalone | Request changes | Medium |
| P1 | attribute usage to launch accounts | #13273 | attribute usage to launch accounts | Standalone | Request changes | Medium |
| P1 | authenticate via az CLI Entra login with token fallback | #12201 | authenticate via az CLI Entra login with token fallback | Standalone | Review soon | Medium |
| P1 | automatically close merged workspaces | #14042 | automatically close merged workspaces | Standalone | Review soon | Medium |
| P1 | Beads (bd) local issue tracker as a task source | #14013 | Beads (bd) local issue tracker as a task source | Standalone | Review soon | Medium |
| P1 | bind projects to a specific gh account | #13664 | bind projects to a specific gh account | Standalone | Review soon | Medium |
| P1 | bound host tunnel memory | #14504 | bound host tunnel memory | Standalone | Defer | Medium |
| P1 | bound POSIX hook stdin so agy cannot hang loading | #15821 | bound POSIX hook stdin so agy cannot hang loading | Standalone | Request changes | Medium |
| P1 | bound tunnel route resources | #14495 | bound tunnel route resources | Standalone | Defer | Medium |
| P1 | bridge client page renderer mounts | #14578 | bridge client page renderer mounts | Standalone | Defer | Medium |
| P1 | browser action recorder with agent-ready session logs | #12542 | browser action recorder with agent-ready session logs | Standalone | Request changes | Medium |
| P1 | canonical agent-session journal with crash-safe receipts and epoch cursors (phase 1c) | #13085 | canonical agent-session journal with crash-safe receipts and epoch cursors (phase 1c) | Standalone | Request changes | Medium |
| P1 | Claude structured chat — full migration (adapter, translation, desktop + mobile clients) | #13584 | Claude structured chat — full migration (adapter, translation, desktop + mobile clients) | Standalone | Request changes | Medium |
| P1 | compose paired client host lifecycle | #14558 | compose paired client host lifecycle | Standalone | Defer | Medium |
| P1 | compose paired client host runtime | #14613 | compose paired client host runtime | Standalone | Defer | Medium |
| P1 | configure creation stage timeouts | #13026 | configure creation stage timeouts | Standalone | Request changes | Medium |
| P1 | convert non-Git folders to Git repositories from the import dialog | #12914 | convert non-Git folders to Git repositories from the import dialog | Standalone | Request changes | Medium |
| P1 | copy markdown from the panel header | #14528 | copy markdown from the panel header | Standalone | Review soon | Medium |
| P1 | cpu/memory/uptime columns, shared sort, and a ports memory sparkline | #14972 | cpu/memory/uptime columns, shared sort, and a ports memory sparkline | Standalone | Review soon | Medium |
| P1 | create child worktrees from the composer | #14201 | create child worktrees from the composer | Standalone | Request changes | Medium |
| P1 | deploy, activate and roll back a versioned orcad install | #16384 | deploy, activate and roll back a versioned orcad install | Standalone | Request changes | Medium |
| P1 | discard restores the working tree from the index, not HEAD | #16440 | discard restores the working tree from the index, not HEAD | Standalone | Review soon | Medium |
| P1 | discover native session models from the runtime | #13183 | discover native session models from the runtime | Standalone | Request changes | Medium |
| P1 | discover repos inside a git parent and surface their change counts | #13102 | discover repos inside a git parent and surface their change counts | Standalone | Request changes | Medium |
| P1 | enable structured chat/TUI toggle | #14601 | enable structured chat/TUI toggle | Standalone | Request changes | Medium |
| P1 | ensure DACL allows renderer bootstrap in packaged installs | #17143 | ensure DACL allows renderer bootstrap in packaged installs | Standalone | Review soon | Medium |
| P1 | execute client page commands locally | #14566 | execute client page commands locally | Standalone | Defer | Medium |
| P1 | Feat/editor git gutter and new file | #13447 | Feat/editor git gutter and new file | Standalone | Request changes | Medium |
| P1 | fence client host leases | #14484 | fence client host leases | Standalone | Defer | Medium |
| P1 | fence route pages to renderer owners | #14520 | fence route pages to renderer owners | Standalone | Defer | Medium |
| P1 | file icon theme picker with Symbols support | #15131 | file icon theme picker with Symbols support | Standalone | Review soon | Medium |
| P1 | filter the workspace list by status | #13971 | filter the workspace list by status | Standalone | Review soon | Medium |
| P1 | give a Run a parent Run | #15263 | give a Run a parent Run | Standalone | Review soon | Medium |
| P1 | group Copy path/branch/PR-MR URL in the worktree row menu | #12240 | group Copy path/branch/PR-MR URL in the worktree row menu | Standalone | Request changes | Medium |
| P1 | host-routed proxy for workspace dev servers, configurable from settings | #13318 | host-routed proxy for workspace dev servers, configurable from settings | Standalone | Request changes | Medium |
| P1 | inline git blame for the cursor line, plus a status-bar segment | #13321 | inline git blame for the cursor line, plus a status-bar segment | Standalone | Request changes | Medium |
| P1 | iTerm-style Ctrl/Cmd modifier remap on macOS | #12019 | iTerm-style Ctrl/Cmd modifier remap on macOS | Standalone | Request changes | Medium |
| P1 | kanban board view for Jira issues in the Tasks panel | #13054 | kanban board view for Jira issues in the Tasks panel | Standalone | Request changes | Medium |
| P1 | let a session continue on a different host | #16105 | let a session continue on a different host | Standalone | Defer | Medium |
| P1 | let users pick a custom icon for "Open in" apps | #13879 | let users pick a custom icon for "Open in" apps | Standalone | Review soon | Medium |
| P1 | LSP support in the editor and diff views (tsgo-first) | #14873 | LSP support in the editor and diff views (tsgo-first) | Standalone | Review soon | Medium |
| P1 | make nested workspace drops reliable | #13446 | make nested workspace drops reliable | Standalone | Defer | Medium |
| P1 | make renderer memory attribution honest about what it cannot explain | #12940 | make renderer memory attribution honest about what it cannot explain | Standalone | Defer | Medium |
| P1 | migrate workspace UI to hybrid WebView | #13386 | migrate workspace UI to hybrid WebView | Standalone | Defer | Medium |
| P1 | move freeze-prone sync fs off the main thread | #12015 | move freeze-prone sync fs off the main thread | Standalone | Request changes | Medium |
| P1 | multi-branch Git Graph view with worktree overlay | #14047 | multi-branch Git Graph view with worktree overlay | Standalone | Review soon | Medium |
| P1 | name remote terminal sessions instead of showing pids | #16006 | name remote terminal sessions instead of showing pids | Standalone | Defer | Medium |
| P1 | open .xlsx and .xlsm workbooks in a sheet viewer | #13532 | open .xlsx and .xlsm workbooks in a sheet viewer | Standalone | Request changes | Medium |
| P1 | open a workspace from the worktree ring popover | #14645 | open a workspace from the worktree ring popover | Standalone | Request changes | Medium |
| P1 | open agent details in slideout drawer | #12185 | open agent details in slideout drawer | Standalone | Request changes | Medium |
| P1 | open custom app scheme links with user approval | #13237 | open custom app scheme links with user approval | Standalone | Request changes | Medium |
| P1 | open Explorer-dragged files in a split pane | #13982 | open Explorer-dragged files in a split pane | Standalone | Review soon | Medium |
| P1 | open files with the system default app or a picked app | #12866 | open files with the system default app or a picked app | Standalone | Request changes | Medium |
| P1 | opt-in setting to terminate sessions on quit | #14652 | opt-in setting to terminate sessions on quit | Standalone | Review soon | Medium |
| P1 | optional Pake web-shell plus renderer occupancy proof | #15338 | optional Pake web-shell plus renderer occupancy proof | Standalone | Defer | Medium |
| P1 | orchestrate page reconciliation | #14769 | orchestrate page reconciliation | Standalone | Defer | Medium |
| P1 | per-agent terminal theme overrides in Appearance | #14293 | per-agent terminal theme overrides in Appearance | Standalone | Review soon | Medium |
| P1 | per-file progress and cancel for files dropped onto a remote workspace | #16107 | per-file progress and cancel for files dropped onto a remote workspace | Standalone | Review soon | Medium |
| P1 | prepare route-scoped Electron partitions | #14516 | prepare route-scoped Electron partitions | Standalone | Defer | Medium |
| P1 | preserve client host through reconnect grace | #14691 | preserve client host through reconnect grace | Standalone | Defer | Medium |
| P1 | preserve executor across authority changes | #14876 | preserve executor across authority changes | Standalone | Defer | Medium |
| P1 | prove node-pty loads before anything requires it | #16374 | prove node-pty loads before anything requires it | Standalone | Request changes | Medium |
| P1 | quarantine client-hosted WebContents before navigation | #14517 | quarantine client-hosted WebContents before navigation | Standalone | Defer | Medium |
| P1 | read OpenCode transcripts from its SQLite session store | #15026 | read OpenCode transcripts from its SQLite session store | Standalone | Review soon | Medium |
| P1 | release a structured session when its chat closes | #15415 | release a structured session when its chat closes | Standalone | Request changes | Medium |
| P1 | release parent chunks pinned by drained output slices | #13040 | release parent chunks pinned by drained output slices | Standalone | Request changes | Medium |
| P1 | report remote Orca runtime hosts, not just the local machine | #16000 | report remote Orca runtime hosts, not just the local machine | Standalone | Review soon | Medium |
| P1 | retain client page renderer guests | #14596 | retain client page renderer guests | Standalone | Defer | Medium |
| P1 | retire route pages on process loss | #14519 | retire route pages on process loss | Standalone | Defer | Medium |
| P1 | route paired browser sockets through runtime | #14470 | route paired browser sockets through runtime | Standalone | Defer | Medium |
| P1 | run the project's formatter after a save | #13757 | run the project's formatter after a save | Standalone | Review soon | Medium |
| P1 | run the terminal daemon, and the ops contract around it | #16375 | run the terminal daemon, and the ops contract around it | Standalone | Request changes | Medium |
| P1 | scope model discovery to pinned PTY accounts | #13270 | scope model discovery to pinned PTY accounts | Standalone | Request changes | Medium |
| P1 | scope the sidebar to Spaces | #13335 | scope the sidebar to Spaces | Standalone | Defer | Medium |
| P1 | separate row wash from word chip for readable diffs | #12777 | separate row wash from word chip for readable diffs | Standalone | Review soon | Medium |
| P1 | settle host commands on lease socket | #14557 | settle host commands on lease socket | Standalone | Defer | Medium |
| P1 | settle page retirement in two phases | #14539 | settle page retirement in two phases | Standalone | Defer | Medium |
| P1 | show Kiro subscription credits | #14001 | show Kiro subscription credits | Standalone | Review soon | Medium |
| P1 | show linked PR/MR numbers on workspace cards | #14269 | show linked PR/MR numbers on workspace cards | Standalone | Review soon | Medium |
| P1 | show running services and their owning project | #12190 | show running services and their owning project | Standalone | Request changes | Medium |
| P1 | Split filesystem watcher responsibilities | #17274 | Split filesystem watcher responsibilities | Standalone | Request changes | Medium |
| P1 | stream file uploads instead of buffering whole files | #16106 | stream file uploads instead of buffering whole files | Standalone | Review soon | Medium |
| P1 | support account-scoped agent launches | #13271 | support account-scoped agent launches | Standalone | Request changes | Medium |
| P1 | support Bitbucket Data Center for hosted-review status | #12111 | support Bitbucket Data Center for hosted-review status | Standalone | Review soon | Medium |
| P1 | support native Windows teammate panes | #16116 | support native Windows teammate panes | Standalone | Defer | Medium |
| P1 | support Pi mobile chat | #12325 | support Pi mobile chat | Standalone | Request changes | Medium |
| P1 | support split left and split up | #13984 | support split left and split up | Standalone | Review soon | Medium |
| P1 | surface agent notices in Chat and offer reauthentication | #14339 #15661 | Coordinate 2 proposals for surface agent notices in Chat and offer reauthentication. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P1 | surface Trae CLI session history | #13515 | surface Trae CLI session history | Standalone | Request changes | Medium |
| P1 | terminal groups — extra terminal/agent cards on a project's existing checkout | #15501 | terminal groups — extra terminal/agent cards on a project's existing checkout | Standalone | Review soon | Medium |
| P1 | terminal keypad layout toggle with full on-screen keyboard | #14540 | terminal keypad layout toggle with full on-screen keyboard | Standalone | Review soon | Medium |
| P1 | track Qwen Code as a status agent with managed hooks and working tui-idle | #12555 | track Qwen Code as a status agent with managed hooks and working tui-idle | Standalone | Request changes | Medium |
| P1 | user-selectable CJK font + warmed installed-font list | #13779 | user-selectable CJK font + warmed installed-font list | Standalone | Review soon | Medium |
| P1 | add a setting to turn off rename-on-double-click | #12801 | add a setting to turn off rename-on-double-click | Standalone | Request changes | Medium |
| P1 | add Antigravity (AGY) transcript decoder and Native Chat support | #15773 | add Antigravity (AGY) transcript decoder and Native Chat support | Standalone | Review soon | Medium |
| P1 | add Copy Session ID to the terminal context menu | #16264 | add Copy Session ID to the terminal context menu | Standalone | Review soon | Medium |
| P1 | add diagnostic report collection and copy-to-clipboard | #12636 | add diagnostic report collection and copy-to-clipboard | Standalone | Request changes | Medium |
| P1 | add font smoothing setting (default / antialiased / subpixel) | #13056 | add font smoothing setting (default / antialiased / subpixel) | Standalone | Request changes | Medium |
| P1 | add Hermes native chat support | #15301 | add Hermes native chat support | Standalone | Review soon | Medium |
| P1 | add inline folder source control with git actions | #13291 | add inline folder source control with git actions | Standalone | Request changes | Medium |
| P1 | add Turkish (tr) language support and README | #13196 | add Turkish (tr) language support and README | Standalone | Review soon | Medium |
| P1 | allow hiding the terminal command button | #13001 | allow hiding the terminal command button | Standalone | Request changes | Medium |
| P1 | Claude API Console usage tracking | #12973 | Claude API Console usage tracking | Standalone | Review soon | Medium |
| P1 | Discord Rich Presence (experimental) | #14286 | Discord Rich Presence (experimental) | Standalone | Review soon | Medium |
| P1 | distinguish interactive and prompt-only runtimes | #16227 | distinguish interactive and prompt-only runtimes | Standalone | Defer | Medium |
| P1 | establish client-hosted tunnel contracts | #14440 | establish client-hosted tunnel contracts | Standalone | Defer | Medium |
| P1 | let OMP task subagent rows resume as their own sessions | #12889 | let OMP task subagent rows resume as their own sessions | Standalone | Request changes | Medium |
| P1 | let users hide optional agent-row fields | #13195 | let users hide optional agent-row fields | Standalone | Request changes | Medium |
| P1 | link a Jira issue from Edit Worktree Details | #13825 | link a Jira issue from Edit Worktree Details | Standalone | Review soon | Medium |
| P1 | offer WSL agent detection when the Windows picker is empty | #12794 | offer WSL agent detection when the Windows picker is empty | Standalone | Request changes | Medium |
| P1 | paste copied files into a File Explorer folder | #14781 | paste copied files into a File Explorer folder | Standalone | Review soon | Medium |
| P1 | rebuild Antigravity quota discovery | #12095 | rebuild Antigravity quota discovery | Standalone | Request changes | Medium |
| P1 | remember Worktree View as the default Dashboard view | #14780 | remember Worktree View as the default Dashboard view | Standalone | Review soon | Medium |
| P1 | render Kimi Code transcripts | #16397 | render Kimi Code transcripts | Standalone | Review soon | Medium |
| P1 | resize CSV table columns | #13223 | resize CSV table columns | Standalone | Review soon | Medium |
| P1 | saved and custom JQL filters in the Tasks panel | #13395 | saved and custom JQL filters in the Tasks panel | Standalone | Request changes | Medium |
| P1 | show ZCode Coding Plan quota | #14556 | show ZCode Coding Plan quota | Standalone | Defer | Medium |
| P1 | supervise orchestration workers and transcripts | #16228 | supervise orchestration workers and transcripts | Standalone | Defer | Medium |
| P1 | teach the file tree with a one-shot callout that sets the default | #12744 | teach the file tree with a one-shot callout that sets the default | Standalone | Request changes | Medium |
| P1 | authenticate page command results | #14553 | authenticate page command results | Standalone | Defer | Medium |
| P1 | backfill fork upstream for SSH repos on connect | #12970 | backfill fork upstream for SSH repos on connect | Standalone | Request changes | Medium |
| P1 | bound client page command dispatch | #14550 | bound client page command dispatch | Standalone | Defer | Medium |
| P1 | harden bootstrap and cross-plane orchestration | #16349 | harden bootstrap and cross-plane orchestration | Standalone | Review soon | Medium |
| P1 | negotiate client page commands | #14544 | negotiate client page commands | Standalone | Defer | Medium |
| P1 | plan client page reconciliation | #14617 | plan client page reconciliation | Standalone | Defer | Medium |
| P1 | preview .docx / .xlsx / .pdf in editor | #15763 | preview .docx / .xlsx / .pdf in editor | Standalone | Review soon | Medium |
| P1 | replace fenced tunnel generations | #14507 | replace fenced tunnel generations | Standalone | Defer | Medium |
| P1 | report client page inventory | #14648 | report client page inventory | Standalone | Defer | Medium |
| P1 | route tunnels through execution hosts | #14513 | route tunnels through execution hosts | Standalone | Defer | Medium |
| P1 | supervise fresh Pi workers over RPC | #15451 | supervise fresh Pi workers over RPC | Standalone | Defer | Medium |
| P1 | sample the near-death renderer heap (unblocks the 42-crash OOM cluster) | #12491 | sample the near-death renderer heap (unblocks the 42-crash OOM cluster) | Standalone | Request changes | Medium |
| P2 | [STA-5729] Prevent live coordinator takeover of orchestration Runs | #16859 | [STA-5729] Prevent live coordinator takeover of orchestration Runs | Standalone | Request changes | Medium |
| P2 | a failed shared-quota read is an Antigravity error, not an absent reading | #17200 | a failed shared-quota read is an Antigravity error, not an absent reading | Standalone | Merge | Medium |
| P2 | a recycled PTY id must not replay the dead shell's bytes | #17148 | a recycled PTY id must not replay the dead shell's bytes | Standalone | Request changes | Medium |
| P2 | accept bare environment ids as project --host | #13191 | accept bare environment ids as project --host | Standalone | Request changes | Medium |
| P2 | accept Cursor events on the Claude compatibility route | #14640 | accept Cursor events on the Claude compatibility route | Standalone | Review soon | Medium |
| P2 | add --no-offscreen-browser flag | #13434 | add --no-offscreen-browser flag | Standalone | Request changes | Medium |
| P2 | add "Copy Terminal ID" and "Copy Session ID" to the tab context menu | #16269 | add "Copy Terminal ID" and "Copy Session ID" to the tab context menu | Standalone | Review soon | Medium |
| P2 | add a packaged-artifact contract for the CLI launch paths | #15085 | add a packaged-artifact contract for the CLI launch paths | Standalone | Request changes | Medium |
| P2 | add an opt-in Parallel Search MCP preset | #16537 | add an opt-in Parallel Search MCP preset | Standalone | Review soon | Medium |
| P2 | add Aside as a Chromium cookie-import source | #15452 | add Aside as a Chromium cookie-import source | Standalone | Review soon | Medium |
| P2 | add authenticated Windows loopback fallback | #16623 #17218 | Coordinate 2 proposals for add authenticated Windows loopback fallback. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | Add background Quick Command execution | #12737 | Add background Quick Command execution | Standalone | Request changes | Medium |
| P2 | Add Bullet to the supported agents | #13296 | Add Bullet to the supported agents | Standalone | Request changes | Medium |
| P2 | add F2 rename keybinding via the shortcut registry | #14699 | add F2 rename keybinding via the shortcut registry | Standalone | Review soon | Medium |
| P2 | Add insertion-only quick commands that don't immediately submit Enter | #16867 | Add insertion-only quick commands that don't immediately submit Enter | Standalone | Request changes | Medium |
| P2 | add keyboard shortcuts for cycling projects | #15843 | add keyboard shortcuts for cycling projects | Standalone | Review soon | Medium |
| P2 | Add local shell command identity markers | #16915 | Add local shell command identity markers | Standalone | Review soon | Medium |
| P2 | Add multi-desktop mobile project view | #14989 | Add multi-desktop mobile project view | Standalone | Review soon | Medium |
| P2 | add OMP commit-message agent spec for Source Control AI | #15654 #15678 | Coordinate 2 proposals for add OMP commit-message agent spec for Source Control AI. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | Add quick command duplication with a list cap | #16813 | Add quick command duplication with a list cap | Standalone | Review soon | Medium |
| P2 | add responsive resizable Markdown tables | #12048 | add responsive resizable Markdown tables | Standalone | Merge | Medium |
| P2 | Add shortcuts to navigate active worktrees | #14689 | Add shortcuts to navigate active worktrees | Standalone | Review soon | Medium |
| P2 | Add SSH host registration to Orca CLI | #16351 | Add SSH host registration to Orca CLI | Standalone | Defer | Medium |
| P2 | add VCL (Varnish Configuration Language) syntax highlighting | #15437 | add VCL (Varnish Configuration Language) syntax highlighting | Standalone | Review soon | Medium |
| P2 | add workspace-scoped browser session profiles (#14559) | #16091 | add workspace-scoped browser session profiles (#14559) | Standalone | Review soon | Medium |
| P2 | add worktree pin controls | #13897 | add worktree pin controls | Standalone | Review soon | Medium |
| P2 | Adopt Codex terminal sessions into structured native chat | #15411 | Adopt Codex terminal sessions into structured native chat | Standalone | Request changes | Medium |
| P2 | adopt only the real user replay as a Claude send's identity | #15657 | adopt only the real user replay as a Claude send's identity | Standalone | Review soon | Medium |
| P2 | adopt provisioned recipe checkout roots | #13870 | adopt provisioned recipe checkout roots | Standalone | Review soon | Medium |
| P2 | align multiline filter toggle row text and icons to top-left | #16054 | align multiline filter toggle row text and icons to top-left | Standalone | Review soon | Medium |
| P2 | allow panels to read plugin storage (storage.get panel: true) | #14766 | allow panels to read plugin storage (storage.get panel: true) | Standalone | Review soon | Medium |
| P2 | Allow plugin panels to invoke their own worker commands | #12229 | Allow plugin panels to invoke their own worker commands | Standalone | Review soon | Medium |
| P2 | Allow sandboxed panels to read their plugin's own storage (storage.get/storage.keys) | #13220 | Allow sandboxed panels to read their plugin's own storage (storage.get/storage.keys) | Standalone | Review soon | Medium |
| P2 | anchor literal image-marker stripping to a real image send (STA-4363) | #14939 | anchor literal image-marker stripping to a real image send (STA-4363) | Standalone | Review soon | Medium |
| P2 | answer every request when a param schema throws (STA-4818) | #15460 | answer every request when a param schema throws (STA-4818) | Standalone | Review soon | Medium |
| P2 | arm first-work branch rename in headless orca serve | #17070 | arm first-work branch rename in headless orca serve | Standalone | Review soon | Medium |
| P2 | atomically start workers and release terminal custody | #17007 | atomically start workers and release terminal custody | Standalone | Request changes | Medium |
| P2 | attach a reclaim command to each residual resource in mutation recovery | #15949 #15966 | Coordinate 2 proposals for attach a reclaim command to each residual resource in mutation recovery. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | attribute account add from the WSL bridge to the caller's distro | #17093 | attribute account add from the WSL bridge to the caller's distro | Standalone | Review soon | Medium |
| P2 | attribute agent rows to the agent's live worktree via hook cwd | #16574 | attribute agent rows to the agent's live worktree via hook cwd | Standalone | Review soon | Medium |
| P2 | attribute Cursor legacy transcripts to their project cwd | #13935 #14616 #15705 | Coordinate 3 proposals for attribute Cursor legacy transcripts to their project cwd. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | auto-dismiss paste focus-cancellation instead of sticky error banner | #13988 #16819 | Coordinate 2 proposals for auto-dismiss paste focus-cancellation instead of sticky error banner. | Competing | Choose one preferred solution | Medium |
| P2 | auto-surface CLI-added remote servers in the running IDE | #13596 | auto-surface CLI-added remote servers in the running IDE | Standalone | Review soon | Medium |
| P2 | autofix scheduled CI run 33021799961 failures | #16816 | autofix scheduled CI run 33021799961 failures | Standalone | Request changes | Medium |
| P2 | avoid duplicate Windows profile hooks | #15312 | avoid duplicate Windows profile hooks | Standalone | Review soon | Medium |
| P2 | avoid repeated capability probes during file imports | #14555 | avoid repeated capability probes during file imports | Standalone | Review soon | Medium |
| P2 | bind worker placement to the Run, not the task | #14841 | bind worker placement to the Run, not the task | Standalone | Review soon | Medium |
| P2 | bindable tab.moveToNewPaneColumn action | #16465 | bindable tab.moveToNewPaneColumn action | Standalone | Review soon | Medium |
| P2 | bounce lifecycle rejections to the sender | #13217 | bounce lifecycle rejections to the sender | Standalone | Request changes | Medium |
| P2 | bound git subprocess execution with an atomic admission scheduler | #16874 | bound git subprocess execution with an atomic admission scheduler | Standalone | Request changes | Medium |
| P2 | bound main-process filesystem reads so a stalled mount cannot freeze the app | #12149 | bound main-process filesystem reads so a stalled mount cannot freeze the app | Standalone | Request changes | Medium |
| P2 | bound memory for headless orca serve | #13684 | bound memory for headless orca serve | Standalone | Review soon | Medium |
| P2 | bound the aggregated PTY error surface so recurring near-duplicate errors can't grow it with | #15306 | bound the aggregated PTY error surface so recurring near-duplicate errors can't grow it with | Standalone | Review soon | Medium |
| P2 | bound the codex POSIX hook's stdin read and exec the script from the wrapper | #15892 | bound the codex POSIX hook's stdin read and exec the script from the wrapper | Standalone | Review soon | Medium |
| P2 | bound WSL installed skill discovery | #12314 | bound WSL installed skill discovery | Standalone | Request changes | Medium |
| P2 | build(preload): fail the build when a sandboxed preload needs a Node builtin | #13110 | build(preload): fail the build when a sandboxed preload needs a Node builtin | Standalone | Request changes | Medium |
| P2 | bulk stage reviewed files | #17204 | bulk stage reviewed files | Standalone | Review soon | Medium |
| P2 | bundle Nerd Font terminal fallback | #17220 | bundle Nerd Font terminal fallback | Standalone | Merge | Medium |
| P2 | Cache main-process compilation between launches | #13487 | Cache main-process compilation between launches | Standalone | Request changes | Medium |
| P2 | cancel redundant mail repair after immediate delivery (STA-4235) | #14391 | cancel redundant mail repair after immediate delivery (STA-4235) | Standalone | Review soon | Medium |
| P2 | characterize renderer death containment | #16120 | characterize renderer death containment | Standalone | Request changes | Medium |
| P2 | cherry-pick: restore CIM fallback for relay hosts with no native binding (#16550) for 1.4.18 | #16573 | cherry-pick: restore CIM fallback for relay hosts with no native binding (#16550) for 1.4.18 | Standalone | Review soon | Medium |
| P2 | ci(e2e): gate PRs on the green golden lane and cover renderer invariance | #15302 | ci(e2e): gate PRs on the green golden lane and cover renderer invariance | Standalone | Review soon | Medium |
| P2 | ci(mobile): publish the Android APK as orca-app-release.apk | #16606 | ci(mobile): publish the Android APK as orca-app-release.apk | Standalone | Review soon | Medium |
| P2 | classify a permission-denied runtime connect instead of reporting "starting" | #13583 | classify a permission-denied runtime connect instead of reporting "starting" | Standalone | Request changes | Medium |
| P2 | classify ask --json outcome for engine resume | #13188 | classify ask --json outcome for engine resume | Standalone | Request changes | Medium |
| P2 | close guest-owned split tab | #17281 | close guest-owned split tab | Standalone | Review soon | Medium |
| P2 | close readiness gaps found by merged-change audit | #17159 | close readiness gaps found by merged-change audit | Standalone | Request changes | Medium |
| P2 | coalesce scroll-intent settles instead of one per wheel event | #16207 | coalesce scroll-intent settles instead of one per wheel event | Standalone | Review soon | Medium |
| P2 | codify desktop composition regression checks | #17172 | codify desktop composition regression checks | Standalone | Merge | Medium |
| P2 | collapse path-equal worktree rows without losing lineage | #15872 | collapse path-equal worktree rows without losing lineage | Standalone | Review soon | Medium |
| P2 | commit AskUserQuestion answers on preview-style selectors | #16914 #16929 | Coordinate 2 proposals for commit AskUserQuestion answers on preview-style selectors. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | Complete agent-session-rules delivery + fix repo-context wiring across all call sites | #14046 | Complete agent-session-rules delivery + fix repo-context wiring across all call sites | Standalone | Review soon | Medium |
| P2 | contain crashes and preserve diagnostics | #16348 | contain crashes and preserve diagnostics | Standalone | Request changes | Medium |
| P2 | continue a session in a new worktree | #16794 | continue a session in a new worktree | Standalone | Review soon | Medium |
| P2 | converge the persisted WS fallback port after the default port recovers (STA-4859) | #15533 | converge the persisted WS fallback port after the default port recovers (STA-4859) | Standalone | Request changes | Medium |
| P2 | copy relay terminal IDs from the remote PTY handle | #15554 | copy relay terminal IDs from the remote PTY handle | Standalone | Review soon | Medium |
| P2 | correct active-tab surface in light mode (#16283) | #16481 | correct active-tab surface in light mode (#16283) | Standalone | Review soon | Medium |
| P2 | correct agent commands, shell hooks, and runtime routing | #14838 | correct agent commands, shell hooks, and runtime routing | Standalone | Review soon | Medium |
| P2 | count Codex sessions from running WSL distros | #16050 | count Codex sessions from running WSL distros | Standalone | Review soon | Medium |
| P2 | count IME commits and coalesced echoes in the typing probe | #16952 #17171 | Coordinate 2 proposals for count IME commits and coalesced echoes in the typing probe. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | Create ssh worktree error | #15022 | Create ssh worktree error | Standalone | Request changes | Medium |
| P2 | declare terminal Helper protected-folder access | #16824 | declare terminal Helper protected-folder access | Standalone | Review soon | Medium |
| P2 | default worker-start --agent to the Settings default agent | #15935 | default worker-start --agent to the Settings default agent | Standalone | Review soon | Medium |
| P2 | defensive worktree selection hardening (#16241) | #16253 | defensive worktree selection hardening (#16241) | Standalone | Review soon | Medium |
| P2 | deliver paired agent completion and permission alerts | #16280 | deliver paired agent completion and permission alerts | Standalone | Request changes | Medium |
| P2 | derive the Claude Keychain account the way Claude Code does | #12862 #16673 | Coordinate 2 proposals for derive the Claude Keychain account the way Claude Code does. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | detect extracted AppImage CLI launches without APPDIR | #13136 #13289 | Coordinate 2 proposals for detect extracted AppImage CLI launches without APPDIR. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | detect Homebrew-installed CLIs in the install-dir fallback | #15960 | detect Homebrew-installed CLIs in the install-dir fallback | Standalone | Review soon | Medium |
| P2 | disable setuid sandbox for headless CLI on extracted runtime | #14230 | disable setuid sandbox for headless CLI on extracted runtime | Standalone | Review soon | Medium |
| P2 | disclaim TCC responsibility at PTY spawn instead of relying on login(1) | #17191 | disclaim TCC responsibility at PTY spawn instead of relying on login(1) | Standalone | Request changes | Medium |
| P2 | discover effort menus from the host CLI catalog (STA-4320) | #15687 #15890 | Coordinate 2 proposals for discover effort menus from the host CLI catalog (STA-4320). | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | dismiss the banner id a Claude background turn announced (STA-4592) | #15047 | dismiss the banner id a Claude background turn announced (STA-4592) | Standalone | Review soon | Medium |
| P2 | dispatch coordinate pointer input in process instead of one subprocess per event | #15309 | dispatch coordinate pointer input in process instead of one subprocess per event | Standalone | Review soon | Medium |
| P2 | document cmd.exe quoting for gesture JSON | #13249 | document cmd.exe quoting for gesture JSON | Standalone | Request changes | Medium |
| P2 | document cross-runtime federation | #14063 | document cross-runtime federation | Standalone | Review soon | Medium |
| P2 | document run-use takeover preconditions | #13256 | document run-use takeover preconditions | Standalone | Request changes | Medium |
| P2 | document runtime outage delivery | #12997 | document runtime outage delivery | Standalone | Request changes | Medium |
| P2 | document terminal read --screen and realign drifted help usage | #15893 | document terminal read --screen and realign drifted help usage | Standalone | Review soon | Medium |
| P2 | document worker-stop terminal-close contract | #13198 | document worker-stop terminal-close contract | Standalone | Request changes | Medium |
| P2 | don't hand a non-JS npm_execpath to node in build:native | #16657 | don't hand a non-JS npm_execpath to node in build:native | Standalone | Review soon | Medium |
| P2 | don't re-run an agent resume against a relay that never held the terminal (STA-5698) | #16989 | don't re-run an agent resume against a relay that never held the terminal (STA-5698) | Standalone | Review soon | Medium |
| P2 | drain the reaped child's journal writes before an attach reports | #17160 | drain the reaped child's journal writes before an attach reports | Standalone | Request changes | Medium |
| P2 | drop a recorded permission escalation the settings no longer grant | #15606 | drop a recorded permission escalation the settings no longer grant | Standalone | Review soon | Medium |
| P2 | drop disposed queued inspections | #17187 | drop disposed queued inspections | Standalone | Request changes | Medium |
| P2 | eliminate recurring PowerShell process polling | #17115 | eliminate recurring PowerShell process polling | Standalone | Request changes | Medium |
| P2 | emit browser_element_not_interactable for dead controls | #13243 | emit browser_element_not_interactable for dead controls | Standalone | Request changes | Medium |
| P2 | enable isolated floating tab reordering | #16754 | enable isolated floating tab reordering | Standalone | Review soon | Medium |
| P2 | enforce list-issues pagination backstops | #16128 | enforce list-issues pagination backstops | Standalone | Review soon | Medium |
| P2 | enforce one bounded structured writer | #14251 | enforce one bounded structured writer | Standalone | Defer | Medium |
| P2 | enforce the bridge contract the renderer already trusts | #17192 | enforce the bridge contract the renderer already trusts | Standalone | Merge | Medium |
| P2 | engage GPU software-rendering fallback across launches | #12488 | engage GPU software-rendering fallback across launches | Standalone | Request changes | Medium |
| P2 | escalate renderer launch-failed to a Restart Orca prompt instead of reloading a dead webCont | #12487 | escalate renderer launch-failed to a Restart Orca prompt instead of reloading a dead webCont | Standalone | Request changes | Medium |
| P2 | exclude a directory subtree in the git-grep search fallback | #15721 | exclude a directory subtree in the git-grep search fallback | Standalone | Review soon | Medium |
| P2 | expand serve host agent-skills install guide | #13262 | expand serve host agent-skills install guide | Standalone | Review soon | Medium |
| P2 | Explain broken npx shim skill update failures | #17028 | Explain broken npx shim skill update failures | Standalone | Review soon | Medium |
| P2 | explain tab titles vs agents paneKey join | #12813 | explain tab titles vs agents paneKey join | Standalone | Request changes | Medium |
| P2 | export plugin factory instead of object default (#16245) | #16270 | export plugin factory instead of object default (#16245) | Standalone | Review soon | Medium |
| P2 | Expose active workspace in macOS window metadata | #12569 | Expose active workspace in macOS window metadata | Standalone | Request changes | Medium |
| P2 | expose client-hosted tab placement (STA-5504) | #16502 | expose client-hosted tab placement (STA-5504) | Standalone | Review soon | Medium |
| P2 | fail safe on concurrent WSL auth drain writes | #16786 | fail safe on concurrent WSL auth drain writes | Standalone | Review soon | Medium |
| P2 | fail terminal create without a terminal handle | #13204 | fail terminal create without a terminal handle | Standalone | Request changes | Medium |
| P2 | fail worker startup on early agent exit | #16233 | fail worker startup on early agent exit | Standalone | Review soon | Medium |
| P2 | fall back to default Pi/OMP session roots for non-absolute env values | #13020 | fall back to default Pi/OMP session roots for non-absolute env values | Standalone | Review soon | Medium |
| P2 | fall back to parent-pane worktree for orchestration workers | #17019 | fall back to parent-pane worktree for orchestration workers | Standalone | Review soon | Medium |
| P2 | fall back when search-index lag returns zero items | #12819 #13138 #13561 | Coordinate 3 proposals for fall back when search-index lag returns zero items. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | fast-forward a claimed existing branch inside its new worktree (#15645) | #15868 | fast-forward a claimed existing branch inside its new worktree (#15645) | Standalone | Review soon | Medium |
| P2 | feed the relay-withheld reattach tail into main's model behind an ingest fence (STA-4716) | #15347 | feed the relay-withheld reattach tail into main's model behind an ingest fence (STA-4716) | Standalone | Review soon | Medium |
| P2 | fence final-pane close by incarnation (STA-4489) | #15582 | fence final-pane close by incarnation (STA-4489) | Standalone | Defer | Medium |
| P2 | fence I/O by process incarnation | #15585 | fence I/O by process incarnation | Standalone | Review soon | Medium |
| P2 | fill missing zh translations and align agent terminology policy | #17049 | fill missing zh translations and align agent terminology policy | Standalone | Review soon | Medium |
| P2 | fill OpenCode block glyphs in the DOM renderer | #15955 | fill OpenCode block glyphs in the DOM renderer | Standalone | Review soon | Medium |
| P2 | Filter workspaces by catalog agent | #15334 | Filter workspaces by catalog agent | Standalone | Review soon | Medium |
| P2 | find the SFTP-visible home below a chrooted start directory | #17073 | find the SFTP-visible home below a chrooted start directory | Standalone | Review soon | Medium |
| P2 | finish agent list pagination | #16119 | finish agent list pagination | Standalone | Request changes | Medium |
| P2 | finish agent list pagination (ports #16119 onto main) | #17056 | finish agent list pagination (ports #16119 onto main) | Standalone | Review soon | Medium |
| P2 | Fix a skill install lock release moving a directory it no longer owns | #17118 | Fix a skill install lock release moving a directory it no longer owns | Standalone | Review soon | Medium |
| P2 | Fix authorization for coalesced worktree scans | #17112 | Fix authorization for coalesced worktree scans | Standalone | Review soon | Medium |
| P2 | Fix Chromium descriptor inheritance into the terminal daemon and its PTY children (Linux/Win | #16963 | Fix Chromium descriptor inheritance into the terminal daemon and its PTY children (Linux/Win | Standalone | Review soon | Medium |
| P2 | Fix inherited PTY setup launch state | #16909 | Fix inherited PTY setup launch state | Standalone | Review soon | Medium |
| P2 | Fix inline agent mouse wheel scrolling | #17103 | Fix inline agent mouse wheel scrolling | Standalone | Review soon | Medium |
| P2 | Fix installed skill visibility by provider registry | #16284 | Fix installed skill visibility by provider registry | Standalone | Review soon | Medium |
| P2 | Fix macOS daemon PTY kqueue descriptor leak | #16870 | Fix macOS daemon PTY kqueue descriptor leak | Standalone | Review soon | Medium |
| P2 | Fix macOS updater relaunch races during installation | #17137 | Fix macOS updater relaunch races during installation | Standalone | Review soon | Medium |
| P2 | Fix mobile browser frames after reconnect (STA-4128) | #16122 | Fix mobile browser frames after reconnect (STA-4128) | Standalone | Request changes | Medium |
| P2 | Fix mobile capability recovery after reconnect | #16850 | Fix mobile capability recovery after reconnect | Standalone | Review soon | Medium |
| P2 | Fix orchestration CLI recovery, settled-Dispatch mail, and guide defects | #16919 | Fix orchestration CLI recovery, settled-Dispatch mail, and guide defects | Standalone | Review soon | Medium |
| P2 | Fix orchestration delivery head-of-line visibility | #16840 | Fix orchestration delivery head-of-line visibility | Standalone | Review soon | Medium |
| P2 | Fix paired web skill commands to use host platform | #16072 | Fix paired web skill commands to use host platform | Standalone | Defer | Medium |
| P2 | Fix populated sidebar lineage drop targets | #15167 | Fix populated sidebar lineage drop targets | Standalone | Defer | Medium |
| P2 | Fix PR unlink for auto-detected reviews | #16898 | Fix PR unlink for auto-detected reviews | Standalone | Review soon | Medium |
| P2 | Fix review note shortcuts in AI diffs | #15255 | Fix review note shortcuts in AI diffs | Standalone | Review soon | Medium |
| P2 | Fix sidebar grouping for paired remote projects | #16315 | Fix sidebar grouping for paired remote projects | Standalone | Review soon | Medium |
| P2 | flag a config host whose machine is already registered under another name | #15750 | flag a config host whose machine is already registered under another name | Standalone | Review soon | Medium |
| P2 | focus the pane a host-delegated split creates | #16513 #16886 | Coordinate 2 proposals for focus the pane a host-delegated split creates. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | follow agent-side session renames in agent rows | #16431 | follow agent-side session renames in agent rows | Standalone | Review soon | Medium |
| P2 | follow live Claude session names instead of the first prompt (STA-4865) | #15659 | follow live Claude session names instead of the first prompt (STA-4865) | Standalone | Request changes | Medium |
| P2 | forward the client's resolved agent args to paired hosts | #15867 | forward the client's resolved agent args to paired hosts | Standalone | Review soon | Medium |
| P2 | Gate paired-runtime terminal mounts on host snapshots | #15624 #15807 | Coordinate 2 proposals for Gate paired-runtime terminal mounts on host snapshots. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | gate pending agent-status retries | #17254 | gate pending agent-status retries | Standalone | Review soon | Medium |
| P2 | gate the CDP proxy on Origin and loopback Host | #12921 | gate the CDP proxy on Origin and loopback Host | Standalone | Request changes | Medium |
| P2 | gate the OSC 9999 parser with a pane-bound nonce | #14709 | gate the OSC 9999 parser with a pane-bound nonce | Standalone | Request changes | Medium |
| P2 | GC expired proven-absent leaf PTY verdicts | #12810 #13146 | Coordinate 2 proposals for GC expired proven-absent leaf PTY verdicts. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | give each worktree its own dev userData profile | #15648 | give each worktree its own dev userData profile | Standalone | Review soon | Medium |
| P2 | give Orca's own durable deletions the rm retry policy | #17252 | give Orca's own durable deletions the rm retry policy | Standalone | Request changes | Medium |
| P2 | give terminal send a lossless payload route with --text-stdin | #12239 | give terminal send a lossless payload route with --text-stdin | Standalone | Request changes | Medium |
| P2 | give the CLI one entrypoint by extracting the AppImage once | #15081 | give the CLI one entrypoint by extracting the AppImage once | Standalone | Review soon | Medium |
| P2 | give the listener lists one registration path | #17279 | give the listener lists one registration path | Standalone | Merge | Medium |
| P2 | give the Windows lane's teardowns the repo's rm retry policy | #17227 | give the Windows lane's teardowns the repo's rm retry policy | Standalone | Review soon | Medium |
| P2 | give user-facing deletions the repo's rm retry policy | #17245 | give user-facing deletions the repo's rm retry policy | Standalone | Review soon | Medium |
| P2 | guarantee directory handle closure via fs-opendir-scope | #17035 | guarantee directory handle closure via fs-opendir-scope | Standalone | Review soon | Medium |
| P2 | harden regional preference recovery | #16487 | harden regional preference recovery | Standalone | Review soon | Medium |
| P2 | hibernate Hermes sessions | #12075 | hibernate Hermes sessions | Standalone | Request changes | Medium |
| P2 | Highlight incomplete onboarding progress in the sidebar | #16547 | Highlight incomplete onboarding progress in the sidebar | Standalone | Review soon | Medium |
| P2 | highlight systemd and Quadlet unit files | #15571 | highlight systemd and Quadlet unit files | Standalone | Review soon | Medium |
| P2 | highlight XAML files as XML | #16530 | highlight XAML files as XML | Standalone | Review soon | Medium |
| P2 | honor pinned workspace display preference | #15495 #15881 | Coordinate 2 proposals for honor pinned workspace display preference. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | honor the per-host workspace directory when resolving worktree paths | #15321 | honor the per-host workspace directory when resolving worktree paths | Standalone | Review soon | Medium |
| P2 | honour the step in a cron field's bare start value (5/15 ran hourly) | #15605 #15864 | Coordinate 2 proposals for honour the step in a cron field's bare start value (5/15 ran hourly). | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | ignore orphan remote-tracking refs in branch conflicts | #16699 | ignore orphan remote-tracking refs in branch conflicts | Standalone | Review soon | Medium |
| P2 | ignore status posts from an extension Orca did not launch | #17243 | ignore status posts from an extension Orca did not launch | Standalone | Review soon | Medium |
| P2 | include open files in all-types cycling | #16422 | include open files in all-types cycling | Standalone | Review soon | Medium |
| P2 | include verified selected home in resume discovery snapshot (STA-4919) | #15660 | include verified selected home in resume discovery snapshot (STA-4919) | Standalone | Review soon | Medium |
| P2 | index folder-workspace tabs so they are reachable from the palette | #17039 | index folder-workspace tabs so they are reachable from the palette | Standalone | Review soon | Medium |
| P2 | index unread completion tabs once per snapshot | #17246 | index unread completion tabs once per snapshot | Standalone | Merge | Medium |
| P2 | install anti-detection before first document | #14796 | install anti-detection before first document | Standalone | Review soon | Medium |
| P2 | install SSH Codex hooks into login-shell CODEX_HOME (STA-4054) | #15715 | install SSH Codex hooks into login-shell CODEX_HOME (STA-4054) | Standalone | Review soon | Medium |
| P2 | install supervisor disconnect quit after app environment init | #16762 | install supervisor disconnect quit after app environment init | Standalone | Review soon | Medium |
| P2 | keep a Claude pane spinning across a mid-turn Orca restart | #16538 | keep a Claude pane spinning across a mid-turn Orca restart | Standalone | Request changes | Medium |
| P2 | keep a composition tail in the colours its cells had | #16024 | keep a composition tail in the colours its cells had | Standalone | Review soon | Medium |
| P2 | keep a deliberately slept workspace from respawning its PTY | #13343 | keep a deliberately slept workspace from respawning its PTY | Standalone | Request changes | Medium |
| P2 | keep a tab launch draft out of split sibling composers | #16883 | keep a tab launch draft out of split sibling composers | Standalone | Request changes | Medium |
| P2 | keep a workspace Windows refused to delete, and say why | #17173 | keep a workspace Windows refused to delete, and say why | Standalone | Review soon | Medium |
| P2 | keep agent input cursor on the prompt after buffer replay | #12808 | keep agent input cursor on the prompt after buffer replay | Standalone | Request changes | Medium |
| P2 | keep Android layout intact in Samsung DeX / external-display windows | #16018 | keep Android layout intact in Samsung DeX / external-display windows | Standalone | Review soon | Medium |
| P2 | keep archived sessions out of backfill | #14029 | keep archived sessions out of backfill | Standalone | Review soon | Medium |
| P2 | keep attach guard behind client timeout | #16415 | keep attach guard behind client timeout | Standalone | Review soon | Medium |
| P2 | keep authenticated hosts on partial auth failure | #13052 | keep authenticated hosts on partial auth failure | Standalone | Review soon | Medium |
| P2 | keep cold workspace search within frame budget | #15683 | keep cold workspace search within frame budget | Standalone | Defer | Medium |
| P2 | keep currency dollars out of markdown math spans | #13551 | keep currency dollars out of markdown math spans | Standalone | Merge | Medium |
| P2 | keep currency dollars out of rich-editor math spans | #15677 | keep currency dollars out of rich-editor math spans | Standalone | Review soon | Medium |
| P2 | keep current notification session | #16997 #17068 | Coordinate 2 proposals for keep current notification session. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | keep gh auth prompts from dying on OSC 11 replies | #14170 | keep gh auth prompts from dying on OSC 11 replies | Standalone | Request changes | Medium |
| P2 | keep Hangul composition intact while a turn streams | #16938 #17169 | Coordinate 2 proposals for keep Hangul composition intact while a turn streams. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | keep keystroke echo responsive under dense-SGR output floods | #12525 #12624 | Coordinate 2 proposals for keep keystroke echo responsive under dense-SGR output floods. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | keep launched agent rows after conversation titles | #15665 | keep launched agent rows after conversation titles | Standalone | Review soon | Medium |
| P2 | keep low-contrast themes legible in match-terminal sidebar and terminal ghost text | #17000 | keep low-contrast themes legible in match-terminal sidebar and terminal ghost text | Standalone | Review soon | Medium |
| P2 | keep named Codex App tasks and parent rollouts | #15062 | keep named Codex App tasks and parent rollouts | Standalone | Review soon | Medium |
| P2 | keep OMP identity and forward ask/approval events | #15713 | keep OMP identity and forward ask/approval events | Standalone | Review soon | Medium |
| P2 | keep OpenCode identity through Claude hooks | #13385 | keep OpenCode identity through Claude hooks | Standalone | Defer | Medium |
| P2 | keep parent session icon under nested Claude/Codex | #14012 | keep parent session icon under nested Claude/Codex | Standalone | Review soon | Medium |
| P2 | keep pasted issue images off Windows gh argv (#15832) | #15877 | keep pasted issue images off Windows gh argv (#15832) | Standalone | Review soon | Medium |
| P2 | keep project header labels from switching to the repo name | #16877 | keep project header labels from switching to the repo name | Standalone | Review soon | Medium |
| P2 | Keep project ring positions stable across Agent Map repacks | #17018 | Keep project ring positions stable across Agent Map repacks | Standalone | Review soon | Medium |
| P2 | keep recoverable connect failures revivable | #13150 | keep recoverable connect failures revivable | Standalone | Review soon | Medium |
| P2 | keep remote browsers usable across mixed versions | #14987 | keep remote browsers usable across mixed versions | Standalone | Review soon | Medium |
| P2 | keep remote-runtime agent sessions visible while parked | #15443 | keep remote-runtime agent sessions visible while parked | Standalone | Review soon | Medium |
| P2 | keep same-host same-remote clones as separate projects | #16388 | keep same-host same-remote clones as separate projects | Standalone | Review soon | Medium |
| P2 | keep spaced batch launcher paths intact when spawning | #13501 | keep spaced batch launcher paths intact when spawning | Standalone | Request changes | Medium |
| P2 | keep the changed-code quality gate runnable on huge changed sets | #17201 | keep the changed-code quality gate runnable on huge changed sets | Standalone | Review soon | Medium |
| P2 | keep the first font-family when importing config | #16090 | keep the first font-family when importing config | Standalone | Review soon | Medium |
| P2 | keep the host pill legible on the selected workspace card | #15975 | keep the host pill legible on the selected workspace card | Standalone | Review soon | Medium |
| P2 | keep the launch ack from re-pinging quoted mentions | #16273 | keep the launch ack from re-pinging quoted mentions | Standalone | Defer | Medium |
| P2 | keep the PR branch name when the push target is unresolved | #17021 | keep the PR branch name when the push target is unresolved | Standalone | Review soon | Medium |
| P2 | Keep the preview open when it sends you to the worktree | #16866 | Keep the preview open when it sends you to the worktree | Standalone | Review soon | Medium |
| P2 | keep transcript selections alive through pane pointerdown | #16468 | keep transcript selections alive through pane pointerdown | Standalone | Review soon | Medium |
| P2 | keep WSL API-key runtime auth from being restored as ChatGPT | #15819 | keep WSL API-key runtime auth from being restored as ChatGPT | Standalone | Request changes | Medium |
| P2 | Keep your WSL Claude profile when switching accounts | #12226 | Keep your WSL Claude profile when switching accounts | Standalone | Defer | Medium |
| P2 | key task presets on statusCategory instead of resolution | #16809 | key task presets on statusCategory instead of resolution | Standalone | Review soon | Medium |
| P2 | land on the previously active tab when the last tab of a kind closes | #15114 | land on the previously active tab when the last tab of a kind closes | Standalone | Review soon | Medium |
| P2 | land the lazy-chunk recovery reload instead of letting the navigation guard veto it | #12489 | land the lazy-chunk recovery reload instead of letting the navigation guard veto it | Standalone | Request changes | Medium |
| P2 | Lead the dashboard card with its review, its CI, and its ticket | #16856 | Lead the dashboard card with its review, its CI, and its ticket | Standalone | Review soon | Medium |
| P2 | lengthen background no-PR refresh interval | #12162 | lengthen background no-PR refresh interval | Standalone | Request changes | Medium |
| P2 | let a live renderer heal an unavailable graph | #16708 | let a live renderer heal an unavailable graph | Standalone | Review soon | Medium |
| P2 | let a live text selection keep Cmd+C | #16744 | let a live text selection keep Cmd+C | Standalone | Review soon | Medium |
| P2 | Let an idle Agent Dashboard card remove its worktree | #16858 | Let an idle Agent Dashboard card remove its worktree | Standalone | Review soon | Medium |
| P2 | let language packs translate the install form and log controls | #14121 | let language packs translate the install form and log controls | Standalone | Review soon | Medium |
| P2 | Let macOS actually ask for notification permission instead of silently claiming it was grant | #12210 | Let macOS actually ask for notification permission instead of silently claiming it was grant | Standalone | Request changes | Medium |
| P2 | let Pi use its configured default model | #15649 | let Pi use its configured default model | Standalone | Request changes | Medium |
| P2 | let sandboxed panels call storage.get, so a panel can render live state | #15643 | let sandboxed panels call storage.get, so a panel can render live state | Standalone | Review soon | Medium |
| P2 | let the agent drawer yield to the page the user just opened | #16599 | let the agent drawer yield to the page the user just opened | Standalone | Review soon | Medium |
| P2 | link worker-created sub-Runs | #16784 | link worker-created sub-Runs | Standalone | Review soon | Medium |
| P2 | load the next page of commits on scroll | #14472 | load the next page of commits on scroll | Standalone | Review soon | Medium |
| P2 | Local PTY inspection: degraded reads become unverifiable evidence, not agent exits | #16955 | Local PTY inspection: degraded reads become unverifiable evidence, not agent exits | Standalone | Review soon | Medium |
| P2 | localize Orca Account settings and navigation to Korean | #15849 | localize Orca Account settings and navigation to Korean | Standalone | Review soon | Medium |
| P2 | localize the remaining contextual tour steps | #12713 | localize the remaining contextual tour steps | Standalone | Request changes | Medium |
| P2 | lock in upstream->origin API repository fallback (#16474) | #16483 | lock in upstream->origin API repository fallback (#16474) | Standalone | Review soon | Medium |
| P2 | make agent markdown text selectable | #16534 | make agent markdown text selectable | Standalone | Review soon | Medium |
| P2 | make chunk-load recovery real — epoch-gated retry and a main-process Restart action | #14661 | make chunk-load recovery real — epoch-gated retry and a main-process Restart action | Standalone | Review soon | Medium |
| P2 | make Claude /resume reachable from Orca Mobile (STA-4617) | #16684 | make Claude /resume reachable from Orca Mobile (STA-4617) | Standalone | Review soon | Medium |
| P2 | Make local Git metadata observation event-driven | #16352 | Make local Git metadata observation event-driven | Standalone | Request changes | Medium |
| P2 | make new-project dialog popovers scrollable | #16413 | make new-project dialog popovers scrollable | Standalone | Review soon | Medium |
| P2 | make pid-record publish atomic via claim-then-link | #16924 | make pid-record publish atomic via claim-then-link | Standalone | Review soon | Medium |
| P2 | Make post-paste submit delay per-agent, bump codex to 300ms | #16716 | Make post-paste submit delay per-agent, bump codex to 300ms | Standalone | Request changes | Medium |
| P2 | make Settings skill install unattended | #13948 #15669 | Coordinate 2 proposals for make Settings skill install unattended. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | make shard 15 failures deterministic | #16871 | make shard 15 failures deterministic | Standalone | Review soon | Medium |
| P2 | make the cold-hydration spec check its own captured snapshot | #17031 | make the cold-hydration spec check its own captured snapshot | Standalone | Review soon | Medium |
| P2 | make the Copy context selection hint clickable | #16204 | make the Copy context selection hint clickable | Standalone | Review soon | Medium |
| P2 | make the macOS click fence diagnosable and settle its pre-press probe | #15102 | make the macOS click fence diagnosable and settle its pre-press probe | Standalone | Review soon | Medium |
| P2 | make the max-lines ratchet and perf benches actually gate, and give PTY state an owner | #15727 | make the max-lines ratchet and perf benches actually gate, and give PTY state an owner | Standalone | Review soon | Medium |
| P2 | make the POSIX hook command spawnable as argv[0] | #16222 | make the POSIX hook command spawnable as argv[0] | Standalone | Review soon | Medium |
| P2 | make the Reporter field a real user picker so issues can be created | #17090 | make the Reporter field a real user picker so issues can be created | Standalone | Review soon | Medium |
| P2 | make viewport presets scrollable when larger than the pane | #13294 | make viewport presets scrollable when larger than the pane | Standalone | Request changes | Medium |
| P2 | mark sidebar done on idle_prompt and StopCancelled | #15230 | mark sidebar done on idle_prompt and StopCancelled | Standalone | Review soon | Medium |
| P2 | match mirrored targets to runtime terminals | #16231 | match mirrored targets to runtime terminals | Standalone | Review soon | Medium |
| P2 | match permission title keywords on word boundaries | #15729 | match permission title keywords on word boundaries | Standalone | Review soon | Medium |
| P2 | match WSL /mnt/c sessions to Windows workspaces (STA-4973) | #15650 | match WSL /mnt/c sessions to Windows workspaces (STA-4973) | Standalone | Request changes | Medium |
| P2 | move the Google cookie clear into Settings, behind a confirmation | #14686 | move the Google cookie clear into Settings, behind a confirmation | Standalone | Review soon | Medium |
| P2 | Name the command each agent is running, on its card | #16860 | Name the command each agent is running, on its card | Standalone | Review soon | Medium |
| P2 | name the id-kind mismatch when --ack is given a message id | #15743 | name the id-kind mismatch when --ack is given a message id | Standalone | Review soon | Medium |
| P2 | narrow status observer updates | #17249 | narrow status observer updates | Standalone | Merge | Medium |
| P2 | never publish a usage reply Orca could not read as a successful reading | #17193 | never publish a usage reply Orca could not read as a successful reading | Standalone | Review soon | Medium |
| P2 | Never read an unanswerable hasPty probe as proven PTY absence | #16932 | Never read an unanswerable hasPty probe as proven PTY absence | Standalone | Review soon | Medium |
| P2 | notify only after turn finalization | #12837 | notify only after turn finalization | Standalone | Defer | Medium |
| P2 | notify the renderer when the active account changes outside it | #17265 | notify the renderer when the active account changes outside it | Standalone | Merge | Medium |
| P2 | omit SYSTEMROOT from POSIX Claude-compat hook commands | #17203 | omit SYSTEMROOT from POSIX Claude-compat hook commands | Standalone | Merge | Medium |
| P2 | one oversized-file limit and a recoverable Open Anyway path | #16595 | one oversized-file limit and a recoverable Open Anyway path | Standalone | Review soon | Medium |
| P2 | only spend auto-recovery on the real deadline | #13153 | only spend auto-recovery on the real deadline | Standalone | Review soon | Medium |
| P2 | only the Windows console-limit failure keeps a dead terminal open (STA-5604) | #16991 | only the Windows console-limit failure keeps a dead terminal open (STA-5604) | Standalone | Review soon | Medium |
| P2 | open Runtime worktrees in external editors | #15129 | open Runtime worktrees in external editors | Standalone | Request changes | Medium |
| P2 | open the window before asking the OS keyring about stored secrets | #17015 | open the window before asking the OS keyring about stored secrets | Standalone | Review soon | Medium |
| P2 | pace the EAGAIN write retry so a stalled reader can't saturate the daemon thread | #15319 | pace the EAGAIN write retry so a stalled reader can't saturate the daemon thread | Standalone | Review soon | Medium |
| P2 | parse Grok question option payloads | #16343 | parse Grok question option payloads | Standalone | Defer | Medium |
| P2 | parse partial-clone remote filters | #16371 | parse partial-clone remote filters | Standalone | Review soon | Medium |
| P2 | partition workspace sessions | #16178 | partition workspace sessions | Standalone | Review soon | Medium |
| P2 | Pass paired Web UI context into agent sessions | #17043 | Pass paired Web UI context into agent sessions | Standalone | Review soon | Medium |
| P2 | paste OS-copied files through target host | #15521 | paste OS-copied files through target host | Standalone | Review soon | Medium |
| P2 | Per-agent terminal theme overrides in Settings → Appearance | #14186 | Per-agent terminal theme overrides in Settings → Appearance | Standalone | Review soon | Medium |
| P2 | persist exact terminal owner identity | #16277 | persist exact terminal owner identity | Standalone | Review soon | Medium |
| P2 | persist the dispatch_input failure cause on the Dispatch | #15964 | persist the dispatch_input failure cause on the Dispatch | Standalone | Review soon | Medium |
| P2 | pin recoverable worker start receipt (STA-4674) | #16848 | pin recoverable worker start receipt (STA-4674) | Standalone | Review soon | Medium |
| P2 | pin the migration-unsupported replay as unreachable | #17269 | pin the migration-unsupported replay as unreachable | Standalone | Merge | Medium |
| P2 | prefer Pi/OMP harness names in session history (STA-2467) | #15696 | prefer Pi/OMP harness names in session history (STA-2467) | Standalone | Request changes | Medium |
| P2 | prefer stored worker defaults in worker-start guidance | #15568 | prefer stored worker defaults in worker-start guidance | Standalone | Review soon | Medium |
| P2 | preserve consent-gated Claude models (STA-4834) | #15664 #15865 | Coordinate 2 proposals for preserve consent-gated Claude models (STA-4834). | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | preserve Ctrl+Shift chords for direct OMP launches | #17082 | preserve Ctrl+Shift chords for direct OMP launches | Standalone | Review soon | Medium |
| P2 | preserve desktop custom terminal titles | #16202 | preserve desktop custom terminal titles | Standalone | Review soon | Medium |
| P2 | Preserve exact linked tasks in automations | #15374 | Preserve exact linked tasks in automations | Standalone | Review soon | Medium |
| P2 | Preserve legacy daemon ownership when liveness is unavailable | #16900 | Preserve legacy daemon ownership when liveness is unavailable | Standalone | Review soon | Medium |
| P2 | preserve local file tab order | #13233 #16085 | Coordinate 2 proposals for preserve local file tab order. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | preserve ordinary user-set config keys across managed-home remirrors | #15682 | preserve ordinary user-set config keys across managed-home remirrors | Standalone | Review soon | Medium |
| P2 | preserve OS trust and network policy for first-party traffic | #16399 | preserve OS trust and network policy for first-party traffic | Standalone | Review soon | Medium |
| P2 | preserve paired web host identity | #14364 | preserve paired web host identity | Standalone | Defer | Medium |
| P2 | preserve pane identity for agent-name task titles | #15037 | preserve pane identity for agent-name task titles | Standalone | Review soon | Medium |
| P2 | preserve remote CLI argument boundaries | #16320 | preserve remote CLI argument boundaries | Standalone | Review soon | Medium |
| P2 | preserve rich markdown selection across tab switches | #14940 | preserve rich markdown selection across tab switches | Standalone | Review soon | Medium |
| P2 | preserve terminals during transient mount loss | #16966 | preserve terminals during transient mount loss | Standalone | Review soon | Medium |
| P2 | preserve unmounted mobile browser tabs | #14792 | preserve unmounted mobile browser tabs | Standalone | Review soon | Medium |
| P2 | preserve untouched markdown bytes when saving from the rich editor (#16469) | #16479 | preserve untouched markdown bytes when saving from the rich editor (#16469) | Standalone | Review soon | Medium |
| P2 | preserve user ZDOTDIR in the zsh overlay instead of collapsing to $HOME (#12507) | #12543 | preserve user ZDOTDIR in the zsh overlay instead of collapsing to $HOME (#12507) | Standalone | Request changes | Medium |
| P2 | preserve worktree names across scan stalls | #16723 | preserve worktree names across scan stalls | Standalone | Review soon | Medium |
| P2 | press keys through a US-layout CDP key table instead of a subprocess per keystroke | #15310 | press keys through a US-layout CDP key table instead of a subprocess per keystroke | Standalone | Review soon | Medium |
| P2 | prevent Create from hanging on selected PR | #17153 | prevent Create from hanging on selected PR | Standalone | Request changes | Medium |
| P2 | prevent restored terminal spawn storms | #15742 | prevent restored terminal spawn storms | Standalone | Review soon | Medium |
| P2 | project providerSession.id as sessionId on agent.status.changed | #15640 #15680 | Coordinate 2 proposals for project providerSession.id as sessionId on agent.status.changed. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | promote folders that become git repos without re-add | #15694 | promote folders that become git repos without re-add | Standalone | Review soon | Medium |
| P2 | protect repository-managed hook config symlinks | #15831 | protect repository-managed hook config symlinks | Standalone | Review soon | Medium |
| P2 | prove visible terminal identity | #17139 | prove visible terminal identity | Standalone | Review soon | Medium |
| P2 | provenance-gated PTY-churn RSS harness + STA-3515 re-measurement on a #16870-inclusive build | #16948 | provenance-gated PTY-churn RSS harness + STA-3515 re-measurement on a #16870-inclusive build | Standalone | Review soon | Medium |
| P2 | put pinned folder workspaces in the Pinned section | #16799 | put pinned folder workspaces in the Pinned section | Standalone | Review soon | Medium |
| P2 | rank Ctrl+P results with recent file history | #16579 | rank Ctrl+P results with recent file history | Standalone | Review soon | Medium |
| P2 | rank tui-idle evidence instead of inferring idle from silence | #14642 | rank tui-idle evidence instead of inferring idle from silence | Standalone | Review soon | Medium |
| P2 | rate-cap WebGL glyph-atlas recovery on streaming output | #12486 | rate-cap WebGL glyph-atlas recovery on streaming output | Standalone | Request changes | Medium |
| P2 | re-land WSL direct-home cutover with counsel findings fixed | #16854 | re-land WSL direct-home cutover with counsel findings fixed | Standalone | Review soon | Medium |
| P2 | reap the proven relay generation instead of orphaning it (#8585) | #12760 #15489 | Coordinate 2 proposals for reap the proven relay generation instead of orphaning it (#8585). | Competing | Choose one preferred solution | Medium |
| P2 | recognize Antigravity 1.1.17 ready prompt | #15840 #15852 | Coordinate 2 proposals for recognize Antigravity 1.1.17 ready prompt. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | recognize Cline OSC titles in worktree agent rows | #13959 | recognize Cline OSC titles in worktree agent rows | Standalone | Review soon | Medium |
| P2 | recognize symlinks targeting canonical skill location as provider aliases | #16459 | recognize symlinks targeting canonical skill location as provider aliases | Standalone | Review soon | Medium |
| P2 | record post-startup process exits (STA-5709) | #16875 | record post-startup process exits (STA-5709) | Standalone | Review soon | Medium |
| P2 | recover commit ref badges on Git before 2.43 | #15508 #15590 | Coordinate 2 proposals for recover commit ref badges on Git before 2.43. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | recover oversized workspace updates | #15929 | recover oversized workspace updates | Standalone | Review soon | Medium |
| P2 | recover stripped task deps | #16743 | recover stripped task deps | Standalone | Review soon | Medium |
| P2 | recover terminals after headless serve restarts | #13247 | recover terminals after headless serve restarts | Standalone | Request changes | Medium |
| P2 | recover the runtime host disconnected glyph | #16518 | recover the runtime host disconnected glyph | Standalone | Review soon | Medium |
| P2 | Recover unreachable main windows after display changes | #17080 | Recover unreachable main windows after display changes | Standalone | Request changes | Medium |
| P2 | Refresh current LAN endpoints while a phone is on Relay | #14576 | Refresh current LAN endpoints while a phone is on Relay | Standalone | Review soon | Medium |
| P2 | refuse to submit a CLI prompt over an unsent composer draft | #16290 | refuse to submit a CLI prompt over an unsent composer draft | Standalone | Review soon | Medium |
| P2 | register dir-handle-closure reliability gate | #17034 | register dir-handle-closure reliability gate | Standalone | Review soon | Medium |
| P2 | reject claims about the private reference corpus in changed files | #17063 | reject claims about the private reference corpus in changed files | Standalone | Review soon | Medium |
| P2 | reject empty terminal handles | #16742 #16745 | Coordinate 2 proposals for reject empty terminal handles. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | reject locale ids Intl cannot parse | #12533 | reject locale ids Intl cannot parse | Standalone | Review soon | Medium |
| P2 | reject malformed base64 padding | #12027 | reject malformed base64 padding | Standalone | Review soon | Medium |
| P2 | reject requests for detached clients | #16321 | reject requests for detached clients | Standalone | Review soon | Medium |
| P2 | release browser driver state after desktop takeover | #15754 | release browser driver state after desktop takeover | Standalone | Review soon | Medium |
| P2 | release completed worker terminals by default | #16217 | release completed worker terminals by default | Standalone | Review soon | Medium |
| P2 | release popup origin bar contents | #17234 | release popup origin bar contents | Standalone | Merge | Medium |
| P2 | remove dead hook IPC and derive shared agent defaults | #16089 | remove dead hook IPC and derive shared agent defaults | Standalone | Review soon | Medium |
| P2 | Remove experimental feature requirement from orchestration guide | #14064 | Remove experimental feature requirement from orchestration guide | Standalone | Request changes | Medium |
| P2 | remove legacy Gemini CLI support | #12789 | remove legacy Gemini CLI support | Standalone | Request changes | Medium |
| P2 | rename a pane by double-clicking its header | #15792 | rename a pane by double-clicking its header | Standalone | Defer | Medium |
| P2 | render every failed-source repo instead of silently dropping it (#16473) | #16482 | render every failed-source repo instead of silently dropping it (#16473) | Standalone | Review soon | Medium |
| P2 | render the streaming reply below the prompt it answers | #15609 | render the streaming reply below the prompt it answers | Standalone | Review soon | Medium |
| P2 | Replace Electron desktop host with Tauri/Pake | #15340 | Replace Electron desktop host with Tauri/Pake | Standalone | Defer | Medium |
| P2 | report a missing display instead of dying in uv_close | #15084 | report a missing display instead of dying in uv_close | Standalone | Request changes | Medium |
| P2 | report limited when an un-cursored read withholds transcript lines | #15269 | report limited when an un-cursored read withholds transcript lines | Standalone | Review soon | Medium |
| P2 | report OMP terminal and interactive states | #14279 #14605 | Coordinate 2 proposals for report OMP terminal and interactive states. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | require double Escape to interrupt Claude turns | #13566 #15674 | Coordinate 2 proposals for require double Escape to interrupt Claude turns. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | reset inherited zoom on remote and offscreen pages | #16676 | reset inherited zoom on remote and offscreen pages | Standalone | Review soon | Medium |
| P2 | reset question card state when prompt changes | #16934 | reset question card state when prompt changes | Standalone | Review soon | Medium |
| P2 | resolve --workspace-status by column name | #17135 | resolve --workspace-status by column name | Standalone | Review soon | Medium |
| P2 | resolve document tab close by id or entityId (#16205) | #16480 | resolve document tab close by id or entityId (#16205) | Standalone | Review soon | Medium |
| P2 | resolve Linux Git metadata paths on Windows | #17175 | resolve Linux Git metadata paths on Windows | Standalone | Review soon | Medium |
| P2 | resolve plugin-pack plurals with the declared locale | #12505 | resolve plugin-pack plurals with the declared locale | Standalone | Review soon | Medium |
| P2 | resolve watcher targets concurrently | #17166 | resolve watcher targets concurrently | Standalone | Review soon | Medium |
| P2 | restore Antigravity workspace metadata | #15775 | restore Antigravity workspace metadata | Standalone | Review soon | Medium |
| P2 | restore Cursor status updates in reused panes | #12714 #14626 #15695 | Coordinate 3 proposals for restore Cursor status updates in reused panes. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | restore Cursor workspace metadata | #14482 | restore Cursor workspace metadata | Standalone | Review soon | Medium |
| P2 | restore gated PTY buffer on hidden-to-visible reveal | #15689 | restore gated PTY buffer on hidden-to-visible reveal | Standalone | Review soon | Medium |
| P2 | restore lossy initial remote snapshots | #17113 | restore lossy initial remote snapshots | Standalone | Review soon | Medium |
| P2 | restore sessions after restart via OpenCode-family hooks | #13990 | restore sessions after restart via OpenCode-family hooks | Standalone | Review soon | Medium |
| P2 | restore terminal input when reopening worktrees | #16239 | restore terminal input when reopening worktrees | Standalone | Review soon | Medium |
| P2 | restore the shell icon after an agent exits | #13776 #15711 | Coordinate 2 proposals for restore the shell icon after an agent exits. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | resume OMP sessions after worktree sleep | #16276 | resume OMP sessions after worktree sleep | Standalone | Review soon | Medium |
| P2 | resume quiet Claude sessions instead of restoring bare shells | #15701 | resume quiet Claude sessions instead of restoring bare shells | Standalone | Review soon | Medium |
| P2 | resync the file tree after a watch subscription gap | #15702 | resync the file tree after a watch subscription gap | Standalone | Review soon | Medium |
| P2 | Retain restored agents in worktree inventory after restart | #16156 | Retain restored agents in worktree inventory after restart | Standalone | Review soon | Medium |
| P2 | retain sleeping agent records until resume spawns | #16279 | retain sleeping agent records until resume spawns | Standalone | Review soon | Medium |
| P2 | retire a created pool name whatever the client claims (STA-4471) | #14919 | retire a created pool name whatever the client claims (STA-4471) | Standalone | Review soon | Medium |
| P2 | retire agent resume records past an absolute age | #16845 | retire agent resume records past an absolute age | Standalone | Review soon | Medium |
| P2 | retire empty previous-generation daemons after protocol bumps | #15670 | retire empty previous-generation daemons after protocol bumps | Standalone | Review soon | Medium |
| P2 | retire optimistic echoes the agent absorbed as a continuation | #15283 | retire optimistic echoes the agent absorbed as a continuation | Standalone | Review soon | Medium |
| P2 | retire orphaned relays during version GC instead of skipping them | #15636 #15691 | Coordinate 2 proposals for retire orphaned relays during version GC instead of skipping them. | Competing | Choose one preferred solution | Medium |
| P2 | retire resume state after confirmed agent exit | #14534 #15666 | Coordinate 2 proposals for retire resume state after confirmed agent exit. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | reuse rich-mode eligibility per render | #17219 | reuse rich-mode eligibility per render | Standalone | Review soon | Medium |
| P2 | reveal local worktrees even when a remote runtime is active | #16559 | reveal local worktrees even when a remote runtime is active | Standalone | Review soon | Medium |
| P2 | roll up cancelled checks as their own muted aggregate verdict | #15858 #15901 | Coordinate 2 proposals for roll up cancelled checks as their own muted aggregate verdict. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | route packaged CLI launches before Electron | #14006 | route packaged CLI launches before Electron | Standalone | Review soon | Medium |
| P2 | route reminted pane keys to canonical identity (STA-3993) | #15714 | route reminted pane keys to canonical identity (STA-3993) | Standalone | Review soon | Medium |
| P2 | route self-hosted hosts through GITLAB_HOST for mr/issue commands | #12310 | route self-hosted hosts through GITLAB_HOST for mr/issue commands | Standalone | Request changes | Medium |
| P2 | route the status-bar popover scan to the workspace's host | #17048 | route the status-bar popover scan to the workspace's host | Standalone | Review soon | Medium |
| P2 | route zoom gestures to PDF viewer | #17241 | route zoom gestures to PDF viewer | Standalone | Review soon | Medium |
| P2 | runtime-owned evidence for completion, gates, leases and worker identity | #17038 | runtime-owned evidence for completion, gates, leases and worker identity | Standalone | Review soon | Medium |
| P2 | Saving and editing files now works in a per-workspace environment | #12221 | Saving and editing files now works in a per-workspace environment | Standalone | Request changes | Medium |
| P2 | say when empty check still has sibling-run unread | #14751 | say when empty check still has sibling-run unread | Standalone | Review soon | Medium |
| P2 | say why the runtime is unreachable instead of reporting "starting" | #17164 | say why the runtime is unreachable instead of reporting "starting" | Standalone | Review soon | Medium |
| P2 | scale interactive-redraw windows by measured echo latency | #16268 | scale interactive-redraw windows by measured echo latency | Standalone | Review soon | Medium |
| P2 | scan SSH hosts owned by a paired runtime | #14171 | scan SSH hosts owned by a paired runtime | Standalone | Review soon | Medium |
| P2 | scope optimistic echoes to the conversation they were sent into | #15032 | scope optimistic echoes to the conversation they were sent into | Standalone | Review soon | Medium |
| P2 | seed list preview from daemon snapshots after restart (STA-4326) | #15679 | seed list preview from daemon snapshots after restart (STA-4326) | Standalone | Review soon | Medium |
| P2 | send a multi-line composer message as one paste | #15206 | send a multi-line composer message as one paste | Standalone | Request changes | Medium |
| P2 | send multi-line agent prompts from the launch paths as one paste | #15205 | send multi-line agent prompts from the launch paths as one paste | Standalone | Defer | Medium |
| P2 | send the caller handle from dispatch-show | #15965 | send the caller handle from dispatch-show | Standalone | Review soon | Medium |
| P2 | separate image attachment paths from following prompt text (STA-4847) | #15690 | separate image attachment paths from following prompt text (STA-4847) | Standalone | Review soon | Medium |
| P2 | separate session backfill baseline from launch updates | #16252 | separate session backfill baseline from launch updates | Standalone | Review soon | Medium |
| P2 | serve favicon.ico and favicon.png from headless orca serve | #14057 | serve favicon.ico and favicon.png from headless orca serve | Standalone | Review soon | Medium |
| P2 | set push.autoSetupRemote when claiming an existing local branch (#15645) | #15796 | set push.autoSetupRemote when claiming an existing local branch (#15645) | Standalone | Defer | Medium |
| P2 | settle CLI prompts for cursor-agent | #14851 | settle CLI prompts for cursor-agent | Standalone | Review soon | Medium |
| P2 | settle OMP status from agent-end contract | #14884 #15658 #17209 | Coordinate 3 proposals for settle OMP status from agent-end contract. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | share Git fixture command | #16155 | share Git fixture command | Standalone | Request changes | Medium |
| P2 | show Codex's effective model in the session picker (STA-4317) | #15688 | show Codex's effective model in the session picker (STA-4317) | Standalone | Review soon | Medium |
| P2 | Show remote host failure details in a submenu | #17062 | Show remote host failure details in a submenu | Standalone | Review soon | Medium |
| P2 | show resumed sessions in the worktree sidebar before the first prompt | #15097 | show resumed sessions in the worktree sidebar before the first prompt | Standalone | Review soon | Medium |
| P2 | show SSH labels in Run on picker | #16115 | show SSH labels in Run on picker | Standalone | Review soon | Medium |
| P2 | show the Active Server's usage in the rate-limit badges | #15804 #15880 | Coordinate 2 proposals for show the Active Server's usage in the rate-limit badges. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | show the cursor while a CJK preedit covers its cell | #16951 #17105 #17170 | Coordinate 3 proposals for show the cursor while a CJK preedit covers its cell. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | show unlimited Business usage | #16323 | show unlimited Business usage | Standalone | Review soon | Medium |
| P2 | size issue list columns by panel width, not viewport | #16627 | size issue list columns by panel width, not viewport | Standalone | Review soon | Medium |
| P2 | size the Windows launcher-compile test budget from measurement | #17116 | size the Windows launcher-compile test budget from measurement | Standalone | Review soon | Medium |
| P2 | skip Devin first-run workspace trust prompt | #15860 | skip Devin first-run workspace trust prompt | Standalone | Review soon | Medium |
| P2 | skip disabled diagnostic serialization | #17176 | skip disabled diagnostic serialization | Standalone | Merge | Medium |
| P2 | skip missing Windows repo worktree spawns | #17091 | skip missing Windows repo worktree spawns | Standalone | Review soon | Medium |
| P2 | skip unchanged cache rewrites | #16220 | skip unchanged cache rewrites | Standalone | Review soon | Medium |
| P2 | spin the dot for an agent the user started by hand | #15777 | spin the dot for an agent the user started by hand | Standalone | Review soon | Medium |
| P2 | Split relay Git handler responsibilities | #17217 | Split relay Git handler responsibilities | Standalone | Request changes | Medium |
| P2 | Split runtime file client layers | #17188 | Split runtime file client layers | Standalone | Request changes | Medium |
| P2 | Split Settings page responsibilities | #17271 | Split Settings page responsibilities | Standalone | Request changes | Medium |
| P2 | Split speech session lifecycle | #17123 | Split speech session lifecycle | Standalone | Review soon | Medium |
| P2 | stabilize E2E tests and document scheduled CI failures | #16721 | stabilize E2E tests and document scheduled CI failures | Standalone | Request changes | Medium |
| P2 | standardize Simplified Chinese product terminology | #15464 | standardize Simplified Chinese product terminology | Standalone | Defer | Medium |
| P2 | start an agent with a prompt at workspace creation | #15579 | start an agent with a prompt at workspace creation | Standalone | Defer | Medium |
| P2 | stop a failed delete showing Electron's IPC envelope | #17230 | stop a failed delete showing Electron's IPC envelope | Standalone | Review soon | Medium |
| P2 | stop calling a readiness timeout a failed launch | #15268 | stop calling a readiness timeout a failed launch | Standalone | Review soon | Medium |
| P2 | stop CLI commands from falling through to Chromium startup | #15083 | stop CLI commands from falling through to Chromium startup | Standalone | Request changes | Medium |
| P2 | stop cutting a failed fetch/pull/push down to git's closing line | #17275 | stop cutting a failed fetch/pull/push down to git's closing line | Standalone | Merge | Medium |
| P2 | stop deleting a workspace after confirm when it turns out to be busy | #17074 | stop deleting a workspace after confirm when it turns out to be busy | Standalone | Review soon | Medium |
| P2 | Stop Escape interrupting the agent from a dashboard preview | #16857 | Stop Escape interrupting the agent from a dashboard preview | Standalone | Review soon | Medium |
| P2 | stop leaking the Git credential guard into terminals Orca chose not to guard | #17014 | stop leaking the Git credential guard into terminals Orca chose not to guard | Standalone | Review soon | Medium |
| P2 | stop live output jumping off-screen | #16601 | stop live output jumping off-screen | Standalone | Review soon | Medium |
| P2 | stop multi-host project-group headers from colliding | #13599 #13611 | Coordinate 2 proposals for stop multi-host project-group headers from colliding. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | stop path resolution from creating ~/.claude | #16257 | stop path resolution from creating ~/.claude | Standalone | Review soon | Medium |
| P2 | stop path resolution from creating the config directory | #12309 | stop path resolution from creating the config directory | Standalone | Merge | Medium |
| P2 | stop permission-denied runtimes reporting starting | #16697 | stop permission-denied runtimes reporting starting | Standalone | Review soon | Medium |
| P2 | stop reading a missing worktree row as an empty tab list | #17223 | stop reading a missing worktree row as an empty tab list | Standalone | Merge | Medium |
| P2 | stop remote deletes from reappearing after path-spelling misses | #16782 | stop remote deletes from reappearing after path-spelling misses | Standalone | Review soon | Medium |
| P2 | stop reporting an unresumable delivery as a dead session | #14974 | stop reporting an unresumable delivery as a dead session | Standalone | Review soon | Medium |
| P2 | stop reporting Grok usage as 0% when the API omits the percent | #15878 | stop reporting Grok usage as 0% when the API omits the percent | Standalone | Review soon | Medium |
| P2 | stop runaway padding in serialized markdown tables | #13686 | stop runaway padding in serialized markdown tables | Standalone | Review soon | Medium |
| P2 | stop session scans stalling on stopped WSL distros | #15475 | stop session scans stalling on stopped WSL distros | Standalone | Review soon | Medium |
| P2 | stop shadowing navigator.webdriver on the instance | #17196 | stop shadowing navigator.webdriver on the instance | Standalone | Request changes | Medium |
| P2 | stop telling agents to detach worktree lineage | #15461 | stop telling agents to detach worktree lineage | Standalone | Review soon | Medium |
| P2 | stop the pane error toast showing Electron's IPC envelope | #17255 | stop the pane error toast showing Electron's IPC envelope | Standalone | Review soon | Medium |
| P2 | stop the skill picker cap from erasing whole scopes | #16462 | stop the skill picker cap from erasing whole scopes | Standalone | Review soon | Medium |
| P2 | stop the update scheduler when the app quits | #17221 | stop the update scheduler when the app quits | Standalone | Merge | Medium |
| P2 | stop the usage cards recommending orchestration for handoffs | #14996 | stop the usage cards recommending orchestration for handoffs | Standalone | Merge | Medium |
| P2 | stop treating waiting Actions as failures | #13609 #16632 | Coordinate 2 proposals for stop treating waiting Actions as failures. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | stop xterm.js version text leaking into Codex | #16491 | stop xterm.js version text leaking into Codex | Standalone | Review soon | Medium |
| P2 | submit Quick Commands in agent TUIs | #16562 | submit Quick Commands in agent TUIs | Standalone | Review soon | Medium |
| P2 | support raw HTML tags like <br> in markdown viewers | #13122 | support raw HTML tags like <br> in markdown viewers | Standalone | Request changes | Medium |
| P2 | support status authority without randomUUID | #16235 | support status authority without randomUUID | Standalone | Review soon | Medium |
| P2 | support strict bare repositories | #16446 | support strict bare repositories | Standalone | Review soon | Medium |
| P2 | suppress resume after relay replacement | #16839 | suppress resume after relay replacement | Standalone | Review soon | Medium |
| P2 | surface an unverifiable worktree dot when agent hooks are missing | #16104 | surface an unverifiable worktree dot when agent hooks are missing | Standalone | Review soon | Medium |
| P2 | surface blocked Delivery backlogs | #15469 | surface blocked Delivery backlogs | Standalone | Review soon | Medium |
| P2 | surface hidden command groups in root help | #13205 | surface hidden command groups in root help | Standalone | Request changes | Medium |
| P2 | surface host context labels on pinned worktree rows | #13424 #13572 | Coordinate 2 proposals for surface host context labels on pinned worktree rows. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | surface Pi tool approval requests as blocked | #17236 | surface Pi tool approval requests as blocked | Standalone | Merge | Medium |
| P2 | surface reserved-identity install errors for local forks | #12606 | surface reserved-identity install errors for local forks | Standalone | Review soon | Medium |
| P2 | survive a non-string repoId on hydrated setup rows | #16718 | survive a non-string repoId on hydrated setup rows | Standalone | Request changes | Medium |
| P2 | sweep descendants when tearing down hand-typed agent sessions | #16713 | sweep descendants when tearing down hand-typed agent sessions | Standalone | Review soon | Medium |
| P2 | sync agent default launch settings to paired runtime | #16566 | sync agent default launch settings to paired runtime | Standalone | Review soon | Medium |
| P2 | take hook-server alias ownership before replay, not after | #17262 | take hook-server alias ownership before replay, not after | Standalone | Merge | Medium |
| P2 | tear down terminals on deletion | #13615 | tear down terminals on deletion | Standalone | Request changes | Medium |
| P2 | treat a dead status owner PID as claimable | #16118 | treat a dead status owner PID as claimable | Standalone | Review soon | Medium |
| P2 | trigger slash skill picker at any word boundary | #16610 | trigger slash skill picker at any word boundary | Standalone | Review soon | Medium |
| P2 | trust OS certificates for Linear API requests | #15450 | trust OS certificates for Linear API requests | Standalone | Review soon | Medium |
| P2 | unlink .asar files during host tree removal (#16958) | #16978 | unlink .asar files during host tree removal (#16958) | Standalone | Review soon | Medium |
| P2 | upload dropped files to remote Orca runtime worktrees | #16567 | upload dropped files to remote Orca runtime worktrees | Standalone | Review soon | Medium |
| P2 | use global history for floating terminals | #15947 | use global history for floating terminals | Standalone | Review soon | Medium |
| P2 | use the external display viewport | #16641 | use the external display viewport | Standalone | Review soon | Medium |
| P2 | verify creates with a fresh listing | #16700 | verify creates with a fresh listing | Standalone | Review soon | Medium |
| P2 | wait for Codex composer before paste | #14888 | wait for Codex composer before paste | Standalone | Review soon | Medium |
| P2 | wait for the host snapshot to hold the baseline before capturing it | #17138 | wait for the host snapshot to hold the baseline before capturing it | Standalone | Review soon | Medium |
| P2 | Windows suite: from 289 failures to zero, plus image-to-pet creation | #15994 | Windows suite: from 289 failures to zero, plus image-to-pet creation | Standalone | Review soon | Medium |
| P2 | withdraw unproven DOM spacing repair | #13371 | withdraw unproven DOM spacing repair | Standalone | Merge | Medium |
| P2 | worktree create keeps slash-containing branch names | #13130 | worktree create keeps slash-containing branch names | Standalone | Request changes | Medium |
| P2 | write runtime currentHash for mirrored hook trust | #16568 | write runtime currentHash for mirrored hook trust | Standalone | Request changes | Medium |
| P2 | yield terminal byte fallbacks to active app keybindings | #15226 | yield terminal byte fallbacks to active app keybindings | Standalone | Review soon | Medium |
| P2 | [Fix] MiniMax: add CN endpoint selector + API key auth (#14264) | #14929 | [Fix] MiniMax: add CN endpoint selector + API key auth (#14264) | Standalone | Review soon | Medium |
| P2 | [HOLD] fix(terminal): stop dropping renderer-bound bytes for hidden panes | #14250 | [HOLD] fix(terminal): stop dropping renderer-bound bytes for hidden panes | Standalone | Defer | Medium |
| P2 | [perf-remote] perf(renderer): avoid duplicate remote session inventory | #13577 | [perf-remote] perf(renderer): avoid duplicate remote session inventory | Standalone | Request changes | Medium |
| P2 | abandon stuck relay recovery on revoked credentials | #13997 | abandon stuck relay recovery on revoked credentials | Standalone | Review soon | Medium |
| P2 | accept an empty --value in fill and select commands | #16030 | accept an empty --value in fill and select commands | Standalone | Review soon | Medium |
| P2 | actionable error when file open path is outside worktree | #13967 | actionable error when file open path is outside worktree | Standalone | Review soon | Medium |
| P2 | activate the window when a context menu opens while unfocused | #14546 | activate the window when a context menu opens while unfocused | Standalone | Review soon | Medium |
| P2 | add a real profile-reset operation, wired to nothing | #15543 | add a real profile-reset operation, wired to nothing | Standalone | Review soon | Medium |
| P2 | add collapse and expand all actions | #13963 | add collapse and expand all actions | Standalone | Review soon | Medium |
| P2 | Add cross-protocol daemon reattach coverage | #12403 | Add cross-protocol daemon reattach coverage | Standalone | Request changes | Medium |
| P2 | Add multi-agent Rooms | #13888 | Add multi-agent Rooms | Standalone | Review soon | Medium |
| P2 | add Ukrainian README translation | #16124 | add Ukrainian README translation | Standalone | Review soon | Medium |
| P2 | adopt pty.attach viewport on reattach | #13300 | adopt pty.attach viewport on reattach | Standalone | Request changes | Medium |
| P2 | adopt robust Settings AUMID polling for UWP e2e test | #13048 | adopt robust Settings AUMID polling for UWP e2e test | Standalone | Request changes | Medium |
| P2 | after closing a tab, return to the previous one | #15220 | after closing a tab, return to the previous one | Standalone | Review soon | Medium |
| P2 | align Agents sidebar badge with actual unread agent count | #15446 #15457 | Coordinate 2 proposals for align Agents sidebar badge with actual unread agent count. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | Allow editing Linear assignees and labels in list view | #13435 | Allow editing Linear assignees and labels in list view | Standalone | Request changes | Medium |
| P2 | allow repo-local OpenCode permissions | #14433 | allow repo-local OpenCode permissions | Standalone | Defer | Medium |
| P2 | Allow worktree lineage across repo and project boundaries | #12755 | Allow worktree lineage across repo and project boundaries | Standalone | Request changes | Medium |
| P2 | always render the per-agent Environment field | #17195 | always render the per-agent Environment field | Standalone | Defer | Medium |
| P2 | answer a query in its own turn when the kernel is quiet (#13892) | #13998 | answer a query in its own turn when the kernel is quiet (#13892) | Standalone | Review soon | Medium |
| P2 | apply the app-wide HTTP proxy to embedded browser sessions | #15536 | apply the app-wide HTTP proxy to embedded browser sessions | Standalone | Review soon | Medium |
| P2 | arm PtyStartupIngress for non-agent panes to suppress OSC 10/11 reply echo on POSIX | #14307 #16123 | Coordinate 2 proposals for arm PtyStartupIngress for non-agent panes to suppress OSC 10/11 reply echo on POSIX. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | ask before closing the window when a terminal probe could not answer | #17044 | ask before closing the window when a terminal probe could not answer | Standalone | Review soon | Medium |
| P2 | attribute each split pane's runtime title to its own leaf (STA-3264) | #14702 | attribute each split pane's runtime title to its own leaf (STA-3264) | Standalone | Review soon | Medium |
| P2 | avoid blocking cmd.exe agent launch on preflight CLI | #16111 | avoid blocking cmd.exe agent launch on preflight CLI | Standalone | Review soon | Medium |
| P2 | avoid garbled TUI frame after app restart | #13464 | avoid garbled TUI frame after app restart | Standalone | Request changes | Medium |
| P2 | avoid quadratic terminal-tail whitespace trimming | #14329 | avoid quadratic terminal-tail whitespace trimming | Standalone | Review soon | Medium |
| P2 | back off host probes a wedged runtime never answers | #15293 | back off host probes a wedged runtime never answers | Standalone | Review soon | Medium |
| P2 | bind remote setup-hook execution to the exact approved content | #15087 | bind remote setup-hook execution to the exact approved content | Standalone | Request changes | Medium |
| P2 | block Cut Release on #14302 terminal goldens | #14398 | block Cut Release on #14302 terminal goldens | Standalone | Review soon | Medium |
| P2 | blur the file search input on Escape | #12293 #14283 | Coordinate 2 proposals for blur the file search input on Escape. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | bound git grep fallback records | #13476 | bound git grep fallback records | Standalone | Request changes | Medium |
| P2 | bound host admission | #14493 | bound host admission | Standalone | Defer | Medium |
| P2 | bound local/WSL Cursor sidecar discovery | #13617 | bound local/WSL Cursor sidecar discovery | Standalone | Request changes | Medium |
| P2 | bundle ripgrep so local search works without a user-installed rg | #13116 | bundle ripgrep so local search works without a user-installed rg | Standalone | Request changes | Medium |
| P2 | cancel in-flight ripgrep listings (STA-4310) | #14588 | cancel in-flight ripgrep listings (STA-4310) | Standalone | Review soon | Medium |
| P2 | cancel superseded content scans | #13587 | cancel superseded content scans | Standalone | Request changes | Medium |
| P2 | Cap AI Vault history depth to 250 for performance | #13089 | Cap AI Vault history depth to 250 for performance | Standalone | Request changes | Medium |
| P2 | cap remote project refresh concurrency | #13631 | cap remote project refresh concurrency | Standalone | Request changes | Medium |
| P2 | cap runtime file listings before SSH transport | #12025 | cap runtime file listings before SSH transport | Standalone | Request changes | Medium |
| P2 | claim the status pane when the inherited owner PID is dead (STA-5245) | #16631 | claim the status pane when the inherited owner PID is dead (STA-5245) | Standalone | Review soon | Medium |
| P2 | Clarify remote file mutation version mismatch messages | #12443 | Clarify remote file mutation version mismatch messages | Standalone | Request changes | Medium |
| P2 | close #16924 review P2s — degrade warn, reap comment, Windows claim-reap CI | #16979 | close #16924 review P2s — degrade warn, reap comment, Windows claim-reap CI | Standalone | Review soon | Medium |
| P2 | close browser tabs by page id | #14369 | close browser tabs by page id | Standalone | Review soon | Medium |
| P2 | close headless terminal tabs whose persisted session record is missing | #12922 | close headless terminal tabs whose persisted session record is missing | Standalone | Review soon | Medium |
| P2 | close restored PTYs with missing tabs | #12905 | close restored PTYs with missing tabs | Standalone | Defer | Medium |
| P2 | Close tab on mobile back to prev | #16146 | Close tab on mobile back to prev | Standalone | Request changes | Medium |
| P2 | close terminal preview with pane shortcut | #13961 | close terminal preview with pane shortcut | Standalone | Review soon | Medium |
| P2 | collapse duplicate per-team status rows in the Tasks filter | #16879 | collapse duplicate per-team status rows in the Tasks filter | Standalone | Review soon | Medium |
| P2 | compare workspace path prefixes with the cross-platform path helpers | #14890 | compare workspace path prefixes with the cross-platform path helpers | Standalone | Review soon | Medium |
| P2 | complete prime-agent title profiles and headless commit env | #13707 | complete prime-agent title profiles and headless commit env | Standalone | Review soon | Medium |
| P2 | contain reattach to existing panes, quarantine orphans | #12743 | contain reattach to existing panes, quarantine orphans | Standalone | Request changes | Medium |
| P2 | contain WebGL context-loss churn and trace recovery declines (#12452) | #13027 | contain WebGL context-loss churn and trace recovery declines (#12452) | Standalone | Request changes | Medium |
| P2 | correct cross-repository GitHub work-item pagination | #12139 | correct cross-repository GitHub work-item pagination | Standalone | Request changes | Medium |
| P2 | cover editor reference-error paths | #16847 | cover editor reference-error paths | Standalone | Review soon | Medium |
| P2 | Cover the mobile approval card dropping on a live state transition | #12237 | Cover the mobile approval card dropping on a live state transition | Standalone | Merge | Medium |
| P2 | Cursor/image cursor advance cf6c | #14857 | Cursor/image cursor advance cf6c | Standalone | Review soon | Medium |
| P2 | decouple notification host ownership | #13000 | decouple notification host ownership | Standalone | Request changes | Medium |
| P2 | dedupe PTY ownership at hydration instead of dropping rows (reland #13060) | #13267 | dedupe PTY ownership at hydration instead of dropping rows (reland #13060) | Standalone | Request changes | Medium |
| P2 | default conflict-resolution agent to YOLO mode | #15906 | default conflict-resolution agent to YOLO mode | Standalone | Review soon | Medium |
| P2 | defer a focus-cancelled paste instead of discarding it (STA-5272) | #17020 | defer a focus-cancelled paste instead of discarding it (STA-5272) | Standalone | Review soon | Medium |
| P2 | design explicit owner admission follow-up | #12424 | design explicit owner admission follow-up | Standalone | Defer | Medium |
| P2 | detect agents for folder workspaces in the new-tab drawer | #16216 | detect agents for folder workspaces in the new-tab drawer | Standalone | Review soon | Medium |
| P2 | detect Comet under its Perplexity vendor directory on Windows | #14300 | detect Comet under its Perplexity vendor directory on Windows | Standalone | Review soon | Medium |
| P2 | detect git D/F ref conflicts before create (STA-4762) | #15383 | detect git D/F ref conflicts before create (STA-4762) | Standalone | Review soon | Medium |
| P2 | Diagnose Claude launches using Orca proxy | #16833 | Diagnose Claude launches using Orca proxy | Standalone | Review soon | Medium |
| P2 | disambiguate same-named projects in the repository filters (#6235) | #12244 | disambiguate same-named projects in the repository filters (#6235) | Standalone | Request changes | Medium |
| P2 | discover WSL Claude transcripts | #12154 | discover WSL Claude transcripts | Standalone | Request changes | Medium |
| P2 | distinct guard when agent foreground cannot be read | #13162 | distinct guard when agent foreground cannot be read | Standalone | Request changes | Medium |
| P2 | do not re-fire task-complete notifications for replayed agent statuses | #12750 #14635 | Coordinate 2 proposals for do not re-fire task-complete notifications for replayed agent statuses. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | document terminal send --text as raw PTY bytes | #14037 #14073 | Coordinate 2 proposals for document terminal send --text as raw PTY bytes. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | drag the native-chat keyboard down with the swipe | #15662 | drag the native-chat keyboard down with the swipe | Standalone | Review soon | Medium |
| P2 | drive the Git contract tests, and ban vi.mock keys that name no real export | #17222 | drive the Git contract tests, and ban vi.mock keys that name no real export | Standalone | Review soon | Medium |
| P2 | drop a third-party product name from a fit comment | #13259 | drop a third-party product name from a fit comment | Standalone | Merge | Medium |
| P2 | drop completion notifications for worktrees the catalog no longer knows | #15001 | drop completion notifications for worktrees the catalog no longer knows | Standalone | Review soon | Medium |
| P2 | drop unsupported Kimi recipe flags | #14790 | drop unsupported Kimi recipe flags | Standalone | Review soon | Medium |
| P2 | emit neutral JSON from the managed Codex hook | #16439 | emit neutral JSON from the managed Codex hook | Standalone | Review soon | Medium |
| P2 | Enforce complete TypeScript coverage | #16849 | Enforce complete TypeScript coverage | Standalone | Review soon | Medium |
| P2 | enforce Run-scoped dispatch inspection | #14900 | enforce Run-scoped dispatch inspection | Standalone | Request changes | Medium |
| P2 | exit Windows hook guards instead of draining a foreign stdin | #12069 | exit Windows hook guards instead of draining a foreign stdin | Standalone | Request changes | Medium |
| P2 | expand symlinked directories that point outside the workspace | #13246 | expand symlinked directories that point outside the workspace | Standalone | Request changes | Medium |
| P2 | extend GPU software-render fallback to Linux desktop | #14858 | extend GPU software-render fallback to Linux desktop | Standalone | Review soon | Medium |
| P2 | extract WorktreeList into focused modules | #14443 | extract WorktreeList into focused modules | Standalone | Request changes | Medium |
| P2 | failed worktree setup left the gated agent terminal silently waiting for two hours | #16891 | failed worktree setup left the gated agent terminal silently waiting for two hours | Standalone | Review soon | Medium |
| P2 | fast-forward a checked-out existing branch inside its new worktree | #15815 | fast-forward a checked-out existing branch inside its new worktree | Standalone | Review soon | Medium |
| P2 | fence mobile PR merges by exact head | #12668 | fence mobile PR merges by exact head | Standalone | Request changes | Medium |
| P2 | fence navigation on terminal host loss | #14754 | fence navigation on terminal host loss | Standalone | Defer | Medium |
| P2 | fetch linked PR and sub-issues progress field values | #12821 | fetch linked PR and sub-issues progress field values | Standalone | Request changes | Medium |
| P2 | find and use the 1Password SSH agent (no more passphrase prompts for agent-held keys) | #12765 | find and use the 1Password SSH agent (no more passphrase prompts for agent-held keys) | Standalone | Request changes | Medium |
| P2 | finish the Windows command-override tokenizer fix | #15051 | finish the Windows command-override tokenizer fix | Standalone | Request changes | Medium |
| P2 | Fix Codex automation completion ordering | #16801 | Fix Codex automation completion ordering | Standalone | Review soon | Medium |
| P2 | Fix GitLab task resolution for sole nonstandard remotes | #13936 | Fix GitLab task resolution for sole nonstandard remotes | Standalone | Review soon | Medium |
| P2 | Fix macOS updater relaunch races across profiles | #14736 | Fix macOS updater relaunch races across profiles | Standalone | Review soon | Medium |
| P2 | Fix native chat IME composition lag | #15547 | Fix native chat IME composition lag | Standalone | Review soon | Medium |
| P2 | Fix remote agent terminal startup colors | #13865 | Fix remote agent terminal startup colors | Standalone | Review soon | Medium |
| P2 | Fix retry ownership for rejected SSH split cleanup | #14101 | Fix retry ownership for rejected SSH split cleanup | Standalone | Review soon | Medium |
| P2 | Fix terminal federation recovery backoff | #14336 | Fix terminal federation recovery backoff | Standalone | Defer | Medium |
| P2 | flush queued application input after IME commit | #12436 | flush queued application input after IME commit | Standalone | Defer | Medium |
| P2 | follow output when a pinned scroll anchor is trimmed away | #12678 | follow output when a pinned scroll anchor is trimmed away | Standalone | Review soon | Medium |
| P2 | forward the client's resolved agent args to paired hosts | #15611 | forward the client's resolved agent args to paired hosts | Standalone | Review soon | Medium |
| P2 | frame alt-screen pastes when bracketed paste is on | #13553 | frame alt-screen pastes when bracketed paste is on | Standalone | Request changes | Medium |
| P2 | gate bundled zod runtime integrity (STA-4316) | #14587 | gate bundled zod runtime integrity (STA-4316) | Standalone | Request changes | Medium |
| P2 | gate OutputSpan frames behind a negotiated capability (STA-3482) | #12788 | gate OutputSpan frames behind a negotiated capability (STA-3482) | Standalone | Defer | Medium |
| P2 | guard Add Project dialog dismissal while cloning | #14266 | guard Add Project dialog dismissal while cloning | Standalone | Review soon | Medium |
| P2 | heal stuck permission wait after a denied Claude tool | #15078 | heal stuck permission wait after a denied Claude tool | Standalone | Review soon | Medium |
| P2 | hide bare repository backing stores from workspace list | #16561 | hide bare repository backing stores from workspace list | Standalone | Review soon | Medium |
| P2 | highlight the whole .env.* family as ini | #13029 #13239 | Coordinate 2 proposals for highlight the whole .env.* family as ini. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | hold route policy through page retirement | #14518 | hold route policy through page retirement | Standalone | Defer | Medium |
| P2 | hold the fabricated permission BEL for the Codex quiet window | #14715 | hold the fabricated permission BEL for the Codex quiet window | Standalone | Review soon | Medium |
| P2 | honor OS certificate trust for first-party traffic | #15208 | honor OS certificate trust for first-party traffic | Standalone | Review soon | Medium |
| P2 | ignore non-absolute env overrides for agent scan roots | #13118 | ignore non-absolute env overrides for agent scan roots | Standalone | Request changes | Medium |
| P2 | Improve Agent Session History search: rg scopes and AI rank | #15354 | Improve Agent Session History search: rg scopes and AI rank | Standalone | Review soon | Medium |
| P2 | infer worker identity in preambles | #14567 | infer worker identity in preambles | Standalone | Review soon | Medium |
| P2 | install a selected agent from the onboarding step | #14122 | install a selected agent from the onboarding step | Standalone | Review soon | Medium |
| P2 | keep a DA1 answerer for parked panes with raw-byte sidecars | #14002 | keep a DA1 answerer for parked panes with raw-byte sidecars | Standalone | Review soon | Medium |
| P2 | keep a nested child hook's model off the fenced parent row | #13602 | keep a nested child hook's model off the fenced parent row | Standalone | Request changes | Medium |
| P2 | keep a quick command queued until its own spawn takes it (STA-4876) | #15531 | keep a quick command queued until its own spawn takes it (STA-4876) | Standalone | Defer | Medium |
| P2 | keep acknowledged completions in the Done column | #13780 | keep acknowledged completions in the Done column | Standalone | Review soon | Medium |
| P2 | keep agent rows ordered by their session start once state history wraps | #14654 | keep agent rows ordered by their session start once state history wraps | Standalone | Review soon | Medium |
| P2 | keep angle brackets inside consecutive code fences | #13691 #13842 | Coordinate 2 proposals for keep angle brackets inside consecutive code fences. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | keep bold distinct when font weight is 600+ | #14175 | keep bold distinct when font weight is 600+ | Standalone | Request changes | Medium |
| P2 | keep CJK panes from freezing on a half-built glyph atlas | #13765 | keep CJK panes from freezing on a half-built glyph atlas | Standalone | Review soon | Medium |
| P2 | keep client tab-group ratios on remote host snapshots | #13224 | keep client tab-group ratios on remote host snapshots | Standalone | Review soon | Medium |
| P2 | keep Ctrl-W in Git Bash terminals | #13232 | keep Ctrl-W in Git Bash terminals | Standalone | Request changes | Medium |
| P2 | keep direct-SSH projects when a cold start merges the local catalog | #15115 | keep direct-SSH projects when a cold start merges the local catalog | Standalone | Review soon | Medium |
| P2 | keep draining a pty whose client has gone | #15761 | keep draining a pty whose client has gone | Standalone | Request changes | Medium |
| P2 | keep failed local/WSL scans non-authoritative | #14183 | keep failed local/WSL scans non-authoritative | Standalone | Review soon | Medium |
| P2 | keep folder workspaces on execution host | #15685 | keep folder workspaces on execution host | Standalone | Defer | Medium |
| P2 | keep gitless selected folders | #13734 | keep gitless selected folders | Standalone | Review soon | Medium |
| P2 | keep headless runtime alive on desktop Cmd+Q | #15560 | keep headless runtime alive on desktop Cmd+Q | Standalone | Review soon | Medium |
| P2 | keep heartbeats from waking coordinators | #13235 | keep heartbeats from waking coordinators | Standalone | Defer | Medium |
| P2 | keep hookless agents sendable via foreground process proof | #14810 | keep hookless agents sendable via foreground process proof | Standalone | Review soon | Medium |
| P2 | keep image-path pastes tokenized after typed text | #12715 | keep image-path pastes tokenized after typed text | Standalone | Request changes | Medium |
| P2 | keep interrupted Stops working while background tasks run | #12724 | keep interrupted Stops working while background tasks run | Standalone | Request changes | Medium |
| P2 | keep OMP wrapper parse-safe under zsh global aliases | #14215 | keep OMP wrapper parse-safe under zsh global aliases | Standalone | Review soon | Medium |
| P2 | keep one mounted session screen per worktree (supersedes #17068) | #17098 | keep one mounted session screen per worktree (supersedes #17068) | Standalone | Review soon | Medium |
| P2 | keep orchestration check help side-effect free | #12996 | keep orchestration check help side-effect free | Standalone | Request changes | Medium |
| P2 | keep owned agent panes visible when their title carries no agent frame (#14464) | #14650 | keep owned agent panes visible when their title carries no agent frame (#14464) | Standalone | Review soon | Medium |
| P2 | Keep relay completion evidence live/unverifiable/exited, never coerced | #16926 | Keep relay completion evidence live/unverifiable/exited, never coerced | Standalone | Request changes | Medium |
| P2 | keep retired names on an RPC error and route the host's created name (STA-4479, STA-4480) | #14926 | keep retired names on an RPC error and route the host's created name (STA-4479, STA-4480) | Standalone | Review soon | Medium |
| P2 | keep session state for worktrees hidden from the sidebar (#15227) | #15431 | keep session state for worktrees hidden from the sidebar (#15227) | Standalone | Review soon | Medium |
| P2 | keep system-default auth native when hooks are unavailable | #13755 | keep system-default auth native when hooks are unavailable | Standalone | Review soon | Medium |
| P2 | keep the chat viewport steady when history pages in (STA-3333) | #12500 | keep the chat viewport steady when history pages in (STA-3333) | Standalone | Request changes | Medium |
| P2 | keep the pane provider-session binding across a transient clear | #12070 | keep the pane provider-session binding across a transient clear | Standalone | Request changes | Medium |
| P2 | keep the reattach grid push past an exhausted fit budget | #13194 | keep the reattach grid push past an exhausted fit budget | Standalone | Merge | Medium |
| P2 | keep the shell wrapper parseable under zsh global aliases | #14538 | keep the shell wrapper parseable under zsh global aliases | Standalone | Review soon | Medium |
| P2 | keep the workspace selected when its last tab closes | #12142 | keep the workspace selected when its last tab closes | Standalone | Request changes | Medium |
| P2 | land an account-switch restart on the newly selected account | #14877 | land an account-switch restart on the newly selected account | Standalone | Review soon | Medium |
| P2 | lazy-load source cache ledgers | #16219 | lazy-load source cache ledgers | Standalone | Review soon | Medium |
| P2 | let activate() tell a reconnected client from one that never left | #15762 | let activate() tell a reconnected client from one that never left | Standalone | Request changes | Medium |
| P2 | let DevTools own Cmd+V instead of the focused terminal pane | #16288 | let DevTools own Cmd+V instead of the focused terminal pane | Standalone | Review soon | Medium |
| P2 | let the model picker clear the persisted launch override | #13819 | let the model picker clear the persisted launch override | Standalone | Review soon | Medium |
| P2 | let users unpin main workspaces from the top of their group | #15811 | let users unpin main workspaces from the top of their group | Standalone | Review soon | Medium |
| P2 | lift the closed-tab blackhole when a retracted tab comes back (STA-5679) | #16985 | lift the closed-tab blackhole when a retracted tab comes back (STA-5679) | Standalone | Defer | Medium |
| P2 | list default issues via REST so account mismatches surface errors (#16244) | #16294 | list default issues via REST so account mismatches surface errors (#16244) | Standalone | Review soon | Medium |
| P2 | localize Artifacts feature strings to Korean | #13810 | localize Artifacts feature strings to Korean | Standalone | Review soon | Medium |
| P2 | localize caffeinate controls in Chinese | #14772 | localize caffeinate controls in Chinese | Standalone | Review soon | Medium |
| P2 | localize remaining Korean UI strings outside auto catalog | #14044 | localize remaining Korean UI strings outside auto catalog | Standalone | Review soon | Medium |
| P2 | localize the source control dropdown hints | #14127 | localize the source control dropdown hints | Standalone | Review soon | Medium |
| P2 | long-press to select/copy sent Native Chat text (STA-4983) | #15652 | long-press to select/copy sent Native Chat text (STA-4983) | Standalone | Review soon | Medium |
| P2 | make RC/perf update channels readable without hovering (#10590) | #12255 | make RC/perf update channels readable without hovering (#10590) | Standalone | Request changes | Medium |
| P2 | Make terminal link action defaults switchable | #14814 | Make terminal link action defaults switchable | Standalone | Review soon | Medium |
| P2 | make the canonical envelope stripper the only one | #17237 | make the canonical envelope stripper the only one | Standalone | Review soon | Medium |
| P2 | make the Electron install survive release-CDN blips | #14110 | make the Electron install survive release-CDN blips | Standalone | Request changes | Medium |
| P2 | make the software-rendering rescue reachable across launches | #15059 | make the software-rendering rescue reachable across launches | Standalone | Review soon | Medium |
| P2 | match external file changes across Windows path spellings | #14812 | match external file changes across Windows path spellings | Standalone | Review soon | Medium |
| P2 | migrate custom font weights to independent bold (STA-4236) | #14390 | migrate custom font weights to independent bold (STA-4236) | Standalone | Review soon | Medium |
| P2 | mint PTY ids that carry the relay incarnation instead of a restarting counter | #16901 | mint PTY ids that carry the relay incarnation instead of a restarting counter | Standalone | Review soon | Medium |
| P2 | Move a rejected worker_done off ready instead of stranding its Dispatch | #15265 | Move a rejected worker_done off ready instead of stranding its Dispatch | Standalone | Review soon | Medium |
| P2 | name structured Codex chat tabs from their own session | #17092 | name structured Codex chat tabs from their own session | Standalone | Request changes | Medium |
| P2 | native chat no longer claims an empty conversation while the agent is working | #16887 | native chat no longer claims an empty conversation while the agent is working | Standalone | Review soon | Medium |
| P2 | offer the host's real Claude model list in native chat | #15086 | offer the host's real Claude model list in native chat | Standalone | Review soon | Medium |
| P2 | Omniroute baton integration | #13526 | Omniroute baton integration | Standalone | Request changes | Medium |
| P2 | open Create Workspace after its source drawer has closed | #13147 | open Create Workspace after its source drawer has closed | Standalone | Review soon | Medium |
| P2 | open floating terminal when its notification is clicked | #12110 | open floating terminal when its notification is clicked | Standalone | Review soon | Medium |
| P2 | open project select with Cmd/Ctrl+. | #12989 | open project select with Cmd/Ctrl+. | Standalone | Review soon | Medium |
| P2 | open symlinked folders that point outside the workspace | #13069 | open symlinked folders that point outside the workspace | Standalone | Request changes | Medium |
| P2 | open the deep-linked project setup, not the host's first | #12176 | open the deep-linked project setup, not the host's first | Standalone | Merge | Medium |
| P2 | open workers in the coordinator split pane | #13802 | open workers in the coordinator split pane | Standalone | Request changes | Medium |
| P2 | opening tmp files read-only breaks fsync on Windows | #14168 | opening tmp files read-only breaks fsync on Windows | Standalone | Review soon | Medium |
| P2 | orchestration: launch argv-capable worker agents with the dispatch preamble embedded, instea | #16425 | orchestration: launch argv-capable worker agents with the dispatch preamble embedded, instea | Standalone | Review soon | Medium |
| P2 | persist active workspace identity | #14475 | persist active workspace identity | Standalone | Review soon | Medium |
| P2 | pin folder-workspace PTY cwd across paired and SSH topologies (STA-4746) | #15385 | pin folder-workspace PTY cwd across paired and SSH topologies (STA-4746) | Standalone | Request changes | Medium |
| P2 | pin OSC 11 reply before CPR (STA-5634) | #16831 | pin OSC 11 reply before CPR (STA-5634) | Standalone | Review soon | Medium |
| P2 | pin park verdict on slow notice-limit churn | #13161 | pin park verdict on slow notice-limit churn | Standalone | Request changes | Medium |
| P2 | preserve ADF link marks as Markdown hyperlinks | #13604 | preserve ADF link marks as Markdown hyperlinks | Standalone | Review soon | Medium |
| P2 | preserve completed prompt dispatches | #15941 | preserve completed prompt dispatches | Standalone | Review soon | Medium |
| P2 | preserve iPad hardware keyboard focus | #12772 | preserve iPad hardware keyboard focus | Standalone | Merge | Medium |
| P2 | preserve project filter when importing or revealing a repo | #12691 | preserve project filter when importing or revealing a repo | Standalone | Request changes | Medium |
| P2 | preserve remote task launch options | #13448 | preserve remote task launch options | Standalone | Request changes | Medium |
| P2 | preserve run subcommand before launch flags | #13065 | preserve run subcommand before launch flags | Standalone | Request changes | Medium |
| P2 | preserve sessions during uncertain Windows recovery | #14959 | preserve sessions during uncertain Windows recovery | Standalone | Defer | Medium |
| P2 | preserve settled prompt authority | #15583 | preserve settled prompt authority | Standalone | Defer | Medium |
| P2 | preserve slashes in derived branch names | #15104 | preserve slashes in derived branch names | Standalone | Review soon | Medium |
| P2 | preserve slow worktree removal responses | #16060 | preserve slow worktree removal responses | Standalone | Request changes | Medium |
| P2 | Preserve unverifiable terminal sessions and document PTY ownership redesign | #16152 | Preserve unverifiable terminal sessions and document PTY ownership redesign | Standalone | Request changes | Medium |
| P2 | Preserve user-set workspace names across branch changes and collision retries | #12742 | Preserve user-set workspace names across branch changes and collision retries | Standalone | Request changes | Medium |
| P2 | preserve worktree forwarded host | #14562 | preserve worktree forwarded host | Standalone | Review soon | Medium |
| P2 | preserve WSL federated worker lifecycle authority | #15580 | preserve WSL federated worker lifecycle authority | Standalone | Review soon | Medium |
| P2 | prevent terminal font size value from clipping | #12909 | prevent terminal font size value from clipping | Standalone | Request changes | Medium |
| P2 | prune nested ignored dirs on macOS and bound the flush fan-out | #12067 | prune nested ignored dirs on macOS and bound the flush fan-out | Standalone | Review soon | Medium |
| P2 | push Dispatch mailbox mail to idle workers (STA-3105) | #15249 | push Dispatch mailbox mail to idle workers (STA-3105) | Standalone | Request changes | Medium |
| P2 | qualify client page host capabilities | #14531 | qualify client page host capabilities | Standalone | Defer | Medium |
| P2 | re-probe tracked upstreams after SSH reconnect | #12979 | re-probe tracked upstreams after SSH reconnect | Standalone | Merge | Medium |
| P2 | read live Windows env so packaged builds pick up setx tokens | #15435 #15734 | Coordinate 2 proposals for read live Windows env so packaged builds pick up setx tokens. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | read ssh host partitions so stranded tabs stop round-tripping as deletions | #12722 | read ssh host partitions so stranded tabs stop round-tripping as deletions | Standalone | Request changes | Medium |
| P2 | read SSH worktree transcripts on the host that owns them | #13687 #15672 | Coordinate 2 proposals for read SSH worktree transcripts on the host that owns them. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | read the vi.mock factories that hand back a shared mock module, and report dead keys by mock | #17240 | read the vi.mock factories that hand back a shared mock module, and report dead keys by mock | Standalone | Request changes | Medium |
| P2 | reap detached macOS helper processes on every teardown path | #14494 | reap detached macOS helper processes on every teardown path | Standalone | Review soon | Medium |
| P2 | reap owned PTYs when the daemon dies on an uncaught exception (STA-5697) | #16894 | reap owned PTYs when the daemon dies on an uncaught exception (STA-5697) | Standalone | Review soon | Medium |
| P2 | reclaim idle headless browser tab renderers (STA-4341) | #15254 | reclaim idle headless browser tab renderers (STA-4341) | Standalone | Review soon | Medium |
| P2 | reconcile completed Claude background tasks | #15591 | reconcile completed Claude background tasks | Standalone | Defer | Medium |
| P2 | reconcile every hydrated workspace's tab model | #15845 | reconcile every hydrated workspace's tab model | Standalone | Review soon | Medium |
| P2 | Recover agents stalled by a login or network failure | #16738 | Recover agents stalled by a login or network failure | Standalone | Review soon | Medium |
| P2 | recover browser host admission fairly | #14747 | recover browser host admission fairly | Standalone | Defer | Medium |
| P2 | recover Codex subagent state after restart (STA-5329) | #16336 | recover Codex subagent state after restart (STA-5329) | Standalone | Review soon | Medium |
| P2 | recover dispatch completion capability | #14026 | recover dispatch completion capability | Standalone | Review soon | Medium |
| P2 | recover hidden remote agent alerts after resubscription | #16103 | recover hidden remote agent alerts after resubscription | Standalone | Defer | Medium |
| P2 | recover Linux headless runtime after main crashes | #14096 | recover Linux headless runtime after main crashes | Standalone | Review soon | Medium |
| P2 | Recover native chat messages when terminal delivery is unconfirmed | #12643 | Recover native chat messages when terminal delivery is unconfirmed | Standalone | Request changes | Medium |
| P2 | recover overlay hit-test after pane-column snap | #14014 | recover overlay hit-test after pane-column snap | Standalone | Review soon | Medium |
| P2 | release completed run observers | #13641 | release completed run observers | Standalone | Request changes | Medium |
| P2 | release preserved cleanup routes with reviews | #13941 | release preserved cleanup routes with reviews | Standalone | Review soon | Medium |
| P2 | release the occurrence a cancelled send would have taken | #13513 | release the occurrence a cancelled send would have taken | Standalone | Request changes | Medium |
| P2 | reload Jira and Linear state files when another process rewrites them | #13125 | reload Jira and Linear state files when another process rewrites them | Standalone | Review soon | Medium |
| P2 | remove 4px lip above the active terminal tab when not split | #13053 | remove 4px lip above the active terminal tab when not split | Standalone | Review soon | Medium |
| P2 | remove the project on its own host, not another host's row | #13117 | remove the project on its own host, not another host's row | Standalone | Request changes | Medium |
| P2 | render Mermaid HTML labels without stripping foreignObject | #12581 | render Mermaid HTML labels without stripping foreignObject | Standalone | Review soon | Medium |
| P2 | render the vertical scrollbar again while keeping the gutter transparent | #12806 | render the vertical scrollbar again while keeping the gutter transparent | Standalone | Review soon | Medium |
| P2 | repaint after scrollback replay settles on fresh mount | #12927 | repaint after scrollback replay settles on fresh mount | Standalone | Request changes | Medium |
| P2 | Repair E2E test failures with relay build and fixture updates | #15231 | Repair E2E test failures with relay build and fixture updates | Standalone | Request changes | Medium |
| P2 | repair NSIS upgrade metadata that reports cannot-close | #14172 | repair NSIS upgrade metadata that reports cannot-close | Standalone | Request changes | Medium |
| P2 | replace React 185 timers with structural handoffs | #12634 | replace React 185 timers with structural handoffs | Standalone | Request changes | Medium |
| P2 | report a partly-sent ask answer honestly (STA-3333) | #12503 | report a partly-sent ask answer honestly (STA-3333) | Standalone | Request changes | Medium |
| P2 | report app-bound encrypted cookies instead of a silent zero | #13193 | report app-bound encrypted cookies instead of a silent zero | Standalone | Request changes | Medium |
| P2 | report expired sessions terminate cannot reach while the relay is offline | #12797 | report expired sessions terminate cannot reach while the relay is offline | Standalone | Review soon | Medium |
| P2 | report hook status per host, and stop remote Codex reusing an env-less app-server (#8711, #1 | #14621 | report hook status per host, and stop remote Codex reusing an env-less app-server (#8711, #1 | Standalone | Review soon | Medium |
| P2 | require identity for braille guarded sends (STA-4048) | #14169 | require identity for braille guarded sends (STA-4048) | Standalone | Review soon | Medium |
| P2 | require placement retirement before replacement | #14536 | require placement retirement before replacement | Standalone | Defer | Medium |
| P2 | resolve Grok auth from configured WSL runtime | #13839 | resolve Grok auth from configured WSL runtime | Standalone | Review soon | Medium |
| P2 | resolve project ref from non-origin remotes | #13886 | resolve project ref from non-origin remotes | Standalone | Review soon | Medium |
| P2 | resolve VS Code CLI from standard app installs | #14010 | resolve VS Code CLI from standard app installs | Standalone | Review soon | Medium |
| P2 | restore agent homes and the attribution PATH shim after config.fish | #13978 | restore agent homes and the attribution PATH shim after config.fish | Standalone | Request changes | Medium |
| P2 | restore DECTCEM from tracked mode state on live-agent reattach | #14638 | restore DECTCEM from tracked mode state on live-agent reattach | Standalone | Review soon | Medium |
| P2 | restore paired snapshots at the source grid | #12768 | restore paired snapshots at the source grid | Standalone | Request changes | Medium |
| P2 | restore remote replay grid on reveal | #14206 | restore remote replay grid on reveal | Standalone | Review soon | Medium |
| P2 | restore scroll position when returning to a tab | #12464 | restore scroll position when returning to a tab | Standalone | Request changes | Medium |
| P2 | restore shell integration after startup exec | #14176 | restore shell integration after startup exec | Standalone | Request changes | Medium |
| P2 | resume a provider session in the directory the agent reported, not the pane's worktree (STA- | #17087 | resume a provider session in the directory the agent reported, not the pane's worktree (STA- | Standalone | Request changes | Medium |
| P2 | retire a superseded daemon that owns no sessions | #13063 | retire a superseded daemon that owns no sessions | Standalone | Request changes | Medium |
| P2 | retire agent resume records when a shell exit closes its tab | #15545 | retire agent resume records when a shell exit closes its tab | Standalone | Review soon | Medium |
| P2 | retire direct-SSH tabs on publisher retraction instead of snapshot absence (STA-4719) | #15348 | retire direct-SSH tabs on publisher retraction instead of snapshot absence (STA-4719) | Standalone | Review soon | Medium |
| P2 | retire placements on host lease fence | #14753 | retire placements on host lease fence | Standalone | Defer | Medium |
| P2 | retire removed-workspace snapshot tombstones once their holders release (STA-4451) | #14933 | retire removed-workspace snapshot tombstones once their holders release (STA-4451) | Standalone | Review soon | Medium |
| P2 | retire the unpublished-title fallback that minted an agent row and both dots (STA-2926) | #14708 | retire the unpublished-title fallback that minted an agent row and both dots (STA-2926) | Standalone | Review soon | Medium |
| P2 | retry snapshot tabs whose worktree paths resolve after apply | #12903 | retry snapshot tabs whose worktree paths resolve after apply | Standalone | Request changes | Medium |
| P2 | reveal agents through worktree-activation so slept agents wake | #14646 | reveal agents through worktree-activation so slept agents wake | Standalone | Review soon | Medium |
| P2 | reveal remote agent sessions from the dashboard | #16732 | reveal remote agent sessions from the dashboard | Standalone | Review soon | Medium |
| P2 | revert: feat(native-chat): Codex structured native chat restructure (revert #16729) | #17242 | revert: feat(native-chat): Codex structured native chat restructure (revert #16729) | Standalone | Request changes | Medium |
| P2 | revive retired panes on live new turns | #14560 | revive retired panes on live new turns | Standalone | Review soon | Medium |
| P2 | roll review notes back to the persisted list | #14125 | roll review notes back to the persisted list | Standalone | Review soon | Medium |
| P2 | route page-scoped keyboard input through CDP | #13231 | route page-scoped keyboard input through CDP | Standalone | Request changes | Medium |
| P2 | route task issues, MRs, and detail actions to the owning host | #14604 | route task issues, MRs, and detail actions to the owning host | Standalone | Review soon | Medium |
| P2 | route WSL transcripts by PTY provenance | #13934 | route WSL transcripts by PTY provenance | Standalone | Review soon | Medium |
| P2 | say what the liveness vocabulary actually fixes, and dedupe the observation status | #17029 | say what the liveness vocabulary actually fixes, and dedupe the observation status | Standalone | Defer | Medium |
| P2 | scan Claude transcripts from WSL homes | #16933 | scan Claude transcripts from WSL homes | Standalone | Review soon | Medium |
| P2 | scan configured Codex session home (#12186) | #12733 | scan configured Codex session home (#12186) | Standalone | Request changes | Medium |
| P2 | scope capability state to the distro that runs git | #15297 | scope capability state to the distro that runs git | Standalone | Review soon | Medium |
| P2 | scope Git Bash capacity retention | #16662 | scope Git Bash capacity retention | Standalone | Defer | Medium |
| P2 | scope PTY inventory by exact workspace owner | #16180 | scope PTY inventory by exact workspace owner | Standalone | Review soon | Medium |
| P2 | scope the worktree-visibility toggle to its own host | #13211 | scope the worktree-visibility toggle to its own host | Standalone | Request changes | Medium |
| P2 | seed the spawn-window agent status from launch metadata | #14611 | seed the spawn-window agent status from launch metadata | Standalone | Review soon | Medium |
| P2 | send a composing cursor chord once, not twice | #14742 | send a composing cursor chord once, not twice | Standalone | Review soon | Medium |
| P2 | send Native Chat on hardware Enter | #14782 | send Native Chat on hardware Enter | Standalone | Review soon | Medium |
| P2 | send one atomic mouseClick on the legacy remote pane | #15402 | send one atomic mouseClick on the legacy remote pane | Standalone | Review soon | Medium |
| P2 | separate worktree issue metadata | #13119 | separate worktree issue metadata | Standalone | Request changes | Medium |
| P2 | serialize agent-prompt submits per PTY so overlapping sends stop gluing | #14980 | serialize agent-prompt submits per PTY so overlapping sends stop gluing | Standalone | Defer | Medium |
| P2 | serialize desktop viewport ownership | #16065 | serialize desktop viewport ownership | Standalone | Request changes | Medium |
| P2 | settle exited headless terminal closes | #15572 | settle exited headless terminal closes | Standalone | Request changes | Medium |
| P2 | settle OMP status on terminal agent_end via willContinue | #14330 | settle OMP status on terminal agent_end via willContinue | Standalone | Review soon | Medium |
| P2 | ship the appearance-aware macOS icon catalog | #16507 | ship the appearance-aware macOS icon catalog | Standalone | Review soon | Medium |
| P2 | show Codex compaction markers | #14765 | show Codex compaction markers | Standalone | Review soon | Medium |
| P2 | show Codex goal-mode digests (mobile empty transcript) | #13985 | show Codex goal-mode digests (mobile empty transcript) | Standalone | Review soon | Medium |
| P2 | show Fable remaining time in compact usage mode | #13134 #13141 #13226 | Coordinate 3 proposals for show Fable remaining time in compact usage mode. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | show PR line totals in detail header | #13781 | show PR line totals in detail header | Standalone | Review soon | Medium |
| P2 | show project name on status/PR-status grouped cards | #13938 | show project name on status/PR-status grouped cards | Standalone | Review soon | Medium |
| P2 | show project name on Workspace board cards | #13830 | show project name on Workspace board cards | Standalone | Review soon | Medium |
| P2 | show prompts Claude queued while the agent was busy | #14309 #16121 | Coordinate 2 proposals for show prompts Claude queued while the agent was busy. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | Speed up worktree creation with a gated early terminal | #13704 | Speed up worktree creation with a gated early terminal | Standalone | Defer | Medium |
| P2 | Split Codex hook service responsibilities | #17260 | Split Codex hook service responsibilities | Standalone | Request changes | Medium |
| P2 | Split daemon initialization lifecycle | #17161 | Split daemon initialization lifecycle | Standalone | Request changes | Medium |
| P2 | split dispatch-liveness tests out of db.test.ts | #14889 | split dispatch-liveness tests out of db.test.ts | Standalone | Review soon | Medium |
| P2 | Split external automation manager | #17149 | Split external automation manager | Standalone | Request changes | Medium |
| P2 | Split Git worktree responsibilities | #17253 | Split Git worktree responsibilities | Standalone | Request changes | Medium |
| P2 | Split GitHub project view read path | #17266 | Split GitHub project view read path | Standalone | Request changes | Medium |
| P2 | Split GitLab item dialog | #17165 | Split GitLab item dialog | Standalone | Request changes | Medium |
| P2 | Split Linear item drawer responsibilities | #17231 | Split Linear item drawer responsibilities | Standalone | Request changes | Medium |
| P2 | Split local PTY provider responsibilities | #17206 | Split local PTY provider responsibilities | Standalone | Request changes | Medium |
| P2 | Split main window service attachments | #17151 | Split main window service attachments | Standalone | Request changes | Medium |
| P2 | Split mobile host screen layers | #17181 | Split mobile host screen layers | Standalone | Request changes | Medium |
| P2 | Split ports panel layers | #17194 | Split ports panel layers | Standalone | Request changes | Medium |
| P2 | Split relay dispatcher layers | #17174 | Split relay dispatcher layers | Standalone | Request changes | Medium |
| P2 | Split remote terminal multiplexer responsibilities | #17248 | Split remote terminal multiplexer responsibilities | Standalone | Request changes | Medium |
| P2 | Split runtime environments pane layers | #17198 | Split runtime environments pane layers | Standalone | Request changes | Medium |
| P2 | Split runtime RPC server responsibilities | #17270 | Split runtime RPC server responsibilities | Standalone | Request changes | Medium |
| P2 | Split settings navigation metadata | #17157 | Split settings navigation metadata | Standalone | Request changes | Medium |
| P2 | Split telemetry event schema responsibilities | #17235 | Split telemetry event schema responsibilities | Standalone | Request changes | Medium |
| P2 | Split terminal output scheduler pipeline | #17131 | Split terminal output scheduler pipeline | Standalone | Request changes | Medium |
| P2 | STA-5296: keep Claude startup queries answerable on mobile | #16825 | STA-5296: keep Claude startup queries answerable on mobile | Standalone | Review soon | Medium |
| P2 | stabilize scroll through grid resize | #12059 | stabilize scroll through grid resize | Standalone | Request changes | Medium |
| P2 | stop --json throwing a TypeError on a primitive result | #14735 | stop --json throwing a TypeError on a primitive result | Standalone | Review soon | Medium |
| P2 | stop a failed relay --connect from orphaning the live relay (STA-1756) | #15250 | stop a failed relay --connect from orphaning the live relay (STA-1756) | Standalone | Review soon | Medium |
| P2 | stop a leaked hook-server listener from making the 130k-leaf migration test load-decided | #17256 | stop a leaked hook-server listener from making the 130k-leaf migration test load-decided | Standalone | Merge | Medium |
| P2 | stop a leaked real timer from failing the updater scheduling test | #17086 | stop a leaked real timer from failing the updater scheduling test | Standalone | Review soon | Medium |
| P2 | stop a recovery snapshot erasing scrollback it cannot replace | #14594 | stop a recovery snapshot erasing scrollback it cannot replace | Standalone | Review soon | Medium |
| P2 | stop a relay leaking its own pane identity into every pane it spawns | #17257 | stop a relay leaking its own pane identity into every pane it spawns | Standalone | Request changes | Medium |
| P2 | stop a removed worktree from breaking every spawn for the session | #16702 | stop a removed worktree from breaking every spawn for the session | Standalone | Review soon | Medium |
| P2 | stop a tab close reading "could not tell" as "nothing running" | #17079 | stop a tab close reading "could not tell" as "nothing running" | Standalone | Review soon | Medium |
| P2 | stop an unverified PTY loss from deleting tab records | #16585 | stop an unverified PTY loss from deleting tab records | Standalone | Review soon | Medium |
| P2 | stop Antigravity treating --sandbox as the commit prompt | #14157 | stop Antigravity treating --sandbox as the commit prompt | Standalone | Review soon | Medium |
| P2 | stop background panes rendering blank after a system wake | #13833 | stop background panes rendering blank after a system wake | Standalone | Review soon | Medium |
| P2 | stop chasing chunk recovery during a committed update install | #13172 | stop chasing chunk recovery during a committed update install | Standalone | Request changes | Medium |
| P2 | stop Claude TUI remounts on Linux resize restreams (STA-3992) | #14164 | stop Claude TUI remounts on Linux resize restreams (STA-3992) | Standalone | Review soon | Medium |
| P2 | stop deleting the branch a worktree drifted onto | #13877 | stop deleting the branch a worktree drifted onto | Standalone | Review soon | Medium |
| P2 | stop foreground ConPTY helper fanout | #16074 | stop foreground ConPTY helper fanout | Standalone | Defer | Medium |
| P2 | stop Hide sleeping dropping a remote workspace row on a transient PTY gap | #16001 | stop Hide sleeping dropping a remote workspace row on a transient PTY gap | Standalone | Review soon | Medium |
| P2 | Stop keep reconnecting to remote | #12155 | Stop keep reconnecting to remote | Standalone | Request changes | Medium |
| P2 | stop lazy-chunk recovery reloads from killing the user's terminals | #12943 | stop lazy-chunk recovery reloads from killing the user's terminals | Standalone | Defer | Medium |
| P2 | stop losing a startup command when the shell-ready marker is late | #15275 | stop losing a startup command when the shell-ready marker is late | Standalone | Review soon | Medium |
| P2 | stop matching pending echoes across clock domains | #13613 | stop matching pending echoes across clock domains | Standalone | Request changes | Medium |
| P2 | stop painting every project on launch, then walking the list back | #16255 | stop painting every project on launch, then walking the list back | Standalone | Review soon | Medium |
| P2 | stop PTY layout writes from re-rendering every tab strip (STA-3328) | #12371 | stop PTY layout writes from re-rendering every tab strip (STA-3328) | Standalone | Request changes | Medium |
| P2 | stop reading an unreachable terminal as an idle one | #17024 | stop reading an unreachable terminal as an idle one | Standalone | Request changes | Medium |
| P2 | stop reconnect from grafting ghost terminal panes (STA-3077) | #12264 | stop reconnect from grafting ghost terminal panes (STA-3077) | Standalone | Request changes | Medium |
| P2 | stop remote terminals before project removal | #13229 | stop remote terminals before project removal | Standalone | Request changes | Medium |
| P2 | stop reorder drags from selecting header labels | #13849 | stop reorder drags from selecting header labels | Standalone | Review soon | Medium |
| P2 | stop reporting permission-denied worktrees as deleted | #13826 | stop reporting permission-denied worktrees as deleted | Standalone | Request changes | Medium |
| P2 | stop retained output slices pinning whole parent strings | #12939 | stop retained output slices pinning whole parent strings | Standalone | Defer | Medium |
| P2 | stop rewriting the engine user agent so Cloudflare challenges pass (STA-3905) | #17189 | stop rewriting the engine user agent so Cloudflare challenges pass (STA-3905) | Standalone | Review soon | Medium |
| P2 | stop sibling session rows indenting when a lineage expands | #14126 | stop sibling session rows indenting when a lineage expands | Standalone | Review soon | Medium |
| P2 | stop silently deleting workspaces of groups without a parentPath on load | #13344 | stop silently deleting workspaces of groups without a parentPath on load | Standalone | Request changes | Medium |
| P2 | stop the agent row's tool step from flickering on every hook (#11075) | #14682 | stop the agent row's tool step from flickering on every hook (#11075) | Standalone | Review soon | Medium |
| P2 | stop the titlebar spinner on settlement and idle compaction | #16880 | stop the titlebar spinner on settlement and idle compaction | Standalone | Review soon | Medium |
| P2 | stop the WebRTC egress probe timing out its own startup | #17125 | stop the WebRTC egress probe timing out its own startup | Standalone | Request changes | Medium |
| P2 | stop titlebar spinner from crashing on stale session ctx | #14412 #14618 | Coordinate 2 proposals for stop titlebar spinner from crashing on stale session ctx. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | stop Windows checks from reporting a false latest version | #14325 | stop Windows checks from reporting a false latest version | Standalone | Review soon | Medium |
| P2 | stop Windows teardown failing a passed rebuild-native-deps test | #17088 | stop Windows teardown failing a passed rebuild-native-deps test | Standalone | Request changes | Medium |
| P2 | stop workspace delete from waking a sleeping sibling | #14705 | stop workspace delete from waking a sleeping sibling | Standalone | Review soon | Medium |
| P2 | strip Electron's invoke envelope at the preload boundary | #17264 | strip Electron's invoke envelope at the preload boundary | Standalone | Review soon | Medium |
| P2 | strip Kimi hook-result envelopes | #14791 #14807 | Coordinate 2 proposals for strip Kimi hook-result envelopes. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | support helper on macOS 12 | #15720 | support helper on macOS 12 | Standalone | Defer | Medium |
| P2 | support non-secure web contexts | #13142 | support non-secure web contexts | Standalone | Request changes | Medium |
| P2 | surface API auth error messages in Settings | #14045 | surface API auth error messages in Settings | Standalone | Review soon | Medium |
| P2 | surface clipboard copy failures and make verify advisory | #12779 | surface clipboard copy failures and make verify advisory | Standalone | Defer | Medium |
| P2 | surface load-earlier failures and stop retry storms (STA-3333) | #12499 | surface load-earlier failures and stop retry storms (STA-3333) | Standalone | Request changes | Medium |
| P2 | syntax highlighting for Glimmer and Handlebars | #13236 | syntax highlighting for Glimmer and Handlebars | Standalone | Request changes | Medium |
| P2 | syntax-highlight VHDL and SystemVerilog | #12124 | syntax-highlight VHDL and SystemVerilog | Standalone | Request changes | Medium |
| P2 | teach dispatched workers the status message for progress | #14762 | teach dispatched workers the status message for progress | Standalone | Review soon | Medium |
| P2 | tell a settled worker what happened instead of that it is revoked | #14764 | tell a settled worker what happened instead of that it is revoked | Standalone | Review soon | Medium |
| P2 | tell a watched local exit apart from a lost route | #17058 | tell a watched local exit apart from a lost route | Standalone | Request changes | Medium |
| P2 | treat SYSTEMROOT as optional in the Git Bash hook wrapper | #14793 | treat SYSTEMROOT as optional in the Git Bash hook wrapper | Standalone | Review soon | Medium |
| P2 | trim trailing PROMPT_COMMAND separator in the daemon bash wrapper | #14451 | trim trailing PROMPT_COMMAND separator in the daemon bash wrapper | Standalone | Review soon | Medium |
| P2 | update watcher targets incrementally | #16176 | update watcher targets incrementally | Standalone | Review soon | Medium |
| P2 | use a codex-specific 3s managed hook timeout, and cover the EOF pipe-break signature in the | #13900 | use a codex-specific 3s managed hook timeout, and cover the EOF pipe-break signature in the | Standalone | Review soon | Medium |
| P2 | use createBrowserUuid for cross-platform UUID generation | #13101 | use createBrowserUuid for cross-platform UUID generation | Standalone | Merge | Medium |
| P2 | use launch agent for first auto-name | #14431 | use launch agent for first auto-name | Standalone | Review soon | Medium |
| P2 | use native monospace font on iOS | #14093 | use native monospace font on iOS | Standalone | Review soon | Medium |
| P2 | verify derived-sort drops don't accidentally switch to manual | #12762 | verify derived-sort drops don't accidentally switch to manual | Standalone | Request changes | Medium |
| P2 | wait out a disconnected PTY owner's full grace instead of failing the connect | #12749 | wait out a disconnected PTY owner's full grace instead of failing the connect | Standalone | Request changes | Medium |
| P2 | wake a restored idle pane that never speaks again | #13203 | wake a restored idle pane that never speaks again | Standalone | Request changes | Medium |
| P2 | warn before closing SSH work | #17077 | warn before closing SSH work | Standalone | Review soon | Medium |
| P2 | watch the directory of open files outside every worktree root | #15627 | watch the directory of open files outside every worktree root | Standalone | Review soon | Medium |
| P2 | watch the whole worktree so nested external edits reach open editors | #12472 | watch the whole worktree so nested external edits reach open editors | Standalone | Defer | Medium |
| P2 | add GPT Transcribe model | #12116 | add GPT Transcribe model | Standalone | Merge | Medium |
| P2 | Add native Plane task tracker integration | #14692 | Add native Plane task tracker integration | Standalone | Request changes | Medium |
| P2 | add the macOS blur surface for Background Opacity and Window Blur (partial) | #12470 | add the macOS blur surface for Background Opacity and Window Blur (partial) | Standalone | Request changes | Medium |
| P2 | allow zero-message agent sessions | #14200 | allow zero-message agent sessions | Standalone | Review soon | Medium |
| P2 | block delete on branch-attributed shared stash (partial) | #13979 | block delete on branch-attributed shared stash (partial) | Standalone | Review soon | Medium |
| P2 | bound Windows Claude hook stdin before curl | #13560 | bound Windows Claude hook stdin before curl | Standalone | Request changes | Medium |
| P2 | cache legacy worktree clean fallback | #17213 | cache legacy worktree clean fallback | Standalone | Review soon | Medium |
| P2 | closeTerminalTab must not orphan a runtime-owned pty behind tab_not_found (#14719) | #14726 | closeTerminalTab must not orphan a runtime-owned pty behind tab_not_found (#14719) | Standalone | Review soon | Medium |
| P2 | consolidate agent prompt and mailbox PTY delivery ownership | #16198 | consolidate agent prompt and mailbox PTY delivery ownership | Standalone | Request changes | Medium |
| P2 | count a client-initiated ping as proof of life | #12548 | count a client-initiated ping as proof of life | Standalone | Merge | Medium |
| P2 | cover paired Windows ownership races | #15575 | cover paired Windows ownership races | Standalone | Defer | Medium |
| P2 | Daemon terminal-host inspection: a degraded read is unverifiable, never an agent exit | #17003 | Daemon terminal-host inspection: a degraded read is unverifiable, never an agent exit | Standalone | Review soon | Medium |
| P2 | defer the sleeping-agent sweep until a direct-SSH workspace merges its snapshot | #12704 | defer the sleeping-agent sweep until a direct-SSH workspace merges its snapshot | Standalone | Request changes | Medium |
| P2 | deliver agent completion notifications from serve hosts | #12045 | deliver agent completion notifications from serve hosts | Standalone | Request changes | Medium |
| P2 | design durable bounded shutdown follow-up | #12425 | design durable bounded shutdown follow-up | Standalone | Defer | Medium |
| P2 | detect new-tab agents on runtime execution owner | #13977 | detect new-tab agents on runtime execution owner | Standalone | Review soon | Medium |
| P2 | disambiguate same-named projects by host role | #13222 | disambiguate same-named projects by host role | Standalone | Review soon | Medium |
| P2 | dismiss the keyboard after sending to an agent | #17059 | dismiss the keyboard after sending to an agent | Standalone | Review soon | Medium |
| P2 | document status --json runtime capability flags | #13212 | document status --json runtime capability flags | Standalone | Merge | Medium |
| P2 | document terminal read --json result schema | #13173 | document terminal read --json result schema | Standalone | Merge | Medium |
| P2 | don't tear down terminals when a scan lists no worktrees | #12916 | don't tear down terminals when a scan lists no worktrees | Standalone | Request changes | Medium |
| P2 | drop residual per-PTY map entries on teardown | #15286 | drop residual per-PTY map entries on teardown | Standalone | Review soon | Medium |
| P2 | drop the ssh-pty-provider mock key that names no export | #17232 | drop the ssh-pty-provider mock key that names no export | Standalone | Merge | Medium |
| P2 | drop the standalone Chat session launcher | #15372 | drop the standalone Chat session launcher | Standalone | Request changes | Medium |
| P2 | emit a typed exited frame before the terminal stream ends | #12836 | emit a typed exited frame before the terminal stream ends | Standalone | Request changes | Medium |
| P2 | expire the app-wide WebGL DOM suggestion at recovery boundaries | #15455 | expire the app-wide WebGL DOM suggestion at recovery boundaries | Standalone | Review soon | Medium |
| P2 | expose terminal agent status | #12994 | expose terminal agent status | Standalone | Request changes | Medium |
| P2 | fail closed on wedged cookie CDP mutations | #15684 | fail closed on wedged cookie CDP mutations | Standalone | Defer | Medium |
| P2 | fire Marker dispose before clearing line | #13178 | fire Marker dispose before clearing line | Standalone | Request changes | Medium |
| P2 | fix dead links for Goose quickstart and Continue CLI guides | #14574 | fix dead links for Goose quickstart and Continue CLI guides | Standalone | Review soon | Medium |
| P2 | focus multi-agent rows across sibling worktree keys | #13156 | focus multi-agent rows across sibling worktree keys | Standalone | Request changes | Medium |
| P2 | focus the live pane when resuming an already-running session from the sidebar | #12703 | focus the live pane when resuming an already-running session from the sidebar | Standalone | Request changes | Medium |
| P2 | give an SSH pane binding one home — the 2→19→20 mechanism (STA-3077 P) | #13324 | give an SSH pane binding one home — the 2→19→20 mechanism (STA-3077 P) | Standalone | Request changes | Medium |
| P2 | guard SshConnection's SFTP calls against protocol-layer errors (#15479) | #15800 | guard SshConnection's SFTP calls against protocol-layer errors (#15479) | Standalone | Review soon | Medium |
| P2 | hide Codex home-level scratch capsules | #15253 | hide Codex home-level scratch capsules | Standalone | Review soon | Medium |
| P2 | i18n: localize keep-awake / caffeinate status segment for zh, ja, ko, es | #14820 | i18n: localize keep-awake / caffeinate status segment for zh, ja, ko, es | Standalone | Review soon | Medium |
| P2 | isolate late retired tunnel frames | #14694 | isolate late retired tunnel frames | Standalone | Defer | Medium |
| P2 | keep archived Codex sessions out of the real-home backfill | #16882 | keep archived Codex sessions out of the real-home backfill | Standalone | Review soon | Medium |
| P2 | keep attachments on multi-image sends | #16977 | keep attachments on multi-image sends | Standalone | Review soon | Medium |
| P2 | keep COMMITS expand and height across worktrees | #12814 | keep COMMITS expand and height across worktrees | Standalone | Request changes | Medium |
| P2 | keep completed run sessions visible | #15570 | keep completed run sessions visible | Standalone | Review soon | Medium |
| P2 | keep default cookie clearing available | #15044 #15676 | Coordinate 2 proposals for keep default cookie clearing available. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | keep tab order and titles stable on a headless host | #12042 | keep tab order and titles stable on a headless host | Standalone | Request changes | Medium |
| P2 | keep worker-start RPC alive past the 30s socket idle cap | #12126 | keep worker-start RPC alive past the 30s socket idle cap | Standalone | Request changes | Medium |
| P2 | let a deliberate agent /rename win the tab label mid-session | #12481 | let a deliberate agent /rename win the tab label mid-session | Standalone | Request changes | Medium |
| P2 | let a respawned pane's status come back on any provider | #17267 | let a respawned pane's status come back on any provider | Standalone | Review soon | Medium |
| P2 | let an agent's own /rename win the tab label | #12319 | let an agent's own /rename win the tab label | Standalone | Request changes | Medium |
| P2 | make check log excerpts readable before they reach the UI and prompts | #14871 | make check log excerpts readable before they reach the UI and prompts | Standalone | Review soon | Medium |
| P2 | make the published group->tab invariant true for terminals | #17106 | make the published group->tab invariant true for terminals | Standalone | Review soon | Medium |
| P2 | map Salesforce Apex extensions to the apex language id | #14287 | map Salesforce Apex extensions to the apex language id | Standalone | Review soon | Medium |
| P2 | one bind producer, so the superseded-pane fence is live on reattach (STA-3077 F) | #13325 | one bind producer, so the superseded-pane fence is live on reattach (STA-3077 F) | Standalone | Review soon | Medium |
| P2 | only skip the quit warning when the work actually survives | #17085 | only skip the quit warning when the work actually survives | Standalone | Review soon | Medium |
| P2 | open files from PR comments | #13230 | open files from PR comments | Standalone | Request changes | Medium |
| P2 | Open right sidebar by default for new web profiles | #13731 | Open right sidebar by default for new web profiles | Standalone | Review soon | Medium |
| P2 | open the host editor deterministically via a route action | #12554 | open the host editor deterministically via a route action | Standalone | Request changes | Medium |
| P2 | open working-tree file from a change row | #14778 | open working-tree file from a change row | Standalone | Review soon | Medium |
| P2 | park a remote pty only for the worktree that owns it | #13253 | park a remote pty only for the worktree that owns it | Standalone | Request changes | Medium |
| P2 | pin the relay re-establish budget to the deadlines it covers | #15760 | pin the relay re-establish budget to the deadlines it covers | Standalone | Review soon | Medium |
| P2 | pipeline live terminal input instead of awaiting each RPC (STA-3199) | #15708 | pipeline live terminal input instead of awaiting each RPC (STA-3199) | Standalone | Review soon | Medium |
| P2 | preserve live agent on readiness timeout | #15215 | preserve live agent on readiness timeout | Standalone | Defer | Medium |
| P2 | preserve SSH hook launch context (STA-3147) | #16062 | preserve SSH hook launch context (STA-3147) | Standalone | Defer | Medium |
| P2 | preserve the exact preview source group | #16129 | preserve the exact preview source group | Standalone | Review soon | Medium |
| P2 | preview remote terminal HTML taps | #13234 | preview remote terminal HTML taps | Standalone | Merge | Medium |
| P2 | re-attach on restoreRequired instead of expiring the live session | #12456 | re-attach on restoreRequired instead of expiring the live session | Standalone | Request changes | Medium |
| P2 | reap empty macOS TCC login wrappers after shell exit | #13973 | reap empty macOS TCC login wrappers after shell exit | Standalone | Review soon | Medium |
| P2 | reconcile hook relays on startup | #13491 | reconcile hook relays on startup | Standalone | Request changes | Medium |
| P2 | recover provider-only terminal state safely | #16267 | recover provider-only terminal state safely | Standalone | Review soon | Medium |
| P2 | refresh desktop TUI after mobile-fit ends | #14787 | refresh desktop TUI after mobile-fit ends | Standalone | Review soon | Medium |
| P2 | refuse a self-addressed ask instead of blocking | #15266 | refuse a self-addressed ask instead of blocking | Standalone | Review soon | Medium |
| P2 | report when a remote's node-pty has no native job control | #17042 | report when a remote's node-pty has no native job control | Standalone | Review soon | Medium |
| P2 | resolve Devin transcripts under APPDATA on Windows | #15818 | resolve Devin transcripts under APPDATA on Windows | Standalone | Review soon | Medium |
| P2 | restore terminal modes when a pane reattaches to a relay-hosted SSH pty | #13043 | restore terminal modes when a pane reattaches to a relay-hosted SSH pty | Standalone | Request changes | Medium |
| P2 | serve an omp native-chat scenario | #14859 | serve an omp native-chat scenario | Standalone | Review soon | Medium |
| P2 | Show agent names and lineage in dashboard map | #14991 | Show agent names and lineage in dashboard map | Standalone | Review soon | Medium |
| P2 | show phone-launched agent tabs before desktop mounts them | #15204 | show phone-launched agent tabs before desktop mounts them | Standalone | Review soon | Medium |
| P2 | show tooltip for truncated shortcut titles in shortcut… | #16806 | show tooltip for truncated shortcut titles in shortcut… | Standalone | Review soon | Medium |
| P2 | slow certified terminal inventory sweeps | #17182 | slow certified terminal inventory sweeps | Standalone | Request changes | Medium |
| P2 | soft-skip migrated non-GitLab projects in Tasks | #13962 | soft-skip migrated non-GitLab projects in Tasks | Standalone | Review soon | Medium |
| P2 | Split automation dispatch event handling | #17155 | Split automation dispatch event handling | Standalone | Request changes | Medium |
| P2 | Split CDP bridge responsibilities | #17215 | Split CDP bridge responsibilities | Standalone | Request changes | Medium |
| P2 | split Codex account service modules | #17277 | split Codex account service modules | Standalone | Request changes | Medium |
| P2 | Split mobile browser pane modules | #17141 | Split mobile browser pane modules | Standalone | Request changes | Medium |
| P2 | Split resource usage status responsibilities | #17244 | Split resource usage status responsibilities | Standalone | Request changes | Medium |
| P2 | Split web runtime session responsibilities | #17263 | Split web runtime session responsibilities | Standalone | Request changes | Medium |
| P2 | STA-5061: restore Cmd-J host badges | #15891 | STA-5061: restore Cmd-J host badges | Standalone | Review soon | Medium |
| P2 | STA-5496: offer Orca Browser for SSH terminal links | #16503 | STA-5496: offer Orca Browser for SSH terminal links | Standalone | Review soon | Medium |
| P2 | stop bash alias collision from crashing codex/omp shell wrappers | #15844 | stop bash alias collision from crashing codex/omp shell wrappers | Standalone | Review soon | Medium |
| P2 | stop deleting page annotations on navigate/reload | #15019 | stop deleting page annotations on navigate/reload | Standalone | Review soon | Medium |
| P2 | stop duplicating rows in the status-bar popover after Stop Process | #15626 | stop duplicating rows in the status-bar popover after Stop Process | Standalone | Review soon | Medium |
| P2 | stop host snapshots yanking the phone off its current tab | #12471 | stop host snapshots yanking the phone off its current tab | Standalone | Request changes | Medium |
| P2 | stop publishing an active group the phone was never sent | #17100 | stop publishing an active group the phone was never sent | Standalone | Review soon | Medium |
| P2 | stop reconnect grafting panes, stacking leases, and respawning live shells (STA-3077) | #13111 | stop reconnect grafting panes, stacking leases, and respawning live shells (STA-3077) | Standalone | Request changes | Medium |
| P2 | stop remote workspace pulls from resurrecting closed tabs | #12339 | stop remote workspace pulls from resurrecting closed tabs | Standalone | Request changes | Medium |
| P2 | stop separator-variant worktree ids purging live checkouts | #15616 | stop separator-variant worktree ids purging live checkouts | Standalone | Review soon | Medium |
| P2 | stop snapshot applies from erasing worktrees outside the hydration validity set | #13030 | stop snapshot applies from erasing worktrees outside the hydration validity set | Standalone | Review soon | Medium |
| P2 | stop the wake sweep from forking sessions that live SSH panes still own | #12702 | stop the wake sweep from forking sessions that live SSH panes still own | Standalone | Review soon | Medium |
| P2 | stop untyped tool-hook agent_ids from minting phantom subagent rows | #15326 | stop untyped tool-hook agent_ids from minting phantom subagent rows | Standalone | Review soon | Medium |
| P2 | stream an idle-agent reply below the prompt that caused it | #15617 | stream an idle-agent reply below the prompt that caused it | Standalone | Review soon | Medium |
| P2 | strip the invoke envelope from the discard and GitLab list errors | #17259 | strip the invoke envelope from the discard and GitLab list errors | Standalone | Review soon | Medium |
| P2 | submit large agent-prompt pastes after TUI ingest (STA-2912) | #15698 | submit large agent-prompt pastes after TUI ingest (STA-2912) | Standalone | Request changes | Medium |
| P2 | Support Kagi private-session navigation without token persistence | #13943 | Support Kagi private-session navigation without token persistence | Standalone | Request changes | Medium |
| P2 | surface failed attach-only orphan retire for support | #13143 | surface failed attach-only orphan retire for support | Standalone | Request changes | Medium |
| P2 | track closed PTY inventory incrementally | #16174 | track closed PTY inventory incrementally | Standalone | Review soon | Medium |
| P2 | treat an absent worktree and an empty tab list as different answers | #12987 | treat an absent worktree and an empty tab list as different answers | Standalone | Request changes | Medium |
| P2 | use the entered group name when opening a folder | #16881 | use the entered group name when opening a folder | Standalone | Review soon | Medium |
| P2 | verify a sleeping session's tab is gone from every session partition before resuming into a | #13037 | verify a sleeping session's tab is gone from every session partition before resuming into a | Standalone | Request changes | Medium |
| P2 | accept an empty --value in cookie set and --pass in set credentials | #17226 | accept an empty --value in cookie set and --pass in set credentials | Standalone | Merge | Medium |
| P2 | ask before a tab close kills a pty the app cannot vouch for | #17076 | ask before a tab close kills a pty the app cannot vouch for | Standalone | Request changes | Medium |
| P2 | bound git response-stream reassembly on the host | #14510 | bound git response-stream reassembly on the host | Standalone | Merge | Medium |
| P2 | bound stalled setup-split grid polling | #17228 | bound stalled setup-split grid polling | Standalone | Merge | Medium |
| P2 | cap distinct error surface growth | #12809 #13145 | Coordinate 2 proposals for cap distinct error surface growth. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | defer mail pointer when user is actively typing | #14836 | defer mail pointer when user is actively typing | Standalone | Review soon | Medium |
| P2 | do not inherit nice -8 into integrated PTYs | #14786 | do not inherit nice -8 into integrated PTYs | Standalone | Review soon | Medium |
| P2 | document client pairing and port 6768 collision | #13175 | document client pairing and port 6768 collision | Standalone | Request changes | Medium |
| P2 | don't report a connected Codex account as unconfigured when its usage read fails | #17167 | don't report a connected Codex account as unconfigured when its usage read fails | Standalone | Review soon | Medium |
| P2 | fence client page placements | #14529 | fence client page placements | Standalone | Defer | Medium |
| P2 | find cross-fork pull requests when the fork is not `origin` | #12957 #13227 | Coordinate 2 proposals for find cross-fork pull requests when the fork is not `origin`. | Related | Review together; merge in sequence if compatible | Medium |
| P2 | Fix Jira connector routing in Web UI | #16803 | Fix Jira connector routing in Web UI | Standalone | Review soon | Medium |
| P2 | ignore a fit hold with no dimensions | #13951 | ignore a fit hold with no dimensions | Standalone | Review soon | Medium |
| P2 | keep the project selection per task source | #15848 | keep the project selection per task source | Standalone | Review soon | Medium |
| P2 | keepalive slow non-long-poll dispatches past the idle reaper | #15730 | keepalive slow non-long-poll dispatches past the idle reaper | Standalone | Review soon | Medium |
| P2 | let a dual-role terminal read its Dispatch mailbox | #15267 | let a dual-role terminal read its Dispatch mailbox | Standalone | Review soon | Medium |
| P2 | let a new QR supersede deferred pairing recovery | #13174 | let a new QR supersede deferred pairing recovery | Standalone | Merge | Medium |
| P2 | make src/shared the only terminal stream wire definition (STA-3482) | #12834 | make src/shared the only terminal stream wire definition (STA-3482) | Standalone | Review soon | Medium |
| P2 | name the transport failure sign-in and Relay swallow | #13736 | name the transport failure sign-in and Relay swallow | Standalone | Review soon | Medium |
| P2 | never finalize a hidden-output loss where nobody can see it (STA-4869) | #15534 | never finalize a hidden-output loss where nobody can see it (STA-4869) | Standalone | Defer | Medium |
| P2 | note that active/current worktree selectors are local-runtime only | #14035 #14072 | Coordinate 2 proposals for note that active/current worktree selectors are local-runtime only. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P2 | offer Remove on path-bound host setups, behind a confirm | #15610 | offer Remove on path-bound host setups, behind a confirm | Standalone | Review soon | Medium |
| P2 | open WSL Claude sign-in in Windows browser | #12023 | open WSL Claude sign-in in Windows browser | Standalone | Request changes | Medium |
| P2 | preserve standing host reconnect intent | #17067 | preserve standing host reconnect intent | Standalone | Review soon | Medium |
| P2 | preserve WebGL atlas on tab reveal | #13339 | preserve WebGL atlas on tab reveal | Standalone | Request changes | Medium |
| P2 | Prune resolved max-lines suppressions | #17142 | Prune resolved max-lines suppressions | Standalone | Request changes | Medium |
| P2 | raise viewport column cap from 240 to 1024 | #16578 | raise viewport column cap from 240 to 1024 | Standalone | Review soon | Medium |
| P2 | remember last GitHub Start vs Open-in-browser choice | #14779 | remember last GitHub Start vs Open-in-browser choice | Standalone | Review soon | Medium |
| P2 | report counterbalanced WSL Git medians | #13474 | report counterbalanced WSL Git medians | Standalone | Merge | Medium |
| P2 | report real exitCode from terminal wait --for exit | #14774 | report real exitCode from terminal wait --for exit | Standalone | Review soon | Medium |
| P2 | Report the failing command and PATH when a POSIX setup runner fails | #15271 | Report the failing command and PATH when a POSIX setup runner fails | Standalone | Review soon | Medium |
| P2 | restore retained tail when host snapshot is empty | #14184 | restore retained tail when host snapshot is empty | Standalone | Review soon | Medium |
| P2 | retire timed-out provider snapshot acquisitions | #16560 | retire timed-out provider snapshot acquisitions | Standalone | Review soon | Medium |
| P2 | show relay grace period in two units | #13838 | show relay grace period in two units | Standalone | Review soon | Medium |
| P2 | skip unchanged review-note reflows | #17212 | skip unchanged review-note reflows | Standalone | Merge | Medium |
| P2 | Split Claude runtime auth responsibilities | #17268 | Split Claude runtime auth responsibilities | Standalone | Request changes | Medium |
| P2 | Split hosted review creation checks | #17152 | Split hosted review creation checks | Standalone | Request changes | Medium |
| P2 | Split pane tree equalization logic | #17145 | Split pane tree equalization logic | Standalone | Request changes | Medium |
| P2 | stagger and bound metadata polling | #16175 | stagger and bound metadata polling | Standalone | Review soon | Medium |
| P2 | stop a failed diff load from being saved over the file | #14509 | stop a failed diff load from being saved over the file | Standalone | Request changes | Medium |
| P2 | stop rescanning persisted pane tabs | #17179 | stop rescanning persisted pane tabs | Standalone | Review soon | Medium |
| P2 | stop writing hook events Claude Code's schema rejects | #15558 | stop writing hook events Claude Code's schema rejects | Standalone | Review soon | Medium |
| P2 | surface Git dubious ownership instead of empty imports | #13151 | surface Git dubious ownership instead of empty imports | Standalone | Request changes | Medium |
| P2 | track Windows performance work | #13167 | track Windows performance work | Standalone | Request changes | Medium |
| P2 | treat existing WSL Codex runtime home as ready on EISDIR mkdir | #15444 | treat existing WSL Codex runtime home as ready on EISDIR mkdir | Standalone | Review soon | Medium |
| P2 | wait for queued writes in park snapshots | #16141 | wait for queued writes in park snapshots | Standalone | Request changes | Medium |
| P2 | warn implementers that internal subagents must not send worker_done (#15634) | #15795 | warn implementers that internal subagents must not send worker_done (#15634) | Standalone | Review soon | Medium |
| P2 | apply terminal line height to Monaco | #14783 | apply terminal line height to Monaco | Standalone | Review soon | Medium |
| P2 | Extract mobile troubleshoot screen styles | #17146 | Extract mobile troubleshoot screen styles | Standalone | Request changes | Medium |
| P2 | fix broken Continue CLI link in README | #14226 | fix broken Continue CLI link in README | Standalone | Review soon | Medium |
| P2 | isolate unparseable schedules per tick and reject over-range cron steps | #15902 | isolate unparseable schedules per tick and reject over-range cron steps | Standalone | Review soon | Medium |
| P2 | join wrapped PowerShell URLs before opening | #14784 | join wrapped PowerShell URLs before opening | Standalone | Review soon | Medium |
| P2 | prompt before opening custom app protocol links | #13240 | prompt before opening custom app protocol links | Standalone | Request changes | Medium |
| P2 | stop re-wiping the shared glyph atlas on every reveal shot | #13836 | stop re-wiping the shared glyph atlas on every reveal shot | Standalone | Review soon | Medium |
| P2 | syntax-highlight VHDL files | #12123 | syntax-highlight VHDL files | Standalone | Review soon | Medium |
| P2 | validate in-process serve flags like the CLI | #13133 | validate in-process serve flags like the CLI | Standalone | Review soon | Medium |
| P2 | warn that bare brew cask orca is Plotly, not Orca ADE | #14777 | warn that bare brew cask orca is Plotly, not Orca ADE | Standalone | Review soon | Medium |
| P2 | preserve ANSI background under IME preedit | #16230 | preserve ANSI background under IME preedit | Standalone | Review soon | Medium |
| P2 | correct zh-CN translation for editor view toggle buttons | #13723 | correct zh-CN translation for editor view toggle buttons | Standalone | Review soon | Medium |
| P2 | order Issues board columns Backlog -> Done | #12096 | order Issues board columns Backlog -> Done | Standalone | Request changes | Medium |
| P2 | upgrade nanoid to 3.3.18, 5.1.6 (CVE-2026-67213) | #14521 | upgrade nanoid to 3.3.18, 5.1.6 (CVE-2026-67213) | Standalone | Review soon | Medium |
| P2 | [TEST] Stacked PR UI validation — API | #13721 | [TEST] Stacked PR UI validation — API | Standalone | Merge | Medium |
| P2 | keep underscores visible when ligatures are enabled (#13473) | #14055 | keep underscores visible when ligatures are enabled (#13473) | Standalone | Review soon | Medium |
| P2 | key cron day restriction off the literal star, matching vixie | #15900 | key cron day restriction off the literal star, matching vixie | Standalone | Review soon | Medium |
| P2 | [TEST] Stacked PR creation — child | #13741 | [TEST] Stacked PR creation — child | Standalone | Defer | Medium |
| P2 | [TEST] Stacked PR creation — parent | #13740 | [TEST] Stacked PR creation — parent | Standalone | Defer | Medium |
| P2 | [TEST] Stacked PR creation — UI layer | #13738 | [TEST] Stacked PR creation — UI layer | Standalone | Defer | Medium |
| P2 | Windows PR menu reproduction | #16844 | Windows PR menu reproduction | Standalone | Defer | Medium |
| P3 | batch-prune stale local metadata | #17278 | batch-prune stale local metadata | Standalone | Consider closing | Medium |
| P3 | clear stale mobile ws fallback port | #15509 | clear stale mobile ws fallback port | Standalone | Consider closing | Medium |
| P3 | complete OMP stale cwd recovery | #17154 | complete OMP stale cwd recovery | Standalone | Consider closing | Medium |
| P3 | discard a stale authorized-roots rebuild instead of marking the cache clean | #15668 #15726 | Coordinate 2 proposals for discard a stale authorized-roots rebuild instead of marking the cache clean. | Competing | Choose one preferred solution | Medium |
| P3 | drop the stale Settings > Experimental prerequisite | #14034 #14069 | Coordinate 2 proposals for drop the stale Settings > Experimental prerequisite. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P3 | handle static WSL titles and clear stale spinners | #13891 #13923 #14602 | Coordinate 3 proposals for handle static WSL titles and clear stale spinners. | Overlapping | Review together; merge in sequence if compatible | Medium |
| P3 | let live conversation names outrank a stale first-prompt title (STA-2848) | #15703 | let live conversation names outrank a stale first-prompt title (STA-2848) | Standalone | Request changes | Medium |
| P3 | refuse stale same-identity credential overwrites | #13568 | refuse stale same-identity credential overwrites | Standalone | Request changes | Medium |
| P3 | stop a stale scan from pruning lineage created mid-scan | #16656 | stop a stale scan from pruning lineage created mid-scan | Standalone | Consider closing | Medium |
| P3 | stop WSL API-key Codex defaults reading as stale sign-ins | #13254 | stop WSL API-key Codex defaults reading as stale sign-ins | Standalone | Consider closing | Medium |
| P3 | fix a README typo and drop a stale RC cron note | #14569 | fix a README typo and drop a stale RC cron note | Standalone | Consider closing | Medium |
| P3 | make the stale terminal artifact grant assertion deterministic | #16004 | make the stale terminal artifact grant assertion deterministic | Standalone | Consider closing | Medium |
| P3 | mute stale agent status and disable Stop while disconnected (STA-3333) | #12496 | mute stale agent status and disable Stop while disconnected (STA-3333) | Standalone | Request changes | Medium |
| P3 | preserve host PTY binding over stale renderer replay | #16795 | preserve host PTY binding over stale renderer replay | Standalone | Consider closing | Medium |
| P3 | refresh stale capabilities before pairing | #12134 | refresh stale capabilities before pairing | Standalone | Consider closing | Medium |
| P3 | release an abandoned synchronized-output latch on reveal (~1s stale-pane window) | #15021 | release an abandoned synchronized-output latch on reveal (~1s stale-pane window) | Standalone | Consider closing | Medium |
| P3 | retire superseded dispatch authority | #12024 #12312 | Coordinate 2 proposals for retire superseded dispatch authority. | Duplicate | Supersede redundant work | Medium |
| P3 | stop a stale scan from pruning freshly recorded lineage | #12631 | stop a stale scan from pruning freshly recorded lineage | Standalone | Request changes | Medium |
| P3 | update stale E2E test contracts and fake Codex fixtures | #15432 | update stale E2E test contracts and fake Codex fixtures | Standalone | Request changes | Medium |
| P3 | stop stale snapshot applies from erasing freshly created terminal tabs | #13013 | stop stale snapshot applies from erasing freshly created terminal tabs | Standalone | Request changes | Medium |
| P3 | stop titlebar spinner timer when extension ctx turns stale | #14664 | stop titlebar spinner timer when extension ctx turns stale | Standalone | Consider closing | Medium |
P11Password agent-skill setup panel in the integration card (stacked on #12947)1 PR · Standalone · Plugins#
Problem: 1Password agent-skill setup panel in the integration card (stacked on #12947).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12947 Title unavailable (Unclear, Unknown); #14899 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13042 feat(settings): 1Password agent-skill setup panel in the integration card (stacked on #12947) | Vincent Colombo Community · FIRST_TIME_CONTRIBUTOR | #12947 Title unavailable Unclear · Unknown #14899 Title unavailable Unclear · Unknown | Standalone change | ## What this adds Skill management UI for the `onepassword` agent skill, embedded inline in the 1Password integration card (Settings → Integrations) — matching the pattern the Linear card uses. Always visible, independen | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk40 files, +1598/−56. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add --kind folder to repo add1 PR · Standalone · Plugins#
Problem: add --kind folder to repo add.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6913 [Feature]: CLI support for adding a standalone (non-git) folder as a project (Fixes, OPEN); #13358 Title unavailable (Unclear, Unknown); #12540 Title unavailable (Unclear, Unknown); #13534 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13359 feat(cli): add --kind folder to repo add | Anton Novoselov Community · FIRST_TIME_CONTRIBUTOR | #6913 [Feature]: CLI support for adding a standalone (non-git) folder as a project Fixes · OPEN #13358 Title unavailable Unclear · Unknown #12540 Title unavailable Unclear · Unknown #13534 Title unavailable Unclear · Unknown | Standalone change | Closes #6913, implementing the second of the three options its "Proposed solution" lists (an explicit `--kind folder` on `repo add`). Also covers #13358 and #12540, both since closed as duplicates of #6913. ## User-visib | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +136/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add "Open With" submenu listing OS-registered apps1 PR · Standalone · Plugins#
Problem: add "Open With" submenu listing OS-registered apps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13993 [Feature]: "Open With" submenu on file explorer rows — pick among the OS-registered apps for the file's type (Fixes, OPEN); #11252 Title unavailable (Unclear, Unknown); #11414 Title unavailable (Unclear, Unknown); #11268 Title unavailable (Unclear, Unknown); #14397 Title unavailable (Unclear, Unknown); #14403 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13994 feat(file-explorer): add "Open With" submenu listing OS-registered apps | HigumaLu Community · FIRST_TIME_CONTRIBUTOR | #13993 [Feature]: "Open With" submenu on file explorer rows — pick among the OS-registered apps for the file's type Fixes · OPEN #11252 Title unavailable Unclear · Unknown #11414 Title unavailable Unclear · Unknown #11268 Title unavailable Unclear · Unknown #14397 Title unavailable Unclear · Unknown #14403 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Right-click a file in the file explorer → **Open With** → pick any app your OS knows can open that file type (PowerPoint for `.pptx`, an image viewer for `.png`, ...). The default app is listed first, your recent | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +1953/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add `orca linear project create` (3/4)1 PR · Standalone · Plugins#
Problem: add `orca linear project create` (3/4).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15024 Title unavailable (Unclear, Unknown); #15034 Title unavailable (Unclear, Unknown); #15126 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15042 feat(linear): add `orca linear project create` (3/4)Draft | Jinjing Core team · MEMBER | #15024 Title unavailable Unclear · Unknown #15034 Title unavailable Unclear · Unknown #15126 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 16 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk55 files, +4604/−114. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add `orca linear project edit` (4/4)1 PR · Standalone · Plugins#
Problem: add `orca linear project edit` (4/4).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15024 Title unavailable (Unclear, Unknown); #15034 Title unavailable (Unclear, Unknown); #15042 Title unavailable (Unclear, Unknown); #14931 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15126 feat(linear): add `orca linear project edit` (4/4) | Jinjing Core team · MEMBER | #15024 Title unavailable Unclear · Unknown #15034 Title unavailable Unclear · Unknown #15042 Title unavailable Unclear · Unknown #14931 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 918 | $\color{#1a7f37}{\Huge{\math | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2125 files, +151447/−39077. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add `orca linear project update add` (2/4)1 PR · Standalone · Plugins#
Problem: add `orca linear project update add` (2/4).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15024 Title unavailable (Unclear, Unknown); #15042 Title unavailable (Unclear, Unknown); #15126 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15034 feat(linear): add `orca linear project update add` (2/4)Draft | Jinjing Core team · MEMBER | #15024 Title unavailable Unclear · Unknown #15042 Title unavailable Unclear · Unknown #15126 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +3003/−182. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add a native Plane (plane.so) task provider1 PR · Standalone · Plugins#
Problem: add a native Plane (plane.so) task provider.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15328 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15329 feat(plane): add a native Plane (plane.so) task provider | Dragos Boca Community · FIRST_TIME_CONTRIBUTOR | #15328 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can browse tasks from GitHub, GitLab, Linear and Jira. This adds [Plane](https://plane.so) as a fifth. You connect it in Settings with a personal access token and your workspace slug — Plane Cloud or self-ho | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk91 files, +7207/−122. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add a session-safe shared MCP tools bridge runtime1 PR · Standalone · Plugins#
Problem: add a session-safe shared MCP tools bridge runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7362 Title unavailable (Unclear, Unknown); #16211 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16221 feat: add a session-safe shared MCP tools bridge runtime | 叁笙早安 AI Community · FIRST_TIME_CONTRIBUTOR | #7362 Title unavailable Unclear · Unknown #16211 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds the runtime foundation for a session-safe, shared MCP bridge (part of #7362 and the resource-reduction work tracked in #16211). The bridge exposes a bearer-protected Streamable HTTP endpoint on `127.0.0.1 | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +634/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add active pane border for the focused split pane1 PR · Standalone · Plugins#
Problem: add active pane border for the focused split pane.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16734 Highlight the focused terminal pane with a configurable active-pane border (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16735 feat(terminal): add active pane border for the focused split pane | kcisoul Community · FIRST_TIME_CONTRIBUTOR | #16734 Highlight the focused terminal pane with a configurable active-pane border Fixes · OPEN | Standalone change | ## ELI5 When you split the terminal into several panes, it's easy to lose track of which pane your keystrokes will land in. This PR adds an opt-in "Active Pane Border" setting that draws a colored outline around the focu | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +378/−54. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add agent health and CLI updates1 PR · Standalone · Plugins#
Problem: add agent health and CLI updates.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13009 feat(status-bar): add agent health and CLI updates | dngur6344 Community · CONTRIBUTOR | None found | Standalone change | ## Summary Add an Agent status segment to the bottom status bar so users can see whether their linked Claude Code and Codex CLIs are installed, reachable, authenticated, and healthy without leaving the current workspace. | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk35 files, +3912/−91. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add agent project read commands (1/4)1 PR · Standalone · Plugins#
Problem: add agent project read commands (1/4).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15034 Title unavailable (Unclear, Unknown); #15042 Title unavailable (Unclear, Unknown); #15126 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15024 feat(linear): add agent project read commands (1/4)Draft | Jinjing Core team · MEMBER | #15034 Title unavailable Unclear · Unknown #15042 Title unavailable Unclear · Unknown #15126 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 13 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk53 files, +5605/−207. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add API-key-based ClinePass usage tracking1 PR · Standalone · Plugins#
Problem: add API-key-based ClinePass usage tracking.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13032 [Feature]: Add ClinePass quota tracking to the status bar and AI Provider Accounts (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13827 feat(rate-limits): add API-key-based ClinePass usage tracking | euclodius Community · FIRST_TIME_CONTRIBUTOR | #13032 [Feature]: Add ClinePass quota tracking to the status bar and AI Provider Accounts Fixes · OPEN | Standalone change | ## Scope This is an API-key-based implementation related to #13032. It supports Windows + WSL setups through an Orca-owned credential: the user enters the key once in Settings, the Windows Orca process stores it and quer | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk46 files, +2616/−57. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Auggie status hooks1 PR · Standalone · Plugins#
Problem: add Auggie status hooks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16286 [Feature]: Auggie (Augment Code CLI) agent-status hooks (Fixes, OPEN); #11549 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16287 feat(agents): add Auggie status hooks | mpint Community · FIRST_TIME_CONTRIBUTOR | #16286 [Feature]: Auggie (Augment Code CLI) agent-status hooks Fixes · OPEN #11549 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca now understands status events from the Auggie CLI (`auggie`, agent id `aug`): Auggie panes get a live status row (working / waiting / done, current tool, prompt text) and fire completion notifications, like | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +912/−228. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add automation model options and launch at login1 PR · Standalone · Plugins#
Problem: add automation model options and launch at login.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16405 feat: add automation model options and launch at login | WIll Liu Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - persist optional per-automation model and reasoning-effort preferences, snapshot them on runs, and avoid reusing sessions created with different options - apply preferences across existing-workspace, new-wor | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk54 files, +1342/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Brazilian Portuguese (pt-BR) as a supported UI language1 PR · Standalone · Plugins#
Problem: add Brazilian Portuguese (pt-BR) as a supported UI language.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15629 feat(i18n): add Brazilian Portuguese (pt-BR) as a supported UI language | heslanx Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Registers `pt` (Brazilian Portuguese) as a fully supported UI locale, alongside the existing es/ja/ko/zh, and ships a complete translated catalog. ## Commits 1. `feat(i18n): register pt (Brazilian Portuguese) | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +16750/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add CLI import/unimport for existing worktrees1 PR · Standalone · Plugins#
Problem: add CLI import/unimport for existing worktrees.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10671 [Feature]: Add CLI support to selectively adopt an existing Git worktree (Fixes, OPEN); #2654 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13733 feat(worktrees): add CLI import/unimport for existing worktrees | Jooyoung Shin Community · FIRST_TIME_CONTRIBUTOR | #10671 [Feature]: Add CLI support to selectively adopt an existing Git worktree Fixes · OPEN #2654 Title unavailable Unclear · Unknown | Standalone change | ## Summary Repo visibility sources reveal a whole source at once — the built-in `.claude/worktrees` source covers every coding-agent scratch worktree beneath it. `repo.importedExternalWorktreePaths` is the only mechanism | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +1065/−125. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add collapsible folder groups for tabs and sidebar agents1 PR · Standalone · Plugins#
Problem: add collapsible folder groups for tabs and sidebar agents.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #5194 [Feature]: Tab groups: merge tabs into named, collapsible folders (Fixes, OPEN); #14289 [Feature]: Visually group sidebar agent rows by multi-pane tab (Fixes, OPEN); #5201 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15109 feat(tabs): add collapsible folder groups for tabs and sidebar agents | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #5194 [Feature]: Tab groups: merge tabs into named, collapsible folders Fixes · OPEN #14289 [Feature]: Visually group sidebar agent rows by multi-pane tab Fixes · OPEN #5201 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You can put several independent tabs into a named folder, collapse it to a chip, and see the same folders under the worktree’s agent list. Reload keeps the folders. ## What Changed - New session field `tabFolderG | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk66 files, +2094/−98. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Add command palette shortcut keybinding1 PR · Standalone · Plugins#
Problem: Add command palette shortcut keybinding.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16790 [Feature]: Add configurable command palette shortcut (F1) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16793 feat(editor): Add command palette shortcut keybinding | hwantage Community · CONTRIBUTOR | #16790 [Feature]: Add configurable command palette shortcut (F1) Fixes · OPEN | Standalone change | ## ELI5 When working inside code editors, diff viewers, or notebook cells, you can now press `F1` (or your custom configured shortcut such as `Cmd+Shift+P` / `Ctrl+Shift+P`) to open the editor command palette and quickly | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +194/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add curated appearance packs1 PR · Standalone · Plugins#
Problem: add curated appearance packs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9663 Title unavailable (Unclear, Unknown); #17210 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17214 feat(plugins): add curated appearance packsDraft | ColorC Community · FIRST_TIME_CONTRIBUTOR | #9663 Title unavailable Unclear · Unknown #17210 Title unavailable Unclear · Unknown | Standalone change | > **Draft / stacked change:** this branch is intentionally based on #9663 while that PR is still open. It targets that PR's branch so the review diff contains only this increment. Once #9663 merges, the PR can be retarge | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk39 files, +1987/−89. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add default worker, model, and effort UI1 PR · Standalone · Plugins#
Problem: add default worker, model, and effort UI.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14447 Title unavailable (Unclear, Unknown); #14728 Title unavailable (Unclear, Unknown); #15170 Title unavailable (Unclear, Unknown); #15568 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12431 feat(settings): add default worker, model, and effort UI | Johan Kim Community · FIRST_TIME_CONTRIBUTOR | #14447 Title unavailable Unclear · Unknown #14728 Title unavailable Unclear · Unknown #15170 Title unavailable Unclear · Unknown #15568 Title unavailable Unclear · Unknown | Standalone change | ## Summary This PR adds a single-row **Worker defaults** control to Settings → Orchestration. It lets a user choose the default orchestration worker provider, model, and reasoning effort, with the model and effort choice | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +2642/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Droid agent support and composer-on-top layout1 PR · Standalone · Plugins#
Problem: add Droid agent support and composer-on-top layout.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13625 feat(native-chat): add Droid agent support and composer-on-top layout | Ran Aroussi Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds full Droid (Factory's CLI agent) support to the experimental Chat UI, plus an opt-in setting that reverses the chat layout so the composer sits above the transcript. ### Droid support - **Transcript decod | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +2091/−136. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add durable Run capacity targets1 PR · Standalone · Plugins#
Problem: add durable Run capacity targets.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15185 [Feature]: a Run with a ready task, all lanes settled and an idle coordinator has nothing left to wake it (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16852 feat(orchestration): add durable Run capacity targets | Brennan Benson Core team · MEMBER | #15185 [Feature]: a Run with a ready task, all lanes settled and an idle coordinator has nothing left to wake it Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk38 files, +1583/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add forge provider plugin extension point1 PR · Standalone · Plugins#
Problem: add forge provider plugin extension point.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15315 feat(plugins): add forge provider plugin extension point | ZheNing Hu Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds a plugin extension point that lets plugin packs contribute **forge providers** — adapters for self-hosted code platforms that do not speak GitHub, GitLab, Bitbucket, Azure DevOps, or Gitea APIs. This make | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +1288/−57. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Freebuff as a first-class CLI agent1 PR · Standalone · Plugins#
Problem: add Freebuff as a first-class CLI agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #123 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17065 feat(agents): add Freebuff as a first-class CLI agent | Harkaran Brar Community · FIRST_TIME_CONTRIBUTOR | #123 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can now launch **Freebuff** — the free coding agent built on Codebuff's open framework — as a first-class agent, just like the existing Codebuff support. If you have the `freebuff` CLI installed, Orca detect | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +58/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add French UI locale1 PR · Standalone · Plugins#
Problem: add French UI locale.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8756 Title unavailable (Unclear, Unknown); #16357 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16455 feat(i18n): add French UI locale | foXaCe Community · FIRST_TIME_CONTRIBUTOR | #8756 Title unavailable Unclear · Unknown #16357 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds French (`fr`) as a built-in UI language, following the same architecture as the existing `es`/`ja`/`ko`/`zh` locales: - **New catalog**: `src/renderer/src/i18n/locales/fr.json` — complete coverage (**1333 | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +16685/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Gajae Code as a supported TUI agent1 PR · Standalone · Plugins#
Problem: add Gajae Code as a supported TUI agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14447 Title unavailable (Unclear, Unknown); #12935 Title unavailable (Unclear, Unknown); #7579 Title unavailable (Unclear, Unknown); #7805 Title unavailable (Unclear, Unknown); #9319 Title unavailable (Unclear, Unknown); #9326 Title unavailable (Unclear, Unknown); #10476 Title unavailable (Unclear, Unknown); #15025 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13952 feat(agents): add Gajae Code as a supported TUI agent | 나형진(Hyeongjin Na) Community · FIRST_TIME_CONTRIBUTOR | #14447 Title unavailable Unclear · Unknown #12935 Title unavailable Unclear · Unknown #7579 Title unavailable Unclear · Unknown #7805 Title unavailable Unclear · Unknown #9319 Title unavailable Unclear · Unknown #9326 Title unavailable Unclear · Unknown #10476 Title unavailable Unclear · Unknown #15025 Title unavailable Unclear · Unknown | Standalone change | ## What & Why Registers the `gjc` CLI ([Gajae Code](https://gajae-code.com), npm [`gajae-code`](https://www.npmjs.com/package/gajae-code)) as a supported TUI agent, following the Trae/Prime Agent registration pattern. ** | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +131/−62. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Gajae Code to the built-in agent registry1 PR · Standalone · Plugins#
Problem: add Gajae Code to the built-in agent registry.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8451 Title unavailable (Unclear, Unknown); #13952 Title unavailable (Unclear, Unknown); #7805 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15025 feat(agents): add Gajae Code to the built-in agent registry | Bellman Community · FIRST_TIME_CONTRIBUTOR | #8451 Title unavailable Unclear · Unknown #13952 Title unavailable Unclear · Unknown #7805 Title unavailable Unclear · Unknown | Standalone change | ## What this adds [Gajae Code](https://github.com/Yeachan-Heo/gajae-code) (`gjc`) as a built-in agent: it shows up in the agent combobox, agent settings, auto-pick order, tab/status icons, and telemetry — no custom-comma | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +371/−288. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add generic Custom AI Provider usage tracking1 PR · Standalone · Plugins#
Problem: add generic Custom AI Provider usage tracking.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9239 [Feature]: Custom-endpoint (Anthropic-compatible) accounts in AI Provider Accounts (Fixes, OPEN); #16531 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16224 feat: add generic Custom AI Provider usage tracking | Seungjae Jay Lee Community · FIRST_TIME_CONTRIBUTOR | #9239 [Feature]: Custom-endpoint (Anthropic-compatible) accounts in AI Provider Accounts Fixes · OPEN #16531 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca already shows Claude/Codex/Gemini/etc. usage % in the status bar. This adds a "Custom Providers" section so anyone can point Orca at their own internal or corporate usage-tracking API and get the same status | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk44 files, +2757/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Google Gemini & Antigravity token and cost usage tracking1 PR · Standalone · Plugins#
Problem: add Google Gemini & Antigravity token and cost usage tracking.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16647 feat(stats): add Google Gemini & Antigravity token and cost usage tracking | Nguyễn Minh Chiến Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Adds Token and Cost Usage Tracking for Google Gemini CLI and Google Antigravity to Orca's "Stats & Usage" panel, enabling developers to monitor token consumption (input, cached input, output, reasoning), estimate | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk54 files, +3730/−94. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add graph cost report1 PR · Standalone · Plugins#
Problem: add graph cost report.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12125 feat(orchestration): add graph cost report | Ramiro Carnicer Souble Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - add a read-only orca orchestration report --id <run_id> [--json] path over the live runtime database and current structured provider usage snapshots - correlate Run, parent and child Tasks, Dispatch attempts | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk53 files, +4276/−51. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Huly task provider integration1 PR · Standalone · Plugins#
Problem: add Huly task provider integration.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14054 feat(huly): add Huly task provider integrationDraft | Aarav Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Wires Huly as a first-class task provider end-to-end, mirroring the pattern used for Linear/Jira, and surfaces it in the Onboarding Checklist alongside the other integrations. ### Shared types & registry - `Hu | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk75 files, +7359/−112. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add IBM Bob agent support (Bob Shell 2.x)1 PR · Standalone · Plugins#
Problem: add IBM Bob agent support (Bob Shell 2.x).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7691 [Feature]: Add first-class support for IBM Bob / Bob Shell (Fixes, OPEN); #7698 Title unavailable (Unclear, Unknown); #15935 Title unavailable (Unclear, Unknown); #15936 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14895 feat: add IBM Bob agent support (Bob Shell 2.x) | trs-80 Community · FIRST_TIME_CONTRIBUTOR | #7691 [Feature]: Add first-class support for IBM Bob / Bob Shell Fixes · OPEN #7698 Title unavailable Unclear · Unknown #15935 Title unavailable Unclear · Unknown #15936 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Adds IBM Bob (Bob Shell) as a selectable Orca agent, targeting the current Bob Shell 2.x CLI. ## What Changed Rebase of #7698 (by @kiyeonjeon21) onto current main, plus a retarget from the Bob Shell 1.0.6 CLI it | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk45 files, +952/−74. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add inline text color formatting1 PR · Standalone · Plugins#
Problem: add inline text color formatting.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16250 feat(markdown): add inline text color formatting | Daixinyu Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Users can select text in the Markdown editor and apply a color from a small formatting palette, similar to document editors such as Feishu. ## What Changed - Added inline text color formatting to the rich Markdow | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1178/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add intermediate Auto permission mode across supported harnesses1 PR · Standalone · Plugins#
Problem: add intermediate Auto permission mode across supported harnesses.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13081 [Feature]: Support the intermediate permission modes — Claude Code "Auto" mode and Codex "Approve for me" (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13348 feat(agents): add intermediate Auto permission mode across supported harnesses | Dr. Vital Araújo Community · FIRST_TIME_CONTRIBUTOR | #13081 [Feature]: Support the intermediate permission modes — Claude Code "Auto" mode and Codex "Approve for me" Fixes · OPEN | Standalone change | ## What Adds an intermediate **Auto** agent-permission preset between Manual and Yolo. Closes #13081. Today the global preset is binary: Manual (approve everything) or Yolo (fully permissive flags such as <code>--dangero | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +1182/−203. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add JetBrains Junie as a supported agent1 PR · Standalone · Plugins#
Problem: add JetBrains Junie as a supported agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16471 Add JetBrains Junie as a supported agent (Fixes, OPEN); #11549 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16472 feat(junie): add JetBrains Junie as a supported agent | Alexander Prendota Community · FIRST_TIME_CONTRIBUTOR | #16471 Add JetBrains Junie as a supported agent Fixes · OPEN #11549 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can now launch JetBrains' Junie CLI the same way it launches Codex or Devin: it starts Junie's own terminal UI, watches what Junie is doing so the sidebar shows working / waiting / done, can resume a Junie c | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk97 files, +2364/−232. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Jira as a mobile task provider1 PR · Standalone · Plugins#
Problem: add Jira as a mobile task provider.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10950 Title unavailable (Unclear, Unknown); #11121 Title unavailable (Unclear, Unknown); #14512 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13126 feat(tasks): add Jira as a mobile task provider | Minho Yi Community · FIRST_TIME_CONTRIBUTOR | #10950 Title unavailable Unclear · Unknown #11121 Title unavailable Unclear · Unknown #14512 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Your phone can already browse GitHub, GitLab, and Linear tasks. It could not browse Jira, even though the desktop app has had Jira for a while. Now it can — list your issues, search them, open one, and start a wo | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +1866/−541. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Kimchi agent support1 PR · Standalone · Plugins#
Problem: add Kimchi agent support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15917 Agent integration missing: Kimchi coding agent CLI (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15922 feat(agents): add Kimchi agent support | Vilius Community · FIRST_TIME_CONTRIBUTOR | #15917 Agent integration missing: Kimchi coding agent CLI Fixes · OPEN | Standalone change | ## ELI5 Orca now recognizes the Kimchi coding-agent CLI the same way it already recognizes Claude Code, Codex, pi, OMP, etc.: it detects Kimchi panes, derives their titles and status for the sidebar/titlebar, installs Or | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk51 files, +948/−238. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add live appearance previews and backgrounds1 PR · Standalone · Plugins#
Problem: add live appearance previews and backgrounds.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15524 Appearance settings need live previews and per-area backgrounds (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15525 feat(settings): add live appearance previews and backgrounds | Sylen Community · FIRST_TIME_CONTRIBUTOR | #15524 Appearance settings need live previews and per-area backgrounds Fixes · OPEN | Standalone change | ## ELI5 Appearance settings now work like a safe draft: changes appear immediately in a fixed preview, can be saved or discarded, and the terminal plus both sidebars can each use their own background image and effects. # | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk85 files, +7071/−386. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add local Paperclip task source1 PR · Standalone · Plugins#
Problem: add local Paperclip task source.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17197 [Feature]: Add Paperclip as a read-only task source (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17251 feat: add local Paperclip task sourceDraft | LorenzoTTGT Community · FIRST_TIME_CONTRIBUTOR | #17197 [Feature]: Add Paperclip as a read-only task source Fixes · OPEN | Standalone change | ## ELI5 Adds Paperclip beside Linear and Jira in Orca’s Tasks area. A user running Paperclip locally can connect a company/project, browse issues, and open a linked Orca workspace without letting Orca claim or modify the | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk82 files, +2496/−127. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add local terminal bridge stream1 PR · Standalone · Plugins#
Problem: add local terminal bridge stream.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13127 feat(cli): add local terminal bridge stream | John Bindel Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds an authenticated local terminal streaming bridge for external tools: ```text orca terminal bridge --terminal <handle> --json ``` The command streams existing `terminal.subscribe` events as bounded NDJSON | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +2040/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add managed credential profiles1 PR · Standalone · Plugins#
Problem: add managed credential profiles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13274 Title unavailable (Unclear, Unknown); #13273 Title unavailable (Unclear, Unknown); #13272 Title unavailable (Unclear, Unknown); #13271 Title unavailable (Unclear, Unknown); #13270 Title unavailable (Unclear, Unknown); #13183 Title unavailable (Unclear, Unknown); #13276 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13275 feat(command-code): add managed credential profiles | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13274 Title unavailable Unclear · Unknown #13273 Title unavailable Unclear · Unknown #13272 Title unavailable Unclear · Unknown #13271 Title unavailable Unclear · Unknown #13270 Title unavailable Unclear · Unknown #13183 Title unavailable Unclear · Unknown #13276 Title unavailable Unclear · Unknown | Standalone change | ## Summary Orca can now manage isolated Command Code credential profiles by importing only `auth.json` from a user-selected Command Code home into an owner-marked private store. Main validates a bounded regular JSON file | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk137 files, +7199/−477. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add managed Grok and Gemini homes1 PR · Standalone · Plugins#
Problem: add managed Grok and Gemini homes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13275 Title unavailable (Unclear, Unknown); #13274 Title unavailable (Unclear, Unknown); #13273 Title unavailable (Unclear, Unknown); #13272 Title unavailable (Unclear, Unknown); #13271 Title unavailable (Unclear, Unknown); #13270 Title unavailable (Unclear, Unknown); #13183 Title unavailable (Unclear, Unknown); #6963 Title unavailable (Unclear, Unknown); #6921 Title unavailable (Unclear, Unknown); #9496 Title unavailable (Unclear, Unknown); #14447 Title unavailable (Unclear, Unknown); #14476 Title unavailable (Unclear, Unknown); #14728 Title unavailable (Unclear, Unknown); #14608 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13276 feat(accounts): add managed Grok and Gemini homes | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13275 Title unavailable Unclear · Unknown #13274 Title unavailable Unclear · Unknown #13273 Title unavailable Unclear · Unknown #13272 Title unavailable Unclear · Unknown #13271 Title unavailable Unclear · Unknown #13270 Title unavailable Unclear · Unknown #13183 Title unavailable Unclear · Unknown #6963 Title unavailable Unclear · Unknown #6921 Title unavailable Unclear · Unknown #9496 Title unavailable Unclear · Unknown #14447 Title unavailable Unclear · Unknown #14476 Title unavailable Unclear · Unknown #14728 Title unavailable Unclear · Unknown #14608 Title unavailable Unclear · Unknown | Standalone change | ## Summary Add isolated managed-account homes for Grok Build and Gemini CLI using each CLI's documented home override: - Grok: `GROK_HOME` - Gemini: `GEMINI_CLI_HOME` Users can import an existing signed-in CLI home, assi | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk167 files, +10011/−493. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add MiniMax Code as a supported TUI agent1 PR · Standalone · Plugins#
Problem: add MiniMax Code as a supported TUI agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14051 [Feature]: Support MiniMax Code as a first-class TUI agent (Fixes, OPEN); #6239 Title unavailable (Unclear, Unknown); #12935 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14886 feat(agents): add MiniMax Code as a supported TUI agent | DanielWalnut Community · FIRST_TIME_CONTRIBUTOR | #14051 [Feature]: Support MiniMax Code as a first-class TUI agent Fixes · OPEN #6239 Title unavailable Unclear · Unknown #12935 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can now find, launch, label, and display MiniMax Code (`mcode`) like its other first-class terminal agents on desktop and mobile. ## What Changed - Added `minimax-code` to the shared TUI agent contract, desk | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk36 files, +268/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Monokai and explicit light/dark color theme options1 PR · Standalone · Plugins#
Problem: add Monokai and explicit light/dark color theme options.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14038 feat(editor): add Monokai and explicit light/dark color theme options | Martin DUBOIS Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem The Monaco-based file/diff editor is hardcoded to `isDark ? 'vs-dark' : 'vs'` — there's no way to pick an explicit editor color theme independent of the app's light/dark mode. This is inconsistent with the ter | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk62 files, +2810/−119. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add My GitHub panel — sign in, browse, clone, and clean up your own repos1 PR · Standalone · Plugins#
Problem: add My GitHub panel — sign in, browse, clone, and clean up your own repos.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17180 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17190 feat(github): add My GitHub panel — sign in, browse, clone, and clean up your own reposDraft | BayesWang Community · FIRST_TIME_CONTRIBUTOR | #17180 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Adds a "My GitHub" panel to the sidebar (between Tasks and Automations) where you sign in to your own GitHub account with Device Flow (no PAT copy-paste), browse your own repos — recent and private included — and | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk49 files, +2959/−210. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add New Group button and group selector in add-project dialog1 PR · Standalone · Plugins#
Problem: add New Group button and group selector in add-project dialog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15765 feat(sidebar): add New Group button and group selector in add-project dialog | Jose Meira Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Groups existed in Orca but you could only create one through the right-click context menu — and only by grouping two existing projects together. If you had projects loaded and just wanted a new empty group, there | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +240/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add OCaml and MLX syntax highlighting1 PR · Standalone · Plugins#
Problem: add OCaml and MLX syntax highlighting.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16416 [Feature]: Support syntax highlighting for OCaml (.ml/.mli/.mlx) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16421 feat(editor): add OCaml and MLX syntax highlighting | Rusty Key Community · FIRST_TIME_CONTRIBUTOR | #16416 [Feature]: Support syntax highlighting for OCaml (.ml/.mli/.mlx) Fixes · OPEN | Standalone change | ## ELI5 Orca's editor treats OCaml (`.ml`, `.mli`, `.ocamlinit`) and MLX (`.mlx`, OCaml with JSX) files as plain text. This adds syntax highlighting for both. ## What Changed - Registered `ocaml` and `ocaml.mlx` as Monac | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +2439/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add OpenCode native chat support1 PR · Standalone · Plugins#
Problem: add OpenCode native chat support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13287 feat: add OpenCode native chat support | Adnan Khan Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - add OpenCode SQLite transcript mapping for text, reasoning, tool, and patch parts - add live reconciliation for in-place streaming mutations - wire OpenCode into desktop and mobile native-chat eligibility an | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk70 files, +3750/−208. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add opencode2 (v2 beta) support1 PR · Standalone · Plugins#
Problem: add opencode2 (v2 beta) support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14025 [Feature]: Add support for opencode2 (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14053 feat(agents): add opencode2 (v2 beta) support | Xiro The Dev Community · FIRST_TIME_CONTRIBUTOR | #14025 [Feature]: Add support for opencode2 Fixes · OPEN | Standalone change | ## Summary Closes #14025 — adds native support for **opencode2** (the v2 beta of the opencode CLI, installed as its own `opencode2` binary side-by-side with v1). ## What's included - **Launch + detection**: `opencode2` a | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk54 files, +2405/−42. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add opt-in auto-submit for work item Start1 PR · Standalone · Plugins#
Problem: add opt-in auto-submit for work item Start.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7360 [Feature]: Auto-submit the prefilled prompt when starting work from an issue (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16864 feat(tasks): add opt-in auto-submit for work item Start | salvadorgu7 Community · FIRST_TIME_CONTRIBUTOR | #7360 [Feature]: Auto-submit the prefilled prompt when starting work from an issue Fixes · OPEN | Standalone change | Closes #7360 ## Summary - Adds a persisted **Work item Start behavior** setting with `draft` and `submit-after-ready`; missing/invalid values continue to resolve to `draft`. - Makes the canonical Project **Start** and Is | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +735/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add orca skills remove for headless uninstall1 PR · Standalone · Plugins#
Problem: add orca skills remove for headless uninstall.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13099 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13170 feat(cli): add orca skills remove for headless uninstall | BingZ Community · CONTRIBUTOR | #13099 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Headless hosts could install and update bundled skills via `orca skills install` / `update`, but had no matching uninstall path (#13099 lifecycle gap). - Add `orca skills remove` that resolves to the same `n | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +331/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add pure black dark variant1 PR · Standalone · Plugins#
Problem: add pure black dark variant.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16725 [Feature]: Add a pure black (OLED) dark appearance option (Fixes, OPEN); #0 Title unavailable (Unclear, Unknown); #171717 Title unavailable (Unclear, Unknown); #262626 Title unavailable (Unclear, Unknown); #404040 Title unavailable (Unclear, Unknown); #141414 Title unavailable (Unclear, Unknown); #232323 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16727 feat(appearance): add pure black dark variant | Lance Ranara Community · FIRST_TIME_CONTRIBUTOR | #16725 [Feature]: Add a pure black (OLED) dark appearance option Fixes · OPEN #0 Title unavailable Unclear · Unknown #171717 Title unavailable Unclear · Unknown #262626 Title unavailable Unclear · Unknown #404040 Title unavailable Unclear · Unknown #141414 Title unavailable Unclear · Unknown #232323 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca's dark mode isn't actually black — it's a stack of dark grays. On OLED and AMOLED screens, gray pixels stay lit, so the app looks washed out and burns more power than it needs to. This adds a **Pure Black** | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +570/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Qoder CLI (qodercli) as a supported TuiAgent1 PR · Standalone · Plugins#
Problem: add Qoder CLI (qodercli) as a supported TuiAgent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15291 feat: add Qoder CLI (qodercli) as a supported TuiAgent | ZheNing Hu Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Add first-class support for [Qoder CLI](https://www.qoder.com/) as an Orca `TuiAgent`. ### What's included **Core agent support (`src/shared/`)** - `TuiAgent` union + `TUI_AGENT_CONFIG` with `qodercli` detecti | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +632/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Qoder CLI (qodercli/qoderclicn) agents and supervised-hook registration for Qwen Code1 PR · Standalone · Plugins#
Problem: add Qoder CLI (qodercli/qoderclicn) agents and supervised-hook registration for Qwen Code.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12738 [Feature]: Supervised-agent registration for Qwen Code + add Qoder CLI (qodercli / qoderclicn) as orchestratable agents (Fixes, OPEN); #12279 Title unavailable (Unclear, Unknown); #7480 Title unavailable (Unclear, Unknown); #7253 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12910 feat: add Qoder CLI (qodercli/qoderclicn) agents and supervised-hook registration for Qwen Code | jyang2004 Community · FIRST_TIME_CONTRIBUTOR | #12738 [Feature]: Supervised-agent registration for Qwen Code + add Qoder CLI (qodercli / qoderclicn) as orchestratable agents Fixes · OPEN #12279 Title unavailable Unclear · Unknown #7480 Title unavailable Unclear · Unknown #7253 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes #12738 · refs #12279, #7480 Orca could launch **Qwen Code** and assign tasks to it manually, but orchestrator-driven supervised dispatch failed because `qwen-code` has a `TuiAgent` registration yet no ** | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +214/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Qoder CLI as a supported TUI agent1 PR · Standalone · Plugins#
Problem: add Qoder CLI as a supported TUI agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7253 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13311 feat(agents): add Qoder CLI as a supported TUI agent | chencheng (云谦) Community · FIRST_TIME_CONTRIBUTOR | #7253 Title unavailable Unclear · Unknown | Standalone change | <img width="466" height="296" alt="Orca: main 2026-08-09 15 03 16" src="https://github.com/user-attachments/assets/d4331557-ca22-45ee-85d7-9bef9cc60975" /> ## Summary Adds Qoder CLI (`@qoder-ai/qodercli`, binary `qodercl | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk44 files, +599/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add read-only Amphetamine session integration on macOS1 PR · Standalone · Plugins#
Problem: add read-only Amphetamine session integration on macOS.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15932 feat(awake): add read-only Amphetamine session integration on macOS | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 19 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk50 files, +4315/−172. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add reasonix TUI agent provider1 PR · Standalone · Plugins#
Problem: add reasonix TUI agent provider.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12330 feat(agents): add reasonix TUI agent provider | BobcGn Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds **reasonix** (npm-installed terminal coding agent, `reasonix@1.19.4`) as a launchable TUI agent provider in Orca. reasonix installs via `npm install -g reasonix` and runs as a terminal TUI (`reasonix`), m | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +41/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add rich input composer1 PR · Standalone · Plugins#
Problem: add rich input composer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9227 Title unavailable (Unclear, Unknown); #6034 Title unavailable (Unclear, Unknown); #7084 Title unavailable (Unclear, Unknown); #7425 Title unavailable (Unclear, Unknown); #11706 Title unavailable (Unclear, Unknown); #15875 Title unavailable (Unclear, Unknown); #14728 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12932 feat(terminal): add rich input composer | gatsby74 Community · CONTRIBUTOR | #9227 Title unavailable Unclear · Unknown #6034 Title unavailable Unclear · Unknown #7084 Title unavailable Unclear · Unknown #7425 Title unavailable Unclear · Unknown #11706 Title unavailable Unclear · Unknown #15875 Title unavailable Unclear · Unknown #14728 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Writing long prompts straight into a terminal is clumsy: pressing Enter sends each line immediately, pasting images is unreliable, and referencing files means typing exact paths. This adds an optional rich text b | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk118 files, +7488/−245. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Russian (ru) UI language support1 PR · Standalone · Plugins#
Problem: add Russian (ru) UI language support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16736 feat(i18n): add Russian (ru) UI language support | AlexZander85 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Orca can now be switched into Russian. "Russian" (`ru`) is added as a built-in interface language exactly like the existing Chinese, Korean, Japanese, and Spanish locales. Where the translation doesn't cover a ke | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +8261/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Add sequencer continue/skip actions and branch identity display1 PR · Standalone · Plugins#
Problem: Add sequencer continue/skip actions and branch identity display.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15382 Add sequencer continue/skip actions and branch identity display | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 33 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk94 files, +3335/−364. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add setting to skip WSL distros in session history scan2 PRs · Overlapping · Plugins#
Problem: add setting to skip WSL distros in session history scan.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16959 [Feature]: Setting to keep Agent Session History from booting WSL distros (Fixes, OPEN); #16961 Title unavailable (Unclear, Unknown); #15475 Title unavailable (Unclear, Unknown); #16050 Title unavailable (Unclear, Unknown); #16038 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16961 feat(ai-vault): add setting to skip WSL distros in session history scan | Crockyia Community · FIRST_TIME_CONTRIBUTOR | #16959 [Feature]: Setting to keep Agent Session History from booting WSL distros Fixes · OPEN | Cluster contribution | ## ELI5 On Windows, Orca's session history looks inside every WSL distro for agent transcripts. Finding a distro's home folder means starting that distro, so Orca quietly boots WSL (about 1.3 GB of RAM) every few minutes | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +496/−77. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17072 fix(wsl): scan agent sessions only in running distros | OrcaWin Unknown · COLLABORATOR | #16959 [Feature]: Setting to keep Agent Session History from booting WSL distros Fixes · OPEN #16961 Title unavailable Unclear · Unknown #15475 Title unavailable Unclear · Unknown #16050 Title unavailable Unclear · Unknown #16038 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 14 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +1276/−211. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add shell history opt-out1 PR · Standalone · Plugins#
Problem: add shell history opt-out.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16048 [Feature]: Add a per-worktree shell history opt-out to Terminal Settings (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16071 feat(settings): add shell history opt-out | Mir Community · FIRST_TIME_CONTRIBUTOR | #16048 [Feature]: Add a per-worktree shell history opt-out to Terminal Settings Fixes · OPEN | Standalone change | ## ELI5 Users can now turn off Orca's workspace-scoped shell history from Terminal Settings instead of editing the internal profile JSON. ## What Changed - Added a searchable shell-history opt-out as a compact row under | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +416/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Shortcut task provider1 PR · Standalone · Plugins#
Problem: add Shortcut task provider.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16248 feat(tasks): add a native Shortcut (shortcut.com) task provider (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16249 feat(tasks): add Shortcut task provider | Sergio Zamarro Community · FIRST_TIME_CONTRIBUTOR | #16248 feat(tasks): add a native Shortcut (shortcut.com) task provider Fixes · OPEN | Standalone change | ## ELI5 If your team tracks work in Shortcut (shortcut.com), Orca's Tasks page can now show your stories. You paste one API token, and Orca lists your assigned/requested stories, lets you search, edit, comment, create ne | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk105 files, +8034/−106. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Show Whitespace toggle option in diff viewer1 PR · Standalone · Plugins#
Problem: add Show Whitespace toggle option in diff viewer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15118 [Feature]: Add option to show whitespace changes in diff viewer (Show Whitespace) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15120 feat(editor): add Show Whitespace toggle option in diff viewer | hwantage Community · CONTRIBUTOR | #15118 [Feature]: Add option to show whitespace changes in diff viewer (Show Whitespace) Fixes · OPEN | Standalone change | ## ELI5 When reviewing diffs that only contain indentation or whitespace changes, Orca previously hid those differences by default with no way to reveal them or jump between changed lines. This PR adds a **"Show Whitespa | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +63/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add spatial pane focus1 PR · Standalone · Plugins#
Problem: add spatial pane focus.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8263 Title unavailable (Unclear, Unknown); #13984 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15068 feat(terminal): add spatial pane focus | since20I8 Community · FIRST_TIME_CONTRIBUTOR | #8263 Title unavailable Unclear · Unknown #13984 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Split terminals can now move focus in the direction you press — left, right, up, or down — instead of only cycling “next / previous” in the order the panes were created. If nothing is next to you in that directio | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +868/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add worker-start --spec to create and dispatch in one call1 PR · Standalone · Plugins#
Problem: add worker-start --spec to create and dispatch in one call.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13360 [Feature]: worker-start --spec — create the task and dispatch it in one call (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13540 feat(orchestration): add worker-start --spec to create and dispatch in one call | Jooyoung Shin Community · FIRST_TIME_CONTRIBUTOR | #13360 [Feature]: worker-start --spec — create the task and dispatch it in one call Fixes · OPEN | Standalone change | ## Summary Adds `--spec` (and optional `--task-title`) to `orca orchestration worker-start`, so a supervised worker can be created and dispatched in one call instead of the two-mutation `task-create` → `worker-start` id- | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +919/−101. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add ZCode as a first-class supported agent1 PR · Standalone · Plugins#
Problem: add ZCode as a first-class supported agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10564 Feature: Add ZCode (Z.ai / GLM-5.2) as a first-class supported agent (Fixes, OPEN); #10654 Title unavailable (Unclear, Unknown); #14556 Title unavailable (Unclear, Unknown); #16227 Title unavailable (Unclear, Unknown); #16228 Title unavailable (Unclear, Unknown); #14001 Title unavailable (Unclear, Unknown); #16187 Title unavailable (Unclear, Unknown); #16181 Title unavailable (Unclear, Unknown); #16201 Title unavailable (Unclear, Unknown); #2284 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13965 feat(agents): add ZCode as a first-class supported agent | GuanBear Community · FIRST_TIME_CONTRIBUTOR | #10564 Feature: Add ZCode (Z.ai / GLM-5.2) as a first-class supported agent Fixes · OPEN #10654 Title unavailable Unclear · Unknown #14556 Title unavailable Unclear · Unknown #16227 Title unavailable Unclear · Unknown #16228 Title unavailable Unclear · Unknown #14001 Title unavailable Unclear · Unknown #16187 Title unavailable Unclear · Unknown #16181 Title unavailable Unclear · Unknown #16201 Title unavailable Unclear · Unknown #2284 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds ZCode to Orca's first-class agent contract: catalog selection, launch settings, process recognition, managed hooks, normalized lifecycle status, SSH hook installation, mobile/web labels, and telemetry. Th | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk56 files, +1041/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add ZeroClaw agent connector and AI Vault scanner1 PR · Standalone · Plugins#
Problem: add ZeroClaw agent connector and AI Vault scanner.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16597 feat(agent): add ZeroClaw agent connector and AI Vault scanner | Aleksei Tcelishchev Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Adds first-class support for ZeroClaw (`zeroclaw`), an ultra-lightweight Rust-based autonomous agent runtime. Users can launch ZeroClaw from the agent palette, discover active/past ZeroClaw sessions in AI Vault w | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk43 files, +585/−308. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1address-bar convergence — previews and browser tabs convert in place (STA-5681)1 PR · Standalone · Plugins#
Problem: address-bar convergence — previews and browser tabs convert in place (STA-5681).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16920 Title unavailable (Unclear, Unknown); #16679 Title unavailable (Unclear, Unknown); #16921 Title unavailable (Unclear, Unknown); #16975 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16998 feat(browser): address-bar convergence — previews and browser tabs convert in place (STA-5681) | Jinwoo Hong Core team · MEMBER | #16920 Title unavailable Unclear · Unknown #16679 Title unavailable Unclear · Unknown #16921 Title unavailable Unclear · Unknown #16975 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 18 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk56 files, +3323/−409. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1agent context panel — instruction files, skills, MCP, hooks and plugins per workspace1 PR · Standalone · Plugins#
Problem: agent context panel — instruction files, skills, MCP, hooks and plugins per workspace.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14874 [Feature]: Agent context panel — which instruction files, skills, MCP servers, hooks and plugins are active for a workspace, per agent (Fixes, OPEN); #13601 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14875 feat(right-sidebar): agent context panel — instruction files, skills, MCP, hooks and plugins per workspace | smanaton Community · FIRST_TIME_CONTRIBUTOR | #14874 [Feature]: Agent context panel — which instruction files, skills, MCP servers, hooks and plugins are active for a workspace, per agent Fixes · OPEN #13601 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A new **Agent context** tab in the right sidebar shows, for the workspace you have open, everything the coding agents will load when they start: which `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` / Cursor / Copilot in | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk46 files, +4586/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1allow language packs to declare a native display name1 PR · Standalone · Plugins#
Problem: allow language packs to declare a native display name.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13031 [Feature]: Let plugin language packs declare a native display name for the language picker (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13140 feat(plugins): allow language packs to declare a native display name | BingZ Community · CONTRIBUTOR | #13031 [Feature]: Let plugin language packs declare a native display name for the language picker Fixes · OPEN | Standalone change | ## Summary - Optional `displayName` on `languagePacks` contributions (trimmed, 1–80 chars). - Registry forwards it onto `PluginLanguagePackRegistration`. - Appearance language picker uses `displayName` when present; othe | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +100/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1app chrome can match terminal theme; configurable status-bar usage format1 PR · Standalone · Plugins#
Problem: app chrome can match terminal theme; configurable status-bar usage format.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16936 [Feature]: App chrome (tab bar, status bar, side panels) should be able to match the terminal theme (Fixes, OPEN); #16937 [Feature]: Configurable status bar usage format (template with placeholders) (Fixes, OPEN); #17199 [Bug]: File editors (Monaco, Markdown preview, plain text) ignore App Chrome "Match Terminal" and keep the stock app theme (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16768 feat(appearance): app chrome can match terminal theme; configurable status-bar usage format | seedotlee Community · FIRST_TIME_CONTRIBUTOR | #16936 [Feature]: App chrome (tab bar, status bar, side panels) should be able to match the terminal theme Fixes · OPEN #16937 [Feature]: Configurable status bar usage format (template with placeholders) Fixes · OPEN #17199 [Bug]: File editors (Monaco, Markdown preview, plain text) ignore App Chrome "Match Terminal" and keep the stock app theme Fixes · OPEN | Standalone change | ## ELI5 Two appearance settings: (1) the whole app frame (tab strip, status bar, side panels, popovers) can adopt the terminal theme's colors instead of the app theme, and (2) the status bar's usage text can be formatted | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk52 files, +1914/−216. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1apply client page reconciliation1 PR · Standalone · Plugins#
Problem: apply client page reconciliation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14759 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14763 feat(browser): apply client page reconciliationDraft | Jinwoo Hong Core team · MEMBER | #14759 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +2145/−250. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1auto-generate titles for the panes in a split tab1 PR · Standalone · Plugins#
Problem: auto-generate titles for the panes in a split tab.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15780 [Feature]: Auto-generate terminal titles, so the panes in a split tab say what each session is doing (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15781 feat(terminal): auto-generate titles for the panes in a split tab | Ramzi Community · CONTRIBUTOR | #15780 [Feature]: Auto-generate terminal titles, so the panes in a split tab say what each session is doing Fixes · OPEN | Standalone change | ## ELI5 Orca can already name a **tab** after what the agent is doing. It cannot name the **terminals inside** it. Split a tab into four panes and you get four identical black rectangles, and the only way to tell them ap | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +337/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1background image behind terminal panes (#7714)1 PR · Standalone · Plugins#
Problem: background image behind terminal panes (#7714).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7714 [Feature]: Feature Request: Support custom background images in the IDE (Fixes, OPEN); #15524 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15836 feat(terminal): background image behind terminal panes (#7714) | cunicopia Community · FIRST_TIME_CONTRIBUTOR | #7714 [Feature]: Feature Request: Support custom background images in the IDE Fixes · OPEN #15524 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You can now pick a picture and Orca draws it faintly behind every terminal pane — like a wallpaper for your terminals. Opacity and fit are adjustable, and removing it puts everything back exactly how it was. ## W | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +730/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1block-clone shared paths on ReFS1 PR · Standalone · Plugins#
Problem: block-clone shared paths on ReFS.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16618 [Feature]: Use ReFS block cloning for Windows worktree shared paths (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16619 feat(windows): block-clone shared paths on ReFS | Chikage0o0 Community · FIRST_TIME_CONTRIBUTOR | #16618 [Feature]: Use ReFS block cloning for Windows worktree shared paths Fixes · OPEN | Standalone change | ## ELI5 On Windows ReFS, Orca can now create independent Worktree Shared Paths by reusing the source file's existing disk blocks instead of copying every byte. If the paths are not on the same ReFS volume, Orca keeps the | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1100/−77. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bound page reconciliation execution1 PR · Standalone · Plugins#
Problem: bound page reconciliation execution.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14754 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14756 feat(browser): bound page reconciliation executionDraft | Jinwoo Hong Core team · MEMBER | #14754 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +620/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bound producer pause so a lost renderer ACK cannot wedge a PTY1 PR · Standalone · Plugins#
Problem: bound producer pause so a lost renderer ACK cannot wedge a PTY.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12283 [Bug]: Pi agent pane appears frozen at 'working' with no streamed output during long responses (Windows) (Fixes, OPEN); #11178 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17216 fix(terminal): bound producer pause so a lost renderer ACK cannot wedge a PTY | lertian Community · FIRST_TIME_CONTRIBUTOR | #12283 [Bug]: Pi agent pane appears frozen at 'working' with no streamed output during long responses (Windows) Fixes · OPEN #11178 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When a terminal pane produces output faster than the UI can draw it, Orca tells the OS to stop reading that terminal so the program inside blocks and stops flooding. It undoes that once the backlog drains. The pr | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +151/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bound the custom sound's dedupe window so a stalled element cannot silence every later notif2 PRs · Overlapping · Automated release pipeline#
Problem: bound the custom sound's dedupe window so a stalled element cannot silence every later notif.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #15933 [Bug]: Completion notifications intermittently play no sound (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15938 fix(notifications): bound the custom sound's dedupe window so a stalled element cannot silence every later notification | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15933 [Bug]: Completion notifications intermittently play no sound Fixes · OPEN | Cluster contribution | ## What The custom notification sound's dedupe window is now bounded in time. A small `createNotificationSoundPlayback` module (`src/preload/notification-sound-playback.ts`) owns the in-flight flag and releases it on **` | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +193/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15940 fix(notifications): replay completion sounds reliably | Chisa Kotegawa Community · FIRST_TIME_CONTRIBUTOR | #15933 [Bug]: Completion notifications intermittently play no sound Fixes · OPEN | Cluster contribution | ## ELI5 Orca could show two completion notifications close together but play only the first sound. The shared notification sound now restarts for every delivered notification, so later completions are not silently missed | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +117/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bounded host-aware Cursor sidecar history1 PR · Standalone · Plugins#
Problem: bounded host-aware Cursor sidecar history.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11514 perf(ai-vault): bound local and WSL Cursor sidecar discovery (Fixes, OPEN); #11370 Title unavailable (Unclear, Unknown); #11525 Title unavailable (Unclear, Unknown); #13617 Title unavailable (Unclear, Unknown); #14482 Title unavailable (Unclear, Unknown); #14616 Title unavailable (Unclear, Unknown); #13931 Title unavailable (Unclear, Unknown); #13935 Title unavailable (Unclear, Unknown); #12891 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14582 feat(ai-vault): bounded host-aware Cursor sidecar history | Brennan Benson Core team · MEMBER | #11514 perf(ai-vault): bound local and WSL Cursor sidecar discovery Fixes · OPEN #11370 Title unavailable Unclear · Unknown #11525 Title unavailable Unclear · Unknown #13617 Title unavailable Unclear · Unknown #14482 Title unavailable Unclear · Unknown #14616 Title unavailable Unclear · Unknown #13931 Title unavailable Unclear · Unknown #13935 Title unavailable Unclear · Unknown #12891 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 25 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk68 files, +7308/−159. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1carry sender liveness evidence in every Delivery1 PR · Standalone · Plugins#
Problem: carry sender liveness evidence in every Delivery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13761 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15272 feat(orchestration): carry sender liveness evidence in every Delivery | Taras Kornichuk Community · CONTRIBUTOR | #13761 Title unavailable Unclear · Unknown | Standalone change | ## What A coordinator woken by `orca orchestration check` had to spend an extra LLM turn calling `worker-show` and `terminal read` just to learn whether the sender of a message was still working — facts the runtime alrea | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +963/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Claude permission mode picker in the composer, and fix fast mode2 PRs · Overlapping · Automated release pipeline#
Problem: Claude permission mode picker in the composer, and fix fast mode.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #11548 [Feature] Plan mode in chat UI (Fixes, CLOSED); #14752 [Bug]: Chat UI fast mode toggle no longer applies — bare /fast opens a confirmation panel (Fixes, OPEN); #12576 Title unavailable (Unclear, Unknown); #13348 Title unavailable (Unclear, Unknown); #10111 Title unavailable (Unclear, Unknown); #13081 Title unavailable (Unclear, Unknown); #10886 Title unavailable (Unclear, Unknown); #14745 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14745 feat(native-chat): Claude permission mode picker in the composer, and fix fast mode | Jérémy Community · FIRST_TIME_CONTRIBUTOR | #11548 [Feature] Plan mode in chat UI Fixes · CLOSED #14752 [Bug]: Chat UI fast mode toggle no longer applies — bare /fast opens a confirmation panel Fixes · OPEN #12576 Title unavailable Unclear · Unknown #13348 Title unavailable Unclear · Unknown #10111 Title unavailable Unclear · Unknown #13081 Title unavailable Unclear · Unknown #10886 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Claude Code lets you change how much it's allowed to do on its own — ask me every time, auto-accept edits, plan without touching anything, and so on. In the terminal you switch that with Shift+Tab. In Orca's Chat | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk43 files, +2589/−399. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15681 fix(native-chat): set Claude fast mode with /fast on|off (STA-4428) | Brennan Benson Core team · MEMBER | #14752 [Bug]: Chat UI fast mode toggle no longer applies — bare /fast opens a confirmation panel Fixes · OPEN #14745 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +274/−237. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Codex structured chat — full migration (host runtime, journal, wire, desktop + mobile client1 PR · Standalone · Plugins#
Problem: Codex structured chat — full migration (host runtime, journal, wire, desktop + mobile client.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13416 Title unavailable (Unclear, Unknown); #13381 Title unavailable (Unclear, Unknown); #13394 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13438 feat(native-chat): Codex structured chat — full migration (host runtime, journal, wire, desktop + mobile clients) | Brennan Benson Core team · MEMBER | #13416 Title unavailable Unclear · Unknown #13381 Title unavailable Unclear · Unknown #13394 Title unavailable Unclear · Unknown | Standalone change | ## Summary This is stack part C2 and contains only the mobile write spine on top of C1 / #13416. It adds a persisted, kill-safe outbox with one in-flight dispatch, same-client-message-id retries, editable queued messages | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk475 files, +49415/−953. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Codex structured chat without TUI toggle1 PR · Standalone · Plugins#
Problem: Codex structured chat without TUI toggle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13438 Title unavailable (Unclear, Unknown); #14601 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14600 feat(native-chat): Codex structured chat without TUI toggle | Brennan Benson Core team · MEMBER | #13438 Title unavailable Unclear · Unknown #14601 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 206 | $\color{#1a7f37}{\Huge{\math | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk580 files, +56823/−1547. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1copy unresolved PR/MR comments prompt to clipboard1 PR · Standalone · Plugins#
Problem: copy unresolved PR/MR comments prompt to clipboard.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13701 feat(source-control): copy unresolved PR/MR comments prompt to clipboard | Gimics Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds a **"Copy prompt"** counterpart to the existing "Send unresolved PR comments" source-control action. The existing button builds a review-comment resolution prompt and launches it in a **new terminal + age | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +482/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1create subgroups and move groups from the group menu1 PR · Standalone · Plugins#
Problem: create subgroups and move groups from the group menu.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15802 feat(sidebar): create subgroups and move groups from the group menu | Eugenio Valeiras Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | Orca already models nested project groups (`ProjectGroup.parentGroupId`), renders them indented by depth, and the create IPC accepts a parent — but no user surface could build that hierarchy: the store only created root | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +1098/−52. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1create worktrees on a per-workspace environment recipe1 PR · Standalone · Plugins#
Problem: create worktrees on a per-workspace environment recipe.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #123 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17026 feat(cli): create worktrees on a per-workspace environment recipe | Agustin Aon Community · FIRST_TIME_CONTRIBUTOR | #123 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The app can already spin up a fresh VM for a workspace ("Run on"). Now the CLI can too, and deleting the workspace tears the VM down. ## What Changed `orca worktree create --recipe <id>` provisions the repo's `en | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +1313/−229. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1detach a terminal tab group into its own window1 PR · Standalone · Plugins#
Problem: detach a terminal tab group into its own window.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14997 feat(panes): detach a terminal tab group into its own window | Adelin Berard Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Terminal-only tab groups can move into separate Orca windows without creating a second renderer or terminal session. The main window and detached windows continue sharing one store and PTY lifecycle. ## What Chan | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk135 files, +4195/−600. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1detach live tabs into secondary windows1 PR · Standalone · Plugins#
Problem: detach live tabs into secondary windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7811 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16203 feat(terminal): detach live tabs into secondary windows | Chisa Kotegawa Community · FIRST_TIME_CONTRIBUTOR | #7811 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Drag a live terminal tab out of Orca to move it into its own window without restarting the terminal or losing its scrollback. Closing or promoting windows keeps the surviving terminals attached to the correct win | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk186 files, +21534/−1453. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1detect a wedged supervised worker and surface it as a signal1 PR · Standalone · Plugins#
Problem: detect a wedged supervised worker and surface it as a signal.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13762 Title unavailable (Unclear, Unknown); #14897 Title unavailable (Unclear, Unknown); #14979 Title unavailable (Unclear, Unknown); #14961 Title unavailable (Unclear, Unknown); #15274 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15273 feat(orchestration): detect a wedged supervised worker and surface it as a signal | Taras Kornichuk Community · CONTRIBUTOR | #13762 Title unavailable Unclear · Unknown #14897 Title unavailable Unclear · Unknown #14979 Title unavailable Unclear · Unknown #14961 Title unavailable Unclear · Unknown #15274 Title unavailable Unclear · Unknown | Standalone change | A supervised worker that hangs is indistinguishable from one that is thinking hard until the coordinator's own `check --wait` window expires — routinely 15 to 60 minutes of nothing. The runtime already receives turn-boun | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1984/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1durable session records and persisted single-writer lease (native-chat phase 1a)1 PR · Standalone · Plugins#
Problem: durable session records and persisted single-writer lease (native-chat phase 1a).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13084 feat(agent-session): durable session records and persisted single-writer lease (native-chat phase 1a) | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary No user-visible change. This is phase 1a of the native chat work: it lands the durable agent-session record and the persisted single-writer lease that later phases build on. Nothing constructs the store yet, s | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +4117/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1enforce finite worker lifecycles1 PR · Standalone · Plugins#
Problem: enforce finite worker lifecycles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13337 feat(orchestration): enforce finite worker lifecycles | henrynguyeninfo1 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - add atomic Run-level Dispatch budgets with immutable runtime, request, dispatch, and review ceilings - launch supervised workers as fresh leaf-only processes behind an app-independent process-tree watchdog - | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk87 files, +8035/−1258. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1enforce isolated worker authority1 PR · Standalone · Plugins#
Problem: enforce isolated worker authority.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16827 feat(orchestration): enforce isolated worker authority | Gaurang Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Give supervised Codex workers a disposable Docker boundary that can use a dedicated ChatGPT subscription session but cannot inherit the founder's GitHub, SSH, Docker, Orca, browser, plugin, connector, or home-dir | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk68 files, +4416/−147. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1expose deterministic manual queue rank1 PR · Standalone · Plugins#
Problem: expose deterministic manual queue rank.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16079 Expose deterministic Linear manual queue ranks to agents (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16080 feat(linear): expose deterministic manual queue rankDraft | Robert Joseph Wayne Community · FIRST_TIME_CONTRIBUTOR | #16079 Expose deterministic Linear manual queue ranks to agents Fixes · CLOSED | Standalone change | ## ELI5 Agents can now see the same manual queue order that people set in Linear, even when the matching issues span several Linear API pages. ## What Changed - Expose `Issue.sortOrder` in issue, MCP list, project issue, | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +319/−56. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1expose HTML browser action1 PR · Standalone · Plugins#
Problem: expose HTML browser action.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15839 feat(editor): expose HTML browser action | PeaceTis Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 HTML files still open as editable source, but the editor header now shows an explicit **Open in Orca Browser** button so the rendered page is easy to discover. ## What Changed - Replaced the ambiguous icon-only H | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +119/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1expose nested repository scan and import1 PR · Standalone · Plugins#
Problem: expose nested repository scan and import.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8766 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14514 feat(cli): expose nested repository scan and import | hugo Community · FIRST_TIME_CONTRIBUTOR | #8766 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Agents and scripts can now use the same nested-repository scan and import flow that the Orca desktop UI already uses for multi-repo folders. ## What Changed - Added `orca project-group scan-nested --path <folder> | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +456/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1expose workspace notes panel1 PR · Standalone · Plugins#
Problem: expose workspace notes panel.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6503 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13045 feat(sidebar): expose workspace notes panel | Victor Demonchy Community · FIRST_TIME_CONTRIBUTOR | #6503 Title unavailable Unclear · Unknown | Standalone change | ## Summary Implements the workspace note request from [#6503](https://github.com/stablyai/orca/issues/6503) as a built-in right-sidebar Notes panel. - Exposes the existing per-workspace Markdown comment through a discove | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +2804/−98. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1expose worktree --pr for linked GitHub pull requests1 PR · Standalone · Plugins#
Problem: expose worktree --pr for linked GitHub pull requests.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14908 feat(cli): expose worktree --pr for linked GitHub pull requests | s546126 Community · CONTRIBUTOR | None found | Standalone change | ## ELI5 You can already attach a GitHub issue to a worktree from the CLI with `--issue`. This adds the matching `--pr` flag so you can attach (or clear) an existing GitHub pull request the same way. ## What Changed - `or | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +350/−125. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Feat multi agent collabofeat(orchestration): migrate multi-agent collaboration to current ru1 PR · Standalone · Plugins#
Problem: Feat multi agent collabofeat(orchestration): migrate multi-agent collaboration to current ru.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16515 Feat multi agent collabofeat(orchestration): migrate multi-agent collaboration to current runtimeration v2 | user141514 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | # PR Description ## Summary Migrates the previous multi-agent/A2A collaboration work onto the current Orca main architecture and integrates it with the current Run / Task / Dispatch / worker lifecycle. This adds a topolo | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk65 files, +6277/−60. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Feat/orca canvas view and control room1 PR · Standalone · Plugins#
Problem: Feat/orca canvas view and control room.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16872 Feat/orca canvas view and control room | Tech0001 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Orca normally shows terminals inside one project at a time. This adds: - **Canvas** — arrange that project’s existing terminals as movable, resizable cards. - **Control Room** — see and supervise active agents an | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk58 files, +4180/−77. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1filter workspaces by card status2 PRs · Overlapping · Automated release pipeline#
Problem: filter workspaces by card status.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #13996 [Feature]: Filter sidebar workspaces by card status (Todo / In progress / In review / Done) (Fixes, OPEN); #11042 Title unavailable (Unclear, Unknown); #13971 Title unavailable (Unclear, Unknown); #13999 Title unavailable (Unclear, Unknown); #14465 Title unavailable (Unclear, Unknown); #14486 Title unavailable (Unclear, Unknown); #13847 Title unavailable (Unclear, Unknown); #13938 Title unavailable (Unclear, Unknown); #9708 Title unavailable (Unclear, Unknown); #14443 Title unavailable (Unclear, Unknown); #14467 Title unavailable (Unclear, Unknown); #15013 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13999 feat(sidebar): filter workspaces by card status | Yunqian Fan Community · CONTRIBUTOR | #13996 [Feature]: Filter sidebar workspaces by card status (Todo / In progress / In review / Done) Fixes · OPEN #11042 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 The sidebar can already **group** workspaces by status, but it couldn't **filter** by it — so grouping "by project" still showed every card no matter whether it was Todo, In progress, In review, or Done. This add | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +870/−54. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14633 feat(sidebar): filter the workspace list by card status (#13996) | Brennan Benson Core team · MEMBER | #13996 [Feature]: Filter sidebar workspaces by card status (Todo / In progress / In review / Done) Fixes · OPEN #11042 Title unavailable Unclear · Unknown #13971 Title unavailable Unclear · Unknown #13999 Title unavailable Unclear · Unknown #14465 Title unavailable Unclear · Unknown #14486 Title unavailable Unclear · Unknown #13847 Title unavailable Unclear · Unknown #13938 Title unavailable Unclear · Unknown #9708 Title unavailable Unclear · Unknown #14443 Title unavailable Unclear · Unknown #14467 Title unavailable Unclear · Unknown #15013 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +859/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1GLM Coding Plan usage visibility1 PR · Standalone · Plugins#
Problem: GLM Coding Plan usage visibility.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7569 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16772 feat(status-bar): GLM Coding Plan usage visibility | Delweng Community · FIRST_TIME_CONTRIBUTOR | #7569 Title unavailable Unclear · Unknown | Standalone change | Partially addresses #7569 — this lands the GLM Coding Plan portion only; broader custom-provider quota surfaces (and making unsupported providers explicit in the UI) remain open on that issue. ## Summary Adds first-class | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +817/−68. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Improved markdown rendering in editor and preview1 PR · Standalone · Plugins#
Problem: Improved markdown rendering in editor and preview.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13535 feat: Improved markdown rendering in editor and preview | Gimics Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Improves the markdown **editor** and **preview** formatting, more in line with other standards like GitHub, and closes several consistency gaps between them. Renderer-only, **no new dependencies**, no wire/RPC | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +843/−83. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1in-app audio/video preview from the file explorer1 PR · Standalone · Plugins#
Problem: in-app audio/video preview from the file explorer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6751 [Feature]: Allow previewing audio files (mp3, wav, etc) in the orca file explorer (Fixes, OPEN); #8344 Title unavailable (Unclear, Unknown); #12570 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15733 feat: in-app audio/video preview from the file explorer | ChangJun Park Community · FIRST_TIME_CONTRIBUTOR | #6751 [Feature]: Allow previewing audio files (mp3, wav, etc) in the orca file explorer Fixes · OPEN #8344 Title unavailable Unclear · Unknown #12570 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Clicking an audio or video file (mp3, wav, m4a, mp4, mov, webm) in the file explorer used to show "Binary file — cannot display". Now it opens a real in-app player — the same native controls you get in a browser | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +656/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Keep the SSH connection alive when a terminal outruns a slow link1 PR · Standalone · Plugins#
Problem: Keep the SSH connection alive when a terminal outruns a slow link.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12041 Title unavailable (Unclear, Unknown); #11005 Title unavailable (Unclear, Unknown); #11999 Title unavailable (Unclear, Unknown); #1026 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12220 Keep the SSH connection alive when a terminal outruns a slow linkDraft | Neil Core team · MEMBER | #12041 Title unavailable Unclear · Unknown #11005 Title unavailable Unclear · Unknown #11999 Title unavailable Unclear · Unknown #1026 Title unavailable Unclear · Unknown | Standalone change | > ## ⚠️ Draft — not ready to merge > > Three adversarial review rounds each fixed a finding and surfaced another, and **three blocking findings are still open** (see [the conversion comment](https://github.com/stablyai/o | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +594/−42. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1keep unstamped local git worktrees routable when a runtime is saved1 PR · Standalone · Plugins#
Problem: keep unstamped local git worktrees routable when a runtime is saved.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16733 [Bug]: Local git worktrees fail closed with "Terminal creation is unavailable" when any runtime environment is saved (Fixes, CLOSED); #10251 Title unavailable (Unclear, Unknown); #10269 Title unavailable (Unclear, Unknown); #9994 Title unavailable (Unclear, Unknown); #11346 Title unavailable (Unclear, Unknown); #11512 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16829 fix(worktrees): keep unstamped local git worktrees routable when a runtime is saved | Lesley Murfin Community · CONTRIBUTOR | #16733 [Bug]: Local git worktrees fail closed with "Terminal creation is unavailable" when any runtime environment is saved Fixes · CLOSED #10251 Title unavailable Unclear · Unknown #10269 Title unavailable Unclear · Unknown #9994 Title unavailable Unclear · Unknown #11346 Title unavailable Unclear · Unknown #11512 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Save one remote environment in Settings, and Orca stops opening terminals in your ordinary **local** git worktrees — you get *"Terminal creation is unavailable because the worktree owner could not be resolved"* i | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +334/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let orchestration-dispatched workers stay silent1 PR · Standalone · Plugins#
Problem: let orchestration-dispatched workers stay silent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15148 [Feature]: Setting to keep dispatched orchestration workers from raising notifications (Fixes, OPEN); #4995 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15153 feat(notifications): let orchestration-dispatched workers stay silent | Taras Kornichuk Community · CONTRIBUTOR | #15148 [Feature]: Setting to keep dispatched orchestration workers from raising notifications Fixes · OPEN #4995 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When a coordinator agent farms work out to worker agents, only the coordinator's "done" is meant for you. This adds a switch that keeps the workers quiet and leaves the coordinator loud. ## What Changed New notif | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +326/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let plugin keybindings opt into terminal focus1 PR · Standalone · Plugins#
Problem: let plugin keybindings opt into terminal focus.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15642 Plugin keybindings never fire while focus is in a terminal, leaving plugin commands with no reachable trigger (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15725 feat(plugins): let plugin keybindings opt into terminal focus | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15642 Plugin keybindings never fire while focus is in a terminal, leaving plugin commands with no reachable trigger Fixes · OPEN | Standalone change | ## Summary **What** Plugin keybinding contributions gain an explicit `allowInTerminal: true` opt-in, and terminal-context dispatch honors it. Default behaviour is unchanged — a plugin still cannot claim a chord from the | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +107/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let the screen sleep in Keep-computer-awake mode (option A: 1-line)2 PRs · Competing · Automated release pipeline#
Problem: let the screen sleep in Keep-computer-awake mode (option A: 1-line).
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Competing. Linked issues: #17078 [Bug]: "Keep computer awake" also blocks display sleep — the screen never turns off, unlike caffeinate (Fixes, OPEN); #17183 Title unavailable (Unclear, Unknown); #11301 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Choose one implementation after a product and technical comparison; do not land alternatives together.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Not until one implementation is chosen.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Product and technical decision required.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17183 fix(awake): let the screen sleep in Keep-computer-awake mode (option A: 1-line) | luisgonzaleznf Community · FIRST_TIME_CONTRIBUTOR | #17078 [Bug]: "Keep computer awake" also blocks display sleep — the screen never turns off, unlike caffeinate Fixes · OPEN | Alternative implementation | Fixes #17078. **This is option A of two — see the sibling PR for option B; only one should merge.** ## The bug `Keep computer awake` held an Electron `prevent-display-sleep` blocker, so the screen never turned off, never | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +21/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17184 feat(awake): let the screen sleep by default, add a Keep screen on opt-in (option B) | luisgonzaleznf Community · FIRST_TIME_CONTRIBUTOR | #17078 [Bug]: "Keep computer awake" also blocks display sleep — the screen never turns off, unlike caffeinate Fixes · OPEN #17183 Title unavailable Unclear · Unknown #11301 Title unavailable Unclear · Unknown | Alternative implementation | Fixes #17078. **This is option B of two — see #17183 for the 1-line option A; only one should merge.** ## The bug `Keep computer awake` held an Electron `prevent-display-sleep` blocker, so the screen never turned off, ne | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · M Open · checks SUCCESS · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +300/−84. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let users remove the Computer Use skill1 PR · Standalone · Plugins#
Problem: let users remove the Computer Use skill.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13099 [Other]: How can I remove the "Skill Computer Use" ability? (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13163 feat(settings): let users remove the Computer Use skill | BingZ Community · CONTRIBUTOR | #13099 [Other]: How can I remove the "Skill Computer Use" ability? Fixes · CLOSED | Standalone change | ## Summary - Computer Use skill setup only offered Install/Update, so users could not remove it from Orca Settings (#13099). - Add \`buildAgentFeatureSkillRemoveCommand\` (\`npx skills remove <name> --global\`) and a **R | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +296/−66. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1link worktrees to pull requests1 PR · Standalone · Plugins#
Problem: link worktrees to pull requests.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13129 feat(cli): link worktrees to pull requests | I1eanch Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - add `--pull-request` to `orca worktree create` and resolve the verified PR head through the existing runtime RPC - fail closed when the runtime cannot resolve the requested pull request, before any worktree | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +375/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1load more commits in the git history panel2 PRs · Overlapping · Automated release pipeline#
Problem: load more commits in the git history panel.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #14224 [Feature]: Git history panel is capped at 50 commits with no way to load more (Fixes, OPEN); #14305 Title unavailable (Unclear, Unknown); #14472 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14305 feat(source-control): load more commits in the git history panel | Dipak Chaudhari Community · FIRST_TIME_CONTRIBUTOR | #14224 [Feature]: Git history panel is capped at 50 commits with no way to load more Fixes · OPEN | Cluster contribution | Closes #14224. ## Problem `refreshGitHistory` in `SourceControl.tsx` requested a hard-coded 50 commits: ```ts { limit: 50, baseRef: compareBaseRef } ``` so older commits were unreachable from the panel — scrolling fetche | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +467/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14405 feat(source-control): page the git history panel to the end of history | Brennan Benson Core team · MEMBER | #14224 [Feature]: Git history panel is capped at 50 commits with no way to load more Fixes · OPEN #14305 Title unavailable Unclear · Unknown #14472 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 The Commits list in Source Control only ever loaded the newest 50 commits, so anything older was invisible. Now there's a "Load more commits" action that keeps going until you reach the very first commit — and ea | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +1604/−185. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1make Close Others / To The Right / To The Left bindable (#16614)1 PR · Standalone · Plugins#
Problem: make Close Others / To The Right / To The Left bindable (#16614).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16614 [Feature]: Expose "Close Others" / "Close Tabs To The Right/Left" as keybindable actions (Fixes, OPEN); #1623 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17053 feat(keybindings): make Close Others / To The Right / To The Left bindable (#16614) | unkabas Community · FIRST_TIME_CONTRIBUTOR | #16614 [Feature]: Expose "Close Others" / "Close Tabs To The Right/Left" as keybindable actions Fixes · OPEN #1623 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The tab right-click menu can already "Close Others", "Close Tabs To The Right" and "Close Tabs To The Left", but you could not put those on a keyboard shortcut. Now you can assign them in Settings → Shortcuts, an | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +382/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1make Move Tab to Split keybindable1 PR · Standalone · Plugins#
Problem: make Move Tab to Split keybindable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12083 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16324 feat(tabs): make Move Tab to Split keybindable | Hyeon-Gi Jeon Community · FIRST_TIME_CONTRIBUTOR | #12083 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Users can assign shortcuts that move the active tab into a new split in any direction. ## What Changed - Added unassigned `tab.moveToSplitRight`, `Left`, `Down`, and `Up` commands. - Reused one command catalog ac | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +368/−65. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1make multi-agent workflows durable1 PR · Standalone · Plugins#
Problem: make multi-agent workflows durable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15180 [Other]: nothing observes the worker starting a turn — delivery is read from the sender's belief or from terminal noise (Fixes, OPEN); #16660 Title unavailable (Unclear, Unknown); #16522 Title unavailable (Unclear, Unknown); #14907 Title unavailable (Unclear, Unknown); #13047 Title unavailable (Unclear, Unknown); #15190 Title unavailable (Unclear, Unknown); #15976 Title unavailable (Unclear, Unknown); #16377 Title unavailable (Unclear, Unknown); #16902 Title unavailable (Unclear, Unknown); #16529 Title unavailable (Unclear, Unknown); #15951 Title unavailable (Unclear, Unknown); #15186 Title unavailable (Unclear, Unknown); #14832 Title unavailable (Unclear, Unknown); #14840 Title unavailable (Unclear, Unknown); #16095 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16904 feat(orchestration): make multi-agent workflows durable | Jinwoo Hong Core team · MEMBER | #15180 [Other]: nothing observes the worker starting a turn — delivery is read from the sender's belief or from terminal noise Fixes · OPEN #16660 Title unavailable Unclear · Unknown #16522 Title unavailable Unclear · Unknown #14907 Title unavailable Unclear · Unknown #13047 Title unavailable Unclear · Unknown #15190 Title unavailable Unclear · Unknown #15976 Title unavailable Unclear · Unknown #16377 Title unavailable Unclear · Unknown #16902 Title unavailable Unclear · Unknown #16529 Title unavailable Unclear · Unknown #15951 Title unavailable Unclear · Unknown #15186 Title unavailable Unclear · Unknown #14832 Title unavailable Unclear · Unknown #14840 Title unavailable Unclear · Unknown #16095 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 104 | $\color{#1a7f37}{\Huge{\math | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk289 files, +23272/−4162. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1make the heartbeat state a coordinator reads, not mail that wakes it1 PR · Standalone · Plugins#
Problem: make the heartbeat state a coordinator reads, not mail that wakes it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14910 [Feature]: heartbeats wake the coordinator to say nothing changed — make them state, not mail (Fixes, OPEN); #14892 Title unavailable (Unclear, Unknown); #14891 Title unavailable (Unclear, Unknown); #14889 Title unavailable (Unclear, Unknown); #1403 Title unavailable (Unclear, Unknown); #14479 Title unavailable (Unclear, Unknown); #8452 Title unavailable (Unclear, Unknown); #13235 Title unavailable (Unclear, Unknown); #14961 Title unavailable (Unclear, Unknown); #15190 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15173 feat(orchestration): make the heartbeat state a coordinator reads, not mail that wakes it | Tauri-EPO Community · CONTRIBUTOR | #14910 [Feature]: heartbeats wake the coordinator to say nothing changed — make them state, not mail Fixes · OPEN #14892 Title unavailable Unclear · Unknown #14891 Title unavailable Unclear · Unknown #14889 Title unavailable Unclear · Unknown #1403 Title unavailable Unclear · Unknown #14479 Title unavailable Unclear · Unknown #8452 Title unavailable Unclear · Unknown #13235 Title unavailable Unclear · Unknown #14961 Title unavailable Unclear · Unknown #15190 Title unavailable Unclear · Unknown | Standalone change | > **Stacked on #14892**, which is stacked on #14891 and #14889. Until those land their commits show up in this diff. Review only the last commit — the one whose subject matches this PR's title. Naming its SHA here would | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +2433/−291. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1make workspace split divider color configurable1 PR · Standalone · Plugins#
Problem: make workspace split divider color configurable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14887 [Feature]: Make the workspace tab-group split divider color configurable (Fixes, OPEN); #868690 Title unavailable (Unclear, Unknown); #171717 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14893 feat(appearance): make workspace split divider color configurable | gatsby74 Community · CONTRIBUTOR | #14887 [Feature]: Make the workspace tab-group split divider color configurable Fixes · OPEN #868690 Title unavailable Unclear · Unknown #171717 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The gray column between a terminal tab and an editor/browser tab now has its own color pickers. Changing **Dark Divider Color** still only affects splits *inside* a terminal tab, which is what that setting always | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +340/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1manage current issue cycles1 PR · Standalone · Plugins#
Problem: manage current issue cycles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16081 Add safe Linear current-cycle discovery and assignment (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16082 feat(linear): manage current issue cyclesDraft | Robert Joseph Wayne Community · FIRST_TIME_CONTRIBUTOR | #16081 Add safe Linear current-cycle discovery and assignment Fixes · OPEN | Standalone change | ## ELI5 Agents can find the active Linear cycle for an issue team, put an issue into that cycle, or remove its cycle. Orca checks the result before it says the write succeeded. ## What Changed - Add paginated `orca linea | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk32 files, +943/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1managed-account failover and acceptance receipts for supervised workers（受監督工人多帳號遞補與驗收回執）1 PR · Standalone · Plugins#
Problem: managed-account failover and acceptance receipts for supervised workers（受監督工人多帳號遞補與驗收回執）.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14290 feat(orchestration): managed-account failover and acceptance receipts for supervised workers（受監督工人多帳號遞補與驗收回執） | kueitiwan-KTW Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary This PR adds an auditable **managed-account failover** and **coordinator acceptance** loop on top of the existing Run / Task / Dispatch / `worker_done` orchestration contract. It closes two gaps we hit while r | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +3370/−76. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Merge codex-structured-core into Claude lane1 PR · Standalone · Plugins#
Problem: Merge codex-structured-core into Claude lane.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13584 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15356 Merge codex-structured-core into Claude lane | Brennan Benson Core team · MEMBER | #13584 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1335 | $\color{#1a7f37}{\Huge{\mat | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6931 files, +691958/−424816. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1move a live terminal tab to another worktree1 PR · Standalone · Plugins#
Problem: move a live terminal tab to another worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9632 [Feature]: Move an existing terminal (with its running agent) to another workspace (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15108 feat(terminal): move a live terminal tab to another worktree | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #9632 [Feature]: Move an existing terminal (with its running agent) to another workspace Fixes · OPEN | Standalone change | ## ELI5 You can now move a running terminal (and its agent) from one worktree card to another without killing the process. Right-click the tab or the sidebar agent row, or use `orca terminal move`. ## What Changed - CLI: | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk46 files, +2017/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1name the driver of store write chains before React #185 throws1 PR · Standalone · Plugins#
Problem: name the driver of store write chains before React #185 throws.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #185 Title unavailable (Unclear, Unknown); #11326 Title unavailable (Unclear, Unknown); #2746 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15076 feat(crash-reporting): name the driver of store write chains before React #185 throws | Brennan Benson Core team · MEMBER | #185 Title unavailable Unclear · Unknown #11326 Title unavailable Unclear · Unknown #2746 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +870/−89. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1named command profiles to launch an agent under a second CLI command1 PR · Standalone · Plugins#
Problem: named command profiles to launch an agent under a second CLI command.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9456 Title unavailable (Unclear, Unknown); #12930 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16798 feat(agents): named command profiles to launch an agent under a second CLI commandDraft | Murillo Medeiros de Melo Nascimento Community · FIRST_TIME_CONTRIBUTOR | #9456 Title unavailable Unclear · Unknown #12930 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Settings → Agents already lets you override an agent's launch command, but only **one** command per agent. This PR lets you save a few extra *named* commands per agent — for example Claude keeps its default `clau | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +316/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1negotiate page reconciliation commands1 PR · Standalone · Plugins#
Problem: negotiate page reconciliation commands.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14759 feat(browser): negotiate page reconciliation commandsDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +910/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open a folder passed as a launch argument as a project1 PR · Standalone · Plugins#
Problem: open a folder passed as a launch argument as a project.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16475 feat: open a folder passed as a launch argument (orca /path/to/project) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16476 feat(app): open a folder passed as a launch argument as a project | Sam5440 Community · FIRST_TIME_CONTRIBUTOR | #16475 feat: open a folder passed as a launch argument (orca /path/to/project) Fixes · OPEN | Standalone change | ## ELI5 You can now launch Orca with a folder path — `Orca /path/to/project`, `open -a Orca /path/to/project`, or dragging a folder onto the Dock icon — and Orca adds that folder as a project and opens it, the same way e | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +593/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open clicked links in the pane to the side1 PR · Standalone · Plugins#
Problem: open clicked links in the pane to the side.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13390 [Feature]: Open clicked links in the pane to the side, splitting if none exists (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13392 feat(browser): open clicked links in the pane to the side | dcieslak19973 Community · CONTRIBUTOR | #13390 [Feature]: Open clicked links in the pane to the side, splitting if none exists Fixes · OPEN | Standalone change | ## Summary Closes #13390. Clicking an in-app link always opened another tab in the worktree's **active group**, even with a browser pane sitting right beside the source — the handler passed no group at all: ```ts store.c | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +389/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open files and links from the agent preview terminal1 PR · Standalone · Plugins#
Problem: open files and links from the agent preview terminal.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16787 feat(dashboard): open files and links from the agent preview terminal | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem The agent dashboard's preview terminal linkifies URLs but nothing else. Mod+clicking a file path an agent just printed — the single most common thing you want to follow from a dashboard card — does nothing at | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +957/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open sibling files from the path header1 PR · Standalone · Plugins#
Problem: open sibling files from the path header.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16756 Add navigable editor path breadcrumbs for sibling files (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16758 feat(editor): open sibling files from the path header | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #16756 Add navigable editor path breadcrumbs for sibling files Fixes · OPEN | Standalone change | ## ELI5 The file path already visible above the editor now doubles as a quick directory browser. Click any path segment to inspect that folder and open a nearby file without moving to Explorer. ## What Changed - Render r | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +1422/−129. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open the originating session on click1 PR · Standalone · Plugins#
Problem: open the originating session on click.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15943 [Feature]: Reliably open the originating session from completion notifications (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15957 feat(notifications): open the originating session on click | Chisa Kotegawa Community · FIRST_TIME_CONTRIBUTOR | #15943 [Feature]: Reliably open the originating session from completion notifications Fixes · OPEN | Standalone change | ## ELI5 When Orca says a session finished, clicking that notification now takes you back to the exact terminal or native-chat session that produced it. If that session has already closed, Orca opens the project without r | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +1416/−135. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1opt-in 1Password op:// secret resolution for tabs + bundled onepassword agent skill1 PR · Standalone · Plugins#
Problem: opt-in 1Password op:// secret resolution for tabs + bundled onepassword agent skill.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6996 Title unavailable (Unclear, Unknown); #8985 Title unavailable (Unclear, Unknown); #12534 Title unavailable (Unclear, Unknown); #7003 Title unavailable (Unclear, Unknown); #12562 Title unavailable (Unclear, Unknown); #14899 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12947 feat(secrets): opt-in 1Password op:// secret resolution for tabs + bundled onepassword agent skill | Vincent Colombo Community · FIRST_TIME_CONTRIBUTOR | #6996 Title unavailable Unclear · Unknown #8985 Title unavailable Unclear · Unknown #12534 Title unavailable Unclear · Unknown #7003 Title unavailable Unclear · Unknown #12562 Title unavailable Unclear · Unknown #14899 Title unavailable Unclear · Unknown | Standalone change | ## What this adds Opt-in 1Password integration for terminal-tab secrets, in two complementary pieces: **1. Spawn-time `op://` resolution (`feat(secrets)`).** With the new **Settings → Integrations → 1Password** toggle en | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +1479/−56. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1opt-in zmx-backed durable SSH terminals1 PR · Standalone · Plugins#
Problem: opt-in zmx-backed durable SSH terminals.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12798 feat(ssh): opt-in zmx-backed durable SSH terminals | Vivek Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds **opt-in zmx-backed durable SSH terminals**: a per-target setting that moves remote PTY ownership out of the SSH relay into [zmx](https://github.com/neurosnap/zmx) sessions on the remote host. When enable | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk70 files, +4238/−300. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1optional agent-state emoji in tab titles1 PR · Standalone · Plugins#
Problem: optional agent-state emoji in tab titles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15793 [Feature]: Optional agent-state emoji in tab titles (Fixes, OPEN); #15781 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15794 feat(tabs): optional agent-state emoji in tab titlesDraft | Ramzi Community · CONTRIBUTOR | #15793 [Feature]: Optional agent-state emoji in tab titles Fixes · OPEN #15781 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Turn on a setting and each tab gets a small glyph in front of its name: ⚙ while the agent is working, ✋ when it wants your input, ✅ when it is finished. Off by default, so nothing changes unless you ask for it. # | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · M Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +218/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1pick a base branch when creating a workspace from a task2 PRs · Overlapping · Plugins#
Problem: pick a base branch when creating a workspace from a task.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15747 [Feature]: Pick a base branch when creating a workspace from a task (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15748 feat(tasks): pick a base branch when creating a workspace from a task | Gleb Malov Community · FIRST_TIME_CONTRIBUTOR | #15747 [Feature]: Pick a base branch when creating a workspace from a task Fixes · OPEN | Cluster contribution | ELI5 When you start a new workspace from a task (a GitHub issue, GitLab issue, Linear issue, or Jira issue), Orca always branched the new worktree off the project's default branch. Now there's a "Branch from" dropdown in | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +556/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17250 feat(composer): choose a base ref in the New Workspace composer | Vincent Community · FIRST_TIME_CONTRIBUTOR | #15747 [Feature]: Pick a base branch when creating a workspace from a task Fixes · OPEN | Cluster contribution | ## ELI5 When you start a workspace from a Jira, Linear, GitHub or GitLab issue, Orca names it from the issue — but it also silently branches off the project's default branch, with no way to say otherwise. If your team wo | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +592/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1point a Design Mode annotation at a second element or spot1 PR · Standalone · Plugins#
Problem: point a Design Mode annotation at a second element or spot.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11360 Title unavailable (Unclear, Unknown); #8687 Title unavailable (Unclear, Unknown); #8830 Title unavailable (Unclear, Unknown); #9224 Title unavailable (Unclear, Unknown); #15333 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12141 feat(browser): point a Design Mode annotation at a second element or spot | Praveen Emani Community · FIRST_TIME_CONTRIBUTOR | #11360 Title unavailable Unclear · Unknown #8687 Title unavailable Unclear · Unknown #8830 Title unavailable Unclear · Unknown #9224 Title unavailable Unclear · Unknown #15333 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When leaving design feedback in Orca's built-in browser, a note could only point at one element on the page. Instructions involving two things ("move this button below the pricing table") forced you to describe t | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +1159/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1preview videos in the file viewer1 PR · Standalone · Plugins#
Problem: preview videos in the file viewer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12570 feat(mobile): preview videos in the file viewer | Lirone Levy Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Videos (`.mp4`, `.m4v`, `.mov`) can now be previewed in the mobile file viewer. Tapping one previously showed "Binary preview unavailable", because the host reported every previewable binary as `isImage` and R | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +581/−102. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Prime native cache before E2E fanout1 PR · Standalone · Plugins#
Problem: Prime native cache before E2E fanout.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17280 Prime native cache before E2E fanout | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +54/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1profile-driven output status scrape, with IBM Bob1 PR · Standalone · Plugins#
Problem: profile-driven output status scrape, with IBM Bob.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14895 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15936 feat(agent-status): profile-driven output status scrape, with IBM Bob | trs-80 Community · FIRST_TIME_CONTRIBUTOR | #14895 Title unavailable Unclear · Unknown | Standalone change | > Stacked on #14895 (IBM Bob agent support). Review the last three commits; the diff includes that PR's commits until it lands. ## ELI5 Agents with no hooks and no title status can now get working / waiting / done rows f | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk68 files, +2064/−366. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1prove Bun runtime path1 PR · Standalone · Plugins#
Problem: prove Bun runtime path.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16741 feat(orcad): prove Bun runtime path | Neil Core team · MEMBER | None found | Standalone change | ## What - runs orcad under Bun with a Bun-native WebSocket/E2EE transport - runs the terminal daemon under Bun using `Bun.Terminal` instead of `node-pty` - preserves Node/Electron WebSocket and node-pty behavior as the c | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +1320/−145. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1prune expired Codex runtime session logs (#16776)1 PR · Standalone · Plugins#
Problem: prune expired Codex runtime session logs (#16776).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16776 codex-runtime-home/sessions grows unbounded, consumed 11GB with no cleanup mechanism (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16990 feat(codex): prune expired Codex runtime session logs (#16776) | Max Hsu Community · FIRST_TIME_CONTRIBUTOR | #16776 codex-runtime-home/sessions grows unbounded, consumed 11GB with no cleanup mechanism Fixes · OPEN | Standalone change | ## ELI5 Orca keeps a copy of every Codex conversation it has ever run, and never throws any of them away. The reporter's folder had grown to 11 GB and 1,000+ files going back to September 2025. This adds a quiet sweep at | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +393/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1put the daemon in a kill-on-close job so a crash cannot orphan its PTY tree on Windows1 PR · Standalone · Plugins#
Problem: put the daemon in a kill-on-close job so a crash cannot orphan its PTY tree on Windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16894 Title unavailable (Unclear, Unknown); #16901 Title unavailable (Unclear, Unknown); #16843 Title unavailable (Unclear, Unknown); #1693 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16895 fix(relay): put the daemon in a kill-on-close job so a crash cannot orphan its PTY tree on Windows | Brennan Benson Core team · MEMBER | #16894 Title unavailable Unclear · Unknown #16901 Title unavailable Unclear · Unknown #16843 Title unavailable Unclear · Unknown #1693 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +158/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1read Antigravity quota from local runtime4 PRs · Overlapping · Plugins#
Problem: read Antigravity quota from local runtime.
Combined impact: Coordinates 4 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #7809 Antigravity Usage — status-bar segment disappears while toggle is checked (W28) (Fixes, OPEN); #9122 [Bug]: Antigravity usage is a copy of the Gemini quota — wrong pools, and refresh breaks entirely without a local Gemini CLI install (Fixes, OPEN); #8735 Title unavailable (Unclear, Unknown); #15876 Title unavailable (Unclear, Unknown); #11536 Title unavailable (Unclear, Unknown); #12095 Title unavailable (Unclear, Unknown); #14571 Title unavailable (Unclear, Unknown); #12370 Title unavailable (Unclear, Unknown); #15948 Title unavailable (Unclear, Unknown); #16653 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14571 fix(rate-limits): read Antigravity quota from local runtime | Leonardo Community · FIRST_TIME_CONTRIBUTOR | #7809 Antigravity Usage — status-bar segment disappears while toggle is checked (W28) Fixes · OPEN #9122 [Bug]: Antigravity usage is a copy of the Gemini quota — wrong pools, and refresh breaks entirely without a local Gemini CLI install Fixes · OPEN #8735 Title unavailable Unclear · Unknown #15876 Title unavailable Unclear · Unknown #11536 Title unavailable Unclear · Unknown #12095 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Antigravity already knows the real quota for the account it is running. Orca was showing a copy of Gemini usage instead. This change asks the already-running, host-local Antigravity service for its own quota and | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +2252/−201. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15948 fix(usage): fetch native Antigravity quotas via Agy | John Mike Asuncion Community · FIRST_TIME_CONTRIBUTOR | #9122 [Bug]: Antigravity usage is a copy of the Gemini quota — wrong pools, and refresh breaks entirely without a local Gemini CLI install Fixes · OPEN #11536 Title unavailable Unclear · Unknown #12095 Title unavailable Unclear · Unknown #14571 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Orca currently labels a copy of Gemini CLI usage as Antigravity usage. This change asks the installed Antigravity CLI for its own quota report instead, so Orca shows the real Gemini and Claude/GPT five-hour and w | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +555/−73. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16653 Read Antigravity usage from the agy CLI | Gabriel Ayrao Community · FIRST_TIME_CONTRIBUTOR | #9122 [Bug]: Antigravity usage is a copy of the Gemini quota — wrong pools, and refresh breaks entirely without a local Gemini CLI install Fixes · OPEN #12370 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Orca's Antigravity meter was showing Gemini's numbers, because it assumed both share one quota. Google turned Gemini Code Assist off for individuals, so there is nothing left to copy and the meter reads `0%` fore | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +519/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16710 fix(usage): read Antigravity quota from Agy, not the Gemini mirror | Brennan Benson Core team · MEMBER | #9122 [Bug]: Antigravity usage is a copy of the Gemini quota — wrong pools, and refresh breaks entirely without a local Gemini CLI install Fixes · OPEN #11536 Title unavailable Unclear · Unknown #14571 Title unavailable Unclear · Unknown #15948 Title unavailable Unclear · Unknown #16653 Title unavailable Unclear · Unknown #12095 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 19 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +2424/−224. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1read submodule changes when .gitmodules hides them1 PR · Standalone · Plugins#
Problem: read submodule changes when .gitmodules hides them.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15427 [Feature]: Read submodule changes in Source Control when .gitmodules sets ignore = all (Fixes, OPEN); #13102 Title unavailable (Unclear, Unknown); #13989 Title unavailable (Unclear, Unknown); #11673 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15428 feat(source-control): read submodule changes when .gitmodules hides them | Vladimir Community · FIRST_TIME_CONTRIBUTOR | #15427 [Feature]: Read submodule changes in Source Control when .gitmodules sets ignore = all Fixes · OPEN #13102 Title unavailable Unclear · Unknown #13989 Title unavailable Unclear · Unknown #11673 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If a repo tells Git "ignore my submodules", Orca's Source Control panel shows nothing while you work inside a submodule — no rows, no diffs, as if the repo were clean. This adds a per-project switch that tells Gi | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +423/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1reap zombie worktrees & stale daemon generations1 PR · Standalone · Plugins#
Problem: reap zombie worktrees & stale daemon generations.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11342 Title unavailable (Unclear, Unknown); #9193 Title unavailable (Unclear, Unknown); #8585 Title unavailable (Unclear, Unknown); #9045 Title unavailable (Unclear, Unknown); #7843 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12740 feat(aquarium): reap zombie worktrees & stale daemon generationsDraft | Brandon Bennett Community · CONTRIBUTOR | #11342 Title unavailable Unclear · Unknown #9193 Title unavailable Unclear · Unknown #8585 Title unavailable Unclear · Unknown #9045 Title unavailable Unclear · Unknown #7843 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca quietly accumulates leftovers: workspaces whose folders were deleted outside the app ("ghosts"), stale helper processes left over from old app versions, and terminal sessions that keep running after their ta | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk57 files, +3331/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1rebase #9495 onto current main and fix task-reference parsing1 PR · Standalone · Plugins#
Problem: rebase #9495 onto current main and fix task-reference parsing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14622 Add ClickUp as a task source (Fixes, OPEN); #9495 Title unavailable (Unclear, Unknown); #14447 Title unavailable (Unclear, Unknown); #10389 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15788 feat(clickup): rebase #9495 onto current main and fix task-reference parsingDraft | Ramzi Community · CONTRIBUTOR | #14622 Add ClickUp as a task source Fixes · OPEN #9495 Title unavailable Unclear · Unknown #14447 Title unavailable Unclear · Unknown #10389 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can already start work from GitHub, GitLab, Linear and Jira tickets. This adds ClickUp to that list: connect a ClickUp account with a personal API token, browse your tasks in the Tasks panel, and start a wor | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk185 files, +8930/−534. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1recommend merged workspaces instead of protecting them1 PR · Standalone · Plugins#
Problem: recommend merged workspaces instead of protecting them.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16282 Title unavailable (Unclear, Unknown); #13413 Title unavailable (Unclear, Unknown); #13695 Title unavailable (Unclear, Unknown); #13979 Title unavailable (Unclear, Unknown); #10202 Title unavailable (Unclear, Unknown); #8275 Title unavailable (Unclear, Unknown); #12345 Title unavailable (Unclear, Unknown); #16690 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13930 feat(workspace-cleanup): recommend merged workspaces instead of protecting them | Jin Won, Park Community · FIRST_TIME_CONTRIBUTOR | #16282 Title unavailable Unclear · Unknown #13413 Title unavailable Unclear · Unknown #13695 Title unavailable Unclear · Unknown #13979 Title unavailable Unclear · Unknown #10202 Title unavailable Unclear · Unknown #8275 Title unavailable Unclear · Unknown #12345 Title unavailable Unclear · Unknown #16690 Title unavailable Unclear · Unknown | Standalone change | ## Summary Workspace cleanup recommends on inactivity alone. Its git evidence read exists only to keep the destructive path away from unfinished work, so the workspaces users most want to retire — the ones whose branch a | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk48 files, +1089/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1record the iOS simulator screen to a video file1 PR · Standalone · Plugins#
Problem: record the iOS simulator screen to a video file.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #5156 Title unavailable (Unclear, Unknown); #8506 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16624 feat(emulator): record the iOS simulator screen to a video file | KEEN Community · FIRST_TIME_CONTRIBUTOR | #5156 Title unavailable Unclear · Unknown #8506 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You can already see the iOS simulator inside Orca. Now you can hit Record, do the thing, hit stop, and you get a video file of it. ## What Changed - Adds a Record button to the emulator pane toolbar (iOS sessions | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +1012/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1render PlantUML diagrams in preview and rich editor1 PR · Standalone · Plugins#
Problem: render PlantUML diagrams in preview and rich editor.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6804 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15043 feat(markdown): render PlantUML diagrams in preview and rich editor | 5unnyWind Community · FIRST_TIME_CONTRIBUTOR | #6804 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Markdown files can already draw Mermaid diagrams. This makes ` ```plantuml ` blocks draw too, in both the read-only preview and the rich editor. No Java, no external server: the whole engine runs in the renderer. | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +640/−52. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1report an honest submit verdict from terminal send1 PR · Standalone · Plugins#
Problem: report an honest submit verdict from terminal send.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13763 Title unavailable (Unclear, Unknown); #14962 Title unavailable (Unclear, Unknown); #15273 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15274 feat(terminal): report an honest submit verdict from terminal send | Taras Kornichuk Community · CONTRIBUTOR | #13763 Title unavailable Unclear · Unknown #14962 Title unavailable Unclear · Unknown #15273 Title unavailable Unclear · Unknown | Standalone change | ## The failure this closes `orca terminal send --enter` returned success as soon as the bytes reached the PTY. When the Enter was swallowed — a completion popup ate it, or the TUI was mid-turn — the text sat unsubmitted | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1753/−135. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1report guest renderer deaths and key renderer dedupe by webContents identity1 PR · Standalone · Plugins#
Problem: report guest renderer deaths and key renderer dedupe by webContents identity.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15052 Guest and webview renderer deaths are never reported as crashes (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15063 fix(crash-reporting): report guest renderer deaths and key renderer dedupe by webContents identity | Brennan Benson Core team · MEMBER | #15052 Guest and webview renderer deaths are never reported as crashes Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1017/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1report heartbeat freshness on worker-list1 PR · Standalone · Plugins#
Problem: report heartbeat freshness on worker-list.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15951 [Feature]: orchestration worker-list carries no heartbeat information, so the fleet view cannot show which lane went quiet (Fixes, OPEN); #14910 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15963 feat(orchestration): report heartbeat freshness on worker-list | Tauri-EPO Community · CONTRIBUTOR | #15951 [Feature]: orchestration worker-list carries no heartbeat information, so the fleet view cannot show which lane went quiet Fixes · OPEN #14910 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A coordinator watching several agent lanes wants to spot the one that went quiet. Orca already records when each lane last checked in, but nothing showed it on the list of lanes — so you had to ask about each lan | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +643/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1resume closed worker provider sessions1 PR · Standalone · Plugins#
Problem: resume closed worker provider sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14388 [Feature]: Resume a closed orchestration worker's provider session (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14389 feat(orchestration): resume closed worker provider sessionsDraft | Julian Pscheid Community · FIRST_TIME_CONTRIBUTOR | #14388 [Feature]: Resume a closed orchestration worker's provider session Fixes · OPEN | Standalone change | ## ELI5 Orca can now continue a finished worker in the same provider conversation. The command takes the old Orca Dispatch ID, checks that its private resume ticket still belongs to the same provider, server, and workspa | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +2148/−163. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1resume Hermes TUI sessions after crash1 PR · Standalone · Plugins#
Problem: resume Hermes TUI sessions after crash.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15808 [Feature]: Resume Hermes TUI sessions after crash or quit (Fixes, OPEN); #12075 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15809 feat(agents): resume Hermes TUI sessions after crash | Yi Lok Enoch Lam Community · FIRST_TIME_CONTRIBUTOR | #15808 [Feature]: Resume Hermes TUI sessions after crash or quit Fixes · OPEN #12075 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If a Hermes TUI pane dies because Orca, the daemon, or the PTY crashed, Orca should relaunch that same Hermes session with `--tui --resume <id>`, the way it already does for Claude and Codex. Hermes already knows | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +133/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1RTL text-direction toggle for the built-in editor1 PR · Standalone · Plugins#
Problem: RTL text-direction toggle for the built-in editor.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16259 [Feature]: RTL text-direction toggle for the built-in editor (button + `…` menu + shortcut, like Word Wrap) (Fixes, OPEN); #10086 Title unavailable (Unclear, Unknown); #5262 Title unavailable (Unclear, Unknown); #6169 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16291 feat(editor): RTL text-direction toggle for the built-in editor | Yehuda Community · FIRST_TIME_CONTRIBUTOR | #16259 [Feature]: RTL text-direction toggle for the built-in editor (button + `…` menu + shortcut, like Word Wrap) Fixes · OPEN #10086 Title unavailable Unclear · Unknown #5262 Title unavailable Unclear · Unknown #6169 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A Hebrew or Arabic document in Orca's editor is laid out as if it were English: the text hugs the left edge, because the editor has no notion of a document being right-to-left. This adds a small button in the edi | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk59 files, +1231/−112. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1run native teammate panes on Windows1 PR · Standalone · Plugins#
Problem: run native teammate panes on Windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15751 Claude Agent Teams native panes are unreachable on Windows (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15753 feat(agent-teams): run native teammate panes on Windows | thomasytterstrom Community · FIRST_TIME_CONTRIBUTOR | #15751 Claude Agent Teams native panes are unreachable on Windows Fixes · OPEN | Standalone change | ## ELI5 On Windows, Agent Teams quietly gave you in-process teammates instead of real Orca panes. Three separate things blocked the pane path: Orca's `tmux` shim was a `.cmd` that Claude Code cannot spawn, the pane comma | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +472/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1seed the default agent when activating an empty worktree1 PR · Standalone · Plugins#
Problem: seed the default agent when activating an empty worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15912 feat(worktree): seed the default agent when activating an empty worktree | LiuSir Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Clicking a worktree that has no tabs used to open a blank terminal. It now opens the same default agent you already picked in Settings → Agents, unless you set that default to a blank terminal. ## What Changed - | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +332/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1sender-set message delivery class and a count-only check1 PR · Standalone · Plugins#
Problem: sender-set message delivery class and a count-only check.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13645 Title unavailable (Unclear, Unknown); #13650 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15264 feat(orchestration): sender-set message delivery class and a count-only check | Taras Kornichuk Community · CONTRIBUTOR | #13645 Title unavailable Unclear · Unknown #13650 Title unavailable Unclear · Unknown | Standalone change | Closes part of #13645. A sender can now say **when** a message should reach the recipient, and a supervisor can ask **whether** mail exists without paying for a full check. ## Why Orca's mail is a pull: the recipient mus | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +956/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1serve Cursor sidecar scans on the relay and unblock #11525 CI1 PR · Standalone · Plugins#
Problem: serve Cursor sidecar scans on the relay and unblock #11525 CI.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11525 Title unavailable (Unclear, Unknown); #14582 Title unavailable (Unclear, Unknown); #11370 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12891 fix(ai-vault): serve Cursor sidecar scans on the relay and unblock #11525 CI | 5unnyWind Community · FIRST_TIME_CONTRIBUTOR | #11525 Title unavailable Unclear · Unknown #14582 Title unavailable Unclear · Unknown #11370 Title unavailable Unclear · Unknown | Standalone change | Targets `feature-extend-ssh-host-aware-agent-session-hist` (#11525). Merges current `main` and gets the branch green. ## The bug worth reviewing first `createRelayAiVaultFilesystemProvider()` never implemented `scanCurso | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk501 files, +32026/−3493. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1set a default session profile per project1 PR · Standalone · Plugins#
Problem: set a default session profile per project.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13152 feat(browser): set a default session profile per project | Dunz Koi Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Browser tabs could only inherit one app-wide default session profile. Working across projects that need different logged-in accounts (work Google vs. personal, two customer tenants) meant switching the profile | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +578/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1settle exited worker release when tab is absent1 PR · Standalone · Plugins#
Problem: settle exited worker release when tab is absent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13860 Title unavailable (Unclear, Unknown); #13927 Title unavailable (Unclear, Unknown); #15920 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16927 fix: settle exited worker release when tab is absent | niyeahman Community · FIRST_TIME_CONTRIBUTOR | #13860 Title unavailable Unclear · Unknown #13927 Title unavailable Unclear · Unknown #15920 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A worker release can race with terminal reuse. Orca may prove that one PTY process exited, wait while closing the tab, and then accidentally act on a replacement PTY that reused the same terminal identity. This c | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +1020/−153. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1ship browserless npm runtime1 PR · Standalone · Plugins#
Problem: ship browserless npm runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13452 feat(server): ship browserless npm runtime | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## Summary - ship a publishable `@stablyai/orca` package with `orca` and `orca-ide` bins; zero arguments or `serve` starts a foreground browserless host without Electron, Chromium, Xvfb, or FUSE - reuse Orca's existing r | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk181 files, +16567/−849. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show Cmd/Ctrl+1-9 index badges on workspace cards1 PR · Standalone · Plugins#
Problem: show Cmd/Ctrl+1-9 index badges on workspace cards.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16083 feat(sidebar): show Cmd/Ctrl+1-9 index badges on workspace cards | BinyaminEden Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## What Hold **⌘** (Ctrl on Windows/Linux) and each of the first nine workspace cards in the sidebar overlays the digit that jumps to it — the way Safari numbers tabs. Release the key, or move focus off the window, and t | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +278/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show commit files as a directory tree1 PR · Standalone · Plugins#
Problem: show commit files as a directory tree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13942 feat(source-control): show commit files as a directory tree | orbitcrafter Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Expanding a commit in the Source Control history panel listed its changed files flat, so a deep package path was only readable from the dimmed path suffix trailing each filename. Commit detail was the only fil | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +653/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show Cursor monthly usage on the status bar1 PR · Standalone · Plugins#
Problem: show Cursor monthly usage on the status bar.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15516 Title unavailable (Unclear, Unknown); #13837 Title unavailable (Unclear, Unknown); #8669 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16815 feat: show Cursor monthly usage on the status bar | ivo922 Community · FIRST_TIME_CONTRIBUTOR | #15516 Title unavailable Unclear · Unknown #13837 Title unavailable Unclear · Unknown #8669 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The status bar can now show how much of your Cursor monthly plan you have used, the same way it already shows Grok. It reads the login from `cursor-agent` or the Cursor IDE on this machine. No extra Orca Cursor l | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk47 files, +1779/−110. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show host-side gh/glab status on Integrations cards1 PR · Standalone · Plugins#
Problem: show host-side gh/glab status on Integrations cards.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12020 Title unavailable (Unclear, Unknown); #10559 Title unavailable (Unclear, Unknown); #10653 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12028 feat(preflight): show host-side gh/glab status on Integrations cards | dcieslak19973 Community · CONTRIBUTOR | #12020 Title unavailable Unclear · Unknown #10559 Title unavailable Unclear · Unknown #10653 Title unavailable Unclear · Unknown | Standalone change | **What:** Integrations cards stop reporting "Not installed" when `gh`/`glab` actually live on the workspace's SSH execution host. **Risk:** Additive probe, fail-open on every path — no mux, old relay, or timeout all rend | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +868/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show live Codex subagent progress1 PR · Standalone · Plugins#
Problem: show live Codex subagent progress.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12621 [Feature]: Open Codex sub-agent rows to inspect live progress (Fixes, OPEN); #9637 Title unavailable (Unclear, Unknown); #8251 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12311 feat(sidebar): show live Codex subagent progress | Lu Chong Community · FIRST_TIME_CONTRIBUTOR | #12621 [Feature]: Open Codex sub-agent rows to inspect live progress Fixes · OPEN #9637 Title unavailable Unclear · Unknown #8251 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Make live Codex internal subagent rows clickable in both full and compact sidebar views and open the provider-assigned child session in a non-modal, read-only progress sheet. - Keep child discovery live acro | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk51 files, +3415/−126. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show pace reserve/deficit on the provider usage bars1 PR · Standalone · Plugins#
Problem: show pace reserve/deficit on the provider usage bars.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15937 Usage bars show spend but not whether it's ahead of or behind pace for the window (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15596 feat(usage): show pace reserve/deficit on the provider usage bars | Saman Mahdanian Community · FIRST_TIME_CONTRIBUTOR | #15937 Usage bars show spend but not whether it's ahead of or behind pace for the window Fixes · OPEN | Standalone change | ## ELI5 The usage bars tell you how much of your quota is gone, but not whether that's fast or slow for how far into the window you are. This adds a "you should be about here by now" tick on each bar, plus a line saying | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +526/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show PR review comments in the local branch diff (read-only)1 PR · Standalone · Plugins#
Problem: show PR review comments in the local branch diff (read-only).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16076 [Feature]: Show PR review comments inside the local branch diff (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16236 feat: show PR review comments in the local branch diff (read-only) | Marcin Grabowski Community · FIRST_TIME_CONTRIBUTOR | #16076 [Feature]: Show PR review comments inside the local branch diff Fixes · OPEN | Standalone change | ## ELI5 When you're working on a branch that has an open PR, the review comments from GitHub now show up directly inside Orca's branch diffs — right at the lines they were written on. Your own unsubmitted draft comments | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk46 files, +2728/−160. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show provider subscription plan labels1 PR · Standalone · Plugins#
Problem: show provider subscription plan labels.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16296 [Feature]: show provider-reported subscription plans in Usage (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16297 feat(usage): show provider subscription plan labels | Robith Yusuf Community · FIRST_TIME_CONTRIBUTOR | #16296 [Feature]: show provider-reported subscription plans in Usage Fixes · OPEN | Standalone change | ## ELI5 Usage rows now show an account-provided package label when available, such as `Claude · Max 20x` or `Codex · Pro`. ## What Changed - Preserve optional provider `planType` data and format it only at the UI boundar | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +254/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show the active workspace's linked task in a Task panel1 PR · Standalone · Plugins#
Problem: show the active workspace's linked task in a Task panel.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15318 [Feature]: Right sidebar panel for the active workspace's linked task (Fixes, OPEN); #42 Title unavailable (Unclear, Unknown); #12693 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15330 feat(right-sidebar): show the active workspace's linked task in a Task panel | Raphael Huet de Froberville Community · FIRST_TIME_CONTRIBUTOR | #15318 [Feature]: Right sidebar panel for the active workspace's linked task Fixes · OPEN #42 Title unavailable Unclear · Unknown #12693 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A workspace already knows which issue or PR it was created from. The right sidebar shows you everything about the code (files, diff, checks, agents) but not that item, so reading the acceptance criteria means lea | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +905/−147. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1start argv workers with bound authority3 PRs · Overlapping · Plugins#
Problem: start argv workers with bound authority.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16377 [Bug] **[Bug] 1.4.188 regression: every `worker-start` fails with `agent_prompt_stalled`, then revokes the (Fixes, OPEN); #15920 Title unavailable (Unclear, Unknown); #15976 Title unavailable (Unclear, Unknown); #16095 Title unavailable (Unclear, Unknown); #16425 Title unavailable (Unclear, Unknown); #16660 agent_prompt_stalled: dispatch fails ~8s after launch for slow-booting agents (Hermes, agy) — worker completes task but worker_done rejected (Fixes, OPEN); #15180 Title unavailable (Unclear, Unknown); #15958 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16548 fix(orchestration): start argv workers with bound authority | Antonio Fulgêncio Community · FIRST_TIME_CONTRIBUTOR | #16377 [Bug] **[Bug] 1.4.188 regression: every `worker-start` fails with `agent_prompt_stalled`, then revokes the Fixes · OPEN #15920 Title unavailable Unclear · Unknown #15976 Title unavailable Unclear · Unknown #16095 Title unavailable Unclear · Unknown #16425 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Orca now starts argv-capable orchestration workers with their instructions and launch credentials already attached to the process command. It binds the exact terminal before readiness monitoring, so a healthy wor | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +2529/−316. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16664 feat(runtime): make agent prompt stall timeout configurable via env | fredogemilang Community · FIRST_TIME_CONTRIBUTOR | #16660 agent_prompt_stalled: dispatch fails ~8s after launch for slow-booting agents (Hermes, agy) — worker completes task but worker_done rejected Fixes · OPEN | Cluster contribution | ## Problem `AGENT_PROMPT_EFFECT_TIMEOUT_MS` is hardcoded to 5s. Slow-booting agents (Hermes Agent CLI boots in 15-60s, Google Antigravity CLI similar) hit `agent_prompt_stalled` before reaching their first prompt — the d | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +3/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16715 fix(orchestration): fence ambiguous worker starts | erickaquino Community · FIRST_TIME_CONTRIBUTOR | #16377 [Bug] **[Bug] 1.4.188 regression: every `worker-start` fails with `agent_prompt_stalled`, then revokes the Fixes · OPEN #16660 agent_prompt_stalled: dispatch fails ~8s after launch for slow-booting agents (Hermes, agy) — worker completes task but worker_done rejected Fixes · OPEN #15180 Title unavailable Unclear · Unknown #15958 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When Orca presses Enter in an agent pane, it cannot always know immediately whether the agent received the task. Previously, Orca could call that uncertainty a failure, revoke the worker's reporting permission, a | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +952/−90. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1stop an agent from the board without opening its worktree1 PR · Standalone · Plugins#
Problem: stop an agent from the board without opening its worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12095 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16788 feat(dashboard): stop an agent from the board without opening its worktree | MumuTW Community · CONTRIBUTOR | #12095 Title unavailable Unclear · Unknown | Standalone change | Split out of #12095, which bundled this dashboard feature with an unrelated Antigravity quota rewrite. This PR is the dashboard half only — no `src/main/rate-limits/` changes. Rebased onto current `main`. ## Why Clearing | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +913/−94. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1stop list/ps crashing on corrupt workspace layout paths1 PR · Standalone · Plugins#
Problem: stop list/ps crashing on corrupt workspace layout paths.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14016 worktree list/ps crash: Cannot read properties of undefined (reading 'startsWith') (Fixes, OPEN); #14437 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14019 fix(worktrees): stop list/ps crashing on corrupt workspace layout paths | BingZ Community · CONTRIBUTOR | #14016 worktree list/ps crash: Cannot read properties of undefined (reading 'startsWith') Fixes · OPEN #14437 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A corrupt or missing saved workspace path could make `worktree.list` and `worktree.ps` crash before returning any results. The listing path now ignores unusable stored paths while preserving valid layout history. | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +170/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1stop macOS serve crash-looping in _RegisterApplication2 PRs · Duplicate · Automated release pipeline#
Problem: stop macOS serve crash-looping in _RegisterApplication.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Duplicate. Linked issues: #14541 [Bug]: orca serve SIGABRTs in _RegisterApplication before JS (crash loop) (Fixes, OPEN); #9282 Title unavailable (Unclear, Unknown); #10461 Title unavailable (Unclear, Unknown); #10464 Title unavailable (Unclear, Unknown); #12212 Title unavailable (Unclear, Unknown); #14542 Title unavailable (Unclear, Unknown); #14755 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Confirm the preferred implementation and supersede redundant work.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Not until one implementation is chosen.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Likely.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14542 fix(cli): stop macOS serve crash-looping in _RegisterApplication | Thiago Mota Soares Community · CONTRIBUTOR | #14541 [Bug]: orca serve SIGABRTs in _RegisterApplication before JS (crash loop) Fixes · OPEN #9282 Title unavailable Unclear · Unknown #10461 Title unavailable Unclear · Unknown #10464 Title unavailable Unclear · Unknown #12212 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 If something (often an agent) starts a second Orca while one is already running, macOS kills that second process instantly — before Orca's own "already running" check can run. The starter retries, and you get a p | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Supersede |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +754/−104. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14768 fix(cli): decide duplicate-serve before macOS aborts pre-JS (STA-4336) | Jinwoo Hong Core team · MEMBER | #14541 [Bug]: orca serve SIGABRTs in _RegisterApplication before JS (crash loop) Fixes · OPEN #12212 Title unavailable Unclear · Unknown #14542 Title unavailable Unclear · Unknown #14755 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | +893 | −16 | +877 | | Prod | 1 | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · L Open · checks SUCCESS · review None | Supersede |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +2035/−69. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1stop the Help menu funnelling ordinary bug reports into the crash channel1 PR · Standalone · Plugins#
Problem: stop the Help menu funnelling ordinary bug reports into the crash channel.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6147 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12493 fix(feedback): stop the Help menu funnelling ordinary bug reports into the crash channel | Neil Core team · MEMBER | #6147 Title unavailable Unclear · Unknown | Standalone change | ## What this fixes **Signature:** `Reason: no captured crash report` / `- captured_crash_report: false` / `- report_source: help_menu`. **Covers 11 of the 127 reports in this batch.** These are not crashes. They are ordi | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +927/−201. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1supervise an adopted dispatch with --supervise1 PR · Standalone · Plugins#
Problem: supervise an adopted dispatch with --supervise.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13678 Title unavailable (Unclear, Unknown); #13681 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15270 feat(orchestration): supervise an adopted dispatch with --supervise | Taras Kornichuk Community · CONTRIBUTOR | #13678 Title unavailable Unclear · Unknown #13681 Title unavailable Unclear · Unknown | Standalone change | `orca orchestration dispatch --to <handle> --inject --supervise` records the same supervised worker that `worker-start --terminal` records, so the whole `worker-*` set works on an adopted pane. Without `--supervise`, not | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +442/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support Cursor Agent conversations1 PR · Standalone · Plugins#
Problem: support Cursor Agent conversations.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15718 [Feature]: Add Cursor CLI to experimental Chat UI (parity with Grok) (Fixes, CLOSED); #7766 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16796 feat(native-chat): support Cursor Agent conversations | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #15718 [Feature]: Add Cursor CLI to experimental Chat UI (parity with Grok) Fixes · CLOSED #7766 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Cursor Agent sessions can now use Orca's existing Native Chat view instead of being limited to the terminal. Orca reads the transcript produced by the `cursor-agent` CLI and keeps input and Stop routed to the sam | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +721/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support Fast Mono (bionic-reading) fonts1 PR · Standalone · Plugins#
Problem: support Fast Mono (bionic-reading) fonts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14949 Feature: support Fast Mono (bionic-reading) font in the terminal (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14950 feat(terminal): support Fast Mono (bionic-reading) fonts | Ivan Cajic Community · FIRST_TIME_CONTRIBUTOR | #14949 Feature: support Fast Mono (bionic-reading) font in the terminal Fixes · OPEN | Standalone change | ## ELI5 Fast Mono is a font that bolds the first letter of each word ("bionic reading") via OpenType rules that need to see the whole word. Orca's WebGL renderer draws each cell by itself, so every letter looked bold and | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +281/−90. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support keyboard-interactive authentication (MFA)1 PR · Standalone · Plugins#
Problem: support keyboard-interactive authentication (MFA).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8622 [Bug]: SSH connection fails after password when host requires keyboard-interactive MFA (Fixes, OPEN); #8750 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15588 feat(ssh): support keyboard-interactive authentication (MFA) | Allen Community · FIRST_TIME_CONTRIBUTOR | #8622 [Bug]: SSH connection fails after password when host requires keyboard-interactive MFA Fixes · OPEN #8750 Title unavailable Unclear · Unknown | Standalone change | ## Problem Connecting to a host that requires password auth followed by a keyboard-interactive MFA challenge (e.g. a university HPC cluster behind Duo push/OTP) fails immediately after the password is entered: ``` All co | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +1037/−92. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support PowerShell setup scripts on Windows (#16611)1 PR · Standalone · Plugins#
Problem: support PowerShell setup scripts on Windows (#16611).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16611 [Feature]: Support writing the Windows setup script in PowerShell (Fixes, OPEN); #12406 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16616 feat(hooks): support PowerShell setup scripts on Windows (#16611) | Nguyễn Minh Chiến Community · FIRST_TIME_CONTRIBUTOR | #16611 [Feature]: Support writing the Windows setup script in PowerShell Fixes · OPEN #12406 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On Windows, Orca setup scripts and issue commands in `orca.yaml` default to `cmd.exe` unless they start with a bash `#!` line. If an author writes PowerShell in their setup hook, `cmd.exe` fails with syntax error | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +363/−50. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1surface Codex startup dialogs and update flow in chat view2 PRs · Overlapping · Plugins#
Problem: surface Codex startup dialogs and update flow in chat view.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15597 Chat view can't show Codex startup dialogs (update prompt, live update log, or post-update restart) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15600 fix(native-chat): surface Codex startup dialogs and update flow in chat viewDraft | Suzano Community · FIRST_TIME_CONTRIBUTOR | #15597 Chat view can't show Codex startup dialogs (update prompt, live update log, or post-update restart) Fixes · OPEN | Cluster contribution | ## ELI5 When Codex is updating itself or asking a startup question (update available, trust this workspace, etc.), the chat view in Orca shows an empty "Start a chat" box instead of the actual dialog — because chat view | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +2350/−537. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15632 fix(native-chat): surface blocking startup dialogs in the chat view | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15597 Chat view can't show Codex startup dialogs (update prompt, live update log, or post-update restart) Fixes · OPEN | Cluster contribution | ## Summary **What** A pane blocked on a startup dialog now shows an actionable banner in the native chat view, naming the dialog class and offering a switch to the terminal view where it can be answered. Plumbing, in ord | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +339/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1surface merge-queue state as a distinct queued PR state1 PR · Standalone · Plugins#
Problem: surface merge-queue state as a distinct queued PR state.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12316 [Feature]: GitHub queued to merge... status in Checks panel (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16658 feat(github): surface merge-queue state as a distinct queued PR state | Minsu Lee Community · CONTRIBUTOR | #12316 [Feature]: GitHub queued to merge... status in Checks panel Fixes · OPEN | Standalone change | ## ELI5 When your PR is already waiting in GitHub's merge queue, Orca still showed a **Merge when ready** button — as if you still had to put it in the queue. Orca had no way to say "this PR is in the queue", so it fell | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk73 files, +1422/−183. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1switch and create branches from the sidepanel1 PR · Standalone · Plugins#
Problem: switch and create branches from the sidepanel.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16362 [Feature]: Ability to switch and create branch from the sidepanel Source Control UI (Fixes, OPEN); #11571 Title unavailable (Unclear, Unknown); #12984 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16403 feat(source-control): switch and create branches from the sidepanel | Muhammad Ahmad Ali Community · FIRST_TIME_CONTRIBUTOR | #16362 [Feature]: Ability to switch and create branch from the sidepanel Source Control UI Fixes · OPEN #11571 Title unavailable Unclear · Unknown #12984 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The Source Control panel shows which branch you are on, but the name is just text. This makes it a button: click it, search your local branches, switch to one, or type a new name and create it. ## What Changed Th | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk32 files, +1370/−142. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1track Nous Portal usage with credit balances1 PR · Standalone · Plugins#
Problem: track Nous Portal usage with credit balances.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15121 feat(status-bar): track Nous Portal usage with credit balances | Berkay Günaydın Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds a **Nous** provider to the status-bar usage tracker (the provider roster pill in the bottom-left). When a Hermes Nous Portal session exists on disk, a "Nous" row shows: - Usage bar with the consumption pe | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk38 files, +1403/−72. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1unblock pnpm lint and a source assertion on a CRLF checkout1 PR · Standalone · Plugins#
Problem: unblock pnpm lint and a source assertion on a CRLF checkout.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14479 [Bug]: pnpm lint cannot pass on a stock Windows checkout (CRLF line endings) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14481 fix(windows): unblock pnpm lint and a source assertion on a CRLF checkout | JahyunBaek Community · FIRST_TIME_CONTRIBUTOR | #14479 [Bug]: pnpm lint cannot pass on a stock Windows checkout (CRLF line endings) Fixes · OPEN | Standalone change | ## ELI5 On Windows, Git turns line endings into CRLF when it writes files out — that is the default and nobody chooses it. Two things in this repo then compare text and find a difference that isn't really there, so `pnpm | P1 Meaningful core-workflow impact with strategic alignment to Plugins. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +17/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1wait out live OpenCode sqlite locks2 PRs · Overlapping · Automated release pipeline#
Problem: wait out live OpenCode sqlite locks.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #14133 [Bug]: Agent Session History show the database is locked (Fixes, OPEN); #14134 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14134 fix(ai-vault): wait out live OpenCode sqlite locks | BingZ Community · CONTRIBUTOR | #14133 [Bug]: Agent Session History show the database is locked Fixes · OPEN | Cluster contribution | ## ELI5 Orca reads OpenCode's live SQLite database while OpenCode may be writing it. The reader now waits briefly for a lock, stays read-only, and cannot leak a database handle if read-only setup itself fails. ## What Ch | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +238/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15671 fix(ai-vault): handle live OpenCode database contention | Brennan Benson Core team · MEMBER | #14133 [Bug]: Agent Session History show the database is locked Fixes · OPEN #14134 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +478/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1[leas code] Remove expired OMP overlay migration1 PR · Standalone · Automated release pipeline#
Problem: [leas code] Remove expired OMP overlay migration.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7735 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13455 [leas code] Remove expired OMP overlay migration | Neil Core team · MEMBER | #7735 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Remove the temporary OMP source-overlay rescue migration after its documented 2026-08-07 cutoff. - Remove the migration-only source-overlay path lookup and eight migration tests/helpers. - Preserve both old | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +0/−500. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1accept pty:<ptyId> as a terminal selector1 PR · Standalone · Automated release pipeline#
Problem: accept pty:<ptyId> as a terminal selector.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13206 Terminal identity: handles change across restarts and rehydration; make ptyId a first-class selector (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13219 feat(cli): accept pty:<ptyId> as a terminal selector | BingZ Community · CONTRIBUTOR | #13206 Terminal identity: handles change across restarts and rehydration; make ptyId a first-class selector Fixes · OPEN | Standalone change | ## ELI5 Terminal runtime handles can change after Orca restarts, while a terminal's `ptyId` remains stable. The CLI can now accept `--terminal pty:<ptyId>`, resolve it to the current live handle, and document that stable | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +433/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add --no-rotate-pairing flag for a static pairing URL1 PR · Standalone · Automated release pipeline#
Problem: add --no-rotate-pairing flag for a static pairing URL.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13712 feat(serve): add --no-rotate-pairing flag for a static pairing URL | Aarav Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds `--no-rotate-pairing` to `orca serve`. When set, the headless runtime keeps the same pending device across restarts and across pairs, so the printed pairing URL is byte-for-byte stable until the operator | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +103/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add a Linear panel for the workspace's linked issue1 PR · Standalone · Automated release pipeline#
Problem: add a Linear panel for the workspace's linked issue.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12693 [Feature]: Linear issue panel in the right sidebar for the workspace's linked issue (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12698 feat(right-sidebar): add a Linear panel for the workspace's linked issue | Cubatica Community · FIRST_TIME_CONTRIBUTOR | #12693 [Feature]: Linear issue panel in the right sidebar for the workspace's linked issue Fixes · OPEN | Standalone change | Closes #12693 (filed first to ask where you'd want this — happy to rework or drop it if the answer is "not like that"). ## Summary Adds a **`linear` right-sidebar tab** that shows the active workspace's linked Linear iss | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +705/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add a provider-agnostic --needs-attention hook with push notifications1 PR · Standalone · Automated release pipeline#
Problem: add a provider-agnostic --needs-attention hook with push notifications.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12199 feat(worktree): add a provider-agnostic --needs-attention hook with push notifications | Matthew Alexander Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds `orca worktree set --needs-attention <text|null>` so any external tool can flag a worktree as needing attention with a free-form reason, via a documented CLI flag — no more spoofing an internal agent hook | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +1221/−214. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add account-scoped launch selectors1 PR · Standalone · Automated release pipeline#
Problem: add account-scoped launch selectors.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13271 Title unavailable (Unclear, Unknown); #13270 Title unavailable (Unclear, Unknown); #13183 Title unavailable (Unclear, Unknown); #13276 Title unavailable (Unclear, Unknown); #14608 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13272 feat(codex): add account-scoped launch selectors | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13271 Title unavailable Unclear · Unknown #13270 Title unavailable Unclear · Unknown #13183 Title unavailable Unclear · Unknown #13276 Title unavailable Unclear · Unknown #14608 Title unavailable Unclear · Unknown | Standalone change | ## Summary Codex launches now expose account selection in both the quick-launch menu and the Orca CLI. The UI keeps `Current default` available during loading and failures, shows friendly account labels, and sends the ca | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk60 files, +2409/−129. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add an Android emulator harness for device-only repros1 PR · Standalone · Automated release pipeline#
Problem: add an Android emulator harness for device-only repros.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7427 Title unavailable (Unclear, Unknown); #7495 Title unavailable (Unclear, Unknown); #13070 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13366 feat(mobile): add an Android emulator harness for device-only repros | makoto-developer Community · CONTRIBUTOR | #7427 Title unavailable Unclear · Unknown #7495 Title unavailable Unclear · Unknown #13070 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds `pnpm start:emulator:android`, so an Android repro is one command instead of an afternoon. Mobile bugs that only appear under an Android IME keep stalling on "no Android device here": - #7427 — "Japanese | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +608/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Aside as a Chromium cookie-import source1 PR · Standalone · Automated release pipeline#
Problem: add Aside as a Chromium cookie-import source.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12849 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12035 feat(browser): add Aside as a Chromium cookie-import source | doxxx Community · FIRST_TIME_CONTRIBUTOR | #12849 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds **Aside** (`at.studio.AsideBrowser`) to the browser cookie-import sources, so an Orca browser profile can adopt a logged-in Aside session the same way it already can for Chrome, Edge, Arc, Brave, Comet, a | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +182/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add board view, drag-drop, project fields in dialog1 PR · Standalone · Automated release pipeline#
Problem: add board view, drag-drop, project fields in dialog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12302 feat(kanban): add board view, drag-drop, project fields in dialog | Berkay Günaydın Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds a **Board (kanban) view** for GitHub Project `BOARD_LAYOUT` views in the Tasks panel, with drag-and-drop column moves and project field editing in the issue dialog. ### Board view - Rows are grouped by th | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1369/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Cloudflare Tunnel pairing intent1 PR · Standalone · Automated release pipeline#
Problem: add Cloudflare Tunnel pairing intent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14039 [Feature]: Add Cloudflare Tunnel as a pairing target for the browser access link (Fixes, OPEN); #12535 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14040 feat(settings): add Cloudflare Tunnel pairing intent | Pierre-Mike Community · FIRST_TIME_CONTRIBUTOR | #14039 [Feature]: Add Cloudflare Tunnel as a pairing target for the browser access link Fixes · OPEN #12535 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can already hand you a link that opens the whole app in a browser. Today that link only works if the browser can already reach your machine — same Wi-Fi, Tailscale, or an SSH tunnel you set up yourself. This | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +892/−221. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Cursor usage tracking1 PR · Standalone · Automated release pipeline#
Problem: add Cursor usage tracking.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13837 feat(rate-limits): add Cursor usage tracking | Dominik Žabčík Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Shows Cursor plan usage in the status bar, usage roster, Stats, and Accounts when the machine running Orca is signed into Cursor IDE. Auth matches CodexBar: read `cursorAuth/accessToken` (and optional `cachedE | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk56 files, +2232/−101. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add DAP spine — transport, session lifecycle, and host-aware adapter spawn1 PR · Standalone · Automated release pipeline#
Problem: add DAP spine — transport, session lifecycle, and host-aware adapter spawn.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7945 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13281 feat(debug): add DAP spine — transport, session lifecycle, and host-aware adapter spawn | homeshrawat Community · FIRST_TIME_CONTRIBUTOR | #7945 Title unavailable Unclear · Unknown | Standalone change | ## Summary Phase 0 of #7945 (integrated visual debugger). This lands the plumbing every later debugger workstream (breakpoint gutter, session panels, launch-config UI, the real Node/Chrome adapter) builds on top of — no | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk64 files, +4354/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Deepgram Nova-3 dictation1 PR · Standalone · Automated release pipeline#
Problem: add Deepgram Nova-3 dictation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12529 feat(voice): add Deepgram Nova-3 dictation | MaChangH Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Add Deepgram Nova-3 as a Korean cloud dictation provider. - Add settings to configure, replace, and clear a Deepgram API key, with a direct Deepgram Console link. - Keep keys in Electron encrypted storage on | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1191/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add DeepSeek status bar usage provider1 PR · Standalone · Automated release pipeline#
Problem: add DeepSeek status bar usage provider.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12869 [Feature]: DeepSeek usage in the status bar (rate-limit / usage provider) (Fixes, OPEN); #12200 Title unavailable (Unclear, Unknown); #12330 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12873 feat: add DeepSeek status bar usage provider | Wooseong Kim Community · CONTRIBUTOR | #12869 [Feature]: DeepSeek usage in the status bar (rate-limit / usage provider) Fixes · OPEN #12200 Title unavailable Unclear · Unknown #12330 Title unavailable Unclear · Unknown | Standalone change | ## Summary Show **DeepSeek prepaid balance** in the status bar when `DEEPSEEK_API_KEY` is set. Fetches `GET https://api.deepseek.com/user/balance` (Bearer key), prefers the USD balance row, and maps remaining credit into | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +699/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add detached Markdown editor windows1 PR · Standalone · Automated release pipeline#
Problem: add detached Markdown editor windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13441 feat(editor): add detached Markdown editor windows | junteakim Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Add a native detached Markdown editor window from the editor action menu. The popout supports Source, Rich, and Preview modes, Cmd/Ctrl+S, same-document focus reuse, exact dirty tracking, external-change detec | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk40 files, +2645/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add durable conversation wake foundation1 PR · Standalone · Automated release pipeline#
Problem: add durable conversation wake foundation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12033 feat(orchestration): add durable conversation wake foundation | Ramiro Carnicer Souble Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - add a disabled-by-default durable conversation-wake state machine for supervised Run lifecycle messages - add an opt-in, Orca-owned Codex app-server controller with visible remote TUI attachment and exact Ru | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk73 files, +8105/−217. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add fork and child creation actions1 PR · Standalone · Automated release pipeline#
Problem: add fork and child creation actions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12858 feat(worktrees): add fork and child creation actions | lvfen Community · CONTRIBUTOR | None found | Standalone change | ## Summary Add two context-menu actions for quickly creating related worktrees: - **Fork** creates a parallel worktree and defaults its name to `<current>_fork`. - **Create Child** creates a child worktree and defaults i | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +1326/−91. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add GDScript syntax highlighting1 PR · Standalone · Automated release pipeline#
Problem: add GDScript syntax highlighting.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12549 feat(editor): add GDScript syntax highlighting | Wayne Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds first-class GDScript syntax highlighting to Orca text-editor tabs. - Detect `.gd` files and register a lazy TextMate-backed `gdscript` Monaco language. - Vendor Godot Tools’ MIT-licensed GDScript grammar | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +936/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Group by Issue workspace organization1 PR · Standalone · Automated release pipeline#
Problem: add Group by Issue workspace organization.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #5199 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12567 feat(sidebar): add Group by Issue workspace organization | Andres Van Reepingen Community · CONTRIBUTOR | #5199 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The sidebar's workspace list can be grouped by repo or project, but not by the issue you are working on, so worktrees tied to GitHub, Linear, Jira, or GitLab tickets end up scattered. A new "Issue" option under G | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +424/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add inline git blame and file history1 PR · Standalone · Automated release pipeline#
Problem: add inline git blame and file history.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13338 feat: add inline git blame and file history | eric Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds inline Git blame to Monaco file editors and makes per-file Git history easier to reach. - Shows the last commit that touched the active editor line: author, relative time, and commit summary. - Adds a new | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk44 files, +1476/−54. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add keyboard shortcuts to switch AI provider account1 PR · Standalone · Automated release pipeline#
Problem: add keyboard shortcuts to switch AI provider account.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8884 Title unavailable (Unclear, Unknown); #8827 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12792 feat(accounts): add keyboard shortcuts to switch AI provider account | Marcos Tomassi Community · FIRST_TIME_CONTRIBUTOR | #8884 Title unavailable Unclear · Unknown #8827 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds two new global, remappable keyboard shortcuts to jump directly to a host-runtime Claude/Codex account (1-9) without leaving whatever you're doing, with a toast confirming the switch — mirroring the existi | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +497/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add managed accounts1 PR · Standalone · Automated release pipeline#
Problem: add managed accounts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13273 Title unavailable (Unclear, Unknown); #13272 Title unavailable (Unclear, Unknown); #13271 Title unavailable (Unclear, Unknown); #13270 Title unavailable (Unclear, Unknown); #13183 Title unavailable (Unclear, Unknown); #13276 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13274 feat(kimi): add managed accounts | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13273 Title unavailable Unclear · Unknown #13272 Title unavailable Unclear · Unknown #13271 Title unavailable Unclear · Unknown #13270 Title unavailable Unclear · Unknown #13183 Title unavailable Unclear · Unknown #13276 Title unavailable Unclear · Unknown | Standalone change | ## Summary Orca can now create isolated managed Kimi Code accounts through device-code login or import an existing Kimi home by copying only the documented config and credential scope. Each account receives its own owned | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk127 files, +5907/−477. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Odoo as a task provider with ticket panel, chatter and workspace sync1 PR · Standalone · Automated release pipeline#
Problem: add Odoo as a task provider with ticket panel, chatter and workspace sync.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14499 feat(odoo): add Odoo as a task provider with ticket panel, chatter and workspace sync | thba-dynapps Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Orca can talk to an Odoo project instance the same way it already talks to GitHub, GitLab, Linear and Jira: connect a server, browse and filter `project.task` tickets in a kanban or list panel, read and write the | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk281 files, +26144/−415. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add one-tap collapse/expand for all workspace groups1 PR · Standalone · Automated release pipeline#
Problem: add one-tap collapse/expand for all workspace groups.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12411 feat(sidebar): add one-tap collapse/expand for all workspace groups | sudoviber Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Collapsing the workspace list previously required folding each project group one by one. This adds a single toggle that collapses/expands all groups at once, on both desktop and mobile. **Desktop** — new butto | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +527/−78. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Project/Current view toggle and polish card styling1 PR · Standalone · Automated release pipeline#
Problem: add Project/Current view toggle and polish card styling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15156 feat(sidebar): add Project/Current view toggle and polish card styling | Shakib Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - **Project/Current toggle** — replaces the static "Projects" title in the sidebar header with a persisted two-button toggle. **Project** keeps the default grouped workspace list; **Current** narrows the sideb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +80/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add standalone terminal workspace1 PR · Standalone · Automated release pipeline#
Problem: add standalone terminal workspace.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12879 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12887 feat(terminal): add standalone terminal workspace | dngur6344 Community · CONTRIBUTOR | #12879 Title unavailable Unclear · Unknown | Standalone change | ## Summary Add a project-independent terminal section to the left sidebar. Users can open multiple local terminals rooted at their home directory, switch and rename them from the sidebar, and use them in the normal main | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +940/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add terminal shortcut capture notification toggle1 PR · Standalone · Automated release pipeline#
Problem: add terminal shortcut capture notification toggle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14459 [Feature]: Add a setting to disable the 'Terminal shortcut handled' capture toast (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14483 feat(settings): add terminal shortcut capture notification toggle | dngur6344 Community · CONTRIBUTOR | #14459 [Feature]: Add a setting to disable the 'Terminal shortcut handled' capture toast Fixes · OPEN | Standalone change | ## ELI5 Adds a switch in Settings → Shortcuts that lets users hide the one-time toast messages shown when Orca handles a shortcut from a focused terminal. Shortcut handling itself does not change. ## What Changed - Added | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +281/−41. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add zh-TW (Traditional Chinese) locale1 PR · Standalone · Automated release pipeline#
Problem: add zh-TW (Traditional Chinese) locale.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14223 feat(i18n): add zh-TW (Traditional Chinese) localeDraft | WU, CHI-LUNG Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Orca can now run its interface in Traditional Chinese. If your system is set to Taiwan, Hong Kong, or Macau, you get it automatically instead of falling back to English, and you can also pick 繁體中文 from Settings → | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +14932/−28. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1answer an over-capacity response instead of closing the client1 PR · Standalone · Automated release pipeline#
Problem: answer an over-capacity response instead of closing the client.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11943 [Bug]: Accumulated orphaned relay PTYs cause 'Relay control publication capacity exceeded' on reconnect; client permanently disposes multiplexer instead of reconnecting (Fixes, OPEN); #11999 Title unavailable (Unclear, Unknown); #11917 Title unavailable (Unclear, Unknown); #8585 Title unavailable (Unclear, Unknown); #9819 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12068 fix(relay): answer an over-capacity response instead of closing the client | Neil Core team · MEMBER | #11943 [Bug]: Accumulated orphaned relay PTYs cause 'Relay control publication capacity exceeded' on reconnect; client permanently disposes multiplexer instead of reconnecting Fixes · OPEN #11999 Title unavailable Unclear · Unknown #11917 Title unavailable Unclear · Unknown #8585 Title unavailable Unclear · Unknown #9819 Title unavailable Unclear · Unknown | Standalone change | Fixes #11943 ## ELI5 When your laptop reconnects to a remote machine, it asks the remote helper program to hand back the recent screen contents for every terminal you had open — all at once. Each of those answers can be | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +250/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1ask before bulk-closing tabs with running work1 PR · Standalone · Automated release pipeline#
Problem: ask before bulk-closing tabs with running work.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16406 feat(terminal): ask before bulk-closing tabs with running work | Neil Core team · MEMBER | None found | Standalone change | ## Problem Closing a single terminal tab asks before killing a live child process. Every **bulk** close deliberately skipped that prompt: ```ts // No running-process prompt: "Close Others" over N busy tabs would be a mod | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1091/−218. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1attach extra reviews and track sibling branches on the worktree card (#9213)1 PR · Standalone · Automated release pipeline#
Problem: attach extra reviews and track sibling branches on the worktree card (#9213).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9213 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13374 feat(worktree): attach extra reviews and track sibling branches on the worktree card (#9213) | Eugenio Jesus Jose Valeiras Community · CONTRIBUTOR | #9213 Title unavailable Unclear · Unknown | Standalone change | ## Motivation A change that fans out to several destinations — the same work cherry-picked to a release branch and a stage branch, or one branch opening PRs against multiple bases — is invisible on the worktree card toda | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk48 files, +2000/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1attribute usage to launch accounts1 PR · Standalone · Automated release pipeline#
Problem: attribute usage to launch accounts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13272 Title unavailable (Unclear, Unknown); #13271 Title unavailable (Unclear, Unknown); #13270 Title unavailable (Unclear, Unknown); #13183 Title unavailable (Unclear, Unknown); #13276 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13273 feat(codex): attribute usage to launch accounts | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13272 Title unavailable Unclear · Unknown #13271 Title unavailable Unclear · Unknown #13270 Title unavailable Unclear · Unknown #13183 Title unavailable Unclear · Unknown #13276 Title unavailable Unclear · Unknown | Standalone change | ## Summary Codex usage events and rollups can now retain an optional launch-account attribution. The scanner combines managed-home roots with bounded session-launch evidence, keeps same-day usage from different accounts | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk88 files, +3565/−439. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1authenticate via az CLI Entra login with token fallback1 PR · Standalone · Automated release pipeline#
Problem: authenticate via az CLI Entra login with token fallback.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11125 Title unavailable (Unclear, Unknown); #111 Title unavailable (Unclear, Unknown); #12832 Title unavailable (Unclear, Unknown); #15746 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12201 feat(azure-devops): authenticate via az CLI Entra login with token fallback | Yoyo Community · CONTRIBUTOR | #11125 Title unavailable Unclear · Unknown #111 Title unavailable Unclear · Unknown #12832 Title unavailable Unclear · Unknown #15746 Title unavailable Unclear · Unknown | Standalone change | ## Summary Azure DevOps requests now authenticate through the Azure CLI's existing `az login` when no `ORCA_AZURE_DEVOPS_*` token is configured, mirroring how GitHub and GitLab delegate credentials to `gh`/`glab`. Creati | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +642/−64. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1automatically close merged workspaces1 PR · Standalone · Automated release pipeline#
Problem: automatically close merged workspaces.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14537 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14042 feat(worktrees): automatically close merged workspaces | huchister Community · FIRST_TIME_CONTRIBUTOR | #14537 Title unavailable Unclear · Unknown | Standalone change | ### Summary When a workspace's branch has landed in its base, Orca can now close the workspace automatically: terminals are torn down, the git worktree is removed, tracking state and caches are purged, and the orphaned b | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1911/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Beads (bd) local issue tracker as a task source1 PR · Standalone · Automated release pipeline#
Problem: Beads (bd) local issue tracker as a task source.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7268 [Feature] Beads as a Task Source (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14013 feat(tasks): Beads (bd) local issue tracker as a task source | ajchemist Community · FIRST_TIME_CONTRIBUTOR | #7268 [Feature] Beads as a Task Source Fixes · CLOSED | Standalone change | ## ELI5 Your repo can now be its own issue tracker. If a project uses [Beads](https://beads.gascity.com) (`bd`), the Tasks page grows a fifth source next to GitHub/GitLab/Linear/Jira that lists, filters, and opens those | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk114 files, +9551/−156. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bind projects to a specific gh account1 PR · Standalone · Automated release pipeline#
Problem: bind projects to a specific gh account.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13612 [Bug]: Create-worktree GitHub issue/PR search ignores directory-scoped GH_TOKEN (direnv) and uses the globally active gh account (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13664 feat(github): bind projects to a specific gh account | Leo Levintza Community · FIRST_TIME_CONTRIBUTOR | #13612 [Bug]: Create-worktree GitHub issue/PR search ignores directory-scoped GH_TOKEN (direnv) and uses the globally active gh account Fixes · OPEN | Standalone change | ## ELI5 If you're logged into `gh` with two GitHub accounts — work and personal — Orca used whichever one was globally active for every project. So opening the create-worktree dialog on a work repo could search issues as | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +2161/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bound host tunnel memory1 PR · Standalone · Automated release pipeline#
Problem: bound host tunnel memory.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14495 Title unavailable (Unclear, Unknown); #14402 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14504 feat(browser): bound host tunnel memoryDraft | Jinwoo Hong Core team · MEMBER | #14495 Title unavailable Unclear · Unknown #14402 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +1276/−159. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bound POSIX hook stdin so agy cannot hang loading1 PR · Standalone · Automated release pipeline#
Problem: bound POSIX hook stdin so agy cannot hang loading.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15117 Title unavailable (Unclear, Unknown); #11549 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15821 fix(antigravity): bound POSIX hook stdin so agy cannot hang loading | Brennan Benson Core team · MEMBER | #15117 Title unavailable Unclear · Unknown #11549 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +389/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bound tunnel route resources1 PR · Standalone · Automated release pipeline#
Problem: bound tunnel route resources.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14493 Title unavailable (Unclear, Unknown); #14402 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14495 feat(browser): bound tunnel route resourcesDraft | Jinwoo Hong Core team · MEMBER | #14493 Title unavailable Unclear · Unknown #14402 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +485/−72. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bridge client page renderer mounts1 PR · Standalone · Automated release pipeline#
Problem: bridge client page renderer mounts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14566 Title unavailable (Unclear, Unknown); #14440 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14578 feat(browser): bridge client page renderer mountsDraft | Jinwoo Hong Core team · MEMBER | #14566 Title unavailable Unclear · Unknown #14440 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1375/−54. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1browser action recorder with agent-ready session logs1 PR · Standalone · Automated release pipeline#
Problem: browser action recorder with agent-ready session logs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12542 feat(browser): browser action recorder with agent-ready session logs | Berkay Günaydın Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## What this does Adds a **browser action recorder** to the browser pane that captures every user interaction, network request, console message, WebSocket frame, clipboard operation, and storage write into a structured, | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk61 files, +8091/−292. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1canonical agent-session journal with crash-safe receipts and epoch cursors (phase 1c)1 PR · Standalone · Automated release pipeline#
Problem: canonical agent-session journal with crash-safe receipts and epoch cursors (phase 1c).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13085 feat(native-chat): canonical agent-session journal with crash-safe receipts and epoch cursors (phase 1c) | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary Adds the canonical host-side journal for an agent session. Nothing is wired up: no RPC, no provider adapters, no UI. The journal is dormant until a later phase feeds it, so behavior for existing sessions is un | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +4933/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Claude structured chat — full migration (adapter, translation, desktop + mobile clients)1 PR · Standalone · Automated release pipeline#
Problem: Claude structured chat — full migration (adapter, translation, desktop + mobile clients).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13578 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13584 feat(native-chat): Claude structured chat — full migration (adapter, translation, desktop + mobile clients) | Brennan Benson Core team · MEMBER | #13578 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Adds an explicit Claude Chat choice beside Codex Chat only when the runtime capability, detected/enabled agent, and host workspace-support gates all pass. Structured chat remains opt-in and never becomes the | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk142 files, +9991/−1083. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1compose paired client host lifecycle1 PR · Standalone · Automated release pipeline#
Problem: compose paired client host lifecycle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14557 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14558 feat(browser): compose paired client host lifecycleDraft | Jinwoo Hong Core team · MEMBER | #14557 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +766/−41. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1compose paired client host runtime1 PR · Standalone · Automated release pipeline#
Problem: compose paired client host runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14596 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14613 feat(browser): compose paired client host runtimeDraft | Jinwoo Hong Core team · MEMBER | #14596 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +1655/−72. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1configure creation stage timeouts1 PR · Standalone · Automated release pipeline#
Problem: configure creation stage timeouts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9865 [Bug]: SSH worktree creation times out after 30s on large repositories (Fixes, OPEN); #9903 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13026 feat(worktree): configure creation stage timeouts | GhostFlying Community · FIRST_TIME_CONTRIBUTOR | #9865 [Bug]: SSH worktree creation times out after 30s on large repositories Fixes · OPEN #9903 Title unavailable Unclear · Unknown | Standalone change | ## Summary Large repositories can spend significantly longer than the fixed defaults in base-ref refresh, checkout, registration, or post-create file materialization. This caused otherwise healthy worktree creation to be | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk71 files, +8609/−953. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1convert non-Git folders to Git repositories from the import dialog1 PR · Standalone · Automated release pipeline#
Problem: convert non-Git folders to Git repositories from the import dialog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #3839 [Feature]: Option to convert Non-Git repository folders into Git to leverage full features (Fixes, OPEN); #6171 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12914 feat: convert non-Git folders to Git repositories from the import dialog | gatsby74 Community · CONTRIBUTOR | #3839 [Feature]: Option to convert Non-Git repository folders into Git to leverage full features Fixes · OPEN #6171 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If you add a plain folder to Orca that isn't a Git repository, worktrees don't work — today you'd have to remove it, run Git commands yourself, and import it again. This adds a **Convert to Git Repository** butto | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +1641/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1copy markdown from the panel header1 PR · Standalone · Automated release pipeline#
Problem: copy markdown from the panel header.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14526 [Feature]: Copy markdown from the editor panel header (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14528 feat(editor): copy markdown from the panel header | 5unnyWind Community · FIRST_TIME_CONTRIBUTOR | #14526 [Feature]: Copy markdown from the editor panel header Fixes · OPEN | Standalone change | ## ELI5 Markdown tabs now have a copy button in the header. It puts the current file text on the clipboard, including edits you have not saved yet. ## What Changed Added a Copy icon on markdown edit/preview headers (not | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +445/−43. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1cpu/memory/uptime columns, shared sort, and a ports memory sparkline1 PR · Standalone · Automated release pipeline#
Problem: cpu/memory/uptime columns, shared sort, and a ports memory sparkline.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14972 feat(status-bar,ports): cpu/memory/uptime columns, shared sort, and a ports memory sparkline | heslanx Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Ports popover and sidebar panel now show **CPU%, RSS, and Uptime** per listening process, sourced from the `ps`/`lsof` calls the port scanner already runs (macOS/Linux `pcpu`/`rss`/`etime`; Windows CIM `Work | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +2157/−497. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1create child worktrees from the composer1 PR · Standalone · Automated release pipeline#
Problem: create child worktrees from the composer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #123 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14201 feat(worktrees): create child worktrees from the composer | Neil Core team · MEMBER | #123 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Creating a workspace can now optionally place it beneath another Orca worktree. The active eligible worktree is selected by default, and the picker puts recently used parents first. ## What Changed - Added a “Mak | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk34 files, +4586/−225. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1deploy, activate and roll back a versioned orcad install1 PR · Standalone · Automated release pipeline#
Problem: deploy, activate and roll back a versioned orcad install.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16375 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16384 feat(orcad): deploy, activate and roll back a versioned orcad install | Neil Core team · MEMBER | #16375 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +4087/−222. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1discard restores the working tree from the index, not HEAD1 PR · Standalone · Automated release pipeline#
Problem: discard restores the working tree from the index, not HEAD.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16424 [Bug] Orca discards staged changes when discarding unstaged changes (Fixes, OPEN); #5880 Title unavailable (Unclear, Unknown); #11173 Title unavailable (Unclear, Unknown); #16393 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16440 fix(git): discard restores the working tree from the index, not HEAD | Max Hsu Community · FIRST_TIME_CONTRIBUTOR | #16424 [Bug] Orca discards staged changes when discarding unstaged changes Fixes · OPEN #5880 Title unavailable Unclear · Unknown #11173 Title unavailable Unclear · Unknown #16393 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You stage some work, keep editing the same file, then decide the *newest* edits were a mistake and hit Discard. Orca threw away the staged work too. If the file was brand new, Orca deleted it off your disk. This | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +87/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1discover native session models from the runtime1 PR · Standalone · Automated release pipeline#
Problem: discover native session models from the runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13276 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13183 feat(codex): discover native session models from the runtime | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13276 Title unavailable Unclear · Unknown | Standalone change | ## Suggested title `feat(codex): discover native session models from the runtime` ## Summary Native Codex session controls now discover the models exposed by the effective runtime instead of relying only on the static se | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +356/−50. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1discover repos inside a git parent and surface their change counts1 PR · Standalone · Automated release pipeline#
Problem: discover repos inside a git parent and surface their change counts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #6957 Title unavailable (Unclear, Unknown); #7086 Title unavailable (Unclear, Unknown); #3534 Title unavailable (Unclear, Unknown); #2866 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13102 feat(nested-repos): discover repos inside a git parent and surface their change counts | ifobos Community · FIRST_TIME_CONTRIBUTOR | #6957 Title unavailable Unclear · Unknown #7086 Title unavailable Unclear · Unknown #3534 Title unavailable Unclear · Unknown #2866 Title unavailable Unclear · Unknown | Standalone change | ## Summary A repo holding other independent repos was a blind spot: adding the parent registered only the parent, and each nested repo's pending work stayed invisible unless you selected it. Discovery and change counts s | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk41 files, +2458/−95. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1enable structured chat/TUI toggle1 PR · Standalone · Automated release pipeline#
Problem: enable structured chat/TUI toggle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13438 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14601 feat(native-chat): enable structured chat/TUI toggle | Brennan Benson Core team · MEMBER | #13438 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 This stacked follow-up puts back the controls that move one structured Codex session between the chat UI and its agent terminal. ## What Changed - Restores `Open agent TUI`, queued/stop-and-switch actions, switch | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +1298/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1ensure DACL allows renderer bootstrap in packaged installs1 PR · Standalone · Automated release pipeline#
Problem: ensure DACL allows renderer bootstrap in packaged installs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17143 fix(win32): ensure DACL allows renderer bootstrap in packaged installs | OrcaWin Unknown · COLLABORATOR | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Ready · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +37/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1execute client page commands locally1 PR · Standalone · Automated release pipeline#
Problem: execute client page commands locally.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14558 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14566 feat(browser): execute client page commands locallyDraft | Jinwoo Hong Core team · MEMBER | #14558 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1390/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Feat/editor git gutter and new file1 PR · Standalone · Automated release pipeline#
Problem: Feat/editor git gutter and new file.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13447 Feat/editor git gutter and new file | LingyiChen-AI Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Describe the user-visible change. ## Screenshots - Add screenshots or a screen recording for any new or changed UI behavior. - If there is no visual change, say `No visual change`. ## Testing - [ ] `pnpm lint` | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +2677/−130. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1fence client host leases1 PR · Standalone · Automated release pipeline#
Problem: fence client host leases.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14470 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14484 feat(browser): fence client host leasesDraft | Jinwoo Hong Core team · MEMBER | #14470 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +1518/−84. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1fence route pages to renderer owners1 PR · Standalone · Automated release pipeline#
Problem: fence route pages to renderer owners.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14519 Title unavailable (Unclear, Unknown); #14471 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14520 feat(browser): fence route pages to renderer ownersDraft | Jinwoo Hong Core team · MEMBER | #14519 Title unavailable Unclear · Unknown #14471 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +766/−225. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1file icon theme picker with Symbols support1 PR · Standalone · Automated release pipeline#
Problem: file icon theme picker with Symbols support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15131 feat(appearance): file icon theme picker with Symbols support | Daniel Henrique Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Adds a **File Icons** setting in Settings → Appearance that lets users switch between icon themes - Ships the **Symbols** icon set (248 SVGs from [miguelsolorio/vscode-symbols](https://github.com/miguelsolor | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk266 files, +6577/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1filter the workspace list by status1 PR · Standalone · Automated release pipeline#
Problem: filter the workspace list by status.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13971 feat(sidebar): filter the workspace list by status | Jihoon Lee Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## What Adds a **Status** row to the sidebar workspace options menu (⚙ → Show → Status) with a checkbox per workspace status. Unchecking a status hides its workspaces from the sidebar list. Motivation: finished work pile | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +513/−127. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1give a Run a parent Run1 PR · Standalone · Automated release pipeline#
Problem: give a Run a parent Run.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13639 Title unavailable (Unclear, Unknown); #13362 Title unavailable (Unclear, Unknown); #13648 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15263 feat(orchestration): give a Run a parent Run | Taras Kornichuk Community · CONTRIBUTOR | #13639 Title unavailable Unclear · Unknown #13362 Title unavailable Unclear · Unknown #13648 Title unavailable Unclear · Unknown | Standalone change | A Run can now record the Run it nests under, so a nested wave can be walked from either end instead of living as prose in an objective string. ## The problem Waves are shaped GENERAL → CAPTAIN → workers: a coordinator di | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +563/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1group Copy path/branch/PR-MR URL in the worktree row menu1 PR · Standalone · Automated release pipeline#
Problem: group Copy path/branch/PR-MR URL in the worktree row menu.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #6167 [Feature]: add more "Copy XXX" menu item (Fixes, OPEN); #6728 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12240 feat(sidebar): group Copy path/branch/PR-MR URL in the worktree row menu | Neil Core team · MEMBER | #6167 [Feature]: add more "Copy XXX" menu item Fixes · OPEN #6728 Title unavailable Unclear · Unknown | Standalone change | ## Description The sidebar worktree row context menu only offered a single loose **Copy Path** item. There was no way to copy the worktree's branch name or the URL of its linked pull request / merge request without leavi | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +790/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1host-routed proxy for workspace dev servers, configurable from settings1 PR · Standalone · Automated release pipeline#
Problem: host-routed proxy for workspace dev servers, configurable from settings.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13318 feat(preview): host-routed proxy for workspace dev servers, configurable from settings | Erik Ferreira Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds an opt-in **preview proxy** so browsers — including the web client, which cannot SSH-tunnel — can open workspace dev servers directly instead of through the screencast-backed embedded browser. One HTTP li | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk48 files, +3521/−157. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1inline git blame for the cursor line, plus a status-bar segment1 PR · Standalone · Automated release pipeline#
Problem: inline git blame for the cursor line, plus a status-bar segment.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9948 Feature request: Git blame / line annotation in the editor (Fixes, OPEN); #13338 Title unavailable (Unclear, Unknown); #7737 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13321 feat(editor): inline git blame for the cursor line, plus a status-bar segment | Matt Tuusberg Community · FIRST_TIME_CONTRIBUTOR | #9948 Feature request: Git blame / line annotation in the editor Fixes · OPEN #13338 Title unavailable Unclear · Unknown #7737 Title unavailable Unclear · Unknown | Standalone change | Closes #9948. > **Overlap note for maintainers:** #13338 covers the same feature and is still open. Flagging it so you can pick a direction rather than review two overlapping PRs blind. > > The two now take a similar cac | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk61 files, +3146/−108. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1iTerm-style Ctrl/Cmd modifier remap on macOS1 PR · Standalone · Automated release pipeline#
Problem: iTerm-style Ctrl/Cmd modifier remap on macOS.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12009 [Feature]: iTerm-style global Ctrl↔Cmd modifier remap on macOS (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12019 feat(shortcuts): iTerm-style Ctrl/Cmd modifier remap on macOS | Jiwen Cai Community · FIRST_TIME_CONTRIBUTOR | #12009 [Feature]: iTerm-style global Ctrl↔Cmd modifier remap on macOS Fixes · OPEN | Standalone change | Closes #12009. Adds a macOS-only `modifierRemap` setting (`'none' | 'swap-ctrl-cmd'`, default `'none'`) that exchanges Ctrl and Cmd, the way iTerm2's **Preferences → Keys → Remap Modifiers** does. Deliberately not the fu | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +625/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1kanban board view for Jira issues in the Tasks panel1 PR · Standalone · Automated release pipeline#
Problem: kanban board view for Jira issues in the Tasks panel.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9943 Title unavailable (Unclear, Unknown); #10186 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13054 feat(jira): kanban board view for Jira issues in the Tasks panel | Eugenio Jesus Jose Valeiras Community · CONTRIBUTOR | #9943 Title unavailable Unclear · Unknown #10186 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds a **List / Board toggle** to the Jira panel in Tasks, rendering issues as a kanban board — mirroring the existing Linear board pattern. ### Board view - Columns come from `groupJiraIssuesByStatus`, so the | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1229/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let a session continue on a different host1 PR · Standalone · Automated release pipeline#
Problem: let a session continue on a different host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16100 Title unavailable (Unclear, Unknown); #8086 Title unavailable (Unclear, Unknown); #6270 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16105 feat(agents): let a session continue on a different hostDraft | gatsby74 Community · CONTRIBUTOR | #16100 Title unavailable Unclear · Unknown #8086 Title unavailable Unclear · Unknown #6270 Title unavailable Unclear · Unknown | Standalone change | > **Draft — a starting point, not a finished feature.** This works end to end and is fully tested, but it is deliberately a narrow slice and I have not yet captured the UI recording. I am putting it up mainly so there is | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +1776/−60. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let users pick a custom icon for "Open in" apps1 PR · Standalone · Automated release pipeline#
Problem: let users pick a custom icon for "Open in" apps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13635 [Feature]: Let users set a custom icon for "Open in" apps they add (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13879 feat(settings): let users pick a custom icon for "Open in" apps | Jerry Lin Community · FIRST_TIME_CONTRIBUTOR | #13635 [Feature]: Let users set a custom icon for "Open in" apps they add Fixes · OPEN | Standalone change | Closes #13635 Adds a per-row icon picker to **Settings → General → Open In Apps**, so an entry you add yourself no longer renders as another generic `AppWindow` glyph. ## What you can pick - **A bundled glyph** — 16 luci | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1241/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1LSP support in the editor and diff views (tsgo-first)1 PR · Standalone · Automated release pipeline#
Problem: LSP support in the editor and diff views (tsgo-first).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14872 Editor lacks language intelligence (LSP): no real hover types, cross-file navigation, or accurate diagnostics (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14873 feat(editor): LSP support in the editor and diff views (tsgo-first) | Moishi Netzer Community · FIRST_TIME_CONTRIBUTOR | #14872 Editor lacks language intelligence (LSP): no real hover types, cross-file navigation, or accurate diagnostics Fixes · OPEN | Standalone change | ## ELI5 Orca's editor now understands your code the way VS Code does. When you have a language server installed (tsgo, pyright, gopls, rust-analyzer…), hovering a symbol shows its real type, cmd+click jumps to its defini | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk34 files, +2377/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1make nested workspace drops reliable1 PR · Standalone · Automated release pipeline#
Problem: make nested workspace drops reliable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13446 fix(sidebar): make nested workspace drops reliableDraft | Neil Core team · MEMBER | None found | Standalone change | # ⚠️ Still acts funky IMO -Neil ## Summary - make the full worktree-owned surface, including long agent lists, a reliable nesting target while retaining explicit reorder gutters - use static virtual-row geometry and boun | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1615/−128. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1make renderer memory attribution honest about what it cannot explain1 PR · Standalone · Automated release pipeline#
Problem: make renderer memory attribution honest about what it cannot explain.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12622 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12940 fix(crash-reporting): make renderer memory attribution honest about what it cannot explainDraft | Jinwoo Hong Core team · MEMBER | #12622 Title unavailable Unclear · Unknown | Standalone change | ## Summary Orca's renderer leak instrumentation currently explains **0.4%** of the leak it exists to explain. This PR does not fix the leak — it makes a crash report able to say *"we cannot account for 3.8 GB of this"* i | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +560/−289. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1migrate workspace UI to hybrid WebView1 PR · Standalone · Automated release pipeline#
Problem: migrate workspace UI to hybrid WebView.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13386 feat(mobile): migrate workspace UI to hybrid WebViewDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 438 | $\color{#1a7f37}{\Huge{\math | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1488 files, +150981/−11053. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1move freeze-prone sync fs off the main thread1 PR · Standalone · Automated release pipeline#
Problem: move freeze-prone sync fs off the main thread.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11931 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12015 fix(main): move freeze-prone sync fs off the main thread | Neil Core team · MEMBER | #11931 Title unavailable Unclear · Unknown | Standalone change | ## What A synchronous fs syscall on the Electron main thread parks the entire app when its target is on a stalled mount (SMB/NFS, VPN drop, sleeping NAS, unmounted external drive). The app stops repainting and stops answ | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk97 files, +8044/−2118. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1multi-branch Git Graph view with worktree overlay1 PR · Standalone · Automated release pipeline#
Problem: multi-branch Git Graph view with worktree overlay.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14047 feat(git): multi-branch Git Graph view with worktree overlay | Eugenio Jesus Jose Valeiras Community · CONTRIBUTOR | None found | Standalone change | ## What A whole-repo commit graph in the center pane — every branch, remote, and tag with colored lanes, decorated ref pills, and Orca's differentiator: branches checked out in an Orca worktree show a live badge (agent w | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk44 files, +1390/−91. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1name remote terminal sessions instead of showing pids1 PR · Standalone · Automated release pipeline#
Problem: name remote terminal sessions instead of showing pids.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16005 [Feature]: Name remote terminal sessions in the Resource Manager instead of showing raw pids (Fixes, OPEN); #16000 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16006 feat(resource-manager): name remote terminal sessions instead of showing pidsDraft | gatsby74 Community · CONTRIBUTOR | #16005 [Feature]: Name remote terminal sessions in the Resource Manager instead of showing raw pids Fixes · OPEN #16000 Title unavailable Unclear · Unknown | Standalone change | > **Stacked on #16000 — draft until that merges.** > This branch is cut from `feat/remote-runtime-resource-manager`, because the remote snapshot path it enriches only exists there. GitHub therefore shows #16000's commits | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +2088/−316. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open .xlsx and .xlsm workbooks in a sheet viewer1 PR · Standalone · Automated release pipeline#
Problem: open .xlsx and .xlsm workbooks in a sheet viewer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #0 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13532 feat(editor): open .xlsx and .xlsm workbooks in a sheet viewer | Markel Alvarado Community · FIRST_TIME_CONTRIBUTOR | #0 Title unavailable Unclear · Unknown | Standalone change | ## Summary Opening an `.xlsx` file in Orca showed **"Binary file — cannot display"**. The read path had no mime type for workbooks, so they fell through to the generic binary placeholder — even though the editor already | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk102 files, +16247/−160. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open a workspace from the worktree ring popover1 PR · Standalone · Automated release pipeline#
Problem: open a workspace from the worktree ring popover.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10716 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14645 feat(agent-map): open a workspace from the worktree ring popover | Brennan Benson Core team · MEMBER | #10716 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The agent map lets you start agents in a workspace, but there was no way to actually *go* to that workspace. This adds a small button in the workspace popover that takes you there. ## What Changed - **New button* | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +444/−144. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open agent details in slideout drawer1 PR · Standalone · Automated release pipeline#
Problem: open agent details in slideout drawer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #123 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12185 feat(dashboard): open agent details in slideout drawer | Brennan Benson Core team · MEMBER | #123 Title unavailable Unclear · Unknown | Standalone change | ## Summary - opens each dashboard agent in the same mode as its exact active pane: native chat when that session is currently showing native chat, otherwise the live terminal - allows a chat-mode inspector to switch to t | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk72 files, +3528/−1090. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open custom app scheme links with user approval1 PR · Standalone · Automated release pipeline#
Problem: open custom app scheme links with user approval.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13225 Title unavailable (Unclear, Unknown); #13609 Title unavailable (Unclear, Unknown); #13566 Title unavailable (Unclear, Unknown); #13710 Title unavailable (Unclear, Unknown); #13692 Title unavailable (Unclear, Unknown); #13691 Title unavailable (Unclear, Unknown); #13536 Title unavailable (Unclear, Unknown); #13572 Title unavailable (Unclear, Unknown); #8072 Title unavailable (Unclear, Unknown); #13570 Title unavailable (Unclear, Unknown); #13561 Title unavailable (Unclear, Unknown); #13255 Title unavailable (Unclear, Unknown); #13240 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13237 feat(terminal): open custom app scheme links with user approval | BingZ Community · CONTRIBUTOR | #13225 Title unavailable Unclear · Unknown #13609 Title unavailable Unclear · Unknown #13566 Title unavailable Unclear · Unknown #13710 Title unavailable Unclear · Unknown #13692 Title unavailable Unclear · Unknown #13691 Title unavailable Unclear · Unknown #13536 Title unavailable Unclear · Unknown #13572 Title unavailable Unclear · Unknown #8072 Title unavailable Unclear · Unknown #13570 Title unavailable Unclear · Unknown #13561 Title unavailable Unclear · Unknown #13255 Title unavailable Unclear · Unknown #13240 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Terminal WebLinks also match custom app schemes (`obsidian://`, `vscode://`, …). - Clicking a custom scheme routes to `shell:openUrl`, which shows a confirm dialog with the full URL before `shell.openExterna | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +350/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open Explorer-dragged files in a split pane1 PR · Standalone · Automated release pipeline#
Problem: open Explorer-dragged files in a split pane.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13970 [Feature]: Drag a file from the File Explorer onto a pane to open it there, splitting on edge drops (Fixes, OPEN); #289 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13982 feat(tab-group): open Explorer-dragged files in a split pane | Soohan Park Community · FIRST_TIME_CONTRIBUTOR | #13970 [Feature]: Drag a file from the File Explorer onto a pane to open it there, splitting on edge drops Fixes · OPEN #289 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Drag a file out of the File Explorer, drop it on the edge of a pane, and that pane splits with your file opened in the new half. Drop it in the middle of a terminal and nothing changes — the path still goes into | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +954/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1open files with the system default app or a picked app1 PR · Standalone · Automated release pipeline#
Problem: open files with the system default app or a picked app.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12866 feat(file-explorer): open files with the system default app or a picked app | KevinZhangv5 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary The file explorer could only *reveal* an entry in Finder/File Explorer. This adds two ways to actually open it: - **Open with Default App** (`Mod+O`, configurable in Settings → Shortcuts) hands the path to the | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +2013/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1opt-in setting to terminate sessions on quit1 PR · Standalone · Automated release pipeline#
Problem: opt-in setting to terminate sessions on quit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7783 [Bug]: macOS Orca Helper leaves agent terminal processes running after app/runtime is closed (Fixes, OPEN); #7806 Title unavailable (Unclear, Unknown); #9195 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14652 feat(terminal): opt-in setting to terminate sessions on quit | tehKayd Community · FIRST_TIME_CONTRIBUTOR | #7783 [Bug]: macOS Orca Helper leaves agent terminal processes running after app/runtime is closed Fixes · OPEN #7806 Title unavailable Unclear · Unknown #9195 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Today, quitting Orca doesn't stop your terminals — a background daemon keeps every session (including running coding agents) alive so they can reattach warm on relaunch. That's great until you *want* quit to mean | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +179/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1optional Pake web-shell plus renderer occupancy proof1 PR · Standalone · Automated release pipeline#
Problem: optional Pake web-shell plus renderer occupancy proof.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15334 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15338 feat(packaging): optional Pake web-shell plus renderer occupancy proofDraft | s546126 Community · CONTRIBUTOR | #15334 Title unavailable Unclear · Unknown | Standalone change | <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## ELI5 Orca’s real desktop app is still Electron. This PR adds an optional extra recipe that can wrap the already-built web client (`pnpm build:web`) in a tiny Tauri/Pake window, plus | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +974/−113. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1orchestrate page reconciliation1 PR · Standalone · Automated release pipeline#
Problem: orchestrate page reconciliation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14763 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14769 feat(browser): orchestrate page reconciliationDraft | Jinwoo Hong Core team · MEMBER | #14763 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1336/−79. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1per-agent terminal theme overrides in Appearance1 PR · Standalone · Automated release pipeline#
Problem: per-agent terminal theme overrides in Appearance.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14174 Per-agent terminal theme overrides in Settings → Appearance (Fixes, OPEN); #13908 Title unavailable (Unclear, Unknown); #7257 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14293 feat(settings): per-agent terminal theme overrides in Appearance | Ed Zisk Community · FIRST_TIME_CONTRIBUTOR | #14174 Per-agent terminal theme overrides in Settings → Appearance Fixes · OPEN #13908 Title unavailable Unclear · Unknown #7257 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can theme every terminal, but all agents share that one theme, so five side-by-side agent panes look identical. This adds per-agent theme overrides: give Claude a cream theme and Codex Dracula, and each pane | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk66 files, +3412/−474. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1per-file progress and cancel for files dropped onto a remote workspace1 PR · Standalone · Automated release pipeline#
Problem: per-file progress and cancel for files dropped onto a remote workspace.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16077 [Feature]: Show progress while uploading dropped files to a remote workspace (Fixes, OPEN); #16106 Title unavailable (Unclear, Unknown); #15987 Title unavailable (Unclear, Unknown); #9896 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16107 feat(runtime): per-file progress and cancel for files dropped onto a remote workspace | gatsby74 Community · CONTRIBUTOR | #16077 [Feature]: Show progress while uploading dropped files to a remote workspace Fixes · OPEN #16106 Title unavailable Unclear · Unknown #15987 Title unavailable Unclear · Unknown #9896 Title unavailable Unclear · Unknown | Standalone change | Fixes #16077 > Stacked on #16106 (`feat/stream-runtime-upload-staging`). Please merge that first — this branch is based on it, so the diff here will shrink to just the progress/cancel work once it lands. ## The problem D | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +2693/−505. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1prepare route-scoped Electron partitions1 PR · Standalone · Automated release pipeline#
Problem: prepare route-scoped Electron partitions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14402 Title unavailable (Unclear, Unknown); #14513 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14516 feat(browser): prepare route-scoped Electron partitionsDraft | Jinwoo Hong Core team · MEMBER | #14402 Title unavailable Unclear · Unknown #14513 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +1168/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1preserve client host through reconnect grace1 PR · Standalone · Automated release pipeline#
Problem: preserve client host through reconnect grace.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14648 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14691 feat(browser): preserve client host through reconnect graceDraft | Jinwoo Hong Core team · MEMBER | #14648 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 12 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +2786/−342. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1preserve executor across authority changes1 PR · Standalone · Automated release pipeline#
Problem: preserve executor across authority changes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14876 feat(browser): preserve executor across authority changesDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +1208/−287. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1prove node-pty loads before anything requires it1 PR · Standalone · Automated release pipeline#
Problem: prove node-pty loads before anything requires it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16370 Title unavailable (Unclear, Unknown); #9902 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16374 feat(orcad): prove node-pty loads before anything requires it | Neil Core team · MEMBER | #16370 Title unavailable Unclear · Unknown #9902 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +2219/−163. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1quarantine client-hosted WebContents before navigation1 PR · Standalone · Automated release pipeline#
Problem: quarantine client-hosted WebContents before navigation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14516 Title unavailable (Unclear, Unknown); #14471 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14517 feat(browser): quarantine client-hosted WebContents before navigationDraft | Jinwoo Hong Core team · MEMBER | #14516 Title unavailable Unclear · Unknown #14471 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +824/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1read OpenCode transcripts from its SQLite session store1 PR · Standalone · Automated release pipeline#
Problem: read OpenCode transcripts from its SQLite session store.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9307 Desktop: support OpenCode in native Chat UI (Fixes, OPEN); #9308 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15026 feat(native-chat): read OpenCode transcripts from its SQLite session store | xodmd45-ctrl Community · FIRST_TIME_CONTRIBUTOR | #9307 Desktop: support OpenCode in native Chat UI Fixes · OPEN #9308 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 OpenCode keeps its chat history in a SQLite database instead of the JSONL files other agents use, so Orca's native Chat UI showed nothing for OpenCode sessions. This PR teaches Orca to read that database — on a b | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +2895/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1release a structured session when its chat closes1 PR · Standalone · Automated release pipeline#
Problem: release a structured session when its chat closes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15411 Title unavailable (Unclear, Unknown); #15372 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15415 feat(native-chat): release a structured session when its chat closes | Brennan Benson Core team · MEMBER | #15411 Title unavailable Unclear · Unknown #15372 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 37 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk102 files, +4557/−352. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1release parent chunks pinned by drained output slices1 PR · Standalone · Automated release pipeline#
Problem: release parent chunks pinned by drained output slices.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13040 fix(terminal): release parent chunks pinned by drained output slices | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary A partially drained terminal output queue kept whole PTY chunks alive in the renderer heap. `takeQueuedChunk` stored the unconsumed remainder back into the queue as `chunk.data.slice(remaining)`. V8 backs `sli | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +262/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1report remote Orca runtime hosts, not just the local machine1 PR · Standalone · Automated release pipeline#
Problem: report remote Orca runtime hosts, not just the local machine.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15984 [Feature]: Resource Manager should show remote Orca runtime hosts, not just the local machine (Fixes, OPEN); #8394 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16000 feat(resource-manager): report remote Orca runtime hosts, not just the local machine | gatsby74 Community · CONTRIBUTOR | #15984 [Feature]: Resource Manager should show remote Orca runtime hosts, not just the local machine Fixes · OPEN #8394 Title unavailable Unclear · Unknown | Standalone change | ## Summary The Resource Manager only ever reported the local machine. With work running on remote Orca runtime hosts there was no way to see how loaded they were — `memory:getSnapshot` always ran the local collector, and | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1698/−316. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1retain client page renderer guests1 PR · Standalone · Automated release pipeline#
Problem: retain client page renderer guests.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14578 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14596 feat(browser): retain client page renderer guestsDraft | Jinwoo Hong Core team · MEMBER | #14578 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1805/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1retire route pages on process loss1 PR · Standalone · Automated release pipeline#
Problem: retire route pages on process loss.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14518 Title unavailable (Unclear, Unknown); #14471 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14519 feat(browser): retire route pages on process lossDraft | Jinwoo Hong Core team · MEMBER | #14518 Title unavailable Unclear · Unknown #14471 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +334/−131. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1route paired browser sockets through runtime1 PR · Standalone · Automated release pipeline#
Problem: route paired browser sockets through runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14440 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14470 feat(browser): route paired browser sockets through runtimeDraft | Jinwoo Hong Core team · MEMBER | #14440 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +2120/−105. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1run the project's formatter after a save1 PR · Standalone · Automated release pipeline#
Problem: run the project's formatter after a save.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11494 [Feature]: Format on save via a configurable per-project formatter command (Fixes, OPEN); #11275 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13757 feat(editor): run the project's formatter after a save | 5hseok Community · CONTRIBUTOR | #11494 [Feature]: Format on save via a configurable per-project formatter command Fixes · OPEN #11275 Title unavailable Unclear · Unknown | Standalone change | ## Summary Closes #11494. Adds a per-project format-on-save command, so a file saved in Orca's editor comes out formatted the same way it would in the editor you left open next to it. Monaco has no extension host, so `es | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk35 files, +2816/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1run the terminal daemon, and the ops contract around it1 PR · Standalone · Automated release pipeline#
Problem: run the terminal daemon, and the ops contract around it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16374 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16375 feat(orcad): run the terminal daemon, and the ops contract around it | Neil Core team · MEMBER | #16374 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 19 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk66 files, +4771/−296. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1scope model discovery to pinned PTY accounts1 PR · Standalone · Automated release pipeline#
Problem: scope model discovery to pinned PTY accounts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13183 Title unavailable (Unclear, Unknown); #13276 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13270 feat(codex): scope model discovery to pinned PTY accounts | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13183 Title unavailable Unclear · Unknown #13276 Title unavailable Unclear · Unknown | Standalone change | ## Summary Codex model discovery can now resolve the managed account pinned to a PTY and run the existing model probe with that account's effective `CODEX_HOME`. Native-chat enrichment scopes its cache by host and pinned | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +634/−94. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1scope the sidebar to Spaces1 PR · Standalone · Automated release pipeline#
Problem: scope the sidebar to Spaces.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13282 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13335 feat(sidebar): scope the sidebar to SpacesDraft | Egor Orlov Community · FIRST_TIME_CONTRIBUTOR | #13282 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 With many projects, the sidebar becomes one endless list. This adds **Spaces**: named groups of projects, so the sidebar (plus the jump palette and new-workspace picker) shows only the group you pick. A Default S | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk91 files, +5305/−223. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1separate row wash from word chip for readable diffs1 PR · Standalone · Automated release pipeline#
Problem: separate row wash from word chip for readable diffs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12777 feat(diff): separate row wash from word chip for readable diffs | Roger Serra Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Makes the Monaco diff view easier to read. The diff surfaces previously rendered every changed row at full chip weight, so an all-add or all-delete block became a solid slab of color and a changed *word* insid | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +263/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1settle host commands on lease socket1 PR · Standalone · Automated release pipeline#
Problem: settle host commands on lease socket.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14553 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14557 feat(browser): settle host commands on lease socketDraft | Jinwoo Hong Core team · MEMBER | #14553 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +954/−43. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1settle page retirement in two phases1 PR · Standalone · Automated release pipeline#
Problem: settle page retirement in two phases.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14539 feat(browser): settle page retirement in two phasesDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +221/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show Kiro subscription credits1 PR · Standalone · Automated release pipeline#
Problem: show Kiro subscription credits.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9559 Title unavailable (Unclear, Unknown); #9052 Title unavailable (Unclear, Unknown); #15876 Title unavailable (Unclear, Unknown); #16181 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14001 feat(usage): show Kiro subscription credits | GuanBear Community · FIRST_TIME_CONTRIBUTOR | #9559 Title unavailable Unclear · Unknown #9052 Title unavailable Unclear · Unknown #15876 Title unavailable Unclear · Unknown #16181 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can already launch Kiro, but it cannot show how much of the current Kiro subscription credit allowance has been used. This adds a Kiro usage meter to the status bar using Kiro CLI's own local `/usage` comman | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +549/−66. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show linked PR/MR numbers on workspace cards1 PR · Standalone · Automated release pipeline#
Problem: show linked PR/MR numbers on workspace cards.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13329 [Feature]: Show linked PR/MR number directly on workspace cards (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14269 feat(sidebar): show linked PR/MR numbers on workspace cards | Woohyun Park Community · FIRST_TIME_CONTRIBUTOR | #13329 [Feature]: Show linked PR/MR number directly on workspace cards Fixes · OPEN | Standalone change | ## ELI5 Workspace cards now show the linked pull request or merge request number and state directly, so you can identify it without hovering. The number remains clickable and the existing rich hover details still work. # | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +222/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show running services and their owning project1 PR · Standalone · Automated release pipeline#
Problem: show running services and their owning project.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12217 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12190 feat(right-sidebar): show running services and their owning project | Senatori Marcos Community · FIRST_TIME_CONTRIBUTOR | #12217 Title unavailable Unclear · Unknown | Standalone change | ## What this changes When a coding agent starts a background service — a dev server, a `docker compose up` — nothing in Orca tells you. The server holds its port long after the conversation moved on, and the containers a | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk35 files, +3560/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Split filesystem watcher responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split filesystem watcher responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17271 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17274 Split filesystem watcher responsibilities | Neil Core team · MEMBER | #17271 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 20 | $\co | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +2312/−1959. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1stream file uploads instead of buffering whole files1 PR · Standalone · Automated release pipeline#
Problem: stream file uploads instead of buffering whole files.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15987 [Feature]: Stream runtime upload staging instead of buffering whole files (removes the 25 MB per-file import cap) (Fixes, OPEN); #9896 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16106 feat(runtime): stream file uploads instead of buffering whole files | gatsby74 Community · CONTRIBUTOR | #15987 [Feature]: Stream runtime upload staging instead of buffering whole files (removes the 25 MB per-file import cap) Fixes · OPEN #9896 Title unavailable Unclear · Unknown | Standalone change | Fixes #15987 ## The problem Dropping a file onto a terminal in a runtime-environment workspace failed for anything over 25 MB. The failure was fast — about 1.5s — and the toast only said "Failed to upload 1 file", with n | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +857/−290. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support account-scoped agent launches1 PR · Standalone · Automated release pipeline#
Problem: support account-scoped agent launches.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13270 Title unavailable (Unclear, Unknown); #13183 Title unavailable (Unclear, Unknown); #13276 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13271 feat(codex): support account-scoped agent launches | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | #13270 Title unavailable Unclear · Unknown #13183 Title unavailable Unclear · Unknown #13276 Title unavailable Unclear · Unknown | Standalone change | ## Summary Agent launches can now carry an optional `ProviderAccountRef` that identifies the selected provider account without exposing its credential home. Codex launches resolve and validate that reference in the ownin | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk47 files, +1462/−115. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support Bitbucket Data Center for hosted-review status1 PR · Standalone · Automated release pipeline#
Problem: support Bitbucket Data Center for hosted-review status.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12031 [Feature]: Bitbucket Data Center (self-hosted) support (Fixes, OPEN); #12030 Title unavailable (Unclear, Unknown); #9171 Title unavailable (Unclear, Unknown); #12028 Title unavailable (Unclear, Unknown); #10770 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12111 feat(bitbucket): support Bitbucket Data Center for hosted-review status | dcieslak19973 Community · CONTRIBUTOR | #12031 [Feature]: Bitbucket Data Center (self-hosted) support Fixes · OPEN #12030 Title unavailable Unclear · Unknown #9171 Title unavailable Unclear · Unknown #12028 Title unavailable Unclear · Unknown #10770 Title unavailable Unclear · Unknown | Standalone change | **What:** Bitbucket Data Center (self-hosted) pull-request status — DC remotes stop being mis-claimed by the Gitea resolver. **Risk:** Config-gated: claims only `/scm/` remotes or an explicitly configured host; zero chan | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +1492/−231. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support native Windows teammate panes1 PR · Standalone · Automated release pipeline#
Problem: support native Windows teammate panes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15753 Title unavailable (Unclear, Unknown); #15751 Title unavailable (Unclear, Unknown); #15503 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16116 feat(agent-teams): support native Windows teammate panesDraft | OrcaWin Unknown · COLLABORATOR | #15753 Title unavailable Unclear · Unknown #15751 Title unavailable Unclear · Unknown #15503 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 30 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk65 files, +4359/−416. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support Pi mobile chat1 PR · Standalone · Automated release pipeline#
Problem: support Pi mobile chat.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12325 feat(native-chat): support Pi mobile chat | Haolun Zeng Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Enable the existing mobile native chat surface for Pi agents. - Add Pi to the shared native-chat support and transcript-agent resolution. - Decode Pi JSONL `message` records for user, assistant, thinking, tool | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +200/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1support split left and split up1 PR · Standalone · Automated release pipeline#
Problem: support split left and split up.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8263 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13984 feat(terminal): support split left and split up | Jihoon Lee Community · FIRST_TIME_CONTRIBUTOR | #8263 Title unavailable Unclear · Unknown | Standalone change | ## Summary Terminal panes could only split right or down, so there was no way to place a new pane *before* the source pane in its split. This adds **Split Terminal Left** and **Split Terminal Up**. Both are available fro | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +401/−41. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1surface agent notices in Chat and offer reauthentication2 PRs · Overlapping · Automated release pipeline#
Problem: surface agent notices in Chat and offer reauthentication.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #15341 [Bug]: Native Chat silently swallows login-required and other system notices from Claude Code (Fixes, OPEN); #14339 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14339 feat(native-chat): surface agent notices in Chat and offer reauthentication | Farid Murzone Community · FIRST_TIME_CONTRIBUTOR | #15341 [Bug]: Native Chat silently swallows login-required and other system notices from Claude Code Fixes · OPEN | Cluster contribution | ## ELI5 Sometimes Claude Code gets stuck waiting for you to log in (or hits some other notice it needs you to see), and today the Chat view just... says nothing. Your messages sit there unanswered like the app is ignorin | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +814/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15661 fix(native-chat): surface Claude system notices in Chat | Brennan Benson Core team · MEMBER | #15341 [Bug]: Native Chat silently swallows login-required and other system notices from Claude Code Fixes · OPEN #14339 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +626/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1surface Trae CLI session history1 PR · Standalone · Automated release pipeline#
Problem: surface Trae CLI session history.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13058 [Feature] Other CLI features need to be supported. (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13515 feat(ai-vault): surface Trae CLI session history | mosh Community · FIRST_TIME_CONTRIBUTOR | #13058 [Feature] Other CLI features need to be supported. Fixes · OPEN | Standalone change | ## Summary - Add Trae as a distinct AI Vault session identity and surface installed Trae CLI history in Orca workspaces. - Discover bounded `rollout-*.jsonl` histories locally, in WSL homes, and over SSH while pruning `. | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +2294/−577. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1terminal groups — extra terminal/agent cards on a project's existing checkout1 PR · Standalone · Automated release pipeline#
Problem: terminal groups — extra terminal/agent cards on a project's existing checkout.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15501 feat(workspaces): terminal groups — extra terminal/agent cards on a project's existing checkout | Eugenio Jesus Jose Valeiras Community · CONTRIBUTOR | None found | Standalone change | Lets a git project have N terminal/agent cards that share its existing checkout, without creating a worktree. Folder projects have always worked this way (every workspace points at the same directory); this brings the sa | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk43 files, +1457/−109. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1terminal keypad layout toggle with full on-screen keyboard1 PR · Standalone · Automated release pipeline#
Problem: terminal keypad layout toggle with full on-screen keyboard.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14540 feat(mobile): terminal keypad layout toggle with full on-screen keyboard | 神迹不染尘 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds a layout toggle to the mobile terminal accessory area that switches between the existing shortcut-key row and a new full on-screen keyboard, with the choice persisted across sessions. ## What changed ### | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +944/−299. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1track Qwen Code as a status agent with managed hooks and working tui-idle1 PR · Standalone · Automated release pipeline#
Problem: track Qwen Code as a status agent with managed hooks and working tui-idle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11186 Title unavailable (Unclear, Unknown); #11419 Title unavailable (Unclear, Unknown); #8384 Title unavailable (Unclear, Unknown); #7253 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12555 feat(agents): track Qwen Code as a status agent with managed hooks and working tui-idle | TeAmo Community · FIRST_TIME_CONTRIBUTOR | #11186 Title unavailable Unclear · Unknown #11419 Title unavailable Unclear · Unknown #8384 Title unavailable Unclear · Unknown #7253 Title unavailable Unclear · Unknown | Standalone change | ## Summary Running `qwen` terminals now show up as Qwen Code agent cards in Orca workspaces, and `terminal wait --for tui-idle` works for them. Qwen Code gets the same three-way status treatment as Kimi: 1. **Managed sta | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +1299/−313. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1user-selectable CJK font + warmed installed-font list1 PR · Standalone · Automated release pipeline#
Problem: user-selectable CJK font + warmed installed-font list.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13765 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13779 feat(terminal): user-selectable CJK font + warmed installed-font list | Rayim Community · CONTRIBUTOR | #13765 Title unavailable Unclear · Unknown | Standalone change | # feat(terminal): user-selectable CJK font + warmed installed-font list > Stacked on #13765 — the first commit here is that PR's atlas/chain fix. Review the last two commits; this PR becomes a clean two-commit diff once | P1 Meaningful core-workflow impact with strategic alignment to Automated release pipeline. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +430/−91. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add a setting to turn off rename-on-double-click1 PR · Standalone · Agent management and search#
Problem: add a setting to turn off rename-on-double-click.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12800 [Feature]: Setting to turn off rename-on-double-click — folder-name clicks wait 500 ms today (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12801 feat(file-explorer): add a setting to turn off rename-on-double-click | Harim Song Community · FIRST_TIME_CONTRIBUTOR | #12800 [Feature]: Setting to turn off rename-on-double-click — folder-name clicks wait 500 ms today Fixes · OPEN | Standalone change | Closes #12800 ## Problem Clicking a folder **name** in the File Explorer defers its expand/collapse by `DIR_TOGGLE_DOUBLE_CLICK_MS` (500 ms), so a slow double-click can become a rename instead of a visible collapse/re-ex | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +274/−50. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Antigravity (AGY) transcript decoder and Native Chat support1 PR · Standalone · Agent management and search#
Problem: add Antigravity (AGY) transcript decoder and Native Chat support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15773 feat(native-chat): add Antigravity (AGY) transcript decoder and Native Chat support | Ray Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ### Summary This PR adds Native Chat transcript decoding and session integration for **Antigravity (`agy`)**, enabling rich message rendering (including interactive Mermaid diagrams, markdown formatting, tool calls, and | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +349/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Copy Session ID to the terminal context menu1 PR · Standalone · Agent management and search#
Problem: add Copy Session ID to the terminal context menu.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #16261 [Feature]: Add Copy Session ID in context menu presented on right click in the terminal running agent (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16264 feat(terminal): add Copy Session ID to the terminal context menu | Anton Novoselov Community · FIRST_TIME_CONTRIBUTOR | #16261 [Feature]: Add Copy Session ID in context menu presented on right click in the terminal running agent Fixes · OPEN | Standalone change | Closes #16261 ## Problem The terminal context menu offers **Copy Terminal ID** and **Copy Pane ID**, but neither addresses the agent's own conversation. When you want to resume an exact session in the agent CLI, or refer | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +241/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add diagnostic report collection and copy-to-clipboard1 PR · Standalone · Agent management and search#
Problem: add diagnostic report collection and copy-to-clipboard.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12636 feat(ssh): add diagnostic report collection and copy-to-clipboard | Jinjing Core team · MEMBER | None found | Standalone change | ## Summary Adds the ability for users to copy SSH connection diagnostics to the clipboard from the reconnect overlay. The diagnostic report includes: - Current connection status and attempt number - Full timeline of conn | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +3973/−121. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add font smoothing setting (default / antialiased / subpixel)1 PR · Standalone · Agent management and search#
Problem: add font smoothing setting (default / antialiased / subpixel).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13056 feat(terminal): add font smoothing setting (default / antialiased / subpixel) | Aex Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds a `terminalFontSmoothing` setting (`default` / `antialiased` / `subpixel`) under **Terminal → Rendering**, so users can opt the terminal into macOS subpixel smoothing. **The default preserves today's beha | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +214/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Hermes native chat support1 PR · Standalone · Agent management and search#
Problem: add Hermes native chat support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15301 feat: add Hermes native chat support | Alejandro Akbal Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | Implements Hermes native chat from the canonical read-only ~/.hermes/state.db SQLite store, rather than treating JSONL as authoritative. Adds session lookup, ordered message reads, assistant tool calls, tool results, rea | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +1211/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add inline folder source control with git actions1 PR · Standalone · Agent management and search#
Problem: add inline folder source control with git actions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13291 feat: add inline folder source control with git actions | eric Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | Adds an inline folder Source Control panel that supports nested git repo scanning, branch switching/search, staging/discard actions, commit input, base ref picker, and diff opening in the current editor group. ## Screens | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk39 files, +13426/−2542. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1add Turkish (tr) language support and README1 PR · Standalone · Agent management and search#
Problem: add Turkish (tr) language support and README.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13196 feat(i18n): add Turkish (tr) language support and README | Arda Karataş Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary This PR adds full **Turkish (tr)** language support to the StablyAI Orca Agent Development Environment and includes a translated \README.tr.md\. ### Changes Included: - **Shared Types**: Registered \UI_LANGUAG | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +15635/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1allow hiding the terminal command button1 PR · Standalone · Agent management and search#
Problem: allow hiding the terminal command button.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12949 [Feature]: Add a setting to hide the Command button (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13001 feat(settings): allow hiding the terminal command button | Wooseong Kim Community · CONTRIBUTOR | #12949 [Feature]: Add a setting to hide the Command button Fixes · OPEN | Standalone change | ## Description Add a persisted setting to hide the terminal toolbar Command button. ## Focused fix - In scope: a default-on boolean setting, an Appearance > Terminal Toolbar toggle, and the render gate. - Out of scope: q | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +193/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Claude API Console usage tracking1 PR · Standalone · Agent management and search#
Problem: Claude API Console usage tracking.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12973 feat: Claude API Console usage tracking | dcieslak19973 Community · CONTRIBUTOR | None found | Standalone change | ## Summary Implement first-class Claude API Console usage tracking for API-key users, enabling visibility into balance and spending alongside existing subscription billing. ## Implementation (3 of 7 tasks complete) ✅ **T | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +985/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1Discord Rich Presence (experimental)1 PR · Standalone · Agent management and search#
Problem: Discord Rich Presence (experimental).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14285 feat: Discord Rich Presence — show live agent activity on your Discord profile (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14286 feat: Discord Rich Presence (experimental) | Baltasar Ortiz Becerra Community · FIRST_TIME_CONTRIBUTOR | #14285 feat: Discord Rich Presence — show live agent activity on your Discord profile Fixes · OPEN | Standalone change | ## ELI5 When you turn on Discord Rich Presence in Settings → Experimental, Orca quietly connects to the Discord desktop app in the background and shows what you're working on — how many agents are running, which ones are | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +1536/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1distinguish interactive and prompt-only runtimes1 PR · Standalone · Agent management and search#
Problem: distinguish interactive and prompt-only runtimes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13965 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16227 feat(zcode): distinguish interactive and prompt-only runtimesDraft | GuanBear Community · FIRST_TIME_CONTRIBUTOR | #13965 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds the macOS launch adapter for ZCode runtimes that are not equivalent: - A separately installed `zcode-app-cli` remains available as an interactive TUI. - ZCode Desktop's bundled runtime is used only for pr | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk56 files, +1152/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1establish client-hosted tunnel contracts1 PR · Standalone · Agent management and search#
Problem: establish client-hosted tunnel contracts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14402 Title unavailable (Unclear, Unknown); #10046 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14440 feat(browser): establish client-hosted tunnel contractsDraft | Jinwoo Hong Core team · MEMBER | #14402 Title unavailable Unclear · Unknown #10046 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1914/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let OMP task subagent rows resume as their own sessions1 PR · Standalone · Agent management and search#
Problem: let OMP task subagent rows resume as their own sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12885 [Bug]: OMP task subagent rows in Agent Session History are view-only and can't be resumed (Fixes, OPEN); #12803 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12889 feat(ai-vault): let OMP task subagent rows resume as their own sessions | Jinwoo Hong Core team · MEMBER | #12885 [Bug]: OMP task subagent rows in Agent Session History are view-only and can't be resumed Fixes · OPEN #12803 Title unavailable Unclear · Unknown | Standalone change | **What:** OMP task subagent rows in Agent Session History can now be resumed as their own sessions, restoring an affordance #12803 dropped. Claude subagent rows stay view-only — deliberately. **Risk:** One new optional p | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +200/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1let users hide optional agent-row fields1 PR · Standalone · Agent management and search#
Problem: let users hide optional agent-row fields.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12948 [Feature]: Let users choose which fields show in sidebar agent rows (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13195 feat(sidebar): let users hide optional agent-row fields | BingZ Community · CONTRIBUTOR | #12948 [Feature]: Let users choose which fields show in sidebar agent rows Fixes · OPEN | Standalone change | ## Summary - Adds per-field visibility toggles for workspace sidebar agent rows: **provider icon**, **secondary status**, **model label**, and **relative time**. - Defaults keep every field on so existing layouts are unc | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +335/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1link a Jira issue from Edit Worktree Details1 PR · Standalone · Agent management and search#
Problem: link a Jira issue from Edit Worktree Details.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12899 [Bug] update/edit worktree details doesnt let me select jira (Fixes, OPEN); #11659 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13825 feat(jira): link a Jira issue from Edit Worktree Details | Melih Berat ŞANLI Community · CONTRIBUTOR | #12899 [Bug] update/edit worktree details doesnt let me select jira Fixes · OPEN #11659 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes #12899. The worktree issue-link field in **Edit Worktree Details** only offered GitHub and Linear, so pasting a Jira issue URL was rejected with "Not a GitHub issue number or issue URL." Jira is a first- | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +907/−88. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1offer WSL agent detection when the Windows picker is empty1 PR · Standalone · Agent management and search#
Problem: offer WSL agent detection when the Windows picker is empty.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #9725 [Bug]: Agent detection failed on Windows (WSL) (Fixes, CLOSED); #11797 Title unavailable (Unclear, Unknown); #9731 Title unavailable (Unclear, Unknown); #8391 Title unavailable (Unclear, Unknown); #5149 Title unavailable (Unclear, Unknown); #16028 Title unavailable (Unclear, Unknown); #16043 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12794 feat(agents): offer WSL agent detection when the Windows picker is empty | OMGg Community · FIRST_TIME_CONTRIBUTOR | #9725 [Bug]: Agent detection failed on Windows (WSL) Fixes · CLOSED #11797 Title unavailable Unclear · Unknown #9731 Title unavailable Unclear · Unknown #8391 Title unavailable Unclear · Unknown #5149 Title unavailable Unclear · Unknown #16028 Title unavailable Unclear · Unknown #16043 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On Windows, if your coding agents are installed inside WSL rather than on Windows itself, the new-workspace screen's agent picker showed an empty list with no clue why. Now, when nothing is detected and WSL is av | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +479/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1paste copied files into a File Explorer folder1 PR · Standalone · Agent management and search#
Problem: paste copied files into a File Explorer folder.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14530 [Feature]: Support pasting copied files into File Explorer folders and other projects (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14781 feat(explorer): paste copied files into a File Explorer folder | Wooseong Kim Community · CONTRIBUTOR | #14530 [Feature]: Support pasting copied files into File Explorer folders and other projects Fixes · CLOSED | Standalone change | ## Description File Explorer can paste OS-copied files into a folder from the context menu or Cmd/Ctrl+V, including across projects. ## Focused fix - In scope: Paste of clipboard files into the target folder. - Out of sc | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +885/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1rebuild Antigravity quota discovery1 PR · Standalone · Agent management and search#
Problem: rebuild Antigravity quota discovery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #9757 Title unavailable (Unclear, Unknown); #14571 Title unavailable (Unclear, Unknown); #16788 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12095 fix(rate-limits): rebuild Antigravity quota discovery | MumuTW Community · CONTRIBUTOR | #9757 Title unavailable Unclear · Unknown #14571 Title unavailable Unclear · Unknown #16788 Title unavailable Unclear · Unknown | Standalone change | ## Summary This is a rework of the closed [#9757](https://github.com/stablyai/orca/pull/9757), incorporating the maintainer feedback from [issuecomment-5151463530](https://github.com/stablyai/orca/pull/9757#issuecomment- | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk46 files, +2827/−166. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1remember Worktree View as the default Dashboard view1 PR · Standalone · Agent management and search#
Problem: remember Worktree View as the default Dashboard view.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14429 [Feature] Allow Dashboard View to Open in Worktree View by Default (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14780 feat(dashboard): remember Worktree View as the default Dashboard view | Wooseong Kim Community · CONTRIBUTOR | #14429 [Feature] Allow Dashboard View to Open in Worktree View by Default Fixes · OPEN | Standalone change | ## Description Dashboard can remember Worktree View as the default view across restarts. Unset/off keeps the current board. ## Focused fix - In scope: one persisted default. Explicit `view=` / session override still wins | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +273/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1render Kimi Code transcripts1 PR · Standalone · Agent management and search#
Problem: render Kimi Code transcripts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #9610 [Feature] Kimi chat view (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16397 feat(native-chat): render Kimi Code transcripts | Alexander Bocharoff Community · FIRST_TIME_CONTRIBUTOR | #9610 [Feature] Kimi chat view Fixes · CLOSED | Standalone change | ## ELI5 Adds Chat UI support for Kimi Code sessions, alongside Claude, Codex, Grok, and OMP. ## What Changed - New `wire.jsonl` transcript decoder (stateless per line, so the backward-paging tail reader works unchanged): | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1159/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1resize CSV table columns1 PR · Standalone · Agent management and search#
Problem: resize CSV table columns.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12915 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13223 feat(editor): resize CSV table columns | hungrytech Community · FIRST_TIME_CONTRIBUTOR | #12915 Title unavailable Unclear · Unknown | Standalone change | ## Summary Part of #12915. - add draggable resize handles to CSV table headers - keep the header and virtualized body rows on the same column widths - preserve manual widths per file for the current app session, includin | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +332/−38. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1saved and custom JQL filters in the Tasks panel1 PR · Standalone · Agent management and search#
Problem: saved and custom JQL filters in the Tasks panel.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13391 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13395 feat(jira): saved and custom JQL filters in the Tasks panel | Eugenio Jesus Jose Valeiras Community · CONTRIBUTOR | #13391 Title unavailable Unclear · Unknown | Standalone change | Brings Jira's saved filters into the Tasks panel, and lets users define local custom JQL filters, next to the existing Assigned/Reported/All Open/Done presets. ## What it does **Saved Jira filters** — a new "Filters" men | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +1412/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1show ZCode Coding Plan quota1 PR · Standalone · Agent management and search#
Problem: show ZCode Coding Plan quota.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13965 Title unavailable (Unclear, Unknown); #16181 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14556 feat(usage): show ZCode Coding Plan quotaDraft | GuanBear Community · FIRST_TIME_CONTRIBUTOR | #13965 Title unavailable Unclear · Unknown #16181 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds a ZCode Coding Plan usage meter to Orca's existing provider usage UI. This is intentionally independent from ZCode launch and orchestration behavior: it reads the user's local ZCode credential, fetches qu | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk88 files, +1608/−146. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1supervise orchestration workers and transcripts1 PR · Standalone · Agent management and search#
Problem: supervise orchestration workers and transcripts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13965 Title unavailable (Unclear, Unknown); #16227 Title unavailable (Unclear, Unknown); #14556 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16228 feat(zcode): supervise orchestration workers and transcriptsDraft | GuanBear Community · FIRST_TIME_CONTRIBUTOR | #13965 Title unavailable Unclear · Unknown #16227 Title unavailable Unclear · Unknown #14556 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds supervised ZCode workers and transcript support to Orca orchestration: - Chooses persistent TUI input only after positively detecting an interactive client. - Uses bounded startup-prompt execution for pro | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk103 files, +3392/−340. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1teach the file tree with a one-shot callout that sets the default1 PR · Standalone · Agent management and search#
Problem: teach the file tree with a one-shot callout that sets the default.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12744 feat(diff): teach the file tree with a one-shot callout that sets the default | Jinjing Core team · MEMBER | None found | Standalone change | ## Why The combined-diff file tree is opt-in and hidden by default, so most people never find it. Rather than adding another "you can configure this in Settings" line, this points at the toolbar toggle once and resolves | P1 Meaningful core-workflow impact with strategic alignment to Agent management and search. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk32 files, +1342/−88. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1authenticate page command results1 PR · Standalone · SSH/remote re-architecture#
Problem: authenticate page command results.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14550 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14553 feat(browser): authenticate page command resultsDraft | Jinwoo Hong Core team · MEMBER | #14550 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1367/−125. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1backfill fork upstream for SSH repos on connect1 PR · Standalone · SSH/remote re-architecture#
Problem: backfill fork upstream for SSH repos on connect.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #12967 [Bug] Fork upstream is never backfilled for SSH/remote repos, so Project rows stay hidden (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12970 fix(repo): backfill fork upstream for SSH repos on connect | Jinwoo Hong Core team · MEMBER | #12967 [Bug] Fork upstream is never backfilled for SSH/remote repos, so Project rows stay hidden Fixes · OPEN | Standalone change | ## Summary Legacy fork repos on SSH hosts could remain `upstream === undefined` forever. Startup backfill skipped remote repos because their hosts were not connected yet, and no later hook retried them. Since `repo.upstr | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +822/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1bound client page command dispatch1 PR · Standalone · SSH/remote re-architecture#
Problem: bound client page command dispatch.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14544 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14550 feat(browser): bound client page command dispatchDraft | Jinwoo Hong Core team · MEMBER | #14544 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +1141/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1harden bootstrap and cross-plane orchestration1 PR · Standalone · SSH/remote re-architecture#
Problem: harden bootstrap and cross-plane orchestration.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16349 feat(runtime): harden bootstrap and cross-plane orchestration | jimmylee-cell Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - expose evidence-graded bootstrap/profile diagnostics instead of collapsing live-process ambiguity into app-not-running - reject accidental canonical self-send - freeze workers on parent loss and require appr | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk46 files, +2542/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1negotiate client page commands1 PR · Standalone · SSH/remote re-architecture#
Problem: negotiate client page commands.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14539 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14544 feat(browser): negotiate client page commandsDraft | Jinwoo Hong Core team · MEMBER | #14539 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +501/−28. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1plan client page reconciliation1 PR · Standalone · SSH/remote re-architecture#
Problem: plan client page reconciliation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14613 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14617 feat(browser): plan client page reconciliationDraft | Jinwoo Hong Core team · MEMBER | #14613 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +538/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1preview .docx / .xlsx / .pdf in editor1 PR · Standalone · SSH/remote re-architecture#
Problem: preview .docx / .xlsx / .pdf in editor.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #12 Title unavailable (Unclear, Unknown); #11 Title unavailable (Unclear, Unknown); #13 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15763 feat(office-preview): preview .docx / .xlsx / .pdf in editor | ppw-stack Community · CONTRIBUTOR | #12 Title unavailable Unclear · Unknown #11 Title unavailable Unclear · Unknown #13 Title unavailable Unclear · Unknown | Standalone change | ## 简介 编辑器支持 `.docx` / `.xlsx` / `.pdf` 二进制预览：`.pdf` 走既有 `PdfViewer`，`.docx` 走新增 `DocxViewer`（基于 mammoth），`.xlsx` 走新增 `XlsxViewer`（基于 SheetJS `sheet_to_html`）。同一份 `PREVIEWABLE_BINARY_MIME_TYPES` 白名单被主进程 IPC、SSH 中继、runtime | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +2601/−180. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1replace fenced tunnel generations1 PR · Standalone · SSH/remote re-architecture#
Problem: replace fenced tunnel generations.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14504 Title unavailable (Unclear, Unknown); #14402 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14507 feat(browser): replace fenced tunnel generationsDraft | Jinwoo Hong Core team · MEMBER | #14504 Title unavailable Unclear · Unknown #14402 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +786/−183. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1report client page inventory1 PR · Standalone · SSH/remote re-architecture#
Problem: report client page inventory.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14648 feat(browser): report client page inventoryDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk32 files, +1493/−182. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1route tunnels through execution hosts1 PR · Standalone · SSH/remote re-architecture#
Problem: route tunnels through execution hosts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14507 Title unavailable (Unclear, Unknown); #14402 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14513 feat(browser): route tunnels through execution hostsDraft | Jinwoo Hong Core team · MEMBER | #14507 Title unavailable Unclear · Unknown #14402 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 13 | $\color{#1a7f37}{\Huge{\mathb | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +2353/−115. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1supervise fresh Pi workers over RPC1 PR · Standalone · SSH/remote re-architecture#
Problem: supervise fresh Pi workers over RPC.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15451 feat(orchestration): supervise fresh Pi workers over RPCDraft | ChertaS2-whatnot Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | Draft for Gate 5A validation. - Routes fresh local-native Pi orchestration workers through an Orca-owned RPC supervisor. - Keeps lifecycle identity/capability parent-side and exposes only exact source-attested, workspace | P1 Meaningful core-workflow impact with strategic alignment to SSH/remote re-architecture. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk41 files, +5258/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P1sample the near-death renderer heap (unblocks the 42-crash OOM cluster)1 PR · Standalone · Profile and resource management#
Problem: sample the near-death renderer heap (unblocks the 42-crash OOM cluster).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12491 fix(crash-diagnostics): sample the near-death renderer heap (unblocks the 42-crash OOM cluster) | Neil Core team · MEMBER | None found | Standalone change | ## What this fixes **Signature:** renderer death at 90-97% of `heapLimitMB`, reported on four different platform exit encodings — macOS `exit 5` (SIGTRAP), Windows `-536870904` / `0xE0000008` (`reason: oom`), two heap-sh | P1 Meaningful core-workflow impact with strategic alignment to Profile and resource management. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +602/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[STA-5729] Prevent live coordinator takeover of orchestration Runs1 PR · Standalone · Plugins#
Problem: [STA-5729] Prevent live coordinator takeover of orchestration Runs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16859 [STA-5729] Prevent live coordinator takeover of orchestration Runs | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 42 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk79 files, +2782/−193. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2a failed shared-quota read is an Antigravity error, not an absent reading1 PR · Standalone · Plugins#
Problem: a failed shared-quota read is an Antigravity error, not an absent reading.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17193 Title unavailable (Unclear, Unknown); #15876 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17200 fix(rate-limits): a failed shared-quota read is an Antigravity error, not an absent reading | Brennan Benson Core team · MEMBER | #17193 Title unavailable Unclear · Unknown #15876 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +59/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2a recycled PTY id must not replay the dead shell's bytes1 PR · Standalone · Plugins#
Problem: a recycled PTY id must not replay the dead shell's bytes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16970 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17148 fix(terminal): a recycled PTY id must not replay the dead shell's bytes | Brennan Benson Core team · MEMBER | #16970 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +132/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2accept bare environment ids as project --host1 PR · Standalone · Plugins#
Problem: accept bare environment ids as project --host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7810 [Bug]: "Invalid host ID" (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13191 fix(project): accept bare environment ids as project --host | BingZ Community · CONTRIBUTOR | #7810 [Bug]: "Invalid host ID" Fixes · OPEN | Standalone change | ## ELI5 `orca environment list` prints a server id without the `runtime:` prefix, so pasting that id into project setup used to fail as an invalid host. Project setup now accepts the pasted id and treats it as `runtime:< | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +79/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2accept Cursor events on the Claude compatibility route1 PR · Standalone · Plugins#
Problem: accept Cursor events on the Claude compatibility route.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14630 [Bug]: Cursor hooks delivered through the Claude compatibility route are silently dropped (Fixes, OPEN); #1108 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14640 fix(agent-hooks): accept Cursor events on the Claude compatibility route | Dallas Crilley Community · FIRST_TIME_CONTRIBUTOR | #14630 [Bug]: Cursor hooks delivered through the Claude compatibility route are silently dropped Fixes · OPEN #1108 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Cursor sometimes sends status hooks to Orca's Claude URL. Orca trusted the URL, tried to parse the event as Claude, and discarded the Cursor payload, so the working spinner never appeared. This change recognizes | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5437 files, +523147/−195670. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add --no-offscreen-browser flag1 PR · Standalone · Plugins#
Problem: add --no-offscreen-browser flag.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13434 feat(serve): add --no-offscreen-browser flag | Aarav Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds `--no-offscreen-browser` to `orca serve`. When set, the headless runtime skips registering the `OffscreenBrowserBackend`, so browser pane requests from a paired remote/mobile client return null instead of | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +29/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add "Copy Terminal ID" and "Copy Session ID" to the tab context menu1 PR · Standalone · Plugins#
Problem: add "Copy Terminal ID" and "Copy Session ID" to the tab context menu.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16262 [Feature]: Add "Copy Terminal ID", and "Copy Session ID" to the context menu presented on right click on tabs (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16269 feat(tab-bar): add "Copy Terminal ID" and "Copy Session ID" to the tab context menu | Anton Novoselov Community · FIRST_TIME_CONTRIBUTOR | #16262 [Feature]: Add "Copy Terminal ID", and "Copy Session ID" to the context menu presented on right click on tabs Fixes · OPEN | Standalone change | ## ELI5 Right-clicking a terminal tab now offers **Copy Terminal ID** and **Copy Session ID**. Before this, the only way to get a tab's terminal handle was to right-click *inside* the terminal, and the only way to get it | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +321/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add a packaged-artifact contract for the CLI launch paths1 PR · Standalone · Plugins#
Problem: add a packaged-artifact contract for the CLI launch paths.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11609 Title unavailable (Unclear, Unknown); #12530 Title unavailable (Unclear, Unknown); #13719 Title unavailable (Unclear, Unknown); #14229 Title unavailable (Unclear, Unknown); #15081 Title unavailable (Unclear, Unknown); #15084 Title unavailable (Unclear, Unknown); #15083 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15085 test(linux): add a packaged-artifact contract for the CLI launch paths | Neil Core team · MEMBER | #11609 Title unavailable Unclear · Unknown #12530 Title unavailable Unclear · Unknown #13719 Title unavailable Unclear · Unknown #14229 Title unavailable Unclear · Unknown #15081 Title unavailable Unclear · Unknown #15084 Title unavailable Unclear · Unknown #15083 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +339/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add an opt-in Parallel Search MCP preset1 PR · Standalone · Plugins#
Problem: add an opt-in Parallel Search MCP preset.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16537 feat: add an opt-in Parallel Search MCP preset | George Pickett Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Orca can now create a ready-to-use Parallel Search MCP workspace configuration when a user explicitly chooses and confirms that preset. Existing workspaces and the neutral empty-config action are unchanged. ## Wh | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +308/−28. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add Aside as a Chromium cookie-import source1 PR · Standalone · Plugins#
Problem: add Aside as a Chromium cookie-import source.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15454 [Feature]: Add Aside browser to cookie import (Fixes, OPEN); #6768 Title unavailable (Unclear, Unknown); #12849 Title unavailable (Unclear, Unknown); #1923 Title unavailable (Unclear, Unknown); #14295 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15452 feat(browser): add Aside as a Chromium cookie-import source | Geon Community · FIRST_TIME_CONTRIBUTOR | #15454 [Feature]: Add Aside browser to cookie import Fixes · OPEN #6768 Title unavailable Unclear · Unknown #12849 Title unavailable Unclear · Unknown #1923 Title unavailable Unclear · Unknown #14295 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca can copy your logged-in sessions from other browsers so you don't have to sign in again. It already knows about Chrome, Edge, Arc, Brave, Comet, Helium, Firefox, and Safari — this adds **Aside** to that list | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +189/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add authenticated Windows loopback fallback2 PRs · Overlapping · Plugins#
Problem: add authenticated Windows loopback fallback.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16697 Title unavailable (Unclear, Unknown); #16623 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16623 fix(runtime): add authenticated Windows loopback fallback | jimmylee-cell Community · FIRST_TIME_CONTRIBUTOR | #16697 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - publish a random-port IPv4 loopback RPC transport on Windows while keeping the named pipe primary - retry through that endpoint only when the named-pipe connection fails with `EPERM`/`EACCES` - reuse the run | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +162/−42. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17218 fix(runtime): add authenticated Windows loopback fallback | jimmylee-cell Community · FIRST_TIME_CONTRIBUTOR | #16623 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - publish an authenticated OS-assigned IPv4 loopback RPC fallback on Windows while retaining the named pipe as primary - retry only after named-pipe `EPERM`/`EACCES`; reject non-loopback or invalid endpoints - | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +223/−47. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add background Quick Command execution1 PR · Standalone · Plugins#
Problem: Add background Quick Command execution.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12737 Add background Quick Command execution | Matheus Coêlho Community · CONTRIBUTOR | None found | Standalone change | ## ELI5 Quick Commands can now open and run in a new terminal tab without taking you away from the tab or workspace you are currently using. The background terminal remains visible in the tab bar so you can inspect it la | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +1250/−66. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add Bullet to the supported agents1 PR · Standalone · Plugins#
Problem: Add Bullet to the supported agents.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8451 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13296 Add Bullet to the supported agents | Adi Kulkarni Community · FIRST_TIME_CONTRIBUTOR | #8451 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds [Bullet](https://usebullet.com) (`@trybullet/cli`, binary `bullet`) as a built-in TUI agent, so it is detected on PATH, launchable from the agent picker, and shows a working/idle status dot like the other | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +101/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add F2 rename keybinding via the shortcut registry1 PR · Standalone · Plugins#
Problem: add F2 rename keybinding via the shortcut registry.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14693 [Feature]: Keyboard shortcut (F2) to rename files in the File Explorer (Fixes, OPEN); #12800 Title unavailable (Unclear, Unknown); #14728 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14699 feat(file-explorer): add F2 rename keybinding via the shortcut registry | jsk4581 Community · FIRST_TIME_CONTRIBUTOR | #14693 [Feature]: Keyboard shortcut (F2) to rename files in the File Explorer Fixes · OPEN #12800 Title unavailable Unclear · Unknown #14728 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You can now press **F2** (or Enter, as before) to rename the selected file or folder in the File Explorer — the same key every other editor uses. The shortcut also shows up in Settings → Shortcuts, so you can rem | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +127/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add insertion-only quick commands that don't immediately submit Enter1 PR · Standalone · Plugins#
Problem: Add insertion-only quick commands that don't immediately submit Enter.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16867 Add insertion-only quick commands that don't immediately submit Enter | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 12 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk41 files, +954/−172. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add keyboard shortcuts for cycling projects1 PR · Standalone · Plugins#
Problem: add keyboard shortcuts for cycling projects.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15851 [Feature]: Add keyboard shortcuts for cycling projects (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15843 feat: add keyboard shortcuts for cycling projects | PeaceTis Community · FIRST_TIME_CONTRIBUTOR | #15851 [Feature]: Add keyboard shortcuts for cycling projects Fixes · OPEN | Standalone change | ## ELI5 Use one shortcut to move to the project on the left or right instead of selecting projects by number. ## What Changed - Added configurable Previous project and Next project actions with Cmd/Ctrl+Shift+Left/Right | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +450/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add local shell command identity markers1 PR · Standalone · Plugins#
Problem: Add local shell command identity markers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16893 Title unavailable (Unclear, Unknown); #17017 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16915 Add local shell command identity markers | Brennan Benson Core team · MEMBER | #16893 Title unavailable Unclear · Unknown #17017 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 33 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk89 files, +2341/−281. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add multi-desktop mobile project view1 PR · Standalone · Plugins#
Problem: Add multi-desktop mobile project view.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14989 Add multi-desktop mobile project view | Adelin Berard Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Aggregate projects and workspaces from paired desktops in the mobile home view. - Add project search, grouping, sorting, host filtering, and experimental view settings. - Preserve validated cached data durin | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk35 files, +4067/−300. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add OMP commit-message agent spec for Source Control AI2 PRs · Overlapping · Plugins#
Problem: add OMP commit-message agent spec for Source Control AI.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15646 Source Control AI fails for OMP users: 'Choose a supported Source Control AI agent' on every action (incl. first-work auto branch rename) (Fixes, OPEN); #11674 Title unavailable (Unclear, Unknown); #5878 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15654 feat(git): add OMP commit-message agent spec for Source Control AI | puglao Community · FIRST_TIME_CONTRIBUTOR | #15646 Source Control AI fails for OMP users: 'Choose a supported Source Control AI agent' on every action (incl. first-work auto branch rename) Fixes · OPEN #11674 Title unavailable Unclear · Unknown #5878 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Orca can ask your AI coding agent to write commit messages and name branches, but only for agents it has a "recipe" for. OMP was already on Orca's agent list without a recipe, so OMP users got an error instead of | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +217/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15678 fix(source-control-ai): give OMP a commit-message spec | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15646 Source Control AI fails for OMP users: 'Choose a supported Source Control AI agent' on every action (incl. first-work auto branch rename) Fixes · OPEN | Cluster contribution | ## Summary **What** Adds an `omp` entry to `COMMIT_MESSAGE_AGENT_SPECS`, so a default TUI agent of OMP resolves to a working Source Control AI agent instead of failing. **Why** #15646 — `omp` is a first-class `TuiAgent` | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +34/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add quick command duplication with a list cap1 PR · Standalone · Plugins#
Problem: Add quick command duplication with a list cap.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16813 Add quick command duplication with a list cap | Julien Gestin Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Duplicating a quick command copies every field except the id and derives a unique `(copy)` / `(copy N)` label, bounded by the label length cap. Adding and duplicating are both blocked once the list reaches `MA | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +454/−49. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add responsive resizable Markdown tables1 PR · Standalone · Plugins#
Problem: add responsive resizable Markdown tables.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11901 Title unavailable (Unclear, Unknown); #11985 Title unavailable (Unclear, Unknown); #11580 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12048 feat(editor): add responsive resizable Markdown tables | rainL Community · CONTRIBUTOR | #11901 Title unavailable Unclear · Unknown #11985 Title unavailable Unclear · Unknown #11580 Title unavailable Unclear · Unknown | Standalone change | ## Summary Part of #11901. - keep wide rich Markdown tables inside a table-local horizontal scroller - let users resize columns by dragging TipTap's native column boundaries - keep resized widths session-only so Markdown | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +176/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add shortcuts to navigate active worktrees1 PR · Standalone · Plugins#
Problem: Add shortcuts to navigate active worktrees.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14673 Add shortcuts for cycling active worktrees (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14689 Add shortcuts to navigate active worktrees | yyar Community · FIRST_TIME_CONTRIBUTOR | #14673 Add shortcuts for cycling active worktrees Fixes · OPEN | Standalone change | ## ELI5 This adds two shortcuts that move between worktrees that are still active, so sleeping worktrees do not interrupt keyboard navigation. ## What Changed - Added Previous active worktree and Next active worktree act | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +116/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add SSH host registration to Orca CLI1 PR · Standalone · Plugins#
Problem: Add SSH host registration to Orca CLI.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16351 Add SSH host registration to Orca CLIDraft | xiciluan Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Lets another CLI add a specific `~/.ssh/config` host to Orca and register an existing remote project folder, matching the desktop Add host flow without creating a worktree. ## What Changed - Adds idempotent `orca | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +316/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add VCL (Varnish Configuration Language) syntax highlighting1 PR · Standalone · Plugins#
Problem: add VCL (Varnish Configuration Language) syntax highlighting.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15327 [Feature]: Support syntax highlighting for VCL (Varnish Configuration Language) .vcl files (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15437 feat: add VCL (Varnish Configuration Language) syntax highlighting | Simanta Deb Turja Community · FIRST_TIME_CONTRIBUTOR | #15327 [Feature]: Support syntax highlighting for VCL (Varnish Configuration Language) .vcl files Fixes · OPEN | Standalone change | ## ELI5 VCL is the config language for Varnish and Fastly CDN caching. Until now, opening a `.vcl` file in Orca showed a wall of plain monochrome text. This PR teaches Orca's editor to color VCL the same way it already c | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +493/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add workspace-scoped browser session profiles (#14559)1 PR · Standalone · Plugins#
Problem: add workspace-scoped browser session profiles (#14559).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14559 [Feature]: Isolated Browser Profiles / Storage Partitions per Workspace Folder (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16091 feat(browser): add workspace-scoped browser session profiles (#14559) | Sadit Wongprayon Community · FIRST_TIME_CONTRIBUTOR | #14559 [Feature]: Isolated Browser Profiles / Storage Partitions per Workspace Folder Fixes · OPEN | Standalone change | ## ELI5 When working across multiple workspace folders that run local dev servers (e.g. `localhost:3000`), their cookies, authentication, and localStorage previously collided because all workspaces shared the default bro | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +208/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add worktree pin controls1 PR · Standalone · Plugins#
Problem: add worktree pin controls.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13896 [Feature]: Add pin and unpin controls to the Orca CLI (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13897 feat(cli): add worktree pin controls | Alcimério Rangel Community · FIRST_TIME_CONTRIBUTOR | #13896 [Feature]: Add pin and unpin controls to the Orca CLI Fixes · OPEN | Standalone change | Closes #13896 ## Summary Adds explicit `--pin` and `--unpin` controls to `orca worktree set`. The CLI already returned `isPinned` in worktree JSON but could not update it, leaving scripts and agents dependent on the desk | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +85/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Adopt Codex terminal sessions into structured native chat1 PR · Standalone · Plugins#
Problem: Adopt Codex terminal sessions into structured native chat.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15411 Adopt Codex terminal sessions into structured native chat | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 30 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk86 files, +5201/−378. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2adopt only the real user replay as a Claude send's identity1 PR · Standalone · Plugins#
Problem: adopt only the real user replay as a Claude send's identity.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15656 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15657 fix(native-chat): adopt only the real user replay as a Claude send's identity | Brennan Benson Core team · MEMBER | #15656 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On the structured (Claude SDK) lane, Orca shows your message immediately and then waits for Claude to echo it back so it can tie the two together by id. Claude uses the same frame shape (`type: "user"`) for sever | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +1363/−429. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2adopt provisioned recipe checkout roots1 PR · Standalone · Plugins#
Problem: adopt provisioned recipe checkout roots.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13044 [Bug]: Enterprise blocker - Create Workspace cannot use machine-isolated SSH environments (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13870 fix(vm): adopt provisioned recipe checkout roots | Jinwoo Hong Core team · MEMBER | #13044 [Bug]: Enterprise blocker - Create Workspace cannot use machine-isolated SSH environments Fixes · CLOSED | Standalone change | ## Summary - add opt-in `checkoutMode: provisioned-root` recipes that adopt the provisioned `projectRoot` instead of running `git worktree add` - require an explicit schema-v2 result handshake so older Orca builds fail c | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk92 files, +4692/−535. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2align multiline filter toggle row text and icons to top-left1 PR · Standalone · Plugins#
Problem: align multiline filter toggle row text and icons to top-left.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16052 [Bug]: Filter toggle row text is center-aligned and vertically misaligned on multiline localized labels (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16054 fix(ui): align multiline filter toggle row text and icons to top-left | hwantage Community · CONTRIBUTOR | #16052 [Bug]: Filter toggle row text is center-aligned and vertically misaligned on multiline localized labels Fixes · OPEN | Standalone change | ## ELI5 When filter toggle labels in the sidebar wrap across multiple lines (such as under Korean, Japanese, or Spanish localizations), the text was displayed center-aligned and the icon and switch were awkwardly placed | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +4/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2allow panels to read plugin storage (storage.get panel: true)1 PR · Standalone · Plugins#
Problem: allow panels to read plugin storage (storage.get panel: true).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14766 feat(plugins): allow panels to read plugin storage (storage.get panel: true) | Vu Khac Hoi Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Plugin panels (the little side-panel UIs plugins can ship) currently can't read any data — they can only send text to terminals and show notifications. This change lets a panel read data that its own plugin's wor | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +1/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Allow plugin panels to invoke their own worker commands1 PR · Standalone · Plugins#
Problem: Allow plugin panels to invoke their own worker commands.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12229 Allow plugin panels to invoke their own worker commands | Syfyivan Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - add a session-bound `plugin.command.invoke` panel action so a plugin panel can call commands registered by its own worker - preserve the existing plugin consent, manifest contribution, registered-handler, me | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +322/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Allow sandboxed panels to read their plugin's own storage (storage.get/storage.keys)1 PR · Standalone · Plugins#
Problem: Allow sandboxed panels to read their plugin's own storage (storage.get/storage.keys).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13220 Allow sandboxed panels to read their plugin's own storage (storage.get/storage.keys) | Cams626 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | # Allow sandboxed panels to read their plugin's own storage ## User-visible change Plugin panels can now call `storage.get` and `storage.keys` over the panel bridge (previously worker-only). This gives panels their first | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +54/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2anchor literal image-marker stripping to a real image send (STA-4363)1 PR · Standalone · Plugins#
Problem: anchor literal image-marker stripping to a real image send (STA-4363).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14581 Title unavailable (Unclear, Unknown); #14738 Title unavailable (Unclear, Unknown); #14665 Title unavailable (Unclear, Unknown); #14819 Title unavailable (Unclear, Unknown); #14162 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14939 fix(native-chat): anchor literal image-marker stripping to a real image send (STA-4363) | Brennan Benson Core team · MEMBER | #14581 Title unavailable Unclear · Unknown #14738 Title unavailable Unclear · Unknown #14665 Title unavailable Unclear · Unknown #14819 Title unavailable Unclear · Unknown #14162 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 24 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk51 files, +2748/−178. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2answer every request when a param schema throws (STA-4818)1 PR · Standalone · Plugins#
Problem: answer every request when a param schema throws (STA-4818).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15460 fix(rpc): answer every request when a param schema throws (STA-4818) | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +610/−51. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2arm first-work branch rename in headless orca serve1 PR · Standalone · Plugins#
Problem: arm first-work branch rename in headless orca serve.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17069 [Bug]: headless `orca serve` never arms first-work branch/workspace auto-rename (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17070 fix: arm first-work branch rename in headless orca serve | Orcun Simsek Community · FIRST_TIME_CONTRIBUTOR | #17069 [Bug]: headless `orca serve` never arms first-work branch/workspace auto-rename Fixes · OPEN | Standalone change | ## ELI5 When an agent starts its first turn, Orca renames the workspace and branch from `snipefish` to something that describes the work. That rename was wired into the callback that only exists while the desktop window | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +69/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2atomically start workers and release terminal custody1 PR · Standalone · Plugins#
Problem: atomically start workers and release terminal custody.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17004 Worker terminal lifecycle can falsely report prompt acceptance and misclassify deliberate stops (Fixes, OPEN); #15180 Title unavailable (Unclear, Unknown); #14822 Title unavailable (Unclear, Unknown); #14505 Title unavailable (Unclear, Unknown); #15920 Title unavailable (Unclear, Unknown); #13047 Title unavailable (Unclear, Unknown); #15976 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17007 fix(orchestration): atomically start workers and release terminal custody | SSWSer Community · CONTRIBUTOR | #17004 Worker terminal lifecycle can falsely report prompt acceptance and misclassify deliberate stops Fixes · OPEN #15180 Title unavailable Unclear · Unknown #14822 Title unavailable Unclear · Unknown #14505 Title unavailable Unclear · Unknown #15920 Title unavailable Unclear · Unknown #13047 Title unavailable Unclear · Unknown #15976 Title unavailable Unclear · Unknown | Standalone change | ### ELI5 A Worker no longer opens an empty terminal and then tries to type a prompt into an agent UI. Orca now creates one supervised Agent Session with the complete first task already attached, waits for an exact provid | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk239 files, +14659/−3446. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2attach a reclaim command to each residual resource in mutation recovery2 PRs · Overlapping · Automated release pipeline#
Problem: attach a reclaim command to each residual resource in mutation recovery.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #15944 [Other]: worker-start names a residual resource with no stated way to reclaim it (Fixes, OPEN); #15920 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15949 fix(cli): attach a reclaim command to each residual resource in mutation recovery | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15944 [Other]: worker-start names a residual resource with no stated way to reclaim it Fixes · OPEN | Cluster contribution | ## What `orchestrationMutationRecoveryError` now appends a reclaim command for each residual resource after the `--retry-request` advice: - `kind: "terminal"` → `If terminal <handle> is still residual after the outcome i | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +117/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15966 fix(cli): route residual reclaim through the Dispatch, not the handle | Tauri-EPO Community · CONTRIBUTOR | #15944 [Other]: worker-start names a residual resource with no stated way to reclaim it Fixes · OPEN #15920 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When starting a worker fails, Orca tells you it left a terminal behind — and then says nothing about how to clean it up. The orchestration guide mentions the command that would do it exactly once, to forbid a dif | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +533/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2attribute account add from the WSL bridge to the caller's distro1 PR · Standalone · Plugins#
Problem: attribute account add from the WSL bridge to the caller's distro.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17089 [Bug]: Managed Claude accounts do not appear in WSL account manager after successful login (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17093 fix(cli): attribute account add from the WSL bridge to the caller's distro | João Gabriel Ribeiro de Nicola Community · FIRST_TIME_CONTRIBUTOR | #17089 [Bug]: Managed Claude accounts do not appear in WSL account manager after successful login Fixes · OPEN | Standalone change | ## ELI5 Adding a Claude/Codex account from inside WSL (`orca-ide account add`) logged in fine, but the account landed in the **Windows** account list instead of the **WSL** one, so the WSL account manager kept saying "No | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +86/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2attribute agent rows to the agent's live worktree via hook cwd1 PR · Standalone · Plugins#
Problem: attribute agent rows to the agent's live worktree via hook cwd.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10572 Agent rows stay under the pane's original worktree after its shell moves into another one (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16574 fix(agent-status): attribute agent rows to the agent's live worktree via hook cwd | Alexander Bocharoff Community · FIRST_TIME_CONTRIBUTOR | #10572 Agent rows stay under the pane's original worktree after its shell moves into another one Fixes · OPEN | Standalone change | ## ELI5 When an agent (Kimi, Claude Code, Codex, ...) is launched in a terminal tab, Orca attributes its agent-status row to the worktree that tab was created in — forever. But agents commonly `cd` into other worktrees m | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +414/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2attribute Cursor legacy transcripts to their project cwd3 PRs · Overlapping · Automated release pipeline#
Problem: attribute Cursor legacy transcripts to their project cwd.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #13931 [Bug]: Cursor sessions are grouped under "Unknown location" and missing from Workspace history on Windows (Fixes, OPEN); #14582 Title unavailable (Unclear, Unknown); #14616 Title unavailable (Unclear, Unknown); #13935 Title unavailable (Unclear, Unknown); #15650 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13935 fix(ai-vault): attribute Cursor legacy transcripts to their project cwd | BingZ Community · CONTRIBUTOR | #13931 [Bug]: Cursor sessions are grouped under "Unknown location" and missing from Workspace history on Windows Fixes · OPEN #14582 Title unavailable Unclear · Unknown #14616 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - Cursor `agent-transcripts` JSONL has no `cwd`; sessions scanned as `cwd: null` → **Unknown location** and missing from Workspace scope (#13931) - Resolve workspace from the project bucket: prefer `.workspace | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +233/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14616 fix(ai-vault): attribute Cursor legacy transcripts without inventing cwd | OrcaWin Unknown · COLLABORATOR | #13931 [Bug]: Cursor sessions are grouped under "Unknown location" and missing from Workspace history on Windows Fixes · OPEN #13935 Title unavailable Unclear · Unknown #14582 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Cursor Agent Session History rows on Windows were showing up under **Unknown location** and disappearing from the **Workspace** tab. Orca found the transcripts, but they had no folder attached. This PR attaches t | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +654/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15705 fix(ai-vault): attribute Cursor transcripts to their project workspace (STA-3959) | Brennan Benson Core team · MEMBER | #13931 [Bug]: Cursor sessions are grouped under "Unknown location" and missing from Workspace history on Windows Fixes · OPEN #13935 Title unavailable Unclear · Unknown #14616 Title unavailable Unclear · Unknown #15650 Title unavailable Unclear · Unknown #14582 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +972/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2auto-dismiss paste focus-cancellation instead of sticky error banner2 PRs · Competing · SSH/remote re-architecture#
Problem: auto-dismiss paste focus-cancellation instead of sticky error banner.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: SSH/remote re-architecture (stack rank 1).
Relationship: Competing. Linked issues: #13623 [Bug]: Paste cancelled (Fixes, OPEN); #16901 Title unavailable (Unclear, Unknown); #16909 Title unavailable (Unclear, Unknown); #17014 Title unavailable (Unclear, Unknown); #16795 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Choose one implementation after a product and technical comparison; do not land alternatives together.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Not until one implementation is chosen.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Product and technical decision required.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13988 fix(terminal): auto-dismiss paste focus-cancellation instead of sticky error banner | OrcaWin Unknown · COLLABORATOR | #13623 [Bug]: Paste cancelled Fixes · OPEN | Alternative implementation | ## Summary Paste cancellations caused by focus change (the Linux-reported case), disconnect, or safety timeout were parked on the durable `TerminalErrorToast` with a persistent red banner and **"If this persists, please | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Substantial changes needed · M Open · checks SUCCESS · review CHANGES_REQUESTED | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: CHANGES_REQUESTED. Unresolved changes-requested reviews observed: 1. Architecture and risk6 files, +337/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16819 Fix terminal paste cancellation after xterm focus replacement | Brennan Benson Core team · MEMBER | #13623 [Bug]: Paste cancelled Fixes · OPEN #16901 Title unavailable Unclear · Unknown #16909 Title unavailable Unclear · Unknown #17014 Title unavailable Unclear · Unknown #16795 Title unavailable Unclear · Unknown | Alternative implementation | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +64/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2auto-surface CLI-added remote servers in the running IDE1 PR · Standalone · Plugins#
Problem: auto-surface CLI-added remote servers in the running IDE.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13596 feat(remote): auto-surface CLI-added remote servers in the running IDE | Martin Matus Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## User-visible change Running `orca environment add --name <name> --pairing-code <orca://pair?...>` in any terminal now makes the running Orca IDE pick up the new remote server automatically: it appears in the saved-ser | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +271/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2autofix scheduled CI run 33021799961 failures1 PR · Standalone · Plugins#
Problem: autofix scheduled CI run 33021799961 failures.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16430 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16816 test(e2e): autofix scheduled CI run 33021799961 failures | Jinjing Core team · MEMBER | #16430 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +78/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2avoid duplicate Windows profile hooks1 PR · Standalone · Plugins#
Problem: avoid duplicate Windows profile hooks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15292 [Bug]: Windows managed CODEX_HOME loads user hooks twice when Codex starts in the user profile (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15312 fix(codex): avoid duplicate Windows profile hooks | poorpaper Community · CONTRIBUTOR | #15292 [Bug]: Windows managed CODEX_HOME loads user hooks twice when Codex starts in the user profile Fixes · OPEN | Standalone change | ## ELI5 When Codex starts from the Windows user profile, the same `.codex/hooks.json` can be discovered twice: once through Orca's managed user-hook mirror and again as the workspace's project hooks. This change detects | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +175/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2avoid repeated capability probes during file imports1 PR · Standalone · Plugins#
Problem: avoid repeated capability probes during file imports.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14554 [Feature]: Avoid repeated capability probes during remote file imports (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14555 perf(remote): avoid repeated capability probes during file imports | dngur6344 Community · CONTRIBUTOR | #14554 [Feature]: Avoid repeated capability probes during remote file imports Fixes · OPEN | Standalone change | ## ELI5 Uploading a file to a remote Orca server used to ask the server the same safety question before every upload chunk and cleanup step. This change asks once when the import starts, then carries that verified answer | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +262/−100. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bind worker placement to the Run, not the task1 PR · Standalone · Plugins#
Problem: bind worker placement to the Run, not the task.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14840 [Feature]: orchestration guide gives the preferred worker-start path no worktree-placement rule, so one Run produces mixed child and top-level lanes (Fixes, OPEN); #14479 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14841 docs(orchestration): bind worker placement to the Run, not the task | Tauri-EPO Community · CONTRIBUTOR | #14840 [Feature]: orchestration guide gives the preferred worker-start path no worktree-placement rule, so one Run produces mixed child and top-level lanes Fixes · OPEN #14479 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When a coordinator agent splits one job into several supervised workers, it has to decide *where* each worker runs — same worktree, a child worktree, or a top-level one. The guide does explain the rule, but it pu | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +49/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bindable tab.moveToNewPaneColumn action1 PR · Standalone · Plugins#
Problem: bindable tab.moveToNewPaneColumn action.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16464 [Feature]: bindable keybinding action to move a tab to a new pane column (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16465 feat(keybindings): bindable tab.moveToNewPaneColumn action | Grinsven Community · FIRST_TIME_CONTRIBUTOR | #16464 [Feature]: bindable keybinding action to move a tab to a new pane column Fixes · OPEN | Standalone change | ## ELI5 You can already move a tab into its own side-by-side column with the mouse (drag it, or right-click → workspace layout). This adds a keyboard shortcut slot for the same move, so you can bind e.g. `Cmd+E` to it. I | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +204/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bounce lifecycle rejections to the sender1 PR · Standalone · Plugins#
Problem: bounce lifecycle rejections to the sender.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13199 Delivery observability: no sender-visible rejection signal, and one message body was lost on a runtime drop (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13217 fix(orchestration): bounce lifecycle rejections to the sender | BingZ Community · CONTRIBUTOR | #13199 Delivery observability: no sender-visible rejection signal, and one message body was lost on a runtime drop Fixes · OPEN | Standalone change | ## Summary - When Orca rewrites a lifecycle message as `Rejected …` for the coordinator, it also inserts a high-priority `status` bounce for the **worker mailbox that `check` reads**. - Bounce destination: `dispatch:<id> | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +231/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound git subprocess execution with an atomic admission scheduler1 PR · Standalone · Plugins#
Problem: bound git subprocess execution with an atomic admission scheduler.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16038 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16874 perf(git): bound git subprocess execution with an atomic admission scheduler | Brennan Benson Core team · MEMBER | #16038 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 69 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk166 files, +6062/−698. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound main-process filesystem reads so a stalled mount cannot freeze the app1 PR · Standalone · Plugins#
Problem: bound main-process filesystem reads so a stalled mount cannot freeze the app.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12015 Title unavailable (Unclear, Unknown); #11841 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12149 fix(filesystem): bound main-process filesystem reads so a stalled mount cannot freeze the app | Neil Core team · MEMBER | #12015 Title unavailable Unclear · Unknown #11841 Title unavailable Unclear · Unknown | Standalone change | ## Problem A synchronous `fs` call against a stalled mount (SMB/NFS share that stops answering, a hung `sshfs`, a Time Machine volume mid-spindown) parks the Electron main thread in an uninterruptible wait. On macOS the | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk170 files, +10981/−1515. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound memory for headless orca serve1 PR · Standalone · Plugins#
Problem: bound memory for headless orca serve.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13434 Title unavailable (Unclear, Unknown); #13061 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13684 perf(serve): bound memory for headless orca serve | Aarav Community · FIRST_TIME_CONTRIBUTOR | #13434 Title unavailable Unclear · Unknown #13061 Title unavailable Unclear · Unknown | Standalone change | ## Summary Headless `orca serve` inherits the desktop's per-window memory footprint. This caps unbounded long-lived Maps and skips work the serve path does not need. ## Per-PTY memory (bench, N=50, `--expose-gc`) ``` scr | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +424/−135. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound the aggregated PTY error surface so recurring near-duplicate errors can't grow it with1 PR · Standalone · Plugins#
Problem: bound the aggregated PTY error surface so recurring near-duplicate errors can't grow it with.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15241 Renderer memory (and CPU) grows unbounded when a terminal pane keeps emitting distinct/multi-line error messages (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15306 fix(terminal): bound the aggregated PTY error surface so recurring near-duplicate errors can't grow it without limit | erish Community · CONTRIBUTOR | #15241 Renderer memory (and CPU) grows unbounded when a terminal pane keeps emitting distinct/multi-line error messages Fixes · OPEN | Standalone change | ## ELI5 A terminal pane on a flaky connection (like a reconnecting SSH link) keeps surfacing the "same" error over and over, but each occurrence differs slightly (timestamp, port, attempt count). Orca was appending every | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +55/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound the codex POSIX hook's stdin read and exec the script from the wrapper1 PR · Standalone · Plugins#
Problem: bound the codex POSIX hook's stdin read and exec the script from the wrapper.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15833 [Bug]: macOS Codex bridge hook blocks unbounded on stdin — declared timeout not enforced; TUI wedges on "Running 2 UserPromptSubmit hooks" (Fixes, OPEN); #13285 Title unavailable (Unclear, Unknown); #7323 Title unavailable (Unclear, Unknown); #8110 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15892 fix(agent-hooks): bound the codex POSIX hook's stdin read and exec the script from the wrapper | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15833 [Bug]: macOS Codex bridge hook blocks unbounded on stdin — declared timeout not enforced; TUI wedges on "Running 2 UserPromptSubmit hooks" Fixes · OPEN #13285 Title unavailable Unclear · Unknown #7323 Title unavailable Unclear · Unknown #8110 Title unavailable Unclear · Unknown | Standalone change | ## What Two changes to the managed codex POSIX hook so a runner that never closes stdin cannot wedge the agent's turn: 1. **Bounded stdin capture.** `buildPosixHookPayloadCapture` gains an optional `maxWaitSeconds` watch | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +192/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound WSL installed skill discovery1 PR · Standalone · Plugins#
Problem: bound WSL installed skill discovery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15913 [Bug]: WSL installed-skill checks scan unrelated roots and time out on populated installations (Fixes, OPEN); #14204 Title unavailable (Unclear, Unknown); #14670 Title unavailable (Unclear, Unknown); #12964 Title unavailable (Unclear, Unknown); #12974 Title unavailable (Unclear, Unknown); #12978 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12314 perf(skills): bound WSL installed skill discovery | PPP-JH Community · FIRST_TIME_CONTRIBUTOR | #15913 [Bug]: WSL installed-skill checks scan unrelated roots and time out on populated installations Fixes · OPEN #14204 Title unavailable Unclear · Unknown #14670 Title unavailable Unclear · Unknown #12964 Title unavailable Unclear · Unknown #12974 Title unavailable Unclear · Unknown #12978 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca checked whether one WSL skill was installed by scanning every known skill and plugin directory. On larger WSL installations that scan exceeded the timeout, so installed skills appeared missing. This change a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +839/−72. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2build(preload): fail the build when a sandboxed preload needs a Node builtin1 PR · Standalone · Plugins#
Problem: build(preload): fail the build when a sandboxed preload needs a Node builtin.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13110 build(preload): fail the build when a sandboxed preload needs a Node builtin | Neil Core team · MEMBER | None found | Standalone change | ## The problem A sandboxed preload can resolve exactly one module: `electron`. Anything else — a Node builtin, a bare npm external, or a Rollup helper chunk — throws at load. The TypeScript import graph does not show thi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +641/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bulk stage reviewed files1 PR · Standalone · Plugins#
Problem: bulk stage reviewed files.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17204 fix(mobile): bulk stage reviewed files | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +501/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bundle Nerd Font terminal fallback1 PR · Standalone · Plugins#
Problem: bundle Nerd Font terminal fallback.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17168 [Bug]: Orca Mobile terminal does not render Nerd Font glyphs on clean Android installs (Fixes, OPEN); #5712 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17220 fix(mobile): bundle Nerd Font terminal fallback | Arthur Chang Community · FIRST_TIME_CONTRIBUTOR | #17168 [Bug]: Orca Mobile terminal does not render Nerd Font glyphs on clean Android installs Fixes · OPEN #5712 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca Mobile asks Android for a Nerd Font when a terminal prompt contains Powerline or Nerd Font symbols, but that font is not included in the app. This bundles the same symbol font already used by desktop Orca so | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +139/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Cache main-process compilation between launches1 PR · Standalone · Plugins#
Problem: Cache main-process compilation between launches.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13487 Cache main-process compilation between launches | Neil Core team · MEMBER | None found | Standalone change | ## Summary - generate a CommonJS main-process bootstrap that preserves the existing fatal-exit guard and startup diagnostics before loading any main-bundle dependency - enable Node's supported module compile cache on mac | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +690/−233. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cancel redundant mail repair after immediate delivery (STA-4235)1 PR · Standalone · Plugins#
Problem: cancel redundant mail repair after immediate delivery (STA-4235).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14332 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14391 perf(orchestration): cancel redundant mail repair after immediate delivery (STA-4235) | Brennan Benson Core team · MEMBER | #14332 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When a message arrives for an agent, Orca points the agent at it right away. It *also* sets a two-second alarm to try again in case the first attempt silently failed. The bug: the alarm was never turned off after | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +154/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2characterize renderer death containment1 PR · Standalone · Plugins#
Problem: characterize renderer death containment.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16084 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16120 test(serve): characterize renderer death containment | Jinwoo Hong Core team · MEMBER | #16084 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +359/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cherry-pick: restore CIM fallback for relay hosts with no native binding (#16550) for 1.4.181 PR · Standalone · Plugins#
Problem: cherry-pick: restore CIM fallback for relay hosts with no native binding (#16550) for 1.4.18.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16550 Title unavailable (Unclear, Unknown); #15749 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16573 cherry-pick: restore CIM fallback for relay hosts with no native binding (#16550) for 1.4.189 [STA-5549] | Neil Core team · MEMBER | #16550 Title unavailable Unclear · Unknown #15749 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +415/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ci(e2e): gate PRs on the green golden lane and cover renderer invariance1 PR · Standalone · Plugins#
Problem: ci(e2e): gate PRs on the green golden lane and cover renderer invariance.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14583 Title unavailable (Unclear, Unknown); #15181 Title unavailable (Unclear, Unknown); #12955 Title unavailable (Unclear, Unknown); #12785 Title unavailable (Unclear, Unknown); #13252 Title unavailable (Unclear, Unknown); #7172 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15302 ci(e2e): gate PRs on the green golden lane and cover renderer invariance | Brennan Benson Core team · MEMBER | #14583 Title unavailable Unclear · Unknown #15181 Title unavailable Unclear · Unknown #12955 Title unavailable Unclear · Unknown #12785 Title unavailable Unclear · Unknown #13252 Title unavailable Unclear · Unknown #7172 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +276/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ci(mobile): publish the Android APK as orca-app-release.apk1 PR · Standalone · Plugins#
Problem: ci(mobile): publish the Android APK as orca-app-release.apk.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16602 [Feature]: Publish the Android APK under an Orca-specific filename instead of Gradle's app-release.apk (Fixes, OPEN); #7583 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16606 ci(mobile): publish the Android APK as orca-app-release.apk | Rashik Hasnat Community · FIRST_TIME_CONTRIBUTOR | #16602 [Feature]: Publish the Android APK under an Orca-specific filename instead of Gradle's app-release.apk Fixes · OPEN #7583 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When you download Orca for Android, the file that lands in your Downloads folder is called `app-release.apk`. That is Gradle's default name for *every* React Native app — Orca never picked it. This makes the buil | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +86/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2classify a permission-denied runtime connect instead of reporting "starting"1 PR · Standalone · Plugins#
Problem: classify a permission-denied runtime connect instead of reporting "starting".
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13539 Title unavailable (Unclear, Unknown); #12528 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13583 fix(cli): classify a permission-denied runtime connect instead of reporting "starting" | Nathan Fetter Community · FIRST_TIME_CONTRIBUTOR | #13539 Title unavailable Unclear · Unknown #12528 Title unavailable Unclear · Unknown | Standalone change | Addresses **Defect 2 only** of #13539 (`Defect 2 — permission-denied connect is mapped to permanent "starting"`). Deliberately **not** `Closes #13539`: Defect 1, the named-pipe DACL that excludes the Codex sandbox princi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +224/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2classify ask --json outcome for engine resume1 PR · Standalone · Plugins#
Problem: classify ask --json outcome for engine resume.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13184 Orchestration ask: harden pending-question resume contract for external engines (AOS) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13188 feat(orchestration): classify ask --json outcome for engine resume | BingZ Community · CONTRIBUTOR | #13184 Orchestration ask: harden pending-question resume contract for external engines (AOS) Fixes · OPEN | Standalone change | ## Summary - External engines (e.g. AOS) treated `ask --json` **exit 1** timeouts as internal failures even when `messageId` was still pending (#13184). - Add first-class `outcome` + `pending` on the bare `--json` payloa | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +195/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2close guest-owned split tab1 PR · Standalone · Plugins#
Problem: close guest-owned split tab.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17281 fix(browser): close guest-owned split tab | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks PENDING · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: PENDING. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +320/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2close readiness gaps found by merged-change audit1 PR · Standalone · Plugins#
Problem: close readiness gaps found by merged-change audit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17144 [Bug]: SSH relay reconnect stalls on orphaned .install-lock after remote restart during native-deps install (Fixes, OPEN); #17002 Title unavailable (Unclear, Unknown); #17001 Title unavailable (Unclear, Unknown); #16971 Title unavailable (Unclear, Unknown); #17009 Title unavailable (Unclear, Unknown); #17011 Title unavailable (Unclear, Unknown); #17010 Title unavailable (Unclear, Unknown); #17012 Title unavailable (Unclear, Unknown); #17008 Title unavailable (Unclear, Unknown); #17126 Title unavailable (Unclear, Unknown); #17130 Title unavailable (Unclear, Unknown); #17122 Title unavailable (Unclear, Unknown); #17124 Title unavailable (Unclear, Unknown); #17163 Title unavailable (Unclear, Unknown); #17047 Title unavailable (Unclear, Unknown); #17083 Title unavailable (Unclear, Unknown); #17110 Title unavailable (Unclear, Unknown); #17114 Title unavailable (Unclear, Unknown); #17127 Title unavailable (Unclear, Unknown); #17046 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17159 fix: close readiness gaps found by merged-change audit | Neil Core team · MEMBER | #17144 [Bug]: SSH relay reconnect stalls on orphaned .install-lock after remote restart during native-deps install Fixes · OPEN #17002 Title unavailable Unclear · Unknown #17001 Title unavailable Unclear · Unknown #16971 Title unavailable Unclear · Unknown #17009 Title unavailable Unclear · Unknown #17011 Title unavailable Unclear · Unknown #17010 Title unavailable Unclear · Unknown #17012 Title unavailable Unclear · Unknown #17008 Title unavailable Unclear · Unknown #17126 Title unavailable Unclear · Unknown #17130 Title unavailable Unclear · Unknown #17122 Title unavailable Unclear · Unknown #17124 Title unavailable Unclear · Unknown #17163 Title unavailable Unclear · Unknown #17047 Title unavailable Unclear · Unknown #17083 Title unavailable Unclear · Unknown #17110 Title unavailable Unclear · Unknown #17114 Title unavailable Unclear · Unknown #17127 Title unavailable Unclear · Unknown #17046 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 31 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk72 files, +1821/−445. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2coalesce scroll-intent settles instead of one per wheel event1 PR · Standalone · Plugins#
Problem: coalesce scroll-intent settles instead of one per wheel event.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16137 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16207 perf(terminal): coalesce scroll-intent settles instead of one per wheel event | Jason Brashear Community · CONTRIBUTOR | #16137 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Every time you nudge the scroll wheel in a terminal, Orca schedules four little jobs to work out "where is the user actually looking now". A trackpad sends those nudges much faster than the screen redraws, and no | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +206/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2codify desktop composition regression checks1 PR · Standalone · Plugins#
Problem: codify desktop composition regression checks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16911 Title unavailable (Unclear, Unknown); #16949 Title unavailable (Unclear, Unknown); #16950 Title unavailable (Unclear, Unknown); #17104 Title unavailable (Unclear, Unknown); #17169 Title unavailable (Unclear, Unknown); #17170 Title unavailable (Unclear, Unknown); #17171 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17172 docs(ime): codify desktop composition regression checks | Neil Core team · MEMBER | #16911 Title unavailable Unclear · Unknown #16949 Title unavailable Unclear · Unknown #16950 Title unavailable Unclear · Unknown #17104 Title unavailable Unclear · Unknown #17169 Title unavailable Unclear · Unknown #17170 Title unavailable Unclear · Unknown #17171 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 This gives future IME fixes one durable checklist: what each regression means, which component owns provisional text, what evidence is required, and what must be checked on macOS, Windows, and Linux/SSH. ## What | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +52/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2collapse path-equal worktree rows without losing lineage1 PR · Standalone · Plugins#
Problem: collapse path-equal worktree rows without losing lineage.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15561 Title unavailable (Unclear, Unknown); #15526 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15872 fix(worktree): collapse path-equal worktree rows without losing lineage | Neil Core team · MEMBER | #15561 Title unavailable Unclear · Unknown #15526 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +593/−35. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2commit AskUserQuestion answers on preview-style selectors2 PRs · Overlapping · Plugins#
Problem: commit AskUserQuestion answers on preview-style selectors.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16865 [Bug]: Chat UI: answering Claude Code's AskUserQuestion dismisses the card into a false in-progress animation — the CLI never receives the answer (Fixes, OPEN); #16914 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16914 fix(native-chat): commit AskUserQuestion answers on preview-style selectorsDraft | Frederic Barthelemy Community · FIRST_TIME_CONTRIBUTOR | #16865 [Bug]: Chat UI: answering Claude Code's AskUserQuestion dismisses the card into a false in-progress animation — the CLI never receives the answer Fixes · OPEN | Cluster contribution | ## ELI5 When Claude Code asks a question whose options carry example-snippet previews, its TUI selector switches to a list + preview layout where pressing a number only highlights an option — a separate Enter press is th | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · S Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +203/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16929 fix(native-chat): hold the question card and pane state until an answer is confirmedDraft | Frederic Barthelemy Community · FIRST_TIME_CONTRIBUTOR | #16865 [Bug]: Chat UI: answering Claude Code's AskUserQuestion dismisses the card into a false in-progress animation — the CLI never receives the answer Fixes · OPEN #16914 Title unavailable Unclear · Unknown | Cluster contribution | > **Stacked on #16914** — its commit rides along until that PR merges; this PR's own changes are the last two commits (`1f5834ba`, `b3610466`). ## ELI5 #16914 taught the Chat card to deliver preview-style AskUserQuestion | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +858/−51. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Complete agent-session-rules delivery + fix repo-context wiring across all call sites1 PR · Standalone · Plugins#
Problem: Complete agent-session-rules delivery + fix repo-context wiring across all call sites.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14046 Complete agent-session-rules delivery + fix repo-context wiring across all call sites | dcsodm09-ship-it Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary This branch started as a stalled merge reconciliation with `main` (terminal/settings UI, main-process sync, onboarding agent session startup) and grew to include finishing an abandoned feature — per-repo **age | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk195 files, +18006/−1060. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2contain crashes and preserve diagnostics1 PR · Standalone · Plugins#
Problem: contain crashes and preserve diagnostics.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16328 Mobile has no crash telemetry and no error boundary, so any render throw kills the app invisibly (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16348 fix(mobile): contain crashes and preserve diagnostics | Brennan Benson Core team · MEMBER | #16328 Mobile has no crash telemetry and no error boundary, so any render throw kills the app invisibly Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +1747/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2continue a session in a new worktree1 PR · Standalone · Plugins#
Problem: continue a session in a new worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16794 feat(agent-session-continuation): continue a session in a new worktree | DmitryGil Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## What exists today The terminal context menu already offers **Continue in New Session…**, and the dialog carries everything the flow needs: an agent picker, a context mode (`Focused handoff` / `Full session transcript` | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +348/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2converge the persisted WS fallback port after the default port recovers (STA-4859)1 PR · Standalone · Plugins#
Problem: converge the persisted WS fallback port after the default port recovers (STA-4859).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7855 Title unavailable (Unclear, Unknown); #9005 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15533 fix(mobile): converge the persisted WS fallback port after the default port recovers (STA-4859) | OrcaWin Unknown · COLLABORATOR | #7855 Title unavailable Unclear · Unknown #9005 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +507/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2copy relay terminal IDs from the remote PTY handle1 PR · Standalone · Plugins#
Problem: copy relay terminal IDs from the remote PTY handle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15553 [Bug]: Copy Terminal ID fails on relay remotes (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15554 fix(terminal): copy relay terminal IDs from the remote PTY handle | Revofusion Community · FIRST_TIME_CONTRIBUTOR | #15553 [Bug]: Copy Terminal ID fails on relay remotes Fixes · OPEN | Standalone change | ## ELI5 Copy Terminal ID looked up the handle on this machine. Relay terminals live on the remote, so the lookup failed. The menu now copies the remote handle that the pane already has. ## What Changed Copy Terminal ID r | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +43/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2correct active-tab surface in light mode (#16283)1 PR · Standalone · Plugins#
Problem: correct active-tab surface in light mode (#16283).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16283 [Bug] Wrong tab design in light mode (Fixes, OPEN); #171717 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16481 fix(tab-bar): correct active-tab surface in light mode (#16283) | Borja Community · CONTRIBUTOR | #16283 [Bug] Wrong tab design in light mode Fixes · OPEN #171717 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 In light mode the selected tab looked *darker* than the unselected ones, so the active tab appeared receded and an inactive tab looked selected. This makes the active tab read as active in both themes. ## What Ch | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +35/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2correct agent commands, shell hooks, and runtime routing1 PR · Standalone · Plugins#
Problem: correct agent commands, shell hooks, and runtime routing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14838 fix: correct agent commands, shell hooks, and runtime routing | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | "## ELI5\\n\\nThis PR fixes five small regressions where Orca either dropped required shell state, passed an unsupported CLI flag, routed a mutation to the wrong runtime, generated a branch name from harness metadata ins | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk53 files, +1449/−191. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2count Codex sessions from running WSL distros1 PR · Standalone · Plugins#
Problem: count Codex sessions from running WSL distros.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15978 [Bug]: Stats & Usage shows zero Codex usage when Codex runs in WSL (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16050 fix(codex-usage): count Codex sessions from running WSL distros | Sahir Community · FIRST_TIME_CONTRIBUTOR | #15978 [Bug]: Stats & Usage shows zero Codex usage when Codex runs in WSL Fixes · OPEN | Standalone change | ## ELI5 Run Codex inside WSL and Stats & Usage stays at zero forever. The usage scanner only looks at Windows-side folders, but WSL transcripts live inside the distro. This teaches the scanner to look there too, without | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +501/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2count IME commits and coalesced echoes in the typing probe2 PRs · Overlapping · Automated release pipeline#
Problem: count IME commits and coalesced echoes in the typing probe.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #16950 [Bug]: The typing-latency probe records zero samples for CJK input (Fixes, OPEN); #17172 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16952 fix(renderer): count IME commits and coalesced echoes in the typing probe | klaatus Community · FIRST_TIME_CONTRIBUTOR | #16950 [Bug]: The typing-latency probe records zero samples for CJK input Fixes · OPEN | Cluster contribution | ## ELI5 There is a built-in stopwatch for "how long from keypress to seeing the character" (`window.__orcaTypingDiagnostic`). Typing Korean produced **zero** readings, so it looked like Korean had no latency at all. It a | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +454/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17171 fix(diagnostics): measure reconciled IME typing latency | Neil Core team · MEMBER | #16950 [Bug]: The typing-latency probe records zero samples for CJK input Fixes · OPEN #17172 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 The typing probe now times composed text when it actually reaches the terminal, instead of timing IME key presses that send no text. ## What Changed - Observe reconciled xterm composition-session commits, includi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +1898/−552. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Create ssh worktree error1 PR · Standalone · Plugins#
Problem: Create ssh worktree error.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15022 Create ssh worktree error | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 12 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +1445/−371. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2declare terminal Helper protected-folder access1 PR · Standalone · Plugins#
Problem: declare terminal Helper protected-folder access.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13766 [Bug]: New terminals error immediately after upgrade: Operation not permitted (os error 1) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16824 fix(mac): declare terminal Helper protected-folder access | Brennan Benson Core team · MEMBER | #13766 [Bug]: New terminals error immediately after upgrade: Operation not permitted (os error 1) Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +131/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2default worker-start --agent to the Settings default agent1 PR · Standalone · Plugins#
Problem: default worker-start --agent to the Settings default agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14895 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15935 feat(orchestration): default worker-start --agent to the Settings default agent | trs-80 Community · FIRST_TIME_CONTRIBUTOR | #14895 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 `orca orchestration worker-start` now launches the user's default agent (from Settings) when the coordinator doesn't pass `--agent`. ## What Changed - `worker-start` without `--agent` resolves to `defaultTuiAgent | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +132/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2defensive worktree selection hardening (#16241)1 PR · Standalone · Plugins#
Problem: defensive worktree selection hardening (#16241).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16241 Title unavailable (Unclear, Unknown); #185 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16253 fix(sidebar): defensive worktree selection hardening (#16241) | Duy /zuey/ Community · FIRST_TIME_CONTRIBUTOR | #16241 Title unavailable Unclear · Unknown #185 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When selecting worktrees in the sidebar, the application previously updated state during the drawing (render) phase to remove hidden items. This change computes the cleaned-up selection directly without updating | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +291/−60. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2deliver paired agent completion and permission alerts1 PR · Standalone · Plugins#
Problem: deliver paired agent completion and permission alerts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16103 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16280 fix(remote): deliver paired agent completion and permission alerts | Jinwoo Hong Core team · MEMBER | #16103 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +1378/−95. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2derive the Claude Keychain account the way Claude Code does2 PRs · Overlapping · Automated release pipeline#
Problem: derive the Claude Keychain account the way Claude Code does.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #12857 macOS: Claude account add always fails when $USER has characters outside [a-zA-Z0-9._-] (Keychain account mismatch) (Fixes, OPEN); #12862 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12862 fix(claude-accounts): derive the Claude Keychain account the way Claude Code does | hope Community · FIRST_TIME_CONTRIBUTOR | #12857 macOS: Claude account add always fails when $USER has characters outside [a-zA-Z0-9._-] (Keychain account mismatch) Fixes · OPEN | Cluster contribution | Fixes #12857 ## Summary On macOS, adding a Claude account always fails with ``` Claude login completed, but no OAuth credentials were captured. ``` when `$USER` contains a character outside `[a-zA-Z0-9._-]` — e.g. an SSO | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +59/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16673 Fix Claude account add when macOS $USER contains @ | Rudimar Ronsoni Community · FIRST_TIME_CONTRIBUTOR | #12857 macOS: Claude account add always fails when $USER has characters outside [a-zA-Z0-9._-] (Keychain account mismatch) Fixes · OPEN #12862 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 On some Macs the OS username is an email (SSO). Claude Code stores login tokens under a fallback Keychain account named `claude-code-user`. Orca looked up the email instead, so "Add Claude account" failed after a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +147/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2detect extracted AppImage CLI launches without APPDIR2 PRs · Overlapping · Profile and resource management#
Problem: detect extracted AppImage CLI launches without APPDIR.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Profile and resource management (stack rank 1).
Relationship: Overlapping. Linked issues: #13004 AppImage CLI redirect never fires for extracted AppImages: AppRun does not export APPDIR/APPIMAGE (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13136 fix(linux): detect extracted AppImage CLI launches without APPDIR | BingZ Community · CONTRIBUTOR | #13004 AppImage CLI redirect never fires for extracted AppImages: AppRun does not export APPDIR/APPIMAGE Fixes · OPEN | Cluster contribution | ## Summary - Detect packaged AppImage layouts via `AppRun` next to `resources`/`execPath` when `APPDIR`/`APPIMAGE` are missing (extracted squashfs-root on Ubuntu 24.04). - Move the CLI command allow-list to `src/shared/a | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +180/−66. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13289 fix(startup): stop gating the AppImage CLI redirect on APPIMAGE/APPDIR | 창진 Community · FIRST_TIME_CONTRIBUTOR | #13004 AppImage CLI redirect never fires for extracted AppImages: AppRun does not export APPDIR/APPIMAGE Fixes · OPEN | Cluster contribution | ## Summary Fixes #13004. The AppImage CLI redirect (`maybeRedirectAppImageCliLaunch` / `getAppImageCliArgs` in `src/main/startup/appimage-cli-redirect.ts`) never fires for an extracted AppImage or a `.deb` install, so `< | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +129/−113. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2detect Homebrew-installed CLIs in the install-dir fallback1 PR · Standalone · Plugins#
Problem: detect Homebrew-installed CLIs in the install-dir fallback.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15959 [Bug]: Homebrew-installed agent CLIs are missed by the install-dir fallback detection (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15960 fix(agents): detect Homebrew-installed CLIs in the install-dir fallback | Daekeun Kang Community · FIRST_TIME_CONTRIBUTOR | #15959 [Bug]: Homebrew-installed agent CLIs are missed by the install-dir fallback detection Fixes · OPEN | Standalone change | ## ELI5 If you installed Claude Code (or another agent CLI) with Homebrew, Orca could fail to notice it exists whenever brew's bin folder wasn't on `PATH` yet — so skill installs silently skipped Claude Code and the skil | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +88/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2disable setuid sandbox for headless CLI on extracted runtime1 PR · Standalone · Plugins#
Problem: disable setuid sandbox for headless CLI on extracted runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14229 Linux: packaged CLI (orca-ide) crashes on chrome-sandbox SUID error for headless commands, blocking remote-project orchestration (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14230 fix(linux): disable setuid sandbox for headless CLI on extracted runtime | Yunqian Fan Community · CONTRIBUTOR | #14229 Linux: packaged CLI (orca-ide) crashes on chrome-sandbox SUID error for headless commands, blocking remote-project orchestration Fixes · OPEN | Standalone change | ## ELI5 Running a text-only Orca CLI command on Linux (like `orca-ide skills get orchestration`) crashed instead of printing, because the packaged app tried to boot its Chromium GUI — and Chromium's security sandbox abor | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +399/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2disclaim TCC responsibility at PTY spawn instead of relying on login(1)1 PR · Standalone · Plugins#
Problem: disclaim TCC responsibility at PTY spawn instead of relying on login(1).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #1693 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17191 fix(macos): disclaim TCC responsibility at PTY spawn instead of relying on login(1) | Brennan Benson Core team · MEMBER | #1693 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +360/−38. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2discover effort menus from the host CLI catalog (STA-4320)2 PRs · Overlapping · Plugins#
Problem: discover effort menus from the host CLI catalog (STA-4320).
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #14506 [Bug]: bundled Codex reasoning-effort catalog is stale (caps at xhigh), blocking max/ultra that Codex 0.147.0 supports (Fixes, OPEN); #14281 Title unavailable (Unclear, Unknown); #13183 Title unavailable (Unclear, Unknown); #15314 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15687 fix(codex): discover effort menus from the host CLI catalog (STA-4320) | Brennan Benson Core team · MEMBER | #14506 [Bug]: bundled Codex reasoning-effort catalog is stale (caps at xhigh), blocking max/ultra that Codex 0.147.0 supports Fixes · OPEN #14281 Title unavailable Unclear · Unknown #13183 Title unavailable Unclear · Unknown #15314 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +650/−181. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15890 fix(codex): accept max/ultra reasoning effort for aliased and dated model ids | Neil Core team · MEMBER | #14506 [Bug]: bundled Codex reasoning-effort catalog is stale (caps at xhigh), blocking max/ultra that Codex 0.147.0 supports Fixes · OPEN #14281 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +226/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2dismiss the banner id a Claude background turn announced (STA-4592)1 PR · Standalone · Plugins#
Problem: dismiss the banner id a Claude background turn announced (STA-4592).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14580 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15047 fix(notifications): dismiss the banner id a Claude background turn announced (STA-4592) | Brennan Benson Core team · MEMBER | #14580 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +588/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2dispatch coordinate pointer input in process instead of one subprocess per event1 PR · Standalone · Plugins#
Problem: dispatch coordinate pointer input in process instead of one subprocess per event.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15308 Interactive input in the remote browser pane costs ~160ms per event -- every mouse/key event spawns a subprocess on the host (Fixes, OPEN); #10875 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15309 perf(browser): dispatch coordinate pointer input in process instead of one subprocess per event | Jared Meek Community · FIRST_TIME_CONTRIBUTOR | #15308 Interactive input in the remote browser pane costs ~160ms per event -- every mouse/key event spawns a subprocess on the host Fixes · OPEN #10875 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Moving the mouse in the remote browser pane launches a whole new process on the host for every wiggle, click and scroll tick -- about 160ms each, and a click is four of them. This makes the runtime deliver mouse | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +704/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document cmd.exe quoting for gesture JSON1 PR · Standalone · Plugins#
Problem: document cmd.exe quoting for gesture JSON.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12712 Skill guides claim cmd.exe neutrality but use single-quoted JSON in gesture examples (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13249 docs(skills): document cmd.exe quoting for gesture JSON | BingZ Community · CONTRIBUTOR | #12712 Skill guides claim cmd.exe neutrality but use single-quoted JSON in gesture examples Fixes · OPEN | Standalone change | ## ELI5 Windows `cmd.exe` does not use single quotes to group JSON arguments. The existing skill guides said their examples worked in every shell, so a Windows user could copy a gesture command that necessarily fails JSO | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +93/−39. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document cross-runtime federation1 PR · Standalone · Plugins#
Problem: document cross-runtime federation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14063 docs(orchestration): document cross-runtime federation | Calvin Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Orca can already run an orchestration worker on a *different* paired Orca runtime — a laptop coordinating a worker on a VPS, or the reverse. The engine ships and works: it's the existing `orca orchestration worke | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +196/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document run-use takeover preconditions1 PR · Standalone · Plugins#
Problem: document run-use takeover preconditions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12034 `run-use --takeover-legacy` returns `legacy_read_only` for an adopted run with `coordinator_handle: null`, across six attempted terminal configurations (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13256 docs(orchestration): document run-use takeover preconditions | BingZ Community · CONTRIBUTOR | #12034 `run-use --takeover-legacy` returns `legacy_read_only` for an adopted run with `coordinator_handle: null`, across six attempted terminal configurations Fixes · CLOSED | Standalone change | ## Summary `--takeover-legacy` looked like a universal recovery for adopted Runs, but it only works for the auto-adopted recovery Run, from a live agent terminal with matching current-authority proof. Callers hitting `le | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +26/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document runtime outage delivery1 PR · Standalone · Plugins#
Problem: document runtime outage delivery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12986 [Docs] What happens to `worker_done` / `ask` sent while the runtime is unreachable — queued or lost? (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12997 docs(orchestration): document runtime outage delivery | Wooseong Kim Community · CONTRIBUTOR | #12986 [Docs] What happens to `worker_done` / `ask` sent while the runtime is unreachable — queued or lost? Fixes · OPEN | Standalone change | ## Description Document the delivery and recovery contract for orchestration commands during runtime outages. ## Focused fix - In scope: explain direct runtime delivery, the non-retry behavior on transport loss, the `run | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +43/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document terminal read --screen and realign drifted help usage1 PR · Standalone · Plugins#
Problem: document terminal read --screen and realign drifted help usage.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15856 orca-cli skill guide does not document `terminal read --screen` (added in 1.4.187) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15893 docs(cli): document terminal read --screen and realign drifted help usage | Jason Brashear Community · CONTRIBUTOR | #15856 orca-cli skill guide does not document `terminal read --screen` (added in 1.4.187) Fixes · OPEN | Standalone change | ## ELI5 Orca's `terminal read` learned a `--screen` option a couple of versions ago, but the instruction sheet Orca hands to coding agents was never updated to mention it. So agents keep using the old default, which retu | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +6/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document worker-stop terminal-close contract1 PR · Standalone · Plugins#
Problem: document worker-stop terminal-close contract.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13197 worker-stop: clarify the terminal-close contract, or add an explicit --close-terminal flag (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13198 docs(orchestration): document worker-stop terminal-close contract | BingZ Community · CONTRIBUTOR | #13197 worker-stop: clarify the terminal-close contract, or add an explicit --close-terminal flag Fixes · OPEN | Standalone change | ## Summary - Documents the `worker-stop` terminal-close contract on CLI `--help` notes and in the orchestration skill guide. - Successful stop of the **exact live** supervised worker closes that agent terminal and report | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +29/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2don't hand a non-JS npm_execpath to node in build:native1 PR · Standalone · Plugins#
Problem: don't hand a non-JS npm_execpath to node in build:native.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16655 [Bug]: build:native passes the standalone pnpm binary to node, failing with SyntaxError (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16657 fix(build): don't hand a non-JS npm_execpath to node in build:native | Skyler Shaw Community · FIRST_TIME_CONTRIBUTOR | #16655 [Bug]: build:native passes the standalone pnpm binary to node, failing with SyntaxError Fixes · OPEN | Standalone change | ## Author X: [@skythediver](https://x.com/skythediver) ## In short `pnpm build` fails on machines where pnpm was installed as its standalone binary rather than through Corepack or npm. The native build step tries to run | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +80/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2don't re-run an agent resume against a relay that never held the terminal (STA-5698)1 PR · Standalone · Plugins#
Problem: don't re-run an agent resume against a relay that never held the terminal (STA-5698).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16839 Title unavailable (Unclear, Unknown); #16901 Title unavailable (Unclear, Unknown); #16763 Title unavailable (Unclear, Unknown); #16985 Title unavailable (Unclear, Unknown); #16980 Title unavailable (Unclear, Unknown); #16894 Title unavailable (Unclear, Unknown); #16895 Title unavailable (Unclear, Unknown); #16843 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16989 fix(relay): don't re-run an agent resume against a relay that never held the terminal (STA-5698) | Brennan Benson Core team · MEMBER | #16839 Title unavailable Unclear · Unknown #16901 Title unavailable Unclear · Unknown #16763 Title unavailable Unclear · Unknown #16985 Title unavailable Unclear · Unknown #16980 Title unavailable Unclear · Unknown #16894 Title unavailable Unclear · Unknown #16895 Title unavailable Unclear · Unknown #16843 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +420/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drain the reaped child's journal writes before an attach reports1 PR · Standalone · Plugins#
Problem: drain the reaped child's journal writes before an attach reports.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17115 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17160 fix(native-chat): drain the reaped child's journal writes before an attach reports | Brennan Benson Core team · MEMBER | #17115 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +176/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop a recorded permission escalation the settings no longer grant1 PR · Standalone · Plugins#
Problem: drop a recorded permission escalation the settings no longer grant.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6281 Title unavailable (Unclear, Unknown); #10886 Title unavailable (Unclear, Unknown); #15166 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15606 fix(agent-resume): drop a recorded permission escalation the settings no longer grant | mys Community · FIRST_TIME_CONTRIBUTOR | #6281 Title unavailable Unclear · Unknown #10886 Title unavailable Unclear · Unknown #15166 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Orca starts an agent, it remembers the exact command it used so it can bring that session back later. If that command contained a "skip all permission prompts" flag, the flag is remembered too — so turning t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +704/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop disposed queued inspections1 PR · Standalone · Plugins#
Problem: drop disposed queued inspections.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17187 perf(terminals): drop disposed queued inspections | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +93/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2eliminate recurring PowerShell process polling1 PR · Standalone · Plugins#
Problem: eliminate recurring PowerShell process polling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16905 [Bug]: orca-terminal-daemon still spawns powershell.exe every ~2s on v1.4.190 (partial fix from #15209 / #15749) — memory collector + identity probes not migrated to native process-tree reader (Fixes, OPEN); #15209 Title unavailable (Unclear, Unknown); #15749 Title unavailable (Unclear, Unknown); #16696 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17115 fix(windows): eliminate recurring PowerShell process polling | OrcaWin Unknown · COLLABORATOR | #16905 [Bug]: orca-terminal-daemon still spawns powershell.exe every ~2s on v1.4.190 (partial fix from #15209 / #15749) — memory collector + identity probes not migrated to native process-tree reader Fixes · OPEN #15209 Title unavailable Unclear · Unknown #15749 Title unavailable Unclear · Unknown #16696 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 29 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk69 files, +3464/−1501. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2emit browser_element_not_interactable for dead controls1 PR · Standalone · Plugins#
Problem: emit browser_element_not_interactable for dead controls.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13242 Runtime error code `browser_element_not_interactable` is declared but never emitted (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13243 fix(browser): emit browser_element_not_interactable for dead controls | BingZ Community · CONTRIBUTOR | #13242 Runtime error code `browser_element_not_interactable` is declared but never emitted Fixes · OPEN | Standalone change | ## ELI5 Browser actions now distinguish a dead or blocked control from an unknown browser failure, so agents can re-snapshot or choose another control instead of blindly retrying. ## What Changed - Emit `browser_element_ | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +1172/−92. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2enable isolated floating tab reordering1 PR · Standalone · Plugins#
Problem: enable isolated floating tab reordering.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16754 fix(tabs): enable isolated floating tab reordering | moonrailgun Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 The floating terminal window now has its own drag-and-drop context, so its tabs can be reordered without affecting tabs in the main workspace. ## What Changed - Mounted the existing tab drag context inside the fl | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +177/−51. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2enforce list-issues pagination backstops1 PR · Standalone · Plugins#
Problem: enforce list-issues pagination backstops.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16119 Title unavailable (Unclear, Unknown); #15824 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16128 fix(linear): enforce list-issues pagination backstops | Brennan Benson Core team · MEMBER | #16119 Title unavailable Unclear · Unknown #15824 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +342/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2enforce one bounded structured writer1 PR · Standalone · Plugins#
Problem: enforce one bounded structured writer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13438 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14251 fix(codex): enforce one bounded structured writerDraft | KimGyeongSeok Community · FIRST_TIME_CONTRIBUTOR | #13438 Title unavailable Unclear · Unknown | Standalone change | ## Summary - add a host-owned, single-use structured source-write lease for one bound Git worktree - deny shell, Python, MCP, Git, publication, and unbound/canonical/sibling writes in this activation lane - bind request | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk96 files, +7391/−538. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2enforce the bridge contract the renderer already trusts1 PR · Standalone · Plugins#
Problem: enforce the bridge contract the renderer already trusts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17192 fix(preload): enforce the bridge contract the renderer already trusts | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +49/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2engage GPU software-rendering fallback across launches1 PR · Standalone · Plugins#
Problem: engage GPU software-rendering fallback across launches.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12488 fix(gpu): engage GPU software-rendering fallback across launches | Neil Core team · MEMBER | None found | Standalone change | ## What this fixes **Signature:** Windows renderer `render-process-gone { reason: "crashed" }` where a **GPU child process died with the identical exit code 25-100 ms earlier**. Exit codes `-2147483645` (`0x80000003` STA | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +961/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2escalate renderer launch-failed to a Restart Orca prompt instead of reloading a dead webCont1 PR · Standalone · Plugins#
Problem: escalate renderer launch-failed to a Restart Orca prompt instead of reloading a dead webCont.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12487 fix(window): escalate renderer launch-failed to a Restart Orca prompt instead of reloading a dead webContents | Neil Core team · MEMBER | None found | Standalone change | ## What this fixes **Crash signature:** win32 renderer `render-process-gone { reason: 'launch-failed', exitCode: 18 }`, answered by Orca with reloads of the same wedged `webContents`, ending in a permanently blank window | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +249/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2exclude a directory subtree in the git-grep search fallback1 PR · Standalone · Plugins#
Problem: exclude a directory subtree in the git-grep search fallback.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15722 [Bug]: git-grep search fallback ignores a directory exclude that ripgrep honours (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15721 fix: exclude a directory subtree in the git-grep search fallback | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15722 [Bug]: git-grep search fallback ignores a directory exclude that ripgrep honours Fixes · OPEN | Standalone change | ## ELI5 If you exclude `node_modules` from a search, that only works when ripgrep is installed. On a machine without it, Orca falls back to `git grep` — and there the exclude did nothing, so you still got results from in | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +82/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2expand serve host agent-skills install guide1 PR · Standalone · Plugins#
Problem: expand serve host agent-skills install guide.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11885 [Feature]: Add an Orca Serve guide for installing and updating Orca skills (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13262 docs(headless): expand serve host agent-skills install guide | BingZ Community · CONTRIBUTOR | #11885 [Feature]: Add an Orca Serve guide for installing and updating Orca skills Fixes · OPEN | Standalone change | ## Summary Headless `orca serve` operators already had `orca skills install` / `update` in the Linux server reference, but not a full path for discovering skills, installing the common serve set (CLI, orchestration, Line | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +98/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Explain broken npx shim skill update failures1 PR · Standalone · Plugins#
Problem: Explain broken npx shim skill update failures.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17028 Explain broken npx shim skill update failures | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +133/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2explain tab titles vs agents paneKey join1 PR · Standalone · Plugins#
Problem: explain tab titles vs agents paneKey join.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12674 [Docs]: skill guide never explains terminal title semantics (rename sets the tab title) nor the agents[] paneKey join for locating agent panes (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12813 docs(orca-cli): explain tab titles vs agents paneKey join | Wooseong Kim Community · CONTRIBUTOR | #12674 [Docs]: skill guide never explains terminal title semantics (rename sets the tab title) nor the agents[] paneKey join for locating agent panes Fixes · OPEN | Standalone change | ## Description Document tab-title vs `terminals[].title` semantics and the `worktree ps` → `agents[].paneKey` join for locating agent panes in the orca-cli skill guide. ## Focused fix - In scope: `skill-guides/orca-cli.m | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +9/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2export plugin factory instead of object default (#16245)1 PR · Standalone · Plugins#
Problem: export plugin factory instead of object default (#16245).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16245 [Bug]: object default export in orca-opencode-status.js breaks opencode 1.1.23 plugin load (macOS v1.4.188; same defect as #15897 on Linux) (Fixes, OPEN); #15897 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16270 fix(opencode): export plugin factory instead of object default (#16245) | Cal Community · CONTRIBUTOR | #16245 [Bug]: object default export in orca-opencode-status.js breaks opencode 1.1.23 plugin load (macOS v1.4.188; same defect as #15897 on Linux) Fixes · OPEN #15897 Title unavailable Unclear · Unknown | Standalone change | REPO: stablyai/orca | BRANCH: fix/object-default-export-breaks-opencode-16245 | BASE: main | HEAD: adityachaudhary99 TITLE: fix(opencode): export plugin factory instead of object default (#16245) BODY: Closes #16245 Also | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +20/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Expose active workspace in macOS window metadata1 PR · Standalone · Plugins#
Problem: Expose active workspace in macOS window metadata.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12569 Expose active workspace in macOS window metadata | Jordan Yeo Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Orca's custom macOS window currently exposes a generic native title and no represented document, so document-aware utilities can identify Orca but not the active workspace. This PR: - sets the native title to | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +339/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2expose client-hosted tab placement (STA-5504)1 PR · Standalone · Plugins#
Problem: expose client-hosted tab placement (STA-5504).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15448 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16502 fix(browser): expose client-hosted tab placement (STA-5504) | Jinwoo Hong Core team · MEMBER | #15448 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +241/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fail safe on concurrent WSL auth drain writes1 PR · Standalone · Plugins#
Problem: fail safe on concurrent WSL auth drain writes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16504 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16786 fix(codex): fail safe on concurrent WSL auth drain writes | Brennan Benson Core team · MEMBER | #16504 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +807/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fail terminal create without a terminal handle1 PR · Standalone · Plugins#
Problem: fail terminal create without a terminal handle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13200 terminal create returned ok with a null id, and the terminal never appeared in list (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13204 fix(cli): fail terminal create without a terminal handle | BingZ Community · CONTRIBUTOR | #13200 terminal create returned ok with a null id, and the terminal never appeared in list Fixes · OPEN | Standalone change | ## ELI5 `orca terminal create` once reported success but returned no usable terminal handle, so follow-up commands failed later and the terminal never appeared in `terminal list`. The CLI now treats that malformed succes | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +86/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fail worker startup on early agent exit1 PR · Standalone · Plugins#
Problem: fail worker startup on early agent exit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16233 fix(orchestration): fail worker startup on early agent exit | rmarquesAvatel Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | Paquete B del diagnóstico de fábrica (PLANS/ORCA_DIAGNOSTICO_OPENCODE_TERMINAL_READYING_2026_08_23.md). Si el agente muere durante el arranque, el worker ahora falla el startup en vez de quedar colgado; incluye prueba de | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +793/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fall back to default Pi/OMP session roots for non-absolute env values1 PR · Standalone · Plugins#
Problem: fall back to default Pi/OMP session roots for non-absolute env values.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12935 Title unavailable (Unclear, Unknown); #13082 Title unavailable (Unclear, Unknown); #13118 Title unavailable (Unclear, Unknown); #14121 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13020 fix(ai-vault): fall back to default Pi/OMP session roots for non-absolute env values | Evgenii Community · CONTRIBUTOR | #12935 Title unavailable Unclear · Unknown #13082 Title unavailable Unclear · Unknown #13118 Title unavailable Unclear · Unknown #14121 Title unavailable Unclear · Unknown | Standalone change | ## Summary `normalizeAgentSessionsDir` returned non-empty, non-absolute values unchanged, so a degenerate `PI_CODING_AGENT_DIR` / `OMP_CODING_AGENT_DIR` — `rel/path`, `.`, `..`, or the drive-relative `C:`/`C:foo` a Windo | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +25/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fall back to parent-pane worktree for orchestration workers1 PR · Standalone · Plugins#
Problem: fall back to parent-pane worktree for orchestration workers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17019 fix(sidebar): fall back to parent-pane worktree for orchestration workers | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 The sidebar sometimes says "0 running" for a project that actually has an agent working, until the agent's own terminal tab shows up. This fixes that. ## What Changed `liveEntryWorktreeId()` (sidebar per-project | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +45/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fall back when search-index lag returns zero items3 PRs · Overlapping · Automated release pipeline#
Problem: fall back when search-index lag returns zero items.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #12648 [Bug] Projects tab shows "No items match this view's filter" during GitHub's project search-index lag — n (Fixes, OPEN); #13609 Title unavailable (Unclear, Unknown); #13566 Title unavailable (Unclear, Unknown); #13710 Title unavailable (Unclear, Unknown); #13692 Title unavailable (Unclear, Unknown); #13691 Title unavailable (Unclear, Unknown); #13536 Title unavailable (Unclear, Unknown); #13572 Title unavailable (Unclear, Unknown); #8072 Title unavailable (Unclear, Unknown); #13237 Title unavailable (Unclear, Unknown); #13570 Title unavailable (Unclear, Unknown); #13255 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12819 fix(github-project): fall back when search-index lag returns zero items | Wooseong Kim Community · CONTRIBUTOR | #12648 [Bug] Projects tab shows "No items match this view's filter" during GitHub's project search-index lag — n Fixes · OPEN | Cluster contribution | ## Description When an unfiltered Project view returns totalCount 0 via the search-index `query:""` path, retry once with plain `items(first:N)` so index lag does not show a false empty board. ## Focused fix - In scope: | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +73/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13138 fix(github-project): fall back when search-index lag returns zero items | LavyaT Community · FIRST_TIME_CONTRIBUTOR | #12648 [Bug] Projects tab shows "No items match this view's filter" during GitHub's project search-index lag — n Fixes · OPEN | Cluster contribution | ## What GitHub Projects can show "No items match this view's filter" during search-index lag after bulk-population, even when the board has items. The indexed query returns `totalCount: 0` while an unfiltered `items(firs | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +34/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13561 fix(github): skip Projects search index for unfiltered views | BingZ Community · CONTRIBUTOR | #12648 [Bug] Projects tab shows "No items match this view's filter" during GitHub's project search-index lag — n Fixes · OPEN #13609 Title unavailable Unclear · Unknown #13566 Title unavailable Unclear · Unknown #13710 Title unavailable Unclear · Unknown #13692 Title unavailable Unclear · Unknown #13691 Title unavailable Unclear · Unknown #13536 Title unavailable Unclear · Unknown #13572 Title unavailable Unclear · Unknown #8072 Title unavailable Unclear · Unknown #13237 Title unavailable Unclear · Unknown #13570 Title unavailable Unclear · Unknown #13255 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - Unfiltered Project views still called `items(query: \"\")`, which uses GitHub's Projects search index and can return empty results for ~an hour after bulk populate (#12648). - When the view filter is empty/w | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +50/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fast-forward a claimed existing branch inside its new worktree (#15645)1 PR · Standalone · Plugins#
Problem: fast-forward a claimed existing branch inside its new worktree (#15645).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15645 Title unavailable (Unclear, Unknown); #15815 Title unavailable (Unclear, Unknown); #15796 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15868 fix(worktree): fast-forward a claimed existing branch inside its new worktree (#15645) | Neil Core team · MEMBER | #15645 Title unavailable Unclear · Unknown #15815 Title unavailable Unclear · Unknown #15796 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +196/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2feed the relay-withheld reattach tail into main's model behind an ingest fence (STA-4716)1 PR · Standalone · Plugins#
Problem: feed the relay-withheld reattach tail into main's model behind an ingest fence (STA-4716).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14844 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15347 fix(ssh): feed the relay-withheld reattach tail into main's model behind an ingest fence (STA-4716) | Neil Core team · MEMBER | #14844 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When you're working on a server over SSH and the connection blips, the server has been holding on to some terminal output for you. On reconnect it hands that backlog over — but it hands it **straight to your scre | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +982/−41. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fence final-pane close by incarnation (STA-4489)1 PR · Standalone · Plugins#
Problem: fence final-pane close by incarnation (STA-4489).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15582 fix(terminal): fence final-pane close by incarnation (STA-4489)Draft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 21 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk47 files, +2307/−243. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fence I/O by process incarnation1 PR · Standalone · Plugins#
Problem: fence I/O by process incarnation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15584 [Bug]: Terminal I/O can cross PTY process boundaries (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15585 fix(terminal): fence I/O by process incarnation | Alex Community · FIRST_TIME_CONTRIBUTOR | #15584 [Bug]: Terminal I/O can cross PTY process boundaries Fixes · OPEN | Standalone change | ## ELI5 A terminal slot can be reused by a different process. This change lets automation prove that terminal output still belongs to the exact process it selected and stops an in-progress write if that process changes. | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +2338/−107. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fill missing zh translations and align agent terminology policy1 PR · Standalone · Plugins#
Problem: fill missing zh translations and align agent terminology policy.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15464 Title unavailable (Unclear, Unknown); #5046 Title unavailable (Unclear, Unknown); #8923 Title unavailable (Unclear, Unknown); #9574 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17049 fix(i18n): fill missing zh translations and align agent terminology policy | Dazzle-sys Community · FIRST_TIME_CONTRIBUTOR | #15464 Title unavailable Unclear · Unknown #5046 Title unavailable Unclear · Unknown #8923 Title unavailable Unclear · Unknown #9574 Title unavailable Unclear · Unknown | Standalone change | # PR 描述草稿（分支 fix/zh-localization-gaps-and-terminology） ## ELI5 Orca's Simplified Chinese UI had 1,890 strings that showed up in English (or raw machine translation) because the zh catalog lagged behind the code. This fil | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +2583/−446. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fill OpenCode block glyphs in the DOM renderer1 PR · Standalone · Plugins#
Problem: fill OpenCode block glyphs in the DOM renderer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15953 [Bug]: OpenCode composer shows a 1px hairline when GPU acceleration is off (Fixes, OPEN); #15813 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15955 fix(terminal): fill OpenCode block glyphs in the DOM renderer | gatsby74 Community · CONTRIBUTOR | #15953 [Bug]: OpenCode composer shows a 1px hairline when GPU acceleration is off Fixes · OPEN #15813 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 With GPU acceleration off, OpenCode’s composer box has a 1px dark line under it. The DOM renderer was drawing `▀` from the font, which does not fill the cell. This paints those block characters as a CSS fill that | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +319/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Filter workspaces by catalog agent1 PR · Standalone · Plugins#
Problem: Filter workspaces by catalog agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15334 Filter workspaces by catalog agent | s546126 Community · CONTRIBUTOR | None found | Standalone change | ## Summary Adds a workspace Agent filter that matches the existing Host All / multi-select interaction. - The workspace-options menu has an Agent submenu (same control as Hosts). Default is All agents. Clicking one agent | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk40 files, +1637/−118. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2find the SFTP-visible home below a chrooted start directory1 PR · Standalone · Plugins#
Problem: find the SFTP-visible home below a chrooted start directory.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12868 [Bug]: SSH SFTP relay upload fails with "No such file" on Synology NAS (SFTP root lands on shared-folder list, not user home) (Fixes, OPEN); #15479 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17073 fix(ssh): find the SFTP-visible home below a chrooted start directory | Alex Guerrieri Community · FIRST_TIME_CONTRIBUTOR | #12868 [Bug]: SSH SFTP relay upload fails with "No such file" on Synology NAS (SFTP root lands on shared-folder list, not user home) Fixes · OPEN #15479 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On some NAS boxes, the SSH shell and the SFTP file transfer live in different directory trees. Orca used to upload the relay using the shell home path. SFTP does not see that path, so the upload failed with "No s | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +273/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2finish agent list pagination1 PR · Standalone · Plugins#
Problem: finish agent list pagination.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16119 fix(linear): finish agent list pagination | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 12 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +1258/−195. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2finish agent list pagination (ports #16119 onto main)1 PR · Standalone · Plugins#
Problem: finish agent list pagination (ports #16119 onto main).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16119 Title unavailable (Unclear, Unknown); #16770 Title unavailable (Unclear, Unknown); #16168 Title unavailable (Unclear, Unknown); #16128 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17056 fix(linear): finish agent list pagination (ports #16119 onto main) | Brennan Benson Core team · MEMBER | #16119 Title unavailable Unclear · Unknown #16770 Title unavailable Unclear · Unknown #16168 Title unavailable Unclear · Unknown #16128 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 `orca linear list` shows your Linear issues. If you didn't pass a limit, it quietly fetched only the first page — 20 issues — and handed it back as though that were the whole list. Nothing told you anything was m | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk38 files, +1746/−434. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix a skill install lock release moving a directory it no longer owns1 PR · Standalone · Plugins#
Problem: Fix a skill install lock release moving a directory it no longer owns.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17118 Fix a skill install lock release moving a directory it no longer owns | Brennan Benson Core team · MEMBER | #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +301/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix authorization for coalesced worktree scans1 PR · Standalone · Plugins#
Problem: Fix authorization for coalesced worktree scans.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17112 Fix authorization for coalesced worktree scans | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +172/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix Chromium descriptor inheritance into the terminal daemon and its PTY children (Linux/Win1 PR · Standalone · Plugins#
Problem: Fix Chromium descriptor inheritance into the terminal daemon and its PTY children (Linux/Win.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15666 Title unavailable (Unclear, Unknown); #16955 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16963 Fix Chromium descriptor inheritance into the terminal daemon and its PTY children (Linux/Windows) | Brennan Benson Core team · MEMBER | #15666 Title unavailable Unclear · Unknown #16955 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +1420/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix inherited PTY setup launch state1 PR · Standalone · Plugins#
Problem: Fix inherited PTY setup launch state.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16777 Title unavailable (Unclear, Unknown); #16336 Title unavailable (Unclear, Unknown); #16778 Title unavailable (Unclear, Unknown); #16900 Title unavailable (Unclear, Unknown); #16908 Title unavailable (Unclear, Unknown); #16926 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16909 Fix inherited PTY setup launch state | Brennan Benson Core team · MEMBER | #16777 Title unavailable Unclear · Unknown #16336 Title unavailable Unclear · Unknown #16778 Title unavailable Unclear · Unknown #16900 Title unavailable Unclear · Unknown #16908 Title unavailable Unclear · Unknown #16926 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +169/−71. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix inline agent mouse wheel scrolling1 PR · Standalone · Plugins#
Problem: Fix inline agent mouse wheel scrolling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8563 [Bug]: Mouse wheel sends arrow keys to a normal-buffer CLI without mouse reporting, cycling its input history (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17103 Fix inline agent mouse wheel scrolling | Wonjun Community · FIRST_TIME_CONTRIBUTOR | #8563 [Bug]: Mouse wheel sends arrow keys to a normal-buffer CLI without mouse reporting, cycling its input history Fixes · OPEN | Standalone change | ## ELI5 When Codex runs inline, rolling the mouse wheel should move through the transcript. Orca now scrolls the terminal buffer directly instead of letting xterm turn the wheel into Up/Down keys that replace the current | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +103/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix installed skill visibility by provider registry1 PR · Standalone · Plugins#
Problem: Fix installed skill visibility by provider registry.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12422 [Bug] No skill /orchestration, even though it's installed? (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16284 Fix installed skill visibility by provider registry | Brennan Benson Core team · MEMBER | #12422 [Bug] No skill /orchestration, even though it's installed? Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +112/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix macOS daemon PTY kqueue descriptor leak1 PR · Standalone · Plugins#
Problem: Fix macOS daemon PTY kqueue descriptor leak.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12728 Memory leak: orca-terminal-daemon private memory grows to 300-400+ MB per process and is never released; system RAM exhausted (88.5% used) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16870 Fix macOS daemon PTY kqueue descriptor leak | Brennan Benson Core team · MEMBER | #12728 Memory leak: orca-terminal-daemon private memory grows to 300-400+ MB per process and is never released; system RAM exhausted (88.5% used) Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +34/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix macOS updater relaunch races during installation1 PR · Standalone · Plugins#
Problem: Fix macOS updater relaunch races during installation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10291 [Bug]: Orca Fails to Update Because the Running Process Is Automatically Restarted (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17137 Fix macOS updater relaunch races during installation | Jinwoo Hong Core team · MEMBER | #10291 [Bug]: Orca Fails to Update Because the Running Process Is Automatically Restarted Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +1458/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix mobile browser frames after reconnect (STA-4128)1 PR · Standalone · Plugins#
Problem: Fix mobile browser frames after reconnect (STA-4128).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14274 [Bug]: Mobile browser pane freezes on the last frame after a relay/direct-socket transport reconnect (Fixes, OPEN); #14115 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16122 Fix mobile browser frames after reconnect (STA-4128) | Brennan Benson Core team · MEMBER | #14274 [Bug]: Mobile browser pane freezes on the last frame after a relay/direct-socket transport reconnect Fixes · OPEN #14115 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +536/−112. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix mobile capability recovery after reconnect1 PR · Standalone · Plugins#
Problem: Fix mobile capability recovery after reconnect.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16347 One transient status.get failure permanently disables idempotent worktree.create replay and hides the mobile Tasks UI (Fixes, OPEN); #16342 Title unavailable (Unclear, Unknown); #16329 Title unavailable (Unclear, Unknown); #16917 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16850 Fix mobile capability recovery after reconnect | Brennan Benson Core team · MEMBER | #16347 One transient status.get failure permanently disables idempotent worktree.create replay and hides the mobile Tasks UI Fixes · OPEN #16342 Title unavailable Unclear · Unknown #16329 Title unavailable Unclear · Unknown #16917 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +1075/−128. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix orchestration CLI recovery, settled-Dispatch mail, and guide defects1 PR · Standalone · Plugins#
Problem: Fix orchestration CLI recovery, settled-Dispatch mail, and guide defects.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16919 Fix orchestration CLI recovery, settled-Dispatch mail, and guide defects | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +757/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix orchestration delivery head-of-line visibility1 PR · Standalone · Plugins#
Problem: Fix orchestration delivery head-of-line visibility.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16522 orchestration check replays oldest unacked delivery and hides newer messages (head-of-line blocking) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16840 Fix orchestration delivery head-of-line visibility | Brennan Benson Core team · MEMBER | #16522 orchestration check replays oldest unacked delivery and hides newer messages (head-of-line blocking) Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +720/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix paired web skill commands to use host platform1 PR · Standalone · Plugins#
Problem: Fix paired web skill commands to use host platform.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12252 [Bug]: Remote Linux host mis-detected as Windows for agent/platform commands (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16072 Fix paired web skill commands to use host platformDraft | Jinwoo Hong Core team · MEMBER | #12252 [Bug]: Remote Linux host mis-detected as Windows for agent/platform commands Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 29 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk64 files, +2391/−357. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix populated sidebar lineage drop targets1 PR · Standalone · Plugins#
Problem: Fix populated sidebar lineage drop targets.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15167 Fix populated sidebar lineage drop targetsDraft | Sam Lijin Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Dragging a workspace onto a parent that already had children measured the whole expanded subtree as the parent card. That moved the intentional center drop zone away from the parent itself. The drop zone now stop | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +200/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix PR unlink for auto-detected reviews1 PR · Standalone · Plugins#
Problem: Fix PR unlink for auto-detected reviews.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #4242 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16898 Fix PR unlink for auto-detected reviews | Brennan Benson Core team · MEMBER | #4242 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 35 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk92 files, +2514/−198. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix review note shortcuts in AI diffs1 PR · Standalone · Plugins#
Problem: Fix review note shortcuts in AI diffs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15260 [Bug]: Review note shortcuts do not work consistently in AI diffs and folder workspaces (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15255 Fix review note shortcuts in AI diffs | seoahlab Community · FIRST_TIME_CONTRIBUTOR | #15260 [Bug]: Review note shortcuts do not work consistently in AI diffs and folder workspaces Fixes · OPEN | Standalone change | ## ELI5 Review-note shortcuts worked in regular Markdown editors but were ignored in AI diff editors and some folder workspaces. This change makes the existing Add Review Note and Send Review Notes flows work consistentl | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +777/−185. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix sidebar grouping for paired remote projects1 PR · Standalone · Plugins#
Problem: Fix sidebar grouping for paired remote projects.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16315 Fix sidebar grouping for paired remote projects | Luis Sebastian Urrutia Fuentes Community · CONTRIBUTOR | None found | Standalone change | ## ELI5 Moving a paired remote project into a sidebar group could appear to work while leaving the project ungrouped. Group actions now use the project's owning host, and the menu only offers groups that host can use. Wh | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk44 files, +1592/−164. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2flag a config host whose machine is already registered under another name1 PR · Standalone · Plugins#
Problem: flag a config host whose machine is already registered under another name.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15478 [Bug]: Same machine can be added twice as an SSH host (manual IP + ssh-config alias); duplicate entries share one relay so they act as one host (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15750 fix: flag a config host whose machine is already registered under another name | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15478 [Bug]: Same machine can be added twice as an SSH host (manual IP + ssh-config alias); duplicate entries share one relay so they act as one host Fixes · OPEN | Standalone change | ## ELI5 Add a machine by IP, then open the ssh-config picker: the same box shows up as new, because Orca compared the *names* and `172.16.203.131` is not the string `aimp`. Now it also compares where the entry actually c | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +154/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2focus the pane a host-delegated split creates2 PRs · Overlapping · Plugins#
Problem: focus the pane a host-delegated split creates.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16510 [Bug]: Cmd+D split in a paired remote session leaves focus on the source pane (Fixes, OPEN); #5435 Title unavailable (Unclear, Unknown); #16513 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16513 fix(remote): focus the pane a host-delegated split creates | ASDFGHoney Community · FIRST_TIME_CONTRIBUTOR | #16510 [Bug]: Cmd+D split in a paired remote session leaves focus on the source pane Fixes · OPEN #5435 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Split a terminal with `Cmd+D` on your own machine and you can start typing in the new pane straight away. Do it on a workspace hosted by a remote Orca runtime and the pane shows up but your typing still goes to t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +509/−97. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16886 fix(remote): focus host-delegated split panes | Jinwoo Hong Core team · MEMBER | #16510 [Bug]: Cmd+D split in a paired remote session leaves focus on the source pane Fixes · OPEN #5435 Title unavailable Unclear · Unknown #16513 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +1447/−82. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2follow agent-side session renames in agent rows1 PR · Standalone · Plugins#
Problem: follow agent-side session renames in agent rows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9707 [Bug]: Renamed session title is not shown in the sidebar or tab (Fixes, OPEN); #10250 Title unavailable (Unclear, Unknown); #16094 Title unavailable (Unclear, Unknown); #15497 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16431 fix(sidebar): follow agent-side session renames in agent rows | roc Community · FIRST_TIME_CONTRIBUTOR | #9707 [Bug]: Renamed session title is not shown in the sidebar or tab Fixes · OPEN #10250 Title unavailable Unclear · Unknown #16094 Title unavailable Unclear · Unknown #15497 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When you rename a session inside the agent (e.g. Codex `/rename`), Orca's tab already picks up the new name, but the agent row in the left sidebar keeps the old/default label. This PR makes the sidebar row (and t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +174/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2follow live Claude session names instead of the first prompt (STA-4865)1 PR · Standalone · Plugins#
Problem: follow live Claude session names instead of the first prompt (STA-4865).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15497 Claude session name for a terminal pane is resolved once and never refreshed (stale tab label + session list) (Fixes, OPEN); #15703 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15659 fix(tabs): follow live Claude session names instead of the first prompt (STA-4865) | Brennan Benson Core team · MEMBER | #15497 Claude session name for a terminal pane is resolved once and never refreshed (stale tab label + session list) Fixes · OPEN #15703 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 12 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +934/−53. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2forward the client's resolved agent args to paired hosts1 PR · Standalone · Plugins#
Problem: forward the client's resolved agent args to paired hosts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15611 Title unavailable (Unclear, Unknown); #9687 Title unavailable (Unclear, Unknown); #15373 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15867 fix(runtime): forward the client's resolved agent args to paired hosts | Neil Core team · MEMBER | #15611 Title unavailable Unclear · Unknown #9687 Title unavailable Unclear · Unknown #15373 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +126/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Gate paired-runtime terminal mounts on host snapshots2 PRs · Related · Plugins#
Problem: Gate paired-runtime terminal mounts on host snapshots.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Related. Linked issues: #15622 Opening a paired-runtime workspace can respawn every stale terminal (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15624 Gate paired-runtime terminal mounts on host snapshots | Revofusion Community · FIRST_TIME_CONTRIBUTOR | #15622 Opening a paired-runtime workspace can respawn every stale terminal Fixes · OPEN | Cluster contribution | ## ELI5 Orca now waits for the current remote host's terminal list before mounting saved tabs, so dead entries cannot open duplicate shells. ## What Changed - Gate paired-runtime mounts on a connection-matched `session.t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +181/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15807 fix(terminal-pane): gate remote pane spawns on the first session.tabs snapshot | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15622 Opening a paired-runtime workspace can respawn every stale terminal Fixes · OPEN | Cluster contribution | ## Summary **What** A runtime-owned pane with **no PTY binding** now waits for its worktree's first accepted `session.tabs` snapshot before connecting its transport (timer-polled at 200ms — hidden tabs get no animation f | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +191/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2gate pending agent-status retries1 PR · Standalone · Plugins#
Problem: gate pending agent-status retries.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17254 perf(renderer): gate pending agent-status retries | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +249/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2gate the CDP proxy on Origin and loopback Host1 PR · Standalone · Plugins#
Problem: gate the CDP proxy on Origin and loopback Host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #5035 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12921 fix(browser): gate the CDP proxy on Origin and loopback Host | Shani Singh Community · CONTRIBUTOR | #5035 Title unavailable Unclear · Unknown | Standalone change | ## Summary Gate the agent-browser CDP proxy's WebSocket upgrade and HTTP discovery endpoints on two request checks, so only a local CDP client can reach them. `CdpWsProxy` binds an HTTP + WebSocket server on an ephemeral | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +327/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2gate the OSC 9999 parser with a pane-bound nonce1 PR · Standalone · Plugins#
Problem: gate the OSC 9999 parser with a pane-bound nonce.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14033 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14709 fix(agent-status): gate the OSC 9999 parser with a pane-bound nonce | Brennan Benson Core team · MEMBER | #14033 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +801/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2GC expired proven-absent leaf PTY verdicts2 PRs · Overlapping · SSH/remote re-architecture#
Problem: GC expired proven-absent leaf PTY verdicts.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: SSH/remote re-architecture (stack rank 1).
Relationship: Overlapping. Linked issues: #12660 P2: GC expired provenAbsentLeafPtyVerdicts entries without re-probe (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12810 fix(runtime): GC expired proven-absent leaf PTY verdicts | Wooseong Kim Community · CONTRIBUTOR | #12660 P2: GC expired provenAbsentLeafPtyVerdicts entries without re-probe Fixes · OPEN | Cluster contribution | ## Description Sweep TTL-expired `provenAbsentLeafPtyVerdicts` entries without requiring a re-probe of that `ptyId`. Expired absence cache entries previously lived for the process lifetime when a dead leaf was never touc | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +57/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13146 fix(runtime): GC expired proven-absent leaf PTY verdicts | BingZ Community · CONTRIBUTOR | #12660 P2: GC expired provenAbsentLeafPtyVerdicts entries without re-probe Fixes · OPEN | Cluster contribution | ## ELI5 Orca remembers when the terminal controller proves that an old PTY no longer exists, avoiding a probe on every keystroke. Those short-lived records now expire and the cache can never remain above 256 entries afte | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +127/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give each worktree its own dev userData profile1 PR · Standalone · Plugins#
Problem: give each worktree its own dev userData profile.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15647 [Bug]: pnpm dev from two worktrees shares one userData profile, so the CLI silently addresses the wrong dev instance (Fixes, OPEN); #1419 Title unavailable (Unclear, Unknown); #2068 Title unavailable (Unclear, Unknown); #2111 Title unavailable (Unclear, Unknown); #1511 Title unavailable (Unclear, Unknown); #15247 Title unavailable (Unclear, Unknown); #10840 Title unavailable (Unclear, Unknown); #15183 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15648 fix(dev): give each worktree its own dev userData profile | Yorai Levi Community · FIRST_TIME_CONTRIBUTOR | #15647 [Bug]: pnpm dev from two worktrees shares one userData profile, so the CLI silently addresses the wrong dev instance Fixes · OPEN #1419 Title unavailable Unclear · Unknown #2068 Title unavailable Unclear · Unknown #2111 Title unavailable Unclear · Unknown #1511 Title unavailable Unclear · Unknown #15247 Title unavailable Unclear · Unknown #10840 Title unavailable Unclear · Unknown #15183 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If you run `pnpm dev` from two different worktrees, both dev builds write their state into the same folder. They both run fine, but only one of them can be "the" Orca that `orca <cmd>` talks to — and it's whichev | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +332/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give Orca's own durable deletions the rm retry policy1 PR · Standalone · Plugins#
Problem: give Orca's own durable deletions the rm retry policy.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17245 Title unavailable (Unclear, Unknown); #17227 Title unavailable (Unclear, Unknown); #17201 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17252 fix(windows): give Orca's own durable deletions the rm retry policy | Brennan Benson Core team · MEMBER | #17245 Title unavailable Unclear · Unknown #17227 Title unavailable Unclear · Unknown #17201 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +466/−96. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give terminal send a lossless payload route with --text-stdin1 PR · Standalone · Plugins#
Problem: give terminal send a lossless payload route with --text-stdin.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12231 Title unavailable (Unclear, Unknown); #12234 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12239 feat(cli): give terminal send a lossless payload route with --text-stdin | logii Community · FIRST_TIME_CONTRIBUTOR | #12231 Title unavailable Unclear · Unknown #12234 Title unavailable Unclear · Unknown | Standalone change | Addresses the highest-volume half of #12231. Independent of #12234 — different files, no overlap, either can land first. ## Summary `orca terminal send --text` is the busiest payload path in the CLI, and on WSL argv cann | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +138/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give the CLI one entrypoint by extracting the AppImage once1 PR · Standalone · Plugins#
Problem: give the CLI one entrypoint by extracting the AppImage once.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11609 [Bug]: Registered CLI (orca/orca-ide) exits 9 with "bad option: --no-sandbox" on userns-restricted Linux — AppRun injects the Chromium flag into ELECTRON_RUN_AS_NODE invocations (Fixes, OPEN); #12530 [Bug]: Registered AppImage CLI fails without /dev/fuse and has no no-FUSE fallback (Fixes, OPEN); #14229 Title unavailable (Unclear, Unknown); #13719 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15081 fix(linux): give the CLI one entrypoint by extracting the AppImage once | Neil Core team · MEMBER | #11609 [Bug]: Registered CLI (orca/orca-ide) exits 9 with "bad option: --no-sandbox" on userns-restricted Linux — AppRun injects the Chromium flag into ELECTRON_RUN_AS_NODE invocations Fixes · OPEN #12530 [Bug]: Registered AppImage CLI fails without /dev/fuse and has no no-FUSE fallback Fixes · OPEN #14229 Title unavailable Unclear · Unknown #13719 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +448/−252. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give the listener lists one registration path1 PR · Standalone · Plugins#
Problem: give the listener lists one registration path.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17058 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17279 refactor(daemon): give the listener lists one registration path | Brennan Benson Core team · MEMBER | #17058 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +53/−56. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give the Windows lane's teardowns the repo's rm retry policy1 PR · Standalone · Plugins#
Problem: give the Windows lane's teardowns the repo's rm retry policy.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17227 test(windows): give the Windows lane's teardowns the repo's rm retry policy | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +325/−51. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give user-facing deletions the repo's rm retry policy1 PR · Standalone · Plugins#
Problem: give user-facing deletions the repo's rm retry policy.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17227 Title unavailable (Unclear, Unknown); #17252 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17245 fix(windows): give user-facing deletions the repo's rm retry policy | Brennan Benson Core team · MEMBER | #17227 Title unavailable Unclear · Unknown #17252 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +289/−76. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2guarantee directory handle closure via fs-opendir-scope1 PR · Standalone · Plugins#
Problem: guarantee directory handle closure via fs-opendir-scope.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17033 Title unavailable (Unclear, Unknown); #12895 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17035 fix(shared): guarantee directory handle closure via fs-opendir-scope | Quim T. Community · FIRST_TIME_CONTRIBUTOR | #17033 Title unavailable Unclear · Unknown #12895 Title unavailable Unclear · Unknown | Standalone change | ## Linked Issue #17033 (fixes the two leaking sites described there; #12895 has the generator-side root cause) ## ELI5 Some code that lists directories forgets to close the directory handle when something goes wrong (a c | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +219/−43. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2harden regional preference recovery1 PR · Standalone · Plugins#
Problem: harden regional preference recovery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14366 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16487 fix(relay): harden regional preference recovery | Jinwoo Hong Core team · MEMBER | #14366 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +460/−115. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2hibernate Hermes sessions1 PR · Standalone · Plugins#
Problem: hibernate Hermes sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10046 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12075 feat(agents): hibernate Hermes sessions | GoodFarming Community · FIRST_TIME_CONTRIBUTOR | #10046 Title unavailable Unclear · Unknown | Standalone change | ## In plain English Completed local Hermes sessions can return after Orca restarts instead of losing their resumable session identity. ## Summary - treat Hermes as an existing resumable TUI agent - persist its managed-ho | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +59/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Highlight incomplete onboarding progress in the sidebar1 PR · Standalone · Plugins#
Problem: Highlight incomplete onboarding progress in the sidebar.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16545 [Feature]: Highlight incomplete onboarding progress in the sidebar (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16547 Highlight incomplete onboarding progress in the sidebar | dlab-anton Community · FIRST_TIME_CONTRIBUTOR | #16545 [Feature]: Highlight incomplete onboarding progress in the sidebar Fixes · OPEN | Standalone change | ## ELI5 The incomplete onboarding checklist used a muted gray progress ring in the sidebar even though the same ring is green after opening **Getting started**. This makes the sidebar ring green too, so first-time users | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +59/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2highlight systemd and Quadlet unit files1 PR · Standalone · Plugins#
Problem: highlight systemd and Quadlet unit files.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15322 [Feature]: Add syntax highlighting for systemd/Podman Quadlet unit files (.container, .service, .network, ...) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15571 feat(editor): highlight systemd and Quadlet unit files | TracerMain Community · FIRST_TIME_CONTRIBUTOR | #15322 [Feature]: Add syntax highlighting for systemd/Podman Quadlet unit files (.container, .service, .network, ...) Fixes · OPEN | Standalone change | ## ELI5 Orca recognizes a file's type from its extension. This teaches it that systemd and Podman Quadlet files use INI-style syntax, so files such as `postgresql.container` and `app.service` receive the same highlightin | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +43/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2highlight XAML files as XML1 PR · Standalone · Plugins#
Problem: highlight XAML files as XML.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16396 [Feature]: syntax highlighting for .xaml files (WPF/MAUI) (Fixes, OPEN); #16421 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16530 feat(editor): highlight XAML files as XML | Seongho.Bak Community · CONTRIBUTOR | #16396 [Feature]: syntax highlighting for .xaml files (WPF/MAUI) Fixes · OPEN #16421 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca currently opens XAML files as plain text. This teaches the editor to treat `.xaml` files as XML so Monaco's built-in XML highlighting can color their tags, attributes, values, and comments. ## What Changed - | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +6/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2honor pinned workspace display preference2 PRs · Overlapping · Plugins#
Problem: honor pinned workspace display preference.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15494 [Bug][Mobile]: Pinned workspaces remain duplicated in grouped lists (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15495 fix(mobile): honor pinned workspace display preference | GhostFlying Community · FIRST_TIME_CONTRIBUTOR | #15494 [Bug][Mobile]: Pinned workspaces remain duplicated in grouped lists Fixes · OPEN | Cluster contribution | ## ELI5 Desktop normally shows a pinned workspace only once, in the Pinned section. Mobile kept showing that same workspace again in All or another selected group. This change makes mobile follow the desktop preference, | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +152/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15881 fix(mobile): stop duplicating pinned workspaces in grouped lists | Neil Core team · MEMBER | #15494 [Bug][Mobile]: Pinned workspaces remain duplicated in grouped lists Fixes · OPEN | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +468/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2honor the per-host workspace directory when resolving worktree paths1 PR · Standalone · Plugins#
Problem: honor the per-host workspace directory when resolving worktree paths.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15320 [Bug]: Per-host "Workspace Directory" override never reaches worktree path resolution (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15321 fix(worktrees): honor the per-host workspace directory when resolving worktree paths | Buqian Zheng Community · FIRST_TIME_CONTRIBUTOR | #15320 [Bug]: Per-host "Workspace Directory" override never reaches worktree path resolution Fixes · OPEN | Standalone change | ## ELI5 Settings → Workspace Directory lets you say "put worktrees here", and it has an "Apply to: \<host\>" picker so a remote SSH machine can use a different folder than your laptop. That picker saved your answer and t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +293/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2honour the step in a cron field's bare start value (5/15 ran hourly)2 PRs · Overlapping · Plugins#
Problem: honour the step in a cron field's bare start value (5/15 ran hourly).
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15723 [Bug]: a cron field's bare start value drops its step — `5/15` runs hourly, and validates (Fixes, OPEN); #15864 Title unavailable (Unclear, Unknown); #15605 Title unavailable (Unclear, Unknown); #15895 Title unavailable (Unclear, Unknown); #15896 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15605 fix: honour the step in a cron field's bare start value (5/15 ran hourly) | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15723 [Bug]: a cron field's bare start value drops its step — `5/15` runs hourly, and validates Fixes · OPEN #15864 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 If you set an automation's custom cron to `5/15 * * * *` — meaning "every 15 minutes, starting at :05" — Orca accepted it and then ran it **once an hour**. The `/15` was silently thrown away, and the schedule edi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +28/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15864 fix(automations): honour the step in a cron field's bare start value | Neil Core team · MEMBER | #15723 [Bug]: a cron field's bare start value drops its step — `5/15` runs hourly, and validates Fixes · OPEN #15605 Title unavailable Unclear · Unknown #15895 Title unavailable Unclear · Unknown #15896 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +68/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ignore orphan remote-tracking refs in branch conflicts1 PR · Standalone · Plugins#
Problem: ignore orphan remote-tracking refs in branch conflicts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16646 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16699 fix(worktree): ignore orphan remote-tracking refs in branch conflicts | JahyunBaek Community · CONTRIBUTOR | #16646 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca was treating a leftover name under refs/remotes as a real remote branch, so worktree creation could add an unnecessary -2 suffix. The original fix corrected native and WSL creation; the maintainer follow-up | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +48/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ignore status posts from an extension Orca did not launch1 PR · Standalone · Plugins#
Problem: ignore status posts from an extension Orca did not launch.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17243 fix(agent-hooks): ignore status posts from an extension Orca did not launch | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +889/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2include open files in all-types cycling1 PR · Standalone · Plugins#
Problem: include open files in all-types cycling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16389 [Bug]: All-types tab shortcuts skip open file tabs (Fixes, OPEN); #13767 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16422 fix(tabs): include open files in all-types cycling | Han Community · CONTRIBUTOR | #16389 [Bug]: All-types tab shortcuts skip open file tabs Fixes · OPEN #13767 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The tab bar could visibly recover an open file when its saved tab order was stale, but keyboard navigation used the stale list directly. The file stayed clickable while the all-types shortcuts could not reach it. | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +144/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2include verified selected home in resume discovery snapshot (STA-4919)1 PR · Standalone · Plugins#
Problem: include verified selected home in resume discovery snapshot (STA-4919).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15046 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15660 fix(codex): include verified selected home in resume discovery snapshot (STA-4919) | Brennan Benson Core team · MEMBER | #15046 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +335/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2index folder-workspace tabs so they are reachable from the palette1 PR · Standalone · Plugins#
Problem: index folder-workspace tabs so they are reachable from the palette.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9939 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17039 fix(cmd-j): index folder-workspace tabs so they are reachable from the palette | Eugenio Valeiras Community · FIRST_TIME_CONTRIBUTOR | #9939 Title unavailable Unclear · Unknown | Standalone change | ## The bug Every tab in every folder workspace is unreachable from Cmd+J. Searching an agent tab by its exact title returns no result, with the tab open and visible in the sidebar. I hit this with a folder workspace name | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +814/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2index unread completion tabs once per snapshot1 PR · Standalone · Plugins#
Problem: index unread completion tabs once per snapshot.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13554 Title unavailable (Unclear, Unknown); #16173 Title unavailable (Unclear, Unknown); #9318 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17246 perf(renderer): index unread completion tabs once per snapshot | Neil Core team · MEMBER | #13554 Title unavailable Unclear · Unknown #16173 Title unavailable Unclear · Unknown #9318 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +90/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2install anti-detection before first document1 PR · Standalone · Plugins#
Problem: install anti-detection before first document.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14698 fix(browser): install anti-detection before the first guest document (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14796 fix(browser): install anti-detection before first document | BingZ Community · CONTRIBUTOR | #14698 fix(browser): install anti-detection before the first guest document Fixes · OPEN | Standalone change | ## ELI5 The embedded browser now installs its anti-detection browser APIs from the guest preload, before the first page can run JavaScript, instead of racing an asynchronous CDP setup after the webview is already attache | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +967/−199. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2install SSH Codex hooks into login-shell CODEX_HOME (STA-4054)1 PR · Standalone · Plugins#
Problem: install SSH Codex hooks into login-shell CODEX_HOME (STA-4054).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14113 [Bug]: Codex agents are not recognized as agents in Orca and the Agent Dashboard. (Fixes, CLOSED); #15650 Title unavailable (Unclear, Unknown); #15705 Title unavailable (Unclear, Unknown); #15695 Title unavailable (Unclear, Unknown); #15658 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15715 fix(agent-hooks): install SSH Codex hooks into login-shell CODEX_HOME (STA-4054) | Brennan Benson Core team · MEMBER | #14113 [Bug]: Codex agents are not recognized as agents in Orca and the Agent Dashboard. Fixes · CLOSED #15650 Title unavailable Unclear · Unknown #15705 Title unavailable Unclear · Unknown #15695 Title unavailable Unclear · Unknown #15658 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +234/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2install supervisor disconnect quit after app environment init1 PR · Standalone · Plugins#
Problem: install supervisor disconnect quit after app environment init.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16761 orca serve crashes at startup on macOS with "AppEnvironment not initialized" (1.4.190 regression) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16762 fix(serve): install supervisor disconnect quit after app environment init | spellbook Community · FIRST_TIME_CONTRIBUTOR | #16761 orca serve crashes at startup on macOS with "AppEnvironment not initialized" (1.4.190 regression) Fixes · OPEN | Standalone change | ## ELI5 On macOS, `orca serve` asked "am I supervised?" before the app had figured out where its data directory is. Asking that question resolves a path, and resolving a path that early throws on purpose — so the serve p | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +22/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a Claude pane spinning across a mid-turn Orca restart1 PR · Standalone · Plugins#
Problem: keep a Claude pane spinning across a mid-turn Orca restart.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16538 fix(agent-status): keep a Claude pane spinning across a mid-turn Orca restart | Neil Core team · MEMBER | None found | Standalone change | ## ELI5 After an Orca update, a Claude process could keep running in its preserved terminal while every Orca status surface looked idle until Claude emitted another hook. Orca now confirms that restored status only when | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +1084/−35. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a composition tail in the colours its cells had1 PR · Standalone · Plugins#
Problem: keep a composition tail in the colours its cells had.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16025 [Bug]: A composing syllable redraws the row tail in the default foreground, so a dim placeholder reads as entered text (Fixes, OPEN); #12545 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16024 fix(terminal): keep a composition tail in the colours its cells had | Hyeonho Lee (Ethan) Community · CONTRIBUTOR | #16025 [Bug]: A composing syllable redraws the row tail in the default foreground, so a dim placeholder reads as entered text Fixes · OPEN #12545 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When you start typing a Korean syllable into an empty agent CLI prompt, the syllable is still being composed and has not reached the shell yet — so the CLI's grey hint text is still sitting on that row. Orca draw | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +684/−120. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a deliberately slept workspace from respawning its PTY1 PR · Standalone · Plugins#
Problem: keep a deliberately slept workspace from respawning its PTY.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10205 [Bug]: Sleeping workspaces revive without user activation — hard to diagnose (open question on opt-in lifecycle logging) (Fixes, OPEN); #12672 Title unavailable (Unclear, Unknown); #14728 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13343 fix(terminal): keep a deliberately slept workspace from respawning its PTY | gatsby74 Community · CONTRIBUTOR | #10205 [Bug]: Sleeping workspaces revive without user activation — hard to diagnose (open question on opt-in lifecycle logging) Fixes · OPEN #12672 Title unavailable Unclear · Unknown #14728 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Putting a workspace to sleep could briefly stop its terminals and then silently restart them during unrelated background work. Sleeping now sticks until the workspace is explicitly opened or woken, and explicit w | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +385/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a tab launch draft out of split sibling composers1 PR · Standalone · Plugins#
Problem: keep a tab launch draft out of split sibling composers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16695 [Bug]: splitting a pane can restore a stale unsent composer draft into the new pane (Fixes, OPEN); #11253 Title unavailable (Unclear, Unknown); #16290 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16883 fix(native-chat): keep a tab launch draft out of split sibling composers | Neil Core team · MEMBER | #16695 [Bug]: splitting a pane can restore a stale unsent composer draft into the new pane Fixes · OPEN #11253 Title unavailable Unclear · Unknown #16290 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +249/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a workspace Windows refused to delete, and say why1 PR · Standalone · Plugins#
Problem: keep a workspace Windows refused to delete, and say why.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15541 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17173 fix(worktrees): keep a workspace Windows refused to delete, and say why | Brennan Benson Core team · MEMBER | #15541 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +1099/−144. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep agent input cursor on the prompt after buffer replay1 PR · Standalone · Plugins#
Problem: keep agent input cursor on the prompt after buffer replay.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7279 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12808 fix(terminal): keep agent input cursor on the prompt after buffer replay | Yoel Community · CONTRIBUTOR | #7279 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Background agent PTYs were replaying eager-buffered terminal bytes into xterm at the pane's fitted grid instead of the grid those bytes were rendered at. Inline TUIs like Cursor Agent then parked the block c | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +698/−86. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep Android layout intact in Samsung DeX / external-display windows1 PR · Standalone · Plugins#
Problem: keep Android layout intact in Samsung DeX / external-display windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8592 [Bug]: Orca Mobile is unusable in Samsung DeX (severe lag, stale rendering, non-responsive layout) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16018 fix(mobile): keep Android layout intact in Samsung DeX / external-display windows | phs2131 Community · FIRST_TIME_CONTRIBUTOR | #8592 [Bug]: Orca Mobile is unusable in Samsung DeX (severe lag, stale rendering, non-responsive layout) Fixes · OPEN | Standalone change | ## ELI5 On a Galaxy phone in Samsung DeX the Orca app only painted a phone-sized box in the top-left corner of its window, and "restarted" whenever the window was resized or DeX was toggled. The app now fills the window, | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk55 files, +3721/−1642. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep archived sessions out of backfill1 PR · Standalone · Plugins#
Problem: keep archived sessions out of backfill.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14028 Archived Codex tasks can be resurrected by session backfill (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14029 fix(codex): keep archived sessions out of backfill | Darren Morgan Community · FIRST_TIME_CONTRIBUTOR | #14028 Archived Codex tasks can be resurrected by session backfill Fixes · OPEN | Standalone change | ## ELI5 Once a Codex task is archived, Orca now treats that archived file like a do-not-resurrect marker. It will not copy the task back into the active list during background repair. ## What Changed - Resolve the Codex | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +896/−116. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep attach guard behind client timeout1 PR · Standalone · Plugins#
Problem: keep attach guard behind client timeout.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16386 [Bug]: DaemonProtocolError: terminal session attach is canceled on macOS (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16415 fix(daemon): keep attach guard behind client timeout | Han Community · CONTRIBUTOR | #16386 [Bug]: DaemonProtocolError: terminal session attach is canceled on macOS Fixes · OPEN | Standalone change | ## ELI5 The daemon used to cancel a terminal slightly before the app's own timeout handler ran. That ordering could expose an internal `Attach canceled` protocol error and leave the terminal pane on the wrong failure pat | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +74/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep authenticated hosts on partial auth failure1 PR · Standalone · Plugins#
Problem: keep authenticated hosts on partial auth failure.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13052 fix(gitlab): keep authenticated hosts on partial auth failure | David Anderson Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Parse `glab auth status` output even when `glab` exits nonzero because one configured host is unauthenticated. - Preserve and cache hosts successfully reported by the same command instead of falling back to | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +37/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep cold workspace search within frame budget1 PR · Standalone · Plugins#
Problem: keep cold workspace search within frame budget.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15170 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15683 perf(cmd-j): keep cold workspace search within frame budgetDraft | Jinwoo Hong Core team · MEMBER | #15170 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +1488/−189. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep currency dollars out of markdown math spans1 PR · Standalone · Plugins#
Problem: keep currency dollars out of markdown math spans.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13330 Title unavailable (Unclear, Unknown); #15100 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13551 fix(editor): keep currency dollars out of markdown math spans | Brennan Benson Core team · MEMBER | #13330 Title unavailable Unclear · Unknown #15100 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +123/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep currency dollars out of rich-editor math spans1 PR · Standalone · Plugins#
Problem: keep currency dollars out of rich-editor math spans.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15100 Rich editor (TipTap) swallows currency in prose — same class as #13330, on the default surface (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15677 fix(editor): keep currency dollars out of rich-editor math spans | Brennan Benson Core team · MEMBER | #15100 Rich editor (TipTap) swallows currency in prose — same class as #13330, on the default surface Fixes · CLOSED | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +119/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep current notification session2 PRs · Overlapping · Plugins#
Problem: keep current notification session.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16995 [Bug]: Mobile notification tap locks chat composer in the current worktree (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16997 fix(mobile): keep current notification session | Seung Ju Community · FIRST_TIME_CONTRIBUTOR | #16995 [Bug]: Mobile notification tap locks chat composer in the current worktree Fixes · OPEN | Cluster contribution | ## ELI5 Tapping a notification for the screen already open on Mobile no longer reloads that session and disables chat sending. ## What Changed - Treat an already-focused mobile session with the same `hostId` and `worktre | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +117/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17068 Fix same-target mobile notification navigation | Jinwoo Hong Core team · MEMBER | #16995 [Bug]: Mobile notification tap locks chat composer in the current worktree Fixes · OPEN | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +526/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep gh auth prompts from dying on OSC 11 replies1 PR · Standalone · Plugins#
Problem: keep gh auth prompts from dying on OSC 11 replies.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14020 [Bug]: could not prompt: unexpected escape sequence from terminal: ['\x1b' ']'] (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14170 fix(terminal): keep gh auth prompts from dying on OSC 11 replies | Brennan Benson Core team · MEMBER | #14020 [Bug]: could not prompt: unexpected escape sequence from terminal: ['\x1b' ']'] Fixes · CLOSED | Standalone change | ## Summary `gh auth login` on Linux writes an OSC 11 background-color query, then immediately starts a survey key reader. Orca answered that query from the renderer, so over SSH (and any path with a similar RTT) the `\x1 | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +675/−121. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep Hangul composition intact while a turn streams2 PRs · Overlapping · Plugins#
Problem: keep Hangul composition intact while a turn streams.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16911 [Bug]: Hangul/CJK composition is overwritten in the Native Chat composer while a turn streams (Fixes, OPEN); #12829 Title unavailable (Unclear, Unknown); #16260 Title unavailable (Unclear, Unknown); #16 Title unavailable (Unclear, Unknown); #17172 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16938 fix(native-chat): keep Hangul composition intact while a turn streams | klaatus Community · FIRST_TIME_CONTRIBUTOR | #16911 [Bug]: Hangul/CJK composition is overwritten in the Native Chat composer while a turn streams Fixes · OPEN #12829 Title unavailable Unclear · Unknown #16260 Title unavailable Unclear · Unknown #16 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When an agent is streaming a reply, typing Korean into the Native Chat box used to lose and mangle syllables: every incoming chunk re-rendered the box and overwrote the half-finished character before it could be | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +134/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17169 fix(native-chat): preserve IME composition during streaming | Neil Core team · MEMBER | #16911 [Bug]: Hangul/CJK composition is overwritten in the Native Chat composer while a turn streams Fixes · OPEN #17172 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Streaming responses can keep updating while someone types Hangul or CJK text. The composer now lets the browser finish the in-progress character before React synchronizes the draft. ## What Changed - Let the brow | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +323/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep keystroke echo responsive under dense-SGR output floods2 PRs · Overlapping · Automated release pipeline#
Problem: keep keystroke echo responsive under dense-SGR output floods.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #12523 [Bug]: Terminal input echo lags 1-3s while agent streams dense-SGR output (Fixes, OPEN); #12624 Title unavailable (Unclear, Unknown); #12525 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12525 fix(terminal): keep keystroke echo responsive under dense-SGR output floods | fsdwen Community · CONTRIBUTOR | #12523 [Bug]: Terminal input echo lags 1-3s while agent streams dense-SGR output Fixes · OPEN #12624 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary Fixes #12523: typing into a terminal while an agent streams dense-SGR output (per-character color styling — highlighted code, colored diff/log streams) made the keystroke echo appear 1-3 s late. Input was neve | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +1213/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #12624 fix(terminal): keep input responsive during dense SGR output | Neil Core team · MEMBER | #12523 [Bug]: Terminal input echo lags 1-3s while agent streams dense-SGR output Fixes · OPEN #12525 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary Fixes #12523. Dense per-character SGR output parses about 50× slower than plain text in xterm. That lets renderer, parser, and main-delivery FIFO backlogs place seconds of work ahead of the real shell echo for | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1402/−82. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep launched agent rows after conversation titles1 PR · Standalone · Plugins#
Problem: keep launched agent rows after conversation titles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15335 [Bug]: Launched Cursor agents vanish from the sidebar after they set a conversation title (Fixes, OPEN); #10258 Title unavailable (Unclear, Unknown); #15336 Title unavailable (Unclear, Unknown); #8258 Title unavailable (Unclear, Unknown); #14434 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15665 fix(sidebar): keep launched agent rows after conversation titles | Brennan Benson Core team · MEMBER | #15335 [Bug]: Launched Cursor agents vanish from the sidebar after they set a conversation title Fixes · OPEN #10258 Title unavailable Unclear · Unknown #15336 Title unavailable Unclear · Unknown #8258 Title unavailable Unclear · Unknown #14434 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +681/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep low-contrast themes legible in match-terminal sidebar and terminal ghost text1 PR · Standalone · Plugins#
Problem: keep low-contrast themes legible in match-terminal sidebar and terminal ghost text.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16999 [Bug]: Match-terminal sidebar text is nearly invisible on low-contrast themes (Solarized etc.) — fixed 62% muted mix (Fixes, OPEN); #737373 Title unavailable (Unclear, Unknown); #7934 Title unavailable (Unclear, Unknown); #10104 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17000 fix(appearance): keep low-contrast themes legible in match-terminal sidebar and terminal ghost text | seedotlee Community · FIRST_TIME_CONTRIBUTOR | #16999 [Bug]: Match-terminal sidebar text is nearly invisible on low-contrast themes (Solarized etc.) — fixed 62% muted mix Fixes · OPEN #737373 Title unavailable Unclear · Unknown #7934 Title unavailable Unclear · Unknown #10104 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On "soft" low-contrast terminal themes (Solarized, Everforest, Rosé Pine Dawn, Catppuccin Latte…) two things fade out: sidebar text in *Match terminal* mode, and shell autosuggestion "ghost text" in the terminal, | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +478/−76. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep named Codex App tasks and parent rollouts1 PR · Standalone · Plugins#
Problem: keep named Codex App tasks and parent rollouts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15061 [Bug]: Codex AI Vault drops user-named App tasks and parent rollouts that embed worker session_meta (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15062 fix(ai-vault): keep named Codex App tasks and parent rollouts | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #15061 [Bug]: Codex AI Vault drops user-named App tasks and parent rollouts that embed worker session_meta Fixes · OPEN | Standalone change | ## ELI5 Codex App task windows that you rename, and some parent chats that later copy a child `session_meta` into the same file, were scanned and then thrown away. This keeps unnamed internal workers hidden, but shows th | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +269/−60. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep OMP identity and forward ask/approval events1 PR · Standalone · Plugins#
Problem: keep OMP identity and forward ask/approval events.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15658 Title unavailable (Unclear, Unknown); #14279 Title unavailable (Unclear, Unknown); #14605 Title unavailable (Unclear, Unknown); #14278 Title unavailable (Unclear, Unknown); #14018 Title unavailable (Unclear, Unknown); #15711 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15713 fix(agents): keep OMP identity and forward ask/approval events | Brennan Benson Core team · MEMBER | #15658 Title unavailable Unclear · Unknown #14279 Title unavailable Unclear · Unknown #14605 Title unavailable Unclear · Unknown #14278 Title unavailable Unclear · Unknown #14018 Title unavailable Unclear · Unknown #15711 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +976/−559. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep OpenCode identity through Claude hooks1 PR · Standalone · Plugins#
Problem: keep OpenCode identity through Claude hooks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8940 Title unavailable (Unclear, Unknown); #12466 Title unavailable (Unclear, Unknown); #3990 Title unavailable (Unclear, Unknown); #9135 Title unavailable (Unclear, Unknown); #10066 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13385 fix(agents): keep OpenCode identity through Claude hooksDraft | Yunmin Cha Community · FIRST_TIME_CONTRIBUTOR | #8940 Title unavailable Unclear · Unknown #12466 Title unavailable Unclear · Unknown #3990 Title unavailable Unclear · Unknown #9135 Title unavailable Unclear · Unknown #10066 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Keep an OpenCode pane identified as OpenCode when its exact live local foreground process and explicit native `OC | ...` title agree, even if Claude-compatible tooling posts an inherited Claude hook for the | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +750/−58. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep parent session icon under nested Claude/Codex1 PR · Standalone · Plugins#
Problem: keep parent session icon under nested Claude/Codex.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13341 [Bug]: Nested Claude/Codex invocation changes the parent session icon (Fixes, OPEN); #13602 Title unavailable (Unclear, Unknown); #14937 Title unavailable (Unclear, Unknown); #14938 Title unavailable (Unclear, Unknown); #14634 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14012 fix(renderer): keep parent session icon under nested Claude/Codex | OrcaWin Unknown · COLLABORATOR | #13341 [Bug]: Nested Claude/Codex invocation changes the parent session icon Fixes · OPEN #13602 Title unavailable Unclear · Unknown #14937 Title unavailable Unclear · Unknown #14938 Title unavailable Unclear · Unknown #14634 Title unavailable Unclear · Unknown | Standalone change | ## Summary - **Bug:** Nested Claude↔Codex (and other cross-group) invocations became the foreground process / OSC title and rebranded the parent tab icon while the parent session still owned the pane. - **Fix:** While la | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +475/−210. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep pasted issue images off Windows gh argv (#15832)1 PR · Standalone · Plugins#
Problem: keep pasted issue images off Windows gh argv (#15832).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15832 [Bug]: Windows — creating a GitHub issue with a pasted image fails with "spawn ENAMETOOLONG"; the #7704 oversized-body fallback never engages (Fixes, OPEN); #7704 Title unavailable (Unclear, Unknown); #8217 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15877 fix(github): keep pasted issue images off Windows gh argv (#15832) | BingZ Community · CONTRIBUTOR | #15832 [Bug]: Windows — creating a GitHub issue with a pasted image fails with "spawn ENAMETOOLONG"; the #7704 oversized-body fallback never engages Fixes · OPEN #7704 Title unavailable Unclear · Unknown #8217 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Windows refuses to start a program if its command line is too long. Pasting a screenshot into a new GitHub issue turned the image into a huge data-URI and Orca stuffed that whole string onto the `gh` command line | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +445/−171. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep project header labels from switching to the repo name1 PR · Standalone · Plugins#
Problem: keep project header labels from switching to the repo name.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16127 [Bug]: Cross-host project header renames itself depending on which workspaces are visible (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16877 fix(sidebar): keep project header labels from switching to the repo name | Neil Core team · MEMBER | #16127 [Bug]: Cross-host project header renames itself depending on which workspaces are visible Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +158/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Keep project ring positions stable across Agent Map repacks1 PR · Standalone · Plugins#
Problem: Keep project ring positions stable across Agent Map repacks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17018 Keep project ring positions stable across Agent Map repacks | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Project rings on the Agent Dashboard's map view were fully repacked left-to-right from x=0 on every topology change anywhere on the board, so one project growing/shrinking or a new project appearing shifted | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +171/−83. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep recoverable connect failures revivable1 PR · Standalone · Plugins#
Problem: keep recoverable connect failures revivable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12684 remote-runtime: recoverable connect() failures can latch disconnected without a working auto-retry (Fixes, OPEN); #12650 Title unavailable (Unclear, Unknown); #12574 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13150 fix(remote-runtime): keep recoverable connect failures revivable | BingZ Community · CONTRIBUTOR | #12684 remote-runtime: recoverable connect() failures can latch disconnected without a working auto-retry Fixes · OPEN #12650 Title unavailable Unclear · Unknown #12574 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A temporary SSH/runtime outage could leave a terminal showing Reconnect even though neither automatic nor manual recovery could actually restart the connection. This change keeps that recovery path alive without | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +258/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep remote browsers usable across mixed versions1 PR · Standalone · Plugins#
Problem: keep remote browsers usable across mixed versions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14883 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14987 fix(browser): keep remote browsers usable across mixed versions | Jinwoo Hong Core team · MEMBER | #14883 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 31 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk76 files, +5269/−576. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep remote-runtime agent sessions visible while parked1 PR · Standalone · Plugins#
Problem: keep remote-runtime agent sessions visible while parked.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15442 Remote workspace agent session disappears from sidebar when unfocused (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15443 fix(sidebar): keep remote-runtime agent sessions visible while parked | Yunqian Fan Community · CONTRIBUTOR | #15442 Remote workspace agent session disappears from sidebar when unfocused Fixes · OPEN | Standalone change | ## ELI5 When you park a workspace that runs an agent on a remote machine, Orca used to lose track of whether that agent was still working, so the session disappeared from the sidebar until you clicked back into it. This | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +261/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep same-host same-remote clones as separate projects1 PR · Standalone · Plugins#
Problem: keep same-host same-remote clones as separate projects.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16387 [Bug]: Independent same-remote clones collapse into one project on the same host (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16388 fix: keep same-host same-remote clones as separate projects | Hinen Community · FIRST_TIME_CONTRIBUTOR | #16387 [Bug]: Independent same-remote clones collapse into one project on the same host Fixes · OPEN | Standalone change | ## ELI5 When the same Git repository is cloned into two different folders on one machine, Orca now keeps those explicit imports as two projects instead of merging them because their GitHub address matches. The same repos | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +94/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep spaced batch launcher paths intact when spawning1 PR · Standalone · Plugins#
Problem: keep spaced batch launcher paths intact when spawning.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #5983 Title unavailable (Unclear, Unknown); #11384 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13501 fix(windows): keep spaced batch launcher paths intact when spawning | Tae Hyeong, Son Community · FIRST_TIME_CONTRIBUTOR | #5983 Title unavailable Unclear · Unknown #11384 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 To run a `.cmd` launcher, Orca hands a command line to `cmd.exe`, which re-reads it. `cmd.exe` has an old rule: unless a narrow set of conditions all hold, it throws away the first and last quote on the line. Nod | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +155/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the changed-code quality gate runnable on huge changed sets1 PR · Standalone · Plugins#
Problem: keep the changed-code quality gate runnable on huge changed sets.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17201 fix(ci): keep the changed-code quality gate runnable on huge changed sets | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +349/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the first font-family when importing config1 PR · Standalone · Plugins#
Problem: keep the first font-family when importing config.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15985 [Bug]: Ghostty import keeps the last font-family instead of the first (Fixes, OPEN); #8428 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16090 fix(ghostty): keep the first font-family when importing config | Max Hsu Community · FIRST_TIME_CONTRIBUTOR | #15985 [Bug]: Ghostty import keeps the last font-family instead of the first Fixes · OPEN #8428 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Ghostty lets you list `font-family` more than once — the first one is the font you want, the rest are backups for characters the first one doesn't have. When importing that config, Orca kept the **last** one inst | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +25/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the host pill legible on the selected workspace card1 PR · Standalone · Plugins#
Problem: keep the host pill legible on the selected workspace card.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15971 [Bug]: Sidebar host pill loses nearly all contrast on the selected workspace card (worst with Match terminal / Tinted sidebar) (Fixes, OPEN); #171717 Title unavailable (Unclear, Unknown); #444444 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15975 fix(sidebar): keep the host pill legible on the selected workspace card | gatsby74 Community · CONTRIBUTOR | #15971 [Bug]: Sidebar host pill loses nearly all contrast on the selected workspace card (worst with Match terminal / Tinted sidebar) Fixes · OPEN #171717 Title unavailable Unclear · Unknown #444444 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The little `Local Mac` / `Hetzner VPS` pill in the sidebar was painted a fixed shade of grey chosen to look right against the sidebar's background. But when you select a workspace, that card gets its own slightly | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +95/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the launch ack from re-pinging quoted mentions1 PR · Standalone · Plugins#
Problem: keep the launch ack from re-pinging quoted mentions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16246 [Feature]: Option to skip the post-launch PR comment acknowledgement (Fixes, OPEN); #123 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16273 fix(pr-comments): keep the launch ack from re-pinging quoted mentionsDraft | Max Hsu Community · FIRST_TIME_CONTRIBUTOR | #16246 [Feature]: Option to skip the post-launch PR comment acknowledgement Fixes · OPEN #123 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Orca posts its "I've launched an agent on these comments" acknowledgement, it quotes the first line of each comment it is acking. If that line happens to contain `@somebody` or `#123`, GitHub renders it as a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +26/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the PR branch name when the push target is unresolved1 PR · Standalone · Plugins#
Problem: keep the PR branch name when the push target is unresolved.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #536 Title unavailable (Unclear, Unknown); #16646 Title unavailable (Unclear, Unknown); #16699 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17021 fix(worktree): keep the PR branch name when the push target is unresolved | JahyunBaek Community · CONTRIBUTOR | #536 Title unavailable Unclear · Unknown #16646 Title unavailable Unclear · Unknown #16699 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Open a worktree for someone's pull request and Orca sometimes names the branch `their-branch-2` instead of `their-branch`. This makes it use the real name. ## What Changed `isAllowedPushTargetRemoteConflict` requ | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +206/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Keep the preview open when it sends you to the worktree1 PR · Standalone · Plugins#
Problem: Keep the preview open when it sends you to the worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16866 Keep the preview open when it sends you to the worktree | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | "Open worktree" dismissed the preview it was launched from. From the pop-out that is backwards. Revealing focuses the pane in the **main** window — so the pop-out was throwing away the view the user was watching in order | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +16/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep transcript selections alive through pane pointerdown1 PR · Standalone · Plugins#
Problem: keep transcript selections alive through pane pointerdown.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16467 Native Chat: shift-click cannot extend a transcript text selection (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16468 fix(chat): keep transcript selections alive through pane pointerdown | 전창하 Community · FIRST_TIME_CONTRIBUTOR | #16467 Native Chat: shift-click cannot extend a transcript text selection Fixes · OPEN | Standalone change | ## ELI5 When you select text in the chat and then Shift+click to grab more of it, the selection vanished instead of growing. That is because the chat panel lives inside a terminal pane, and clicking anywhere in the pane | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +210/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep WSL API-key runtime auth from being restored as ChatGPT1 PR · Standalone · Plugins#
Problem: keep WSL API-key runtime auth from being restored as ChatGPT.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15819 fix(codex): keep WSL API-key runtime auth from being restored as ChatGPT | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +860/−43. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Keep your WSL Claude profile when switching accounts1 PR · Standalone · Plugins#
Problem: Keep your WSL Claude profile when switching accounts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11824 Title unavailable (Unclear, Unknown); #8795 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12226 Keep your WSL Claude profile when switching accountsDraft | Neil Core team · MEMBER | #11824 Title unavailable Unclear · Unknown #8795 Title unavailable Unclear · Unknown | Standalone change | > **Draft — not ready to merge.** Three adversarial review rounds left four outstanding findings (two of them blockers), and every WSL behaviour below is verified only on macOS with `process.platform` faked and `../wsl` | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1970/−310. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2key task presets on statusCategory instead of resolution1 PR · Standalone · Plugins#
Problem: key task presets on statusCategory instead of resolution.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16808 [Bug]: Jira preset filters key on resolution, so they show the wrong issues in projects without a resolution post-function (Fixes, OPEN); #16398 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16809 fix(jira): key task presets on statusCategory instead of resolution | Daeyoung Jeong Community · FIRST_TIME_CONTRIBUTOR | #16808 [Bug]: Jira preset filters key on resolution, so they show the wrong issues in projects without a resolution post-function Fixes · OPEN #16398 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca's Jira tab has four preset filters (Assigned, Reported, Done, All Open). They decide whether an issue is finished by looking at Jira's `resolution` field. That field is not filled in automatically - a Jira a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +46/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2land on the previously active tab when the last tab of a kind closes1 PR · Standalone · Plugins#
Problem: land on the previously active tab when the last tab of a kind closes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15113 [Feature]: Return to the previously active tab when the last tab of a kind closes (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15114 fix(tabs): land on the previously active tab when the last tab of a kind closes | Taras Kornichuk Community · CONTRIBUTOR | #15113 [Feature]: Return to the previously active tab when the last tab of a kind closes Fixes · OPEN | Standalone change | ## ELI5 Close a tab and you go back to the tab you were on before, not to the first tab in the row. ## What Changed Two tab-close paths chose the landing tab by position instead of by history: - `Terminal.tsx` `handleClo | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +532/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2land the lazy-chunk recovery reload instead of letting the navigation guard veto it1 PR · Standalone · Plugins#
Problem: land the lazy-chunk recovery reload instead of letting the navigation guard veto it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #5787 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12489 fix(renderer): land the lazy-chunk recovery reload instead of letting the navigation guard veto it | Neil Core team · MEMBER | #5787 Title unavailable Unclear · Unknown | Standalone change | ## What this fixes **Signature:** a lazy chunk `import()` rejects (`TypeError: Failed to fetch dynamically imported module: file://…`, or a native `SyntaxError` from corrupt bytes), the built-in recovery reload is reques | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +335/−67. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Lead the dashboard card with its review, its CI, and its ticket1 PR · Standalone · Plugins#
Problem: Lead the dashboard card with its review, its CI, and its ticket.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16856 Lead the dashboard card with its review, its CI, and its ticket | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | The Agent Dashboard's job is to answer *what needs me* at a glance. The two answers that travel with a workspace — is the review green, and which ticket is this — were the least visible things on the card: a 10px pill bu | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +449/−132. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2lengthen background no-PR refresh interval1 PR · Standalone · Plugins#
Problem: lengthen background no-PR refresh interval.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11532 [Bug]: Background PR polling can exhaust the GitHub REST rate limit (5,000/hr) — cached "no PR" branches are re-queried every 60s (Fixes, CLOSED); #11569 Title unavailable (Unclear, Unknown); #12013 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12162 perf(github): lengthen background no-PR refresh interval | Wooseong Kim Community · CONTRIBUTOR | #11532 [Bug]: Background PR polling can exhaust the GitHub REST rate limit (5,000/hr) — cached "no PR" branches are re-queried every 60s Fixes · CLOSED #11569 Title unavailable Unclear · Unknown #12013 Title unavailable Unclear · Unknown | Standalone change | ## Summary Lengthen the GitHub PR refresh coordinator's background no-PR interval from 15 to 60 minutes, reducing repeated O(N) card-list lookups without slowing the selected-worktree path. ## Prior review context PR #11 | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +56/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let a live renderer heal an unavailable graph1 PR · Standalone · Plugins#
Problem: let a live renderer heal an unavailable graph.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16521 [Bug]: macOS desktop v1.4.188 starts with graph unavailable; Orca Mobile shows 0 tabs for every workspace (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16708 fix(runtime): let a live renderer heal an unavailable graph | Brennan Benson Core team · MEMBER | #16521 [Bug]: macOS desktop v1.4.188 starts with graph unavailable; Orca Mobile shows 0 tabs for every workspace Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +389/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let a live text selection keep Cmd+C1 PR · Standalone · Plugins#
Problem: let a live text selection keep Cmd+C.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12323 [Bug]: Cmd+C in the native chat transcript arms browser element-grab instead of copying (Fixes, OPEN); #2195 Title unavailable (Unclear, Unknown); #11348 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16744 fix(browser): let a live text selection keep Cmd+C | Gideon Community · CONTRIBUTOR | #12323 [Bug]: Cmd+C in the native chat transcript arms browser element-grab instead of copying Fixes · OPEN #2195 Title unavailable Unclear · Unknown #11348 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The browser pane borrows ⌘C for "grab a page element". It kept borrowing it even while you were selecting text in a chat transcript, so copying from chat silently did nothing. Now a live text selection wins ⌘C, a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +279/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Let an idle Agent Dashboard card remove its worktree1 PR · Standalone · Plugins#
Problem: Let an idle Agent Dashboard card remove its worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16858 Let an idle Agent Dashboard card remove its worktree | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | An agent that has finished leaves its worktree behind, and clearing it meant leaving the board, finding the row in the sidebar, and deleting it there. The board already knows which workspaces are done — the Idle column * | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +212/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let language packs translate the install form and log controls1 PR · Standalone · Plugins#
Problem: let language packs translate the install form and log controls.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12514 Title unavailable (Unclear, Unknown); #12455 Title unavailable (Unclear, Unknown); #14127 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14121 feat(plugins): let language packs translate the install form and log controls | Evgenii Community · CONTRIBUTOR | #12514 Title unavailable Unclear · Unknown #12455 Title unavailable Unclear · Unknown #14127 Title unavailable Unclear · Unknown | Standalone change | ## Summary Second narrow widening of the plugin-chrome exemption landed in #12514, following the same rule as the first: **a path belongs here only if rewriting it cannot mislead the person deciding whether to trust a pl | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +69/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Let macOS actually ask for notification permission instead of silently claiming it was grant1 PR · Standalone · Plugins#
Problem: Let macOS actually ask for notification permission instead of silently claiming it was grant.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11675 [Bug]: macOS notification permission is never actually requested — notificationPermissionRequested flag is set without the OS prompt appearing (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12210 Let macOS actually ask for notification permission instead of silently claiming it was granted | Neil Core team · MEMBER | #11675 [Bug]: macOS notification permission is never actually requested — notificationPermissionRequested flag is set without the OS prompt appearing Fixes · OPEN | Standalone change | ## Summary On macOS, Orca could report that notifications were enabled while `com.stablyai.orca` had never been registered with Notification Center, and there was no way to recover. Three defects, all in `src/main/ipc/no | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +373/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let Pi use its configured default model1 PR · Standalone · Plugins#
Problem: let Pi use its configured default model.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14407 [Bug]: Pi branch auto-rename hardcodes GitHub Copilot model instead of using Pi's configured provider (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15649 fix(source-control): let Pi use its configured default model | Brennan Benson Core team · MEMBER | #14407 [Bug]: Pi branch auto-rename hardcodes GitHub Copilot model instead of using Pi's configured provider Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +618/−62. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let sandboxed panels call storage.get, so a panel can render live state1 PR · Standalone · Plugins#
Problem: let sandboxed panels call storage.get, so a panel can render live state.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15638 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15643 feat(plugins): let sandboxed panels call storage.get, so a panel can render live state | Yorai Levi Community · FIRST_TIME_CONTRIBUTOR | #15638 Title unavailable Unclear · Unknown | Standalone change | Follows #15638. That issue asked for a host→panel message channel; this is a much smaller change that solves most of the same problem, so I built it instead. ## Problem A plugin panel cannot read **any** state its own wo | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +54/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let the agent drawer yield to the page the user just opened1 PR · Standalone · Plugins#
Problem: let the agent drawer yield to the page the user just opened.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16092 [Bug]: UI elements are overlapping each other. (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16599 fix(dashboard): let the agent drawer yield to the page the user just opened | JahyunBaek Community · CONTRIBUTOR | #16092 [Bug]: UI elements are overlapping each other. Fixes · OPEN | Standalone change | ## ELI5 The agent dashboard slides out next to the sidebar, and the sidebar stays clickable while it is open. So you can click Automations with the dashboard still up — but nothing closed the dashboard, so it stayed on t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +52/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2link worker-created sub-Runs1 PR · Standalone · Plugins#
Problem: link worker-created sub-Runs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16784 fix(orchestration): link worker-created sub-Runs | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +412/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2load the next page of commits on scroll1 PR · Standalone · Plugins#
Problem: load the next page of commits on scroll.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14405 Title unavailable (Unclear, Unknown); #14224 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14472 feat(source-control): load the next page of commits on scroll | JahyunBaek Community · FIRST_TIME_CONTRIBUTOR | #14405 Title unavailable Unclear · Unknown #14224 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The Commits list can now reach old commits, but only one button press at a time — fifty rows per click. Scrolling to the bottom now just keeps going: the next page starts loading before you get there, so the list | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +390/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Local PTY inspection: degraded reads become unverifiable evidence, not agent exits1 PR · Standalone · Plugins#
Problem: Local PTY inspection: degraded reads become unverifiable evidence, not agent exits.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16900 Title unavailable (Unclear, Unknown); #16908 Title unavailable (Unclear, Unknown); #16926 Title unavailable (Unclear, Unknown); #16932 Title unavailable (Unclear, Unknown); #17003 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16955 Local PTY inspection: degraded reads become unverifiable evidence, not agent exits | Brennan Benson Core team · MEMBER | #16900 Title unavailable Unclear · Unknown #16908 Title unavailable Unclear · Unknown #16926 Title unavailable Unclear · Unknown #16932 Title unavailable Unclear · Unknown #17003 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +1267/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2localize Orca Account settings and navigation to Korean1 PR · Standalone · Plugins#
Problem: localize Orca Account settings and navigation to Korean.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15846 [Bug]: (i18n)Missing Korean translation for Orca Account settings navigation and pane (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15849 feat(i18n): localize Orca Account settings and navigation to Korean | hwantage Community · CONTRIBUTOR | #15846 [Bug]: (i18n)Missing Korean translation for Orca Account settings navigation and pane Fixes · OPEN | Standalone change | ## ELI5 The Orca Account menu item and its settings page were displaying in English even when the app language was set to Korean. This PR adds the missing Korean translations so everything in Settings → Orca Account appe | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +22/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2localize the remaining contextual tour steps1 PR · Standalone · Plugins#
Problem: localize the remaining contextual tour steps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12270 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12713 fix(i18n): localize the remaining contextual tour steps | Hansss Community · CONTRIBUTOR | #12270 Title unavailable Unclear · Unknown | Standalone change | ## Summary Every contextual tour except Automations rendered its title and body in English even when the UI language was Korean, next to already-localized Next / Back / Done controls and progress label. Root cause: #1227 | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +810/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2lock in upstream->origin API repository fallback (#16474)1 PR · Standalone · Plugins#
Problem: lock in upstream->origin API repository fallback (#16474).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16474 Title unavailable (Unclear, Unknown); #1317 Title unavailable (Unclear, Unknown); #164 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16483 test(github): lock in upstream->origin API repository fallback (#16474) | Borja Community · CONTRIBUTOR | #16474 Title unavailable Unclear · Unknown #1317 Title unavailable Unclear · Unknown #164 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Adds a regression test that pins Orca's "use the `upstream` remote, else fall back to `origin`" behavior when resolving a repo's GitHub API source. No product code changes. ## What Changed New `src/main/github/gi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +97/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make agent markdown text selectable1 PR · Standalone · Plugins#
Problem: make agent markdown text selectable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16492 [Bug]: iOS app — agent chat text is not selectable (MobileMarkdown Text nodes missing `selectable`) (Fixes, OPEN); #15652 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16534 fix(mobile): make agent markdown text selectable | Seongho.Bak Community · CONTRIBUTOR | #16492 [Bug]: iOS app — agent chat text is not selectable (MobileMarkdown Text nodes missing `selectable`) Fixes · OPEN #15652 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Agent Markdown messages now opt into the native text-selection behavior that React Native leaves disabled by default. Long-press selection can therefore operate on individual prose, code, table, list, and image-l | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +164/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make chunk-load recovery real — epoch-gated retry and a main-process Restart action1 PR · Standalone · Plugins#
Problem: make chunk-load recovery real — epoch-gated retry and a main-process Restart action.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12950 Title unavailable (Unclear, Unknown); #171717 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14661 fix(renderer): make chunk-load recovery real — epoch-gated retry and a main-process Restart action | Brennan Benson Core team · MEMBER | #12950 Title unavailable Unclear · Unknown #171717 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +1716/−71. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make Claude /resume reachable from Orca Mobile (STA-4617)1 PR · Standalone · Plugins#
Problem: make Claude /resume reachable from Orca Mobile (STA-4617).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15067 Title unavailable (Unclear, Unknown); #15672 Title unavailable (Unclear, Unknown); #16682 Title unavailable (Unclear, Unknown); #16773 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16684 fix(native-chat): make Claude /resume reachable from Orca Mobile (STA-4617) | Brennan Benson Core team · MEMBER | #15067 Title unavailable Unclear · Unknown #15672 Title unavailable Unclear · Unknown #16682 Title unavailable Unclear · Unknown #16773 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +959/−80. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Make local Git metadata observation event-driven1 PR · Standalone · Plugins#
Problem: Make local Git metadata observation event-driven.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16352 Make local Git metadata observation event-driven | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +2034/−810. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make new-project dialog popovers scrollable1 PR · Standalone · Plugins#
Problem: make new-project dialog popovers scrollable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16412 [Bug]: Linear new-project dialog popovers do not respond to the wheel (same defect as #16378) (Fixes, OPEN); #16382 Title unavailable (Unclear, Unknown); #15163 Title unavailable (Unclear, Unknown); #16378 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16413 fix(linear): make new-project dialog popovers scrollable | hjkwon Community · CONTRIBUTOR | #16412 [Bug]: Linear new-project dialog popovers do not respond to the wheel (same defect as #16378) Fixes · OPEN #16382 Title unavailable Unclear · Unknown #15163 Title unavailable Unclear · Unknown #16378 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The Linear **new project** dialog has the same broken dropdowns that #16382 just fixed in the **new issue** dialog next door. These ones are sneakier: a scrollbar actually shows up, so they look fine — but the mo | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +149/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make pid-record publish atomic via claim-then-link1 PR · Standalone · Plugins#
Problem: make pid-record publish atomic via claim-then-link.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16908 Title unavailable (Unclear, Unknown); #16979 Title unavailable (Unclear, Unknown); #16900 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16924 fix(daemon): make pid-record publish atomic via claim-then-link | Brennan Benson Core team · MEMBER | #16908 Title unavailable Unclear · Unknown #16979 Title unavailable Unclear · Unknown #16900 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +645/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Make post-paste submit delay per-agent, bump codex to 300ms1 PR · Standalone · Plugins#
Problem: Make post-paste submit delay per-agent, bump codex to 300ms.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16716 Make post-paste submit delay per-agent, bump codex to 300ms | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +176/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make Settings skill install unattended2 PRs · Overlapping · Plugins#
Problem: make Settings skill install unattended.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #13542 CLI skill install hangs forever in inline terminal (skills add blocks on interactive prompt, no timeout) (Fixes, OPEN); #13948 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13948 fix(skills): make Settings skill install unattended | BingZ Community · CONTRIBUTOR | #13542 CLI skill install hangs forever in inline terminal (skills add blocks on interactive prompt, no timeout) Fixes · OPEN | Cluster contribution | ## ELI5 Orca's inline setup terminal cannot answer the Skills CLI agent picker, so the command could wait forever. The terminal-only path now supplies explicit agent targets and `-y`, while commands shown or copied for h | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +180/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15669 fix(skills): surface stdin stall on inline skill install | Brennan Benson Core team · MEMBER | #13542 CLI skill install hangs forever in inline terminal (skills add blocks on interactive prompt, no timeout) Fixes · OPEN #13948 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +393/−73. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make shard 15 failures deterministic1 PR · Standalone · Plugins#
Problem: make shard 15 failures deterministic.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16871 test: make shard 15 failures deterministic | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +59/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the cold-hydration spec check its own captured snapshot1 PR · Standalone · Plugins#
Problem: make the cold-hydration spec check its own captured snapshot.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17017 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17031 test(e2e): make the cold-hydration spec check its own captured snapshot | Brennan Benson Core team · MEMBER | #17017 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +34/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the Copy context selection hint clickable1 PR · Standalone · Plugins#
Problem: make the Copy context selection hint clickable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16204 feat(editor): make the Copy context selection hint clickable | LiuSir Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Selecting code in the editor already showed a "Copy context" shortcut chip. That chip is now a button: click it and it copies the same file/line payload as the keyboard shortcut. ## What Changed - The selection h | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +188/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the macOS click fence diagnosable and settle its pre-press probe1 PR · Standalone · Plugins#
Problem: make the macOS click fence diagnosable and settle its pre-press probe.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15073 [Bug]: macOS coordinate click reports window_not_focused after the final press (Fixes, CLOSED); #15074 computer: pre-press macOS click fence probe is single-shot and non-diagnosable — transient nil focus observations red the scheduled mac e2e lane (Fixes, OPEN); #15169 Title unavailable (Unclear, Unknown); #14894 Title unavailable (Unclear, Unknown); #13048 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15102 fix(computer): make the macOS click fence diagnosable and settle its pre-press probe | Zuz666 Community · CONTRIBUTOR | #15073 [Bug]: macOS coordinate click reports window_not_focused after the final press Fixes · CLOSED #15074 computer: pre-press macOS click fence probe is single-shot and non-diagnosable — transient nil focus observations red the scheduled mac e2e lane Fixes · OPEN #15169 Title unavailable Unclear · Unknown #14894 Title unavailable Unclear · Unknown #13048 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The macOS computer-use clicker checks that every synthetic press still targets the intended window. On CI, Accessibility can briefly report no focused window even when the target is correct. This PR waits through | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +724/−127. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the max-lines ratchet and perf benches actually gate, and give PTY state an owner1 PR · Standalone · Plugins#
Problem: make the max-lines ratchet and perf benches actually gate, and give PTY state an owner.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15727 fix(ci): make the max-lines ratchet and perf benches actually gate, and give PTY state an owner | ojones1965 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Two CI gates were reporting green while the thing they were supposed to guard got worse, and a third gate was never plugged in at all. This fixes both, then takes the first step toward breaking up the 41k-line ru | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +1253/−310. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the POSIX hook command spawnable as argv[0]1 PR · Standalone · Plugins#
Problem: make the POSIX hook command spawnable as argv[0].
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16087 [Bug]: POSIX orca-status PreToolUse hook is not argv[0]-spawnable; Zed Antigravity ACP denies all tools (Fixes, OPEN); #8430 Title unavailable (Unclear, Unknown); #2426 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16222 fix(antigravity): make the POSIX hook command spawnable as argv[0] | Max Hsu Community · FIRST_TIME_CONTRIBUTOR | #16087 [Bug]: POSIX orca-status PreToolUse hook is not argv[0]-spawnable; Zed Antigravity ACP denies all tools Fixes · OPEN #8430 Title unavailable Unclear · Unknown #2426 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca writes its Antigravity status hook into `~/.gemini/config/hooks.json` as a little shell snippet that starts with `if`. Zed's Antigravity ACP host doesn't run hooks through a shell — it splits the string and | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +170/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the Reporter field a real user picker so issues can be created1 PR · Standalone · Plugins#
Problem: make the Reporter field a real user picker so issues can be created.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #4643 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17090 fix(jira): make the Reporter field a real user picker so issues can be created | Brennan Benson Core team · MEMBER | #4643 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +1784/−105. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make viewport presets scrollable when larger than the pane1 PR · Standalone · Plugins#
Problem: make viewport presets scrollable when larger than the pane.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13293 [Bug]: Viewport Size presets clip the page with no way to scroll when larger than the pane (Fixes, OPEN); #1369 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13294 fix(browser): make viewport presets scrollable when larger than the pane | 성지훈 Community · FIRST_TIME_CONTRIBUTOR | #13293 [Bug]: Viewport Size presets clip the page with no way to scroll when larger than the pane Fixes · OPEN #1369 Title unavailable Unclear · Unknown | Standalone change | ## Summary When a Viewport Size preset (e.g. Laptop L — 1440 × 900) is larger than the browser pane, the page is clipped at the pane edge with no way to scroll to the hidden part: - The preset is applied purely via CDP ` | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +171/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2mark sidebar done on idle_prompt and StopCancelled1 PR · Standalone · Plugins#
Problem: mark sidebar done on idle_prompt and StopCancelled.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15225 [Bug]: Grok sidebar stays working after the TUI Stop hook already ran (Fixes, OPEN); #14828 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15230 fix(grok): mark sidebar done on idle_prompt and StopCancelled | JX Community · FIRST_TIME_CONTRIBUTOR | #15225 [Bug]: Grok sidebar stays working after the TUI Stop hook already ran Fixes · OPEN #14828 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Grok already finished and printed `stop`, but Orca kept the yellow working dot because it did not treat Grok''s current idle/cancel hook events as done, and a large Stop post could time out silently. ## What Chan | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +427/−55. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2match mirrored targets to runtime terminals1 PR · Standalone · Plugins#
Problem: match mirrored targets to runtime terminals.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16225 [Bug]: Paired-runtime Markdown review notes fail because mirrored tab IDs are not normalized (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16231 fix(notes): match mirrored targets to runtime terminals | Fartown Community · FIRST_TIME_CONTRIBUTOR | #16225 [Bug]: Paired-runtime Markdown review notes fail because mirrored tab IDs are not normalized Fixes · OPEN | Standalone change | ## ELI5 In a paired Orca session, the renderer gives a mirrored terminal tab a local `web-terminal-*` ID, while the runtime still lists that same terminal by its raw host ID. Review-note sending compared those two spelli | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +10/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2match permission title keywords on word boundaries1 PR · Standalone · Plugins#
Problem: match permission title keywords on word boundaries.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15728 [Bug]: a cwd path segment can make an agent read as "waiting for permission" (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15729 fix: match permission title keywords on word boundaries | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15728 [Bug]: a cwd path segment can make an agent read as "waiting for permission" Fixes · OPEN | Standalone change | ## ELI5 If your project folder is called `permissions`, your agent showed up as "waiting for permission" the whole time it was working. Nothing in the pane was asking for anything — the word just happened to be in the pa | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +49/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2match WSL /mnt/c sessions to Windows workspaces (STA-4973)1 PR · Standalone · Plugins#
Problem: match WSL /mnt/c sessions to Windows workspaces (STA-4973).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15650 fix(ai-vault): match WSL /mnt/c sessions to Windows workspaces (STA-4973) | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +899/−127. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2move the Google cookie clear into Settings, behind a confirmation1 PR · Standalone · Plugins#
Problem: move the Google cookie clear into Settings, behind a confirmation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14683 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14686 fix(browser): move the Google cookie clear into Settings, behind a confirmation | Brennan Benson Core team · MEMBER | #14683 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 13 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +1563/−69. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Name the command each agent is running, on its card1 PR · Standalone · Plugins#
Problem: Name the command each agent is running, on its card.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16860 Name the command each agent is running, on its card | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | The board could tell you an agent was *working* but not what it was working on — and the last message goes stale the moment a turn starts, which is exactly when you want to look. > **Rewritten.** The first version of thi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +70/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2name the id-kind mismatch when --ack is given a message id1 PR · Standalone · Plugins#
Problem: name the id-kind mismatch when --ack is given a message id.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15697 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15743 fix: name the id-kind mismatch when --ack is given a message id | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15697 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 `orchestration check --ack` wants the id of the *batch*, but the only id you can see while reading your messages is each message's own id. Pass that one and the error says it "does not belong to this Run" — so yo | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +27/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2narrow status observer updates1 PR · Standalone · Plugins#
Problem: narrow status observer updates.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17155 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17249 perf(automations): narrow status observer updates | Neil Core team · MEMBER | #17155 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +164/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2never publish a usage reply Orca could not read as a successful reading1 PR · Standalone · Plugins#
Problem: never publish a usage reply Orca could not read as a successful reading.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17167 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17193 fix(rate-limits): never publish a usage reply Orca could not read as a successful reading | Brennan Benson Core team · MEMBER | #17167 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +995/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Never read an unanswerable hasPty probe as proven PTY absence1 PR · Standalone · Plugins#
Problem: Never read an unanswerable hasPty probe as proven PTY absence.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16900 Title unavailable (Unclear, Unknown); #16953 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16932 Never read an unanswerable hasPty probe as proven PTY absence | Brennan Benson Core team · MEMBER | #16900 Title unavailable Unclear · Unknown #16953 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +317/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2notify only after turn finalization1 PR · Standalone · Plugins#
Problem: notify only after turn finalization.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10046 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12837 fix(hermes): notify only after turn finalizationDraft | GoodFarming Community · FIRST_TIME_CONTRIBUTOR | #10046 Title unavailable Unclear · Unknown | Standalone change | ## Summary - keep Hermes `working` through `post_llm_call` - use `on_session_end` as the completed-turn boundary - ignore session start, reset, and finalize events as task-status transitions - retain the final assistant | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · S Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +36/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2notify the renderer when the active account changes outside it1 PR · Standalone · Plugins#
Problem: notify the renderer when the active account changes outside it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17261 [Bug]: Claude account switched from mobile takes effect, but the desktop keeps showing and attributing usage to the old account (Fixes, OPEN); #16466 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17265 fix(accounts): notify the renderer when the active account changes outside it | Tauri-EPO Community · CONTRIBUTOR | #17261 [Bug]: Claude account switched from mobile takes effect, but the desktop keeps showing and attributing usage to the old account Fixes · OPEN #16466 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If you switch your Claude account from your phone, the desktop app keeps showing the old account as active — and paints the incoming usage numbers under the old account's name — even though the new account is rea | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +17/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2omit SYSTEMROOT from POSIX Claude-compat hook commands1 PR · Standalone · Plugins#
Problem: omit SYSTEMROOT from POSIX Claude-compat hook commands.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17202 [Bug]: Grok still skips Claude-compat managed hooks on macOS because the installed command mentions SYSTEMROOT (Fixes, OPEN); #14794 Title unavailable (Unclear, Unknown); #14994 Title unavailable (Unclear, Unknown); #14793 Title unavailable (Unclear, Unknown); #15558 Title unavailable (Unclear, Unknown); #15591 Title unavailable (Unclear, Unknown); #15831 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17203 fix(agent-hooks): omit SYSTEMROOT from POSIX Claude-compat hook commands | BingZ Community · CONTRIBUTOR | #17202 [Bug]: Grok still skips Claude-compat managed hooks on macOS because the installed command mentions SYSTEMROOT Fixes · OPEN #14794 Title unavailable Unclear · Unknown #14994 Title unavailable Unclear · Unknown #14793 Title unavailable Unclear · Unknown #15558 Title unavailable Unclear · Unknown #15591 Title unavailable Unclear · Unknown #15831 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Grok reads Orca's Claude hook command from `~/.claude/settings.json` and, before running it, checks every `$VAR` in the string. On macOS that string still contained a Windows-only `SYSTEMROOT` token, so Grok skip | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +119/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2one oversized-file limit and a recoverable Open Anyway path1 PR · Standalone · Plugins#
Problem: one oversized-file limit and a recoverable Open Anyway path.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16437 Title unavailable (Unclear, Unknown); #1367 Title unavailable (Unclear, Unknown); #16461 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16595 fix(editor): one oversized-file limit and a recoverable Open Anyway path | Neil Core team · MEMBER | #16437 Title unavailable Unclear · Unknown #1367 Title unavailable Unclear · Unknown #16461 Title unavailable Unclear · Unknown | Standalone change | ## What this does When a file is too big for the editor, Orca currently shows a dead "Unable to load file" box with a Retry button that can never work. This replaces that with an explanatory view and an **Open Anyway** a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk42 files, +1818/−85. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2only spend auto-recovery on the real deadline1 PR · Standalone · Plugins#
Problem: only spend auto-recovery on the real deadline.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12683 remote-runtime: markDisconnected() falsely spends auto-recovery window on web-terminal surfaces (stale same-handle reattach) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13153 fix(remote-runtime): only spend auto-recovery on the real deadline | BingZ Community · CONTRIBUTOR | #12683 remote-runtime: markDisconnected() falsely spends auto-recovery window on web-terminal surfaces (stale same-handle reattach) Fixes · OPEN | Standalone change | ## Summary - A UI-only disconnect latch no longer spends the 60-second automatic recovery window. - Only the real recovery deadline records evidence that permits one same-handle reattach under the require-replacement fen | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +58/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2only the Windows console-limit failure keeps a dead terminal open (STA-5604)1 PR · Standalone · Plugins#
Problem: only the Windows console-limit failure keeps a dead terminal open (STA-5604).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16045 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16991 fix(terminal): only the Windows console-limit failure keeps a dead terminal open (STA-5604) | Brennan Benson Core team · MEMBER | #16045 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +563/−167. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open Runtime worktrees in external editors1 PR · Standalone · Plugins#
Problem: open Runtime worktrees in external editors.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15129 fix(shell): open Runtime worktrees in external editors | 墨竹 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 When a worktree lives on a Headless Runtime, Orca should ask a remote-capable editor to open that server path. Previously it treated paths such as `/workspaces/project` as local Windows paths and reported that th | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk34 files, +1776/−246. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open the window before asking the OS keyring about stored secrets1 PR · Standalone · Plugins#
Problem: open the window before asking the OS keyring about stored secrets.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16912 Title unavailable (Unclear, Unknown); #17020 Title unavailable (Unclear, Unknown); #17014 Title unavailable (Unclear, Unknown); #8421 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17015 fix(startup): open the window before asking the OS keyring about stored secrets | Brennan Benson Core team · MEMBER | #16912 Title unavailable Unclear · Unknown #17020 Title unavailable Unclear · Unknown #17014 Title unavailable Unclear · Unknown #8421 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +881/−57. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pace the EAGAIN write retry so a stalled reader can't saturate the daemon thread1 PR · Standalone · Plugins#
Problem: pace the EAGAIN write retry so a stalled reader can't saturate the daemon thread.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11178 Daemon busy-waits on EAGAIN writing to /dev/ptmx — saturates main thread, freezes every terminal on the runtime (Fixes, OPEN); #9797 Title unavailable (Unclear, Unknown); #8104 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15319 fix(pty): pace the EAGAIN write retry so a stalled reader can't saturate the daemon thread | nireak Community · FIRST_TIME_CONTRIBUTOR | #11178 Daemon busy-waits on EAGAIN writing to /dev/ptmx — saturates main thread, freezes every terminal on the runtime Fixes · OPEN #9797 Title unavailable Unclear · Unknown #8104 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Orca writes to a terminal whose program has stopped reading, the kernel says "not now, buffer is full" (`EAGAIN`). Today we immediately ask again — thousands of times a second — which pins a CPU core and fre | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +134/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2parse Grok question option payloads1 PR · Standalone · Plugins#
Problem: parse Grok question option payloads.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16327 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16343 fix(mobile): parse Grok question option payloadsDraft | Brennan Benson Core team · MEMBER | #16327 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +395/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2parse partial-clone remote filters1 PR · Standalone · Plugins#
Problem: parse partial-clone remote filters.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10809 Title unavailable (Unclear, Unknown); #10620 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16371 fix(git): parse partial-clone remote filters | gangliu-kv7 Community · FIRST_TIME_CONTRIBUTOR | #10809 Title unavailable Unclear · Unknown #10620 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Partial clones add a filter annotation such as `[blob:none]` after the `(fetch)` marker in `git remote -v`. Orca expected `(fetch)` to be the end of the line, so it discarded the remote and generic remote identit | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +18/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2partition workspace sessions1 PR · Standalone · Plugins#
Problem: partition workspace sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16178 perf(persistence): partition workspace sessions | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +2323/−67. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Pass paired Web UI context into agent sessions1 PR · Standalone · Plugins#
Problem: Pass paired Web UI context into agent sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17041 Paired Web UI agent sessions lack client surface and host-mode context (Fixes, OPEN); #17117 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17043 Pass paired Web UI context into agent sessions | JasonJarvan Community · FIRST_TIME_CONTRIBUTOR | #17041 Paired Web UI agent sessions lack client surface and host-mode context Fixes · OPEN #17117 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Agents opened from Orca Web now learn that the user is operating a browser against a desktop, `serve`, or `orcad` host. They no longer assume that the user can click controls in the host Electron window. ## What | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +1291/−140. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2paste OS-copied files through target host1 PR · Standalone · Plugins#
Problem: paste OS-copied files through target host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7777 Terminal: pasting an OS-file-manager-copied file should insert its full shell-escaped path (Fixes, OPEN); #15377 [Bug] No longer able to copy/paste images into TUI (Fixes, OPEN); #7786 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15521 fix(terminal): paste OS-copied files through target host | gatsby74 Community · CONTRIBUTOR | #7777 Terminal: pasting an OS-file-manager-copied file should insert its full shell-escaped path Fixes · OPEN #15377 [Bug] No longer able to copy/paste images into TUI Fixes · OPEN #7786 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Copying a file in Finder, Explorer, or a Linux file manager and pasting into an Orca terminal now uses the actual file reference instead of the display-name text that the OS also places on the clipboard. Remote t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1015/−57. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Per-agent terminal theme overrides in Settings → Appearance1 PR · Standalone · Plugins#
Problem: Per-agent terminal theme overrides in Settings → Appearance.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14174 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14186 fix: Per-agent terminal theme overrides in Settings → Appearance | Anuj Singh Community · FIRST_TIME_CONTRIBUTOR | #14174 Title unavailable Unclear · Unknown | Standalone change | ### Addressed all review comments: - **[Blocking]** Issue/PR Feedback: Per-agent terminal theme overrides in Settings → Appearance - **Resolution**: Modified .gitattributes according to specifications - **Test**: `tests/ | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +1/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2persist exact terminal owner identity1 PR · Standalone · Plugins#
Problem: persist exact terminal owner identity.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16277 fix: persist exact terminal owner identity | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 49 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk137 files, +3467/−723. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2persist the dispatch_input failure cause on the Dispatch1 PR · Standalone · Plugins#
Problem: persist the dispatch_input failure cause on the Dispatch.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15958 [Other]: a worker-start that fails at prompt delivery writes no dispatch_input effect, and the federated home keeps none at all (Fixes, OPEN); #14822 Title unavailable (Unclear, Unknown); #14505 Title unavailable (Unclear, Unknown); #15920 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15964 fix(orchestration): persist the dispatch_input failure cause on the Dispatch | Tauri-EPO Community · CONTRIBUTOR | #15958 [Other]: a worker-start that fails at prompt delivery writes no dispatch_input effect, and the federated home keeps none at all Fixes · OPEN #14822 Title unavailable Unclear · Unknown #14505 Title unavailable Unclear · Unknown #15920 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When starting a worker fails while handing it its instructions, Orca writes down *that* it failed but not, in the machine-readable list of what the start actually did, that delivering the prompt was ever attempte | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +498/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pin recoverable worker start receipt (STA-4674)1 PR · Standalone · Plugins#
Problem: pin recoverable worker start receipt (STA-4674).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16590 Title unavailable (Unclear, Unknown); #16548 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16848 test(orchestration): pin recoverable worker start receipt (STA-4674) | Brennan Benson Core team · MEMBER | #16590 Title unavailable Unclear · Unknown #16548 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +83/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pin the migration-unsupported replay as unreachable1 PR · Standalone · Plugins#
Problem: pin the migration-unsupported replay as unreachable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17262 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17269 test(persistence): pin the migration-unsupported replay as unreachable | Brennan Benson Core team · MEMBER | #17262 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Orca opens a profile it builds a `Store`. The `Store` hands a long-lived background object a callback — "if these rows change, save them for me" — and that object only has room for **one** callback at a time | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +79/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prefer Pi/OMP harness names in session history (STA-2467)1 PR · Standalone · Plugins#
Problem: prefer Pi/OMP harness names in session history (STA-2467).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10250 [Bug]: Agent session list names don't match custom names set by the user (Fixes, OPEN); #15659 Title unavailable (Unclear, Unknown); #10393 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15696 fix(ai-vault): prefer Pi/OMP harness names in session history (STA-2467) | Brennan Benson Core team · MEMBER | #10250 [Bug]: Agent session list names don't match custom names set by the user Fixes · OPEN #15659 Title unavailable Unclear · Unknown #10393 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +390/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prefer stored worker defaults in worker-start guidance1 PR · Standalone · Plugins#
Problem: prefer stored worker defaults in worker-start guidance.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12431 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15568 docs(orchestration): prefer stored worker defaults in worker-start guidance | Johan Kim Community · FIRST_TIME_CONTRIBUTOR | #12431 Title unavailable Unclear · Unknown | Standalone change | > **Depends on #12431 — merge that PR first.** This PR documents behavior that #12431 introduces; it is based directly on `main` so the diff shows only the docs change. > > One consequence worth knowing before you review | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +217/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve consent-gated Claude models (STA-4834)2 PRs · Overlapping · Plugins#
Problem: preserve consent-gated Claude models (STA-4834).
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15433 [Bug]: Claude Fable model not selectable in native UI when CLI probe omits it (Fixes, OPEN); #15434 Title unavailable (Unclear, Unknown); #12369 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15664 fix(native-chat): preserve consent-gated Claude models (STA-4834) | Brennan Benson Core team · MEMBER | #15433 [Bug]: Claude Fable model not selectable in native UI when CLI probe omits it Fixes · OPEN #15434 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +249/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15865 fix(native-chat): keep Claude Fable selectable when the CLI probe omits it | Neil Core team · MEMBER | #15433 [Bug]: Claude Fable model not selectable in native UI when CLI probe omits it Fixes · OPEN #15434 Title unavailable Unclear · Unknown #12369 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +117/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve Ctrl+Shift chords for direct OMP launches1 PR · Standalone · Plugins#
Problem: preserve Ctrl+Shift chords for direct OMP launches.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17081 [Bug]: OMP launched from the agent shortcut cannot distinguish Ctrl+Shift chords (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17082 fix(terminal): preserve Ctrl+Shift chords for direct OMP launches | LiuSir Community · FIRST_TIME_CONTRIBUTOR | #17081 [Bug]: OMP launched from the agent shortcut cannot distinguish Ctrl+Shift chords Fixes · OPEN | Standalone change | ## ELI5 OMP asks the terminal whether it supports richer keyboard input before it can tell Ctrl+Shift apart from simpler key presses. Orca already answered that question for a normal terminal, but not early enough when O | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +345/−146. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve desktop custom terminal titles1 PR · Standalone · Plugins#
Problem: preserve desktop custom terminal titles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16200 [Bug]: Desktop custom terminal tab titles are replaced by PTY titles on mobile (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16202 fix(mobile): preserve desktop custom terminal titles | 叁笙早安 AI Community · FIRST_TIME_CONTRIBUTOR | #16200 [Bug]: Desktop custom terminal tab titles are replaced by PTY titles on mobile Fixes · OPEN | Standalone change | ## ELI5 A desktop tab nickname is the user's stable label for a session. The program running inside that terminal can keep changing its own title, but mobile should use that dynamic title only when the user has not suppl | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +70/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Preserve exact linked tasks in automations1 PR · Standalone · Plugins#
Problem: Preserve exact linked tasks in automations.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15374 Preserve exact linked tasks in automations | aprudkin Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 An automation can now remember the exact issue or task it was created for, not only the repository that contains it. A run keeps that identity even if the automation is edited later. ## What Changed - Persist an | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +375/−52. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Preserve legacy daemon ownership when liveness is unavailable1 PR · Standalone · Plugins#
Problem: Preserve legacy daemon ownership when liveness is unavailable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15666 Title unavailable (Unclear, Unknown); #16908 Title unavailable (Unclear, Unknown); #16777 Title unavailable (Unclear, Unknown); #16932 Title unavailable (Unclear, Unknown); #16924 Title unavailable (Unclear, Unknown); #16926 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16900 Preserve legacy daemon ownership when liveness is unavailable | Brennan Benson Core team · MEMBER | #15666 Title unavailable Unclear · Unknown #16908 Title unavailable Unclear · Unknown #16777 Title unavailable Unclear · Unknown #16932 Title unavailable Unclear · Unknown #16924 Title unavailable Unclear · Unknown #16926 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +344/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve local file tab order2 PRs · Overlapping · Automated release pipeline#
Problem: preserve local file tab order.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #13055 [Bug]: Remote server Cmd-clicked files are inserted as the first tab (Fixes, OPEN); #13233 Title unavailable (Unclear, Unknown); #15219 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13233 fix(remote): preserve local file tab order | Wooseong Kim Community · CONTRIBUTOR | #13055 [Bug]: Remote server Cmd-clicked files are inserted as the first tab Fixes · OPEN | Cluster contribution | ## Description Remote file tabs opened from terminal output now preserve their local file-tab positions when the remote tab snapshot is reconciled. The sync layer stops treating host-owned remote layout data as authorita | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +64/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16085 fix(remote): keep locally opened file tabs in their own slots | gatsby74 Community · CONTRIBUTOR | #13055 [Bug]: Remote server Cmd-clicked files are inserted as the first tab Fixes · OPEN #13233 Title unavailable Unclear · Unknown #15219 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 On a remote host, opening a file from an agent's output shoved that file to the front of the tab bar and pushed your agent and terminals to the right. Now the file tab stays where it was opened. ## What Changed B | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +231/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve ordinary user-set config keys across managed-home remirrors1 PR · Standalone · Plugins#
Problem: preserve ordinary user-set config keys across managed-home remirrors.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14473 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15682 fix(codex): preserve ordinary user-set config keys across managed-home remirrors | Brennan Benson Core team · MEMBER | #14473 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1239/−183. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve OS trust and network policy for first-party traffic1 PR · Standalone · Plugins#
Problem: preserve OS trust and network policy for first-party traffic.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13735 [Bug]: Cloud sign-in and Orca Relay fail silently behind TLS-inspecting corporate networks (Fixes, OPEN); #10758 Title unavailable (Unclear, Unknown); #15208 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16399 fix(cloud): preserve OS trust and network policy for first-party traffic | Minidoracat Community · FIRST_TIME_CONTRIBUTOR | #13735 [Bug]: Cloud sign-in and Orca Relay fail silently behind TLS-inspecting corporate networks Fixes · OPEN #10758 Title unavailable Unclear · Unknown #15208 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On inspected corporate networks, the browser can trust the company certificate while Orca's Node-based Cloud and Relay connections reject it. This makes sign-in look successful, then Cloud or Relay fails. Orca no | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk45 files, +2406/−80. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve paired web host identity1 PR · Standalone · Plugins#
Problem: preserve paired web host identity.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14364 fix(sidebar): preserve paired web host identityDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## Summary Fixes [STA-4182](https://linear.app/stably/issue/STA-4182/release-blocking-paired-web-add-project-picker-shows-local). Paired web now keeps the configured Orca Server as the displayed Add Project host when tha | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +679/−123. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve pane identity for agent-name task titles1 PR · Standalone · Plugins#
Problem: preserve pane identity for agent-name task titles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14937 [Bug]: Another agent's name in Claude's task title steals the pane identity (wrong tab icon) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15037 fix(tabs): preserve pane identity for agent-name task titles | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #14937 [Bug]: Another agent's name in Claude's task title steals the pane identity (wrong tab icon) Fixes · OPEN | Standalone change | ## Summary - keep a pane's known agent owner when a task title merely mentions another supported agent - require explicit identity-shaped terminal titles before title evidence can re-own a reused pane - preserve native C | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +190/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve remote CLI argument boundaries1 PR · Standalone · Plugins#
Problem: preserve remote CLI argument boundaries.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16301 [Bug]: Remote CLI bridge misroutes any command whose arguments contain a relay flag such as --connect (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16320 fix: preserve remote CLI argument boundaries | Seongho.Bak Community · CONTRIBUTOR | #16301 [Bug]: Remote CLI bridge misroutes any command whose arguments contain a relay flag such as --connect Fixes · OPEN | Standalone change | ## ELI5 The SSH relay has its own flags, followed by `--orca-cli` and the user's Orca command. It previously kept reading after that boundary, so a user argument such as `--connect` could make the relay change jobs inste | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +53/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve rich markdown selection across tab switches1 PR · Standalone · Plugins#
Problem: preserve rich markdown selection across tab switches.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14800 Editor scroll/cursor position lost after switching tabs or files (no restart needed) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14940 fix(editor): preserve rich markdown selection across tab switches | poorpaper Community · CONTRIBUTOR | #14800 Editor scroll/cursor position lost after switching tabs or files (no restart needed) Fixes · OPEN | Standalone change | ## ELI5 Switching away from a rich Markdown file and back now returns the caret and selection to the same place instead of resetting them to the start. ## What Changed - Cache each rich Markdown selection with the existi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +296/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve terminals during transient mount loss1 PR · Standalone · Plugins#
Problem: preserve terminals during transient mount loss.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16966 fix(workspaces): preserve terminals during transient mount loss | ye4241 Community · CONTRIBUTOR | None found | Standalone change | ## ELI5 When a folder lives on an SMB or other network-mounted volume, a brief disconnect should not make Orca erase its terminals. This change keeps live terminals attached, marks the folder unavailable, and recovers th | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk35 files, +634/−65. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve unmounted mobile browser tabs1 PR · Standalone · Plugins#
Problem: preserve unmounted mobile browser tabs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14598 [Bug]: Browser tabs are missing from the phone's tab list until the desktop displays that workspace (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14792 fix(runtime): preserve unmounted mobile browser tabs | BingZ Community · CONTRIBUTOR | #14598 [Bug]: Browser tabs are missing from the phone's tab list until the desktop displays that workspace Fixes · OPEN | Standalone change | ## ELI5 Orca already remembers browser tabs for every desktop workspace, even while that workspace is not on screen. The phone list was treating a currently mounted browser view as proof that a tab existed, so remembered | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +261/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve untouched markdown bytes when saving from the rich editor (#16469)1 PR · Standalone · Plugins#
Problem: preserve untouched markdown bytes when saving from the rich editor (#16469).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16469 [Bug]: Saving a Markdown file in Orca silently corrupts its content (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16479 fix(editor): preserve untouched markdown bytes when saving from the rich editor (#16469) | Borja Community · CONTRIBUTOR | #16469 [Bug]: Saving a Markdown file in Orca silently corrupts its content Fixes · OPEN | Standalone change | ## ELI5 Editing and saving a Markdown file in Orca's rich (WYSIWYG) editor could silently rewrite parts of the file you never touched. This makes saving preserve untouched bytes exactly. ## What Changed The rich editor s | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +307/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve user ZDOTDIR in the zsh overlay instead of collapsing to $HOME (#12507)1 PR · Standalone · Plugins#
Problem: preserve user ZDOTDIR in the zsh overlay instead of collapsing to $HOME (#12507).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12507 [Bug]: Relay zsh overlay sets ORCA_USER_ZDOTDIR=$HOME instead of preserved ORCA_ORIG_ZDOTDIR — custom ZDOTDIR still broken on SSH/relay (recurrence of #10051) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12543 fix(relay): preserve user ZDOTDIR in the zsh overlay instead of collapsing to $HOME (#12507) | Seeun Park Community · FIRST_TIME_CONTRIBUTOR | #12507 [Bug]: Relay zsh overlay sets ORCA_USER_ZDOTDIR=$HOME instead of preserved ORCA_ORIG_ZDOTDIR — custom ZDOTDIR still broken on SSH/relay (recurrence of #10051) Fixes · OPEN | Standalone change | ## What this fixes Fixes #12507. On an SSH/relay remote zsh session with an XDG-style layout (real config in `~/.config/zsh`, a `~/.zshrc` shim that sources `$ZDOTDIR/.zshrc`), every Orca pane starts with `ZDOTDIR=$HOME` | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +59/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve worktree names across scan stalls1 PR · Standalone · Plugins#
Problem: preserve worktree names across scan stalls.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16724 Worktree names collapse to repository name when a remote scan stalls (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16723 fix(runtime): preserve worktree names across scan stalls | GhostFlying Community · FIRST_TIME_CONTRIBUTOR | #16724 Worktree names collapse to repository name when a remote scan stalls Fixes · OPEN | Standalone change | ## ELI5 When a worktree scan is temporarily slow, keep showing the last branch and workspace name we successfully learned instead of collapsing several worktrees to the repository name. ## What Changed - Reuse the last s | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +62/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2press keys through a US-layout CDP key table instead of a subprocess per keystroke1 PR · Standalone · Plugins#
Problem: press keys through a US-layout CDP key table instead of a subprocess per keystroke.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15308 Title unavailable (Unclear, Unknown); #13231 Title unavailable (Unclear, Unknown); #12912 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15310 fix(browser): press keys through a US-layout CDP key table instead of a subprocess per keystroke | Jared Meek Community · FIRST_TIME_CONTRIBUTOR | #15308 Title unavailable Unclear · Unknown #13231 Title unavailable Unclear · Unknown #12912 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Typing in the remote browser pane launches a new process on the host for every keystroke -- about 160ms per character, so clicking a login field, typing a 17-character password and hitting enter takes ~4 seconds | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +661/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prevent Create from hanging on selected PR1 PR · Standalone · Plugins#
Problem: prevent Create from hanging on selected PR.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17128 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17153 fix(workspaces): prevent Create from hanging on selected PR | Neil Core team · MEMBER | #17128 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +218/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prevent restored terminal spawn storms1 PR · Standalone · Plugins#
Problem: prevent restored terminal spawn storms.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15624 Title unavailable (Unclear, Unknown); #15644 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15742 fix(renderer): prevent restored terminal spawn storms | Jinwoo Hong Core team · MEMBER | #15624 Title unavailable Unclear · Unknown #15644 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1478/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2project providerSession.id as sessionId on agent.status.changed2 PRs · Overlapping · Plugins#
Problem: project providerSession.id as sessionId on agent.status.changed.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15639 agent.status.changed carries no session identifier, so plugins cannot tell two agents in one worktree apart (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15640 feat(plugins): project providerSession.id as sessionId on agent.status.changed | Yorai Levi Community · FIRST_TIME_CONTRIBUTOR | #15639 agent.status.changed carries no session identifier, so plugins cannot tell two agents in one worktree apart Fixes · OPEN | Cluster contribution | Closes #15639. ## Problem `agent.status.changed` gives a plugin two identifiers, and neither identifies the agent session: ``` paneKey = "<tabId UUID>:<layoutLeaf UUID>" ← no session identity worktreeId = "<repoId>::<abs | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +58/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15680 feat(plugins): carry session identifiers on agent.status.changed | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15639 agent.status.changed carries no session identifier, so plugins cannot tell two agents in one worktree apart Fixes · OPEN | Cluster contribution | ## Summary **What** `agent.status.changed` plugin events now carry `sessionId` and `transcriptPath` (both optional) when the status entry captured a provider session, alongside the existing `worktreeId` / `paneKey` / `st | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +61/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2promote folders that become git repos without re-add1 PR · Standalone · Plugins#
Problem: promote folders that become git repos without re-add.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13630 [Bug] Git branches not detecting (Fixes, OPEN); #11480 Title unavailable (Unclear, Unknown); #13702 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15694 fix(repo): promote folders that become git repos without re-add | Brennan Benson Core team · MEMBER | #13630 [Bug] Git branches not detecting Fixes · OPEN #11480 Title unavailable Unclear · Unknown #13702 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +639/−88. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2protect repository-managed hook config symlinks1 PR · Standalone · Plugins#
Problem: protect repository-managed hook config symlinks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6879 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15831 fix: protect repository-managed hook config symlinks | Marc Hansen Community · FIRST_TIME_CONTRIBUTOR | #6879 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca should not rewrite a Claude settings file that is deliberately stored in a Git repository. When the settings path is a symlink into a repository, hook installation now leaves it untouched and explains why in | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +94/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prove visible terminal identity1 PR · Standalone · Plugins#
Problem: prove visible terminal identity.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17117 Visible terminal initialization needs an incarnation-aware Runtime identity proof (Fixes, OPEN); #17041 Title unavailable (Unclear, Unknown); #17043 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17139 fix(terminal): prove visible terminal identity | JasonJarvan Community · FIRST_TIME_CONTRIBUTOR | #17117 Visible terminal initialization needs an incarnation-aware Runtime identity proof Fixes · OPEN #17041 Title unavailable Unclear · Unknown #17043 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 After a terminal is resumed, moved, split, or reconnected, old environment values may no longer identify the terminal the user is actually looking at. This adds a short-lived two-call Runtime proof: the first cal | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +1447/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2provenance-gated PTY-churn RSS harness + STA-3515 re-measurement on a #16870-inclusive build1 PR · Standalone · Plugins#
Problem: provenance-gated PTY-churn RSS harness + STA-3515 re-measurement on a #16870-inclusive build.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16870 Title unavailable (Unclear, Unknown); #16924 Title unavailable (Unclear, Unknown); #16801 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16948 test(daemon): provenance-gated PTY-churn RSS harness + STA-3515 re-measurement on a #16870-inclusive build | Brennan Benson Core team · MEMBER | #16870 Title unavailable Unclear · Unknown #16924 Title unavailable Unclear · Unknown #16801 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +2918/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2put pinned folder workspaces in the Pinned section1 PR · Standalone · Plugins#
Problem: put pinned folder workspaces in the Pinned section.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15362 Title unavailable (Unclear, Unknown); #15404 Title unavailable (Unclear, Unknown); #15545 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16799 fix(sidebar): put pinned folder workspaces in the Pinned section | Daniel Lafraia Community · FIRST_TIME_CONTRIBUTOR | #15362 Title unavailable Unclear · Unknown #15404 Title unavailable Unclear · Unknown #15545 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Pinning a folder workspace now puts it in the left **Pinned** list, the same way pinning a git worktree already does. ## What Changed `buildRows` already treated pin as placement for git worktrees: they leave (or | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +407/−58. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2rank Ctrl+P results with recent file history1 PR · Standalone · Plugins#
Problem: rank Ctrl+P results with recent file history.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16423 [Feature]: Ctrl+P display the results sorted by history (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16579 feat(quick-open): rank Ctrl+P results with recent file history | Wooseong Kim Community · CONTRIBUTOR | #16423 [Feature]: Ctrl+P display the results sorted by history Fixes · OPEN | Standalone change | ## Description Ctrl+P ranked files by fuzzy score then index order, so an empty query was not recent-first. Quick Open now prefers recently opened editor tabs for the active worktree. ## Focused fix - In scope: rank Quic | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +131/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2rank tui-idle evidence instead of inferring idle from silence1 PR · Standalone · Plugins#
Problem: rank tui-idle evidence instead of inferring idle from silence.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #6011 terminal wait --for tui-idle returns satisfied:true in ~0s while an agent TUI is actively working (Fixes, OPEN); #14610 Title unavailable (Unclear, Unknown); #14626 Title unavailable (Unclear, Unknown); #14561 Title unavailable (Unclear, Unknown); #9976 Title unavailable (Unclear, Unknown); #6012 Title unavailable (Unclear, Unknown); #6555 Title unavailable (Unclear, Unknown); #9915 Title unavailable (Unclear, Unknown); #9929 Title unavailable (Unclear, Unknown); #9905 Title unavailable (Unclear, Unknown); #10020 Title unavailable (Unclear, Unknown); #8113 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14642 fix(runtime): rank tui-idle evidence instead of inferring idle from silence | Brennan Benson Core team · MEMBER | #6011 terminal wait --for tui-idle returns satisfied:true in ~0s while an agent TUI is actively working Fixes · OPEN #14610 Title unavailable Unclear · Unknown #14626 Title unavailable Unclear · Unknown #14561 Title unavailable Unclear · Unknown #9976 Title unavailable Unclear · Unknown #6012 Title unavailable Unclear · Unknown #6555 Title unavailable Unclear · Unknown #9915 Title unavailable Unclear · Unknown #9929 Title unavailable Unclear · Unknown #9905 Title unavailable Unclear · Unknown #10020 Title unavailable Unclear · Unknown #8113 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +703/−77. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2rate-cap WebGL glyph-atlas recovery on streaming output1 PR · Standalone · Plugins#
Problem: rate-cap WebGL glyph-atlas recovery on streaming output.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12061 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12486 fix(terminal): rate-cap WebGL glyph-atlas recovery on streaming output | Neil Core team · MEMBER | #12061 Title unavailable Unclear · Unknown | Standalone change | ## What this fixes **Signature:** renderer `render-process-gone { reason: "crashed" }` on Windows (`exitCode -36861` / `-1`) and Linux (`139` = SIGSEGV) after a long session in which the app wiped the **shared** xterm We | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +245/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2re-land WSL direct-home cutover with counsel findings fixed1 PR · Standalone · Plugins#
Problem: re-land WSL direct-home cutover with counsel findings fixed.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16722 Title unavailable (Unclear, Unknown); #16496 Title unavailable (Unclear, Unknown); #16499 Title unavailable (Unclear, Unknown); #16535 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16854 fix(codex): re-land WSL direct-home cutover with counsel findings fixed | Brennan Benson Core team · MEMBER | #16722 Title unavailable Unclear · Unknown #16496 Title unavailable Unclear · Unknown #16499 Title unavailable Unclear · Unknown #16535 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 14 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +3669/−809. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reap the proven relay generation instead of orphaning it (#8585)2 PRs · Competing · Automated release pipeline#
Problem: reap the proven relay generation instead of orphaning it (#8585).
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Competing. Linked issues: #8585 Orphaned detached relays are never reaped: failed --connect deletes the socket but leaves the old relay (and its PTYs/agents) running forever (Fixes, OPEN); #12607 Title unavailable (Unclear, Unknown); #8618 Title unavailable (Unclear, Unknown); #11943 Title unavailable (Unclear, Unknown); #12895 Title unavailable (Unclear, Unknown); #8762 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Choose one implementation after a product and technical comparison; do not land alternatives together.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Not until one implementation is chosen.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Product and technical decision required.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12760 fix(ssh): reap the proven relay generation instead of orphaning it (#8585) | sangha choi Community · FIRST_TIME_CONTRIBUTOR | #8585 Orphaned detached relays are never reaped: failed --connect deletes the socket but leaves the old relay (and its PTYs/agents) running forever Fixes · OPEN #12607 Title unavailable Unclear · Unknown #8618 Title unavailable Unclear · Unknown | Alternative implementation | ## Root cause When a POSIX relay reconnect failed, `launchRelay` ran `rm -f <socket>` and launched a fresh detached relay. Nothing told the relay that still owned that socket to stop, so it stayed resident holding live P | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks Unknown · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +4478/−84. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15489 fix(ssh): kill the relay daemon before discarding its socket | Tingde Liu Community · FIRST_TIME_CONTRIBUTOR | #8585 Orphaned detached relays are never reaped: failed --connect deletes the socket but leaves the old relay (and its PTYs/agents) running forever Fixes · OPEN #11943 Title unavailable Unclear · Unknown #12895 Title unavailable Unclear · Unknown #8762 Title unavailable Unclear · Unknown | Alternative implementation | ## ELI5 When Orca can't reattach to a relay it left running on an SSH host, it deletes the relay's socket file and starts a new one. But the old relay process keeps running — with all your terminals and agents inside it. | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +341/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recognize Antigravity 1.1.17 ready prompt2 PRs · Overlapping · Plugins#
Problem: recognize Antigravity 1.1.17 ready prompt.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15838 [Bug]: Antigravity CLI 1.1.17 ready prompt no longer matches tui-idle, causing worker-start agent_readiness timeout (Fixes, OPEN); #10740 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15840 fix(runtime): recognize Antigravity 1.1.17 ready prompt | DemonZhou Community · FIRST_TIME_CONTRIBUTOR | #15838 [Bug]: Antigravity CLI 1.1.17 ready prompt no longer matches tui-idle, causing worker-start agent_readiness timeout Fixes · OPEN #10740 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Antigravity CLI 1.1.17 no longer keeps its ready prompt as a bare `>`. The text after `>` changes with the active mode — for example, Accept-edits and Plan. Orca only recognized the old bare prompt, so supervised | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +36/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15852 fix(runtime): accept the Antigravity 1.1.17 composer-banner ready prompt | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15838 [Bug]: Antigravity CLI 1.1.17 ready prompt no longer matches tui-idle, causing worker-start agent_readiness timeout Fixes · OPEN | Cluster contribution | ## Summary **What** `findAntigravityReadyPromptIndex` now accepts the idle composer line in either shape: the older bare `>` line, **or** CLI 1.1.17's mode banner (`> Accept-edits mode: file edits auto-approved (shift+ta | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +76/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recognize Cline OSC titles in worktree agent rows1 PR · Standalone · Plugins#
Problem: recognize Cline OSC titles in worktree agent rows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13823 Cline terminals don't appear in sidebar agent rows (Fixes, OPEN); #12466 Title unavailable (Unclear, Unknown); #13840 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13959 fix(agents): recognize Cline OSC titles in worktree agent rows | OrcaWin Unknown · COLLABORATOR | #13823 Cline terminals don't appear in sidebar agent rows Fixes · OPEN #12466 Title unavailable Unclear · Unknown #13840 Title unavailable Unclear · Unknown | Standalone change | ## Summary Cline terminals launched in Orca did not appear in worktree sidebar agent rows or the agent dashboard because the OSC title path never classified them. Live Windows repro (`cline -i` via Orca terminal create) | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +192/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recognize symlinks targeting canonical skill location as provider aliases1 PR · Standalone · Plugins#
Problem: recognize symlinks targeting canonical skill location as provider aliases.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16459 fix(skills): recognize symlinks targeting canonical skill location as provider aliases | KronixDev Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ### Summary When agents share skills via symlinks (e.g. dotfile managers, shared toolchains, or package managers like `skills` CLI), `classifyHomeSkillTopology` previously checked: ```ts isCanonicalTarget = normalizedSki | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +8/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2record post-startup process exits (STA-5709)1 PR · Standalone · Plugins#
Problem: record post-startup process exits (STA-5709).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16875 fix(daemon): record post-startup process exits (STA-5709) | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +410/−44. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover commit ref badges on Git before 2.432 PRs · Overlapping · Plugins#
Problem: recover commit ref badges on Git before 2.43.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #15507 [Bug]: Commit ref badges disappear in Source Control on Git older than 2.43 (Fixes, OPEN); #15358 [Bug]: Projects table sorts an empty assignee list to the top when sorting descending (Fixes, OPEN); #15724 [Bug]: a delimiter-less paneKey is truncated into a tab id, stranding a sleeping agent session (Fixes, OPEN); #15409 Title unavailable (Unclear, Unknown); #15410 Title unavailable (Unclear, Unknown); #15445 Title unavailable (Unclear, Unknown); #14838 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15508 fix(source-control): recover commit ref badges on Git before 2.43 | giryun Community · FIRST_TIME_CONTRIBUTOR | #15507 [Bug]: Commit ref badges disappear in Source Control on Git older than 2.43 Fixes · OPEN | Cluster contribution | ## ELI5 Orca asks Git for each commit's branch/tag labels using a format placeholder that only exists in Git 2.43 and newer. On older Git the request comes back as the literal placeholder text instead of labels, so the C | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +455/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15590 fix: four independent bugs (Project sort/group, Git <2.43 ref badges, agent ack, paneKey parsing) | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15358 [Bug]: Projects table sorts an empty assignee list to the top when sorting descending Fixes · OPEN #15507 [Bug]: Commit ref badges disappear in Source Control on Git older than 2.43 Fixes · OPEN #15724 [Bug]: a delimiter-less paneKey is truncated into a tab id, stranding a sleeping agent session Fixes · OPEN #15409 Title unavailable Unclear · Unknown #15410 Title unavailable Unclear · Unknown #15445 Title unavailable Unclear · Unknown #14838 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Four unrelated defects, one commit each. Sorting a Projects table descending scattered unassigned rows across both ends; commit ref badges vanished entirely on older Git; acknowledging an agent from the Activity | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +608/−93. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover oversized workspace updates1 PR · Standalone · Plugins#
Problem: recover oversized workspace updates.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15238 [Bug]: SSH relay silently drops oversized workspace.changed events, leaving the client's session list stale (Fixes, OPEN); #12339 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15929 fix(ssh): recover oversized workspace updates | GhostFlying Community · FIRST_TIME_CONTRIBUTOR | #15238 [Bug]: SSH relay silently drops oversized workspace.changed events, leaving the client's session list stale Fixes · OPEN #12339 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Large SSH workspace updates could be too big for the relay's notification lane. The relay persisted the update but silently dropped the notification, so the desktop kept showing stale tabs. This change sends a sm | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +582/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover stripped task deps1 PR · Standalone · Plugins#
Problem: recover stripped task deps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16706 task-create --deps rejects non-empty arrays again on 1.4.190 (Windows regression) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16743 fix(orchestration): recover stripped task deps | Pr1p Community · CONTRIBUTOR | #16706 task-create --deps rejects non-empty arrays again on 1.4.190 (Windows regression) Fixes · OPEN | Standalone change | ## ELI5 PowerShell can hand Orca a dependency list where the JSON quotes are gone. Orca now still accepts that list when it clearly contains valid generated task IDs. ## What Changed - Keep normal JSON array parsing for | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +239/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover terminals after headless serve restarts1 PR · Standalone · Plugins#
Problem: recover terminals after headless serve restarts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13158 Title unavailable (Unclear, Unknown); #13142 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13247 fix(web): recover terminals after headless serve restarts | BLUEAT Community · FIRST_TIME_CONTRIBUTOR | #13158 Title unavailable Unclear · Unknown #13142 Title unavailable Unclear · Unknown | Standalone change | ## Summary Paired web terminals now recover after a headless `orca serve` host restart even when the user switches to another internal Orca tab and returns later. Root cause: - Web runtime subscriptions belonged to one W | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +768/−47. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover the runtime host disconnected glyph1 PR · Standalone · Plugins#
Problem: recover the runtime host disconnected glyph.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16516 [Bug]: A saved Orca server stays "disconnected" in the sidebar for the whole session after one failed boot probe (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16518 fix(sidebar): recover the runtime host disconnected glyph | ASDFGHoney Community · FIRST_TIME_CONTRIBUTOR | #16516 [Bug]: A saved Orca server stays "disconnected" in the sidebar for the whole session after one failed boot probe Fixes · OPEN | Standalone change | ## ELI5 Orca remembered "I couldn't reach that server" from the moment it started up, and then never checked again. So if your remote Mac happened to be asleep when Orca launched, its workspaces stayed greyed out with a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +1487/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Recover unreachable main windows after display changes1 PR · Standalone · Plugins#
Problem: Recover unreachable main windows after display changes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17025 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17080 Recover unreachable main windows after display changes | Jinwoo Hong Core team · MEMBER | #17025 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +652/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Refresh current LAN endpoints while a phone is on Relay1 PR · Standalone · Plugins#
Problem: Refresh current LAN endpoints while a phone is on Relay.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14576 Refresh current LAN endpoints while a phone is on Relay | Ordinary Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 When you pair your phone with the desktop, the phone stores the desktop LAN (and Tailscale) addresses from that moment. If the desktop later changes Wi-Fi -- cafe DHCP, a new NIC, leaving the pair-time subnet -- | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +638/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2refuse to submit a CLI prompt over an unsent composer draft1 PR · Standalone · Plugins#
Problem: refuse to submit a CLI prompt over an unsent composer draft.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16289 [Bug]: terminal send --enter appends to the target's unsent draft and submits both (Fixes, OPEN); #16711 Title unavailable (Unclear, Unknown); #14980 Title unavailable (Unclear, Unknown); #10740 Title unavailable (Unclear, Unknown); #12358 Title unavailable (Unclear, Unknown); #14037 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16290 fix(terminal): refuse to submit a CLI prompt over an unsent composer draft | luisgonzaleznf Community · FIRST_TIME_CONTRIBUTOR | #16289 [Bug]: terminal send --enter appends to the target's unsent draft and submits both Fixes · OPEN #16711 Title unavailable Unclear · Unknown #14980 Title unavailable Unclear · Unknown #10740 Title unavailable Unclear · Unknown #12358 Title unavailable Unclear · Unknown #14037 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When one agent messages another terminal with `orca terminal send --text ... --enter`, Orca pastes the text and presses Enter without looking at the target's input box. If the user had a half-typed prompt there, | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +501/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2register dir-handle-closure reliability gate1 PR · Standalone · Plugins#
Problem: register dir-handle-closure reliability gate.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17033 Title unavailable (Unclear, Unknown); #12895 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17034 chore(gates): register dir-handle-closure reliability gate | Quim T. Community · FIRST_TIME_CONTRIBUTOR | #17033 Title unavailable Unclear · Unknown #12895 Title unavailable Unclear · Unknown | Standalone change | ## Linked Issue #17033 (there should ALWAYS be one: this is the gates part of that proposal; happy to re-scope) ## ELI5 The repo already tracks bug-class protections in `config/reliability-gates.jsonc` (99 gates today). | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +99/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reject claims about the private reference corpus in changed files1 PR · Standalone · Plugins#
Problem: reject claims about the private reference corpus in changed files.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #909 Title unavailable (Unclear, Unknown); #14661 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17063 chore(ci): reject claims about the private reference corpus in changed files | Brennan Benson Core team · MEMBER | #909 Title unavailable Unclear · Unknown #14661 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Some of Orca's design notes were written while reading a collection of other projects that is not itself public. Notes about *that collection* — how much of it was looked through, and what was searched for and no | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +407/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reject empty terminal handles2 PRs · Overlapping · Plugins#
Problem: reject empty terminal handles.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16694 [Bug]: empty --terminal handle is accepted and silently targets the worktree-active pane (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16742 fix(cli): reject empty terminal handles | Pr1p Community · CONTRIBUTOR | #16694 [Bug]: empty --terminal handle is accepted and silently targets the worktree-active pane Fixes · OPEN | Cluster contribution | ## ELI5 If a script explicitly says "use this terminal" but passes an empty value, Orca now stops with an error instead of quietly picking some active pane. ## What Changed - Treat `--terminal ""` and bare `--terminal` a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +50/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16745 fix(cli): fail closed on empty --terminal handle (#16694) | programmerWsy Community · FIRST_TIME_CONTRIBUTOR | #16694 [Bug]: empty --terminal handle is accepted and silently targets the worktree-active pane Fixes · OPEN | Cluster contribution | ## ELI5 If a script passes `--terminal ""` (empty handle), Orca used to pretend the flag was never there and quietly talk to whatever pane was currently active. That can be a different tab than the script meant. This cha | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +254/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reject locale ids Intl cannot parse1 PR · Standalone · Plugins#
Problem: reject locale ids Intl cannot parse.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12505 Title unavailable (Unclear, Unknown); #12455 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12533 fix(plugins): reject locale ids Intl cannot parse | Evgenii Community · CONTRIBUTOR | #12505 Title unavailable Unclear · Unknown #12455 Title unavailable Unclear · Unknown | Standalone change | ## Summary Repurposed from canonicalizing the locale at read time to rejecting it at install, per review. `pluginLocaleIdSchema` checks the *shape* of a locale id, not its grammar, and the shape check is looser than BCP | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +29/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reject malformed base64 padding1 PR · Standalone · Plugins#
Problem: reject malformed base64 padding.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #4391 Title unavailable (Unclear, Unknown); #11825 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12027 fix(pairing): reject malformed base64 padding | Henry Su Community · CONTRIBUTOR | #4391 Title unavailable Unclear · Unknown #11825 Title unavailable Unclear · Unknown | Standalone change | ## Summary ### Problem Orca's shared pairing parser accepted malformed Base64 padding in Node while rejecting the same pairing code in browser runtimes. A code formed by adding a single `=` to an unpadded payload that re | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +216/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reject requests for detached clients1 PR · Standalone · Plugins#
Problem: reject requests for detached clients.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16302 [Bug]: Relay requests pending on a detached desktop client hang until timeout instead of failing fast (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16321 fix(relay): reject requests for detached clients | Seongho.Bak Community · CONTRIBUTOR | #16302 [Bug]: Relay requests pending on a detached desktop client hang until timeout instead of failing fast Fixes · OPEN | Standalone change | ## ELI5 When the relay asks a desktop Orca client to do something, it waits for that specific client to answer. If that client disconnects, Orca now stops waiting immediately and reports that the client detached instead | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +142/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2release browser driver state after desktop takeover1 PR · Standalone · Plugins#
Problem: release browser driver state after desktop takeover.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15754 fix: release browser driver state after desktop takeover | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Taking back a browser from a phone now removes the temporary mobile-owner record instead of keeping closed browser page IDs alive for the rest of the process. ## What Changed - Keep browser driver entries only wh | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +166/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2release completed worker terminals by default1 PR · Standalone · Plugins#
Problem: release completed worker terminals by default.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13047 [Bug]: Orchestration worker terminals stay open after settle (Done stack / retained legacy_ambiguous) — no auto-release (Fixes, OPEN); #16211 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16217 fix(orchestration): release completed worker terminals by default | 叁笙早安 AI Community · FIRST_TIME_CONTRIBUTOR | #13047 [Bug]: Orchestration worker terminals stay open after settle (Done stack / retained legacy_ambiguous) — no auto-release Fixes · OPEN #16211 Title unavailable Unclear · Unknown | Standalone change | ## Summary - schedule exact owned-worker terminal cleanup 30 seconds after an accepted succeeded/failed `worker_done` - preserve immediate exact-terminal reuse plus explicit retain, user takeover, transferred/external te | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +195/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2release popup origin bar contents1 PR · Standalone · Plugins#
Problem: release popup origin bar contents.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17234 perf(browser): release popup origin bar contents | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +59/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2remove dead hook IPC and derive shared agent defaults1 PR · Standalone · Plugins#
Problem: remove dead hook IPC and derive shared agent defaults.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #123 Title unavailable (Unclear, Unknown); #16148 Title unavailable (Unclear, Unknown); #16157 Title unavailable (Unclear, Unknown); #16144 Title unavailable (Unclear, Unknown); #16237 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16089 refactor(agents): remove dead hook IPC and derive shared agent defaults | trs-80 Community · FIRST_TIME_CONTRIBUTOR | #123 Title unavailable Unclear · Unknown #16148 Title unavailable Unclear · Unknown #16157 Title unavailable Unclear · Unknown #16144 Title unavailable Unclear · Unknown #16237 Title unavailable Unclear · Unknown | Standalone change | ## Summary This PR removes an unused per-agent hook-status IPC surface and consolidates two duplicated agent-registry behaviors without changing the exported desktop configuration shape: 1. Removes the unused `window.api | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +93/−592. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Remove experimental feature requirement from orchestration guide1 PR · Standalone · Plugins#
Problem: Remove experimental feature requirement from orchestration guide.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14064 Remove experimental feature requirement from orchestration guide | Jinjing Core team · MEMBER | None found | Standalone change | ## Problem The orchestration skill guide documents that users must enable an experimental feature in Settings, but this requirement is no longer necessary. ## Solution Remove the experimental feature requirement from the | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +1/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2remove legacy Gemini CLI support1 PR · Standalone · Plugins#
Problem: remove legacy Gemini CLI support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #5924 Title unavailable (Unclear, Unknown); #7428 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12789 refactor: remove legacy Gemini CLI support | Jinjing Core team · MEMBER | #5924 Title unavailable Unclear · Unknown #7428 Title unavailable Unclear · Unknown | Standalone change | Supersedes #5924 (which stays open). Credit to @siddqamar for the original work and audit — this is a clean re-implementation against current `main` rather than a rebase of those commits, because `main` has moved a long | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk264 files, +2509/−4984. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2rename a pane by double-clicking its header1 PR · Standalone · Plugins#
Problem: rename a pane by double-clicking its header.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15790 [Feature]: Double-click a pane header to rename it (Fixes, OPEN); #15781 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15792 feat(terminal): rename a pane by double-clicking its headerDraft | Ramzi Community · CONTRIBUTOR | #15790 [Feature]: Double-click a pane header to rename it Fixes · OPEN #15781 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Double-click the strip at the top of a split pane and you can type a new name for it, then press Enter. Today you have to right-click and hunt for "Set title". ## What Changed `TerminalPaneHeaderOverlay` now star | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +75/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2render every failed-source repo instead of silently dropping it (#16473)1 PR · Standalone · Plugins#
Problem: render every failed-source repo instead of silently dropping it (#16473).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16473 [Bug]: Tasks page counts more failed projects than it renders — repos with no resolved source are silent (Fixes, OPEN); #16474 Title unavailable (Unclear, Unknown); #1317 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16482 fix(tasks): render every failed-source repo instead of silently dropping it (#16473) | Borja Community · CONTRIBUTOR | #16473 [Bug]: Tasks page counts more failed projects than it renders — repos with no resolved source are silent Fixes · OPEN #16474 Title unavailable Unclear · Unknown #1317 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The Tasks page banner could say "N projects failed" but render fewer than N rows: a repo whose fetch failed with nothing cached vanished from the list while still being counted. This makes every counted repo rend | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +102/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2render the streaming reply below the prompt it answers1 PR · Standalone · Plugins#
Problem: render the streaming reply below the prompt it answers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15608 [Bug]: Streaming reply renders above the prompt it answers, so the sent message is stranded at the bottom (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15609 fix(native-chat): render the streaming reply below the prompt it answers | Jake Bishop Community · FIRST_TIME_CONTRIBUTOR | #15608 [Bug]: Streaming reply renders above the prompt it answers, so the sent message is stranded at the bottom Fixes · OPEN | Standalone change | ## ELI5 When you sent a message in the chat, the agent's reply appeared *above* your message instead of below it — so your own prompt got stranded at the bottom and you had to scroll up to read the answer. This puts the | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +621/−84. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Replace Electron desktop host with Tauri/Pake1 PR · Standalone · Plugins#
Problem: Replace Electron desktop host with Tauri/Pake.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15340 Replace Electron desktop host with Tauri/PakeDraft | s546126 Community · CONTRIBUTOR | None found | Standalone change | <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary This is a **desktop runtime replacement**, not an optional `pake-cli --config` wrap of `out/web`. Orca’s shipped/dev desktop path now launches a **Tauri v2** window (the sam | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk46 files, +6435/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report a missing display instead of dying in uv_close1 PR · Standalone · Plugins#
Problem: report a missing display instead of dying in uv_close.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13719 Title unavailable (Unclear, Unknown); #15083 Title unavailable (Unclear, Unknown); #15081 Title unavailable (Unclear, Unknown); #11609 Title unavailable (Unclear, Unknown); #12530 Title unavailable (Unclear, Unknown); #14229 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15084 fix(linux): report a missing display instead of dying in uv_close | Neil Core team · MEMBER | #13719 Title unavailable Unclear · Unknown #15083 Title unavailable Unclear · Unknown #15081 Title unavailable Unclear · Unknown #11609 Title unavailable Unclear · Unknown #12530 Title unavailable Unclear · Unknown #14229 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +151/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report limited when an un-cursored read withholds transcript lines1 PR · Standalone · Plugins#
Problem: report limited when an un-cursored read withholds transcript lines.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12333 [Bug]: un-cursored `terminal read` reports `limited: false` and `nextCursor === latestCursor` while hundreds of transcript lines are withheld (regression from #9081) (Fixes, OPEN); #10231 Title unavailable (Unclear, Unknown); #7433 Title unavailable (Unclear, Unknown); #13672 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15269 fix(terminal): report limited when an un-cursored read withholds transcript lines | Taras Kornichuk Community · CONTRIBUTOR | #12333 [Bug]: un-cursored `terminal read` reports `limited: false` and `nextCursor === latestCursor` while hundreds of transcript lines are withheld (regression from #9081) Fixes · OPEN #10231 Title unavailable Unclear · Unknown #7433 Title unavailable Unclear · Unknown #13672 Title unavailable Unclear · Unknown | Standalone change | ## Behaviour change An un-cursored `orca terminal read` now sets `limited: true` when the retained transcript holds more completed lines than the response returned. Cursor semantics, the default limit, and which buffer t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +43/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report OMP terminal and interactive states2 PRs · Overlapping · Automated release pipeline#
Problem: report OMP terminal and interactive states.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #14278 OMP terminal agent_end can leave status stuck as working (Fixes, OPEN); #13891 Title unavailable (Unclear, Unknown); #13890 Title unavailable (Unclear, Unknown); #13923 Title unavailable (Unclear, Unknown); #14330 Title unavailable (Unclear, Unknown); #14279 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14279 fix(agents): report OMP terminal and interactive states | outside.observer Community · CONTRIBUTOR | #14278 OMP terminal agent_end can leave status stuck as working Fixes · OPEN #13891 Title unavailable Unclear · Unknown #13890 Title unavailable Unclear · Unknown #13923 Title unavailable Unclear · Unknown #14330 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Orca now treats OMP as OMP consistently. It shows completion, questions, and approval waits at the correct time. ## What Changed - Consume OMP's documented `agent_end.willContinue` signal. - Keep OMP identity sta | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +155/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14605 fix(agents): settle and surface the OMP terminal lifecycle (#14278) | Brennan Benson Core team · MEMBER | #14278 OMP terminal agent_end can leave status stuck as working Fixes · OPEN #14330 Title unavailable Unclear · Unknown #14279 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When an OMP agent finished a turn, the Orca sidebar could show that pane as "working" forever. Orca was waiting for OMP to say "I'm idle now" — a signal OMP never sends. OMP instead tells you on every turn-end wh | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +473/−219. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2require double Escape to interrupt Claude turns2 PRs · Related · Automated release pipeline#
Problem: require double Escape to interrupt Claude turns.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Related. Linked issues: #13547 [Bug]: Escape dismissing Claude Code's /btw composer is inferred as a turn interrupt (false red "Interrupted") (Fixes, OPEN); #13609 Title unavailable (Unclear, Unknown); #13710 Title unavailable (Unclear, Unknown); #13692 Title unavailable (Unclear, Unknown); #13691 Title unavailable (Unclear, Unknown); #13536 Title unavailable (Unclear, Unknown); #13572 Title unavailable (Unclear, Unknown); #8072 Title unavailable (Unclear, Unknown); #13237 Title unavailable (Unclear, Unknown); #13570 Title unavailable (Unclear, Unknown); #13561 Title unavailable (Unclear, Unknown); #13255 Title unavailable (Unclear, Unknown); #14372 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13566 fix(terminal): require double Escape to interrupt Claude turns | BingZ Community · CONTRIBUTOR | #13547 [Bug]: Escape dismissing Claude Code's /btw composer is inferred as a turn interrupt (false red "Interrupted") Fixes · OPEN #13609 Title unavailable Unclear · Unknown #13710 Title unavailable Unclear · Unknown #13692 Title unavailable Unclear · Unknown #13691 Title unavailable Unclear · Unknown #13536 Title unavailable Unclear · Unknown #13572 Title unavailable Unclear · Unknown #8072 Title unavailable Unclear · Unknown #13237 Title unavailable Unclear · Unknown #13570 Title unavailable Unclear · Unknown #13561 Title unavailable Unclear · Unknown #13255 Title unavailable Unclear · Unknown #14372 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - Plain Escape while Claude is `working` was inferred as interrupt after 500 ms even when Claude only dismissed `/btw` or another TUI surface (#13547). - Require a second Escape on the same turn for Claude (sa | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +59/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15674 fix(agent-hooks): trust Claude Stop hooks over plain Escape (STA-3817) | Brennan Benson Core team · MEMBER | #13547 [Bug]: Escape dismissing Claude Code's /btw composer is inferred as a turn interrupt (false red "Interrupted") Fixes · OPEN | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +256/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reset inherited zoom on remote and offscreen pages1 PR · Standalone · Plugins#
Problem: reset inherited zoom on remote and offscreen pages.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16675 Remote browser pages inherit Chromium origin zoom (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16676 fix(browser): reset inherited zoom on remote and offscreen pages | Kaylee Community · CONTRIBUTOR | #16675 Remote browser pages inherit Chromium origin zoom Fixes · OPEN | Standalone change | ## ELI5 Zoom a site in Orca on your Mac, then open that same site from a paired laptop or phone. The remote page comes in huge. This puts remote/offscreen pages back to 100%. ## What Changed Local browser panes already r | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +252/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reset question card state when prompt changes1 PR · Standalone · Plugins#
Problem: reset question card state when prompt changes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16934 fix(native-chat): reset question card state when prompt changes | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - reset question selections, free text, and active step when a reused card receives a new prompt - clamp the active question index and safely handle empty prompts - add a regression test for replacing a multi- | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +61/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve --workspace-status by column name1 PR · Standalone · Plugins#
Problem: resolve --workspace-status by column name.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17119 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17135 fix(cli): resolve --workspace-status by column name | Martin Bernstorff Community · FIRST_TIME_CONTRIBUTOR | #17119 Title unavailable Unclear · Unknown | Standalone change | #17119 Instead of requiring a data-migration and changing the persisted workspaceStatus, I went resolving the label when calling form the CLI. This has breaking changes: If a user submits a workspaceStatus that does not | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +274/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve document tab close by id or entityId (#16205)1 PR · Standalone · Plugins#
Problem: resolve document tab close by id or entityId (#16205).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16205 [Bug]: Document tabs (md/html) cannot be closed — close actions are silent no-ops, duplicate tabs pile up (Fixes, OPEN); #16225 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16480 fix(tabs): resolve document tab close by id or entityId (#16205) | Borja Community · CONTRIBUTOR | #16205 [Bug]: Document tabs (md/html) cannot be closed — close actions are silent no-ops, duplicate tabs pile up Fixes · OPEN #16225 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Closing a Markdown/HTML document tab (its X button, the context-menu Close, or Cmd+W) could silently do nothing, so duplicate tabs piled up. This makes document tabs close reliably. ## What Changed In `TabGroupPa | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +192/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve Linux Git metadata paths on Windows1 PR · Standalone · Plugins#
Problem: resolve Linux Git metadata paths on Windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9284 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17175 fix(wsl): resolve Linux Git metadata paths on Windows | Neil Core team · MEMBER | #9284 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +404/−53. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve plugin-pack plurals with the declared locale1 PR · Standalone · Plugins#
Problem: resolve plugin-pack plurals with the declared locale.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12106 Title unavailable (Unclear, Unknown); #12514 Title unavailable (Unclear, Unknown); #12533 Title unavailable (Unclear, Unknown); #12105 Title unavailable (Unclear, Unknown); #12455 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12505 fix(i18n): resolve plugin-pack plurals with the declared locale | Evgenii Community · CONTRIBUTOR | #12106 Title unavailable Unclear · Unknown #12514 Title unavailable Unclear · Unknown #12533 Title unavailable Unclear · Unknown #12105 Title unavailable Unclear · Unknown #12455 Title unavailable Unclear · Unknown | Standalone change | ## Summary Prototype for #12106, option (1) — routing plural resolution through the locale a plugin pack declares. @nwparker asked for one and said (1) is fine "if perf isn't weird"; it is not, and the measurement below | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +289/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve watcher targets concurrently1 PR · Standalone · Plugins#
Problem: resolve watcher targets concurrently.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16176 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17166 perf(worktrees): resolve watcher targets concurrently | Neil Core team · MEMBER | #16176 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +276/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore Antigravity workspace metadata1 PR · Standalone · Plugins#
Problem: restore Antigravity workspace metadata.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15774 Antigravity setup-prompt sessions are missing from workspace history (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15775 fix(ai-vault): restore Antigravity workspace metadata | Ray Community · FIRST_TIME_CONTRIBUTOR | #15774 Antigravity setup-prompt sessions are missing from workspace history Fixes · OPEN | Standalone change | ## ELI5 Antigravity already records a conversation ID alongside its workspace. Use that exact ID instead of guessing from prompt text, so conversations that begin with setup prompts still appear in the correct workspace | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +67/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore Cursor status updates in reused panes3 PRs · Overlapping · Automated release pipeline#
Problem: restore Cursor status updates in reused panes.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #12686 [Bug]: Some Cursor panes remain Working despite completed stop hooks (Fixes, OPEN); #12714 Title unavailable (Unclear, Unknown); #11127 Title unavailable (Unclear, Unknown); #11075 Title unavailable (Unclear, Unknown); #10391 Title unavailable (Unclear, Unknown); #10258 Title unavailable (Unclear, Unknown); #14434 Title unavailable (Unclear, Unknown); #15658 Title unavailable (Unclear, Unknown); #15674 Title unavailable (Unclear, Unknown); #15665 Title unavailable (Unclear, Unknown); #15714 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12714 fix(agent-hooks): restore Cursor status updates in reused panesDraft | ChangJun Park Community · FIRST_TIME_CONTRIBUTOR | #12686 [Bug]: Some Cursor panes remain Working despite completed stop hooks Fixes · OPEN | Cluster contribution | ## Summary - Restore Cursor status updates when a completed command leaves its terminal pane reusable. - Treat Cursor's live `beforeSubmitPrompt` hook as the new-turn boundary, matching the existing Claude `UserPromptSub | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +94/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14626 fix(agent-hooks): reopen a retired pane on any provider's turn boundary (#12686) | Brennan Benson Core team · MEMBER | #12686 [Bug]: Some Cursor panes remain Working despite completed stop hooks Fixes · OPEN #12714 Title unavailable Unclear · Unknown #11127 Title unavailable Unclear · Unknown #11075 Title unavailable Unclear · Unknown #10391 Title unavailable Unclear · Unknown #10258 Title unavailable Unclear · Unknown #14434 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Orca lets a finished agent pane be reused as a plain shell. When that happens it "retires" the pane, then waits for a hook that proves a new agent has taken it over. It only knew how to recognize Claude saying "n | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +208/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15695 fix(agent-hooks): restore Cursor launch tokens and new-turn restart (STA-3487) | Brennan Benson Core team · MEMBER | #12686 [Bug]: Some Cursor panes remain Working despite completed stop hooks Fixes · OPEN #15658 Title unavailable Unclear · Unknown #15674 Title unavailable Unclear · Unknown #15665 Title unavailable Unclear · Unknown #15714 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +442/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore Cursor workspace metadata1 PR · Standalone · Plugins#
Problem: restore Cursor workspace metadata.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14582 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14482 fix(ai-vault): restore Cursor workspace metadata | WIll Liu Community · FIRST_TIME_CONTRIBUTOR | #14582 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Restore Cursor CLI session workspace metadata by joining transcript session IDs with `.cursor/chats/*/*/meta.json`. - Populate `cwd`, creation/update timestamps, and the workspace-aware resume command so wor | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +407/−67. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore gated PTY buffer on hidden-to-visible reveal1 PR · Standalone · Plugins#
Problem: restore gated PTY buffer on hidden-to-visible reveal.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11726 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15689 fix(terminal): restore gated PTY buffer on hidden-to-visible reveal | Brennan Benson Core team · MEMBER | #11726 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +365/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore lossy initial remote snapshots1 PR · Standalone · Plugins#
Problem: restore lossy initial remote snapshots.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17113 fix(terminal): restore lossy initial remote snapshots | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +651/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore sessions after restart via OpenCode-family hooks1 PR · Standalone · Plugins#
Problem: restore sessions after restart via OpenCode-family hooks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13626 Title unavailable (Unclear, Unknown); #6909 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13990 fix(kilo): restore sessions after restart via OpenCode-family hooks | OrcaWin Unknown · COLLABORATOR | #13626 Title unavailable Unclear · Unknown #6909 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Add first-class Kilo session resume so cold restore after Orca/laptop restart relaunches with `kilo --session <id>` instead of leaving a plain shell. - Install an OpenCode-family status plugin on Kilo launch | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +397/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore terminal input when reopening worktrees1 PR · Standalone · Plugins#
Problem: restore terminal input when reopening worktrees.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16239 fix(mobile): restore terminal input when reopening worktrees | Shahar Mor Community · CONTRIBUTOR | None found | Standalone change | ## ELI5 Returning to a worktree on iPhone no longer leaves its terminal zoomed out with a keyboard that cannot send input. The terminal now waits for the identity already attached to its live host connection instead of r | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +89/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore the shell icon after an agent exits2 PRs · Overlapping · Automated release pipeline#
Problem: restore the shell icon after an agent exits.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #13749 [Bug]: Completed agent icon remains after the pane returns to shell (Fixes, OPEN); #15665 Title unavailable (Unclear, Unknown); #15658 Title unavailable (Unclear, Unknown); #15695 Title unavailable (Unclear, Unknown); #15679 Title unavailable (Unclear, Unknown); #15713 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13776 fix(terminal): restore the shell icon after an agent exits | Hansss Community · CONTRIBUTOR | #13749 [Bug]: Completed agent icon remains after the pane returns to shell Fixes · OPEN | Cluster contribution | ## Summary - Restore the terminal icon after a completed agent exits to the shell. - Clear resumable **sleeping identity** only after fresh foreground-process confirmation. - Resolve legacy numeric pane keys while preser | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +272/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15711 fix(terminal): retire tab icon after confirmed shell return (STA-3867) | Brennan Benson Core team · MEMBER | #13749 [Bug]: Completed agent icon remains after the pane returns to shell Fixes · OPEN #15665 Title unavailable Unclear · Unknown #15658 Title unavailable Unclear · Unknown #15695 Title unavailable Unclear · Unknown #15679 Title unavailable Unclear · Unknown #15713 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +371/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resume OMP sessions after worktree sleep1 PR · Standalone · Plugins#
Problem: resume OMP sessions after worktree sleep.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16276 fix(agent-resume): resume OMP sessions after worktree sleep | LiuSir Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Sleeping a worktree used to bring Claude back with `--resume`. OMP (and other Pi-compatible TUI agents) woke into a blank shell instead. After this change, Orca types `--resume` into the restored shell, using the | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +497/−123. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resume quiet Claude sessions instead of restoring bare shells1 PR · Standalone · Plugins#
Problem: resume quiet Claude sessions instead of restoring bare shells.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11160 [Bug]: Manual Sleep kills stale Claude sessions but wake restores only bare shells (Fixes, OPEN); #12214 Title unavailable (Unclear, Unknown); #12101 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15701 fix(sleep): resume quiet Claude sessions instead of restoring bare shells | Brennan Benson Core team · MEMBER | #11160 [Bug]: Manual Sleep kills stale Claude sessions but wake restores only bare shells Fixes · OPEN #12214 Title unavailable Unclear · Unknown #12101 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +700/−74. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resync the file tree after a watch subscription gap1 PR · Standalone · Plugins#
Problem: resync the file tree after a watch subscription gap.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #10902 [Bug]: Worktree file explorer panel doesn't auto-refresh after agent creates files (Fixes, OPEN); #10392 Title unavailable (Unclear, Unknown); #14802 Title unavailable (Unclear, Unknown); #10264 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15702 fix(explorer): resync the file tree after a watch subscription gap | Brennan Benson Core team · MEMBER | #10902 [Bug]: Worktree file explorer panel doesn't auto-refresh after agent creates files Fixes · OPEN #10392 Title unavailable Unclear · Unknown #14802 Title unavailable Unclear · Unknown #10264 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +142/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Retain restored agents in worktree inventory after restart1 PR · Standalone · Plugins#
Problem: Retain restored agents in worktree inventory after restart.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16156 Retain restored agents in worktree inventory after restart | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 14 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk32 files, +3221/−244. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retain sleeping agent records until resume spawns1 PR · Standalone · Plugins#
Problem: retain sleeping agent records until resume spawns.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16682 Title unavailable (Unclear, Unknown); #16750 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16279 fix(terminal): retain sleeping agent records until resume spawns | Brennan Benson Core team · MEMBER | #16682 Title unavailable Unclear · Unknown #16750 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +316/−41. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire a created pool name whatever the client claims (STA-4471)1 PR · Standalone · Plugins#
Problem: retire a created pool name whatever the client claims (STA-4471).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14350 Title unavailable (Unclear, Unknown); #14917 Title unavailable (Unclear, Unknown); #14924 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14919 fix(worktrees): retire a created pool name whatever the client claims (STA-4471) | Brennan Benson Core team · MEMBER | #14350 Title unavailable Unclear · Unknown #14917 Title unavailable Unclear · Unknown #14924 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +444/−83. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire agent resume records past an absolute age1 PR · Standalone · Plugins#
Problem: retire agent resume records past an absolute age.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14534 Title unavailable (Unclear, Unknown); #14228 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16845 fix(resume): retire agent resume records past an absolute age | qevan Community · FIRST_TIME_CONTRIBUTOR | #14534 Title unavailable Unclear · Unknown #14228 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca remembers "this pane had an agent running" so it can bring the session back later. That memory currently has no expiry date. If an agent ends in a way Orca cannot observe — killed, force quit, machine reboot | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +338/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire empty previous-generation daemons after protocol bumps1 PR · Standalone · Plugins#
Problem: retire empty previous-generation daemons after protocol bumps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9138 Title unavailable (Unclear, Unknown); #13063 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15670 fix(daemon): retire empty previous-generation daemons after protocol bumps | Brennan Benson Core team · MEMBER | #9138 Title unavailable Unclear · Unknown #13063 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +277/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire optimistic echoes the agent absorbed as a continuation1 PR · Standalone · Plugins#
Problem: retire optimistic echoes the agent absorbed as a continuation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15288 [Bug]: A native-chat send ending in \ leaves a queued bubble stranded below later turns (Fixes, OPEN); #15032 Title unavailable (Unclear, Unknown); #13513 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15283 fix(native-chat): retire optimistic echoes the agent absorbed as a continuation | grboy6770 Community · CONTRIBUTOR | #15288 [Bug]: A native-chat send ending in \ leaves a queued bubble stranded below later turns Fixes · OPEN #15032 Title unavailable Unclear · Unknown #13513 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If you finish a message with a backslash and press Enter, the agent does not send it — it treats the backslash as "give me another line" and waits. Your text stays in its input box. When you type the rest and pre | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +205/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire orphaned relays during version GC instead of skipping them2 PRs · Competing · Automated release pipeline#
Problem: retire orphaned relays during version GC instead of skipping them.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Competing. Linked issues: #13614 [Bug]: Relay upgrade orphans the previous relay and its PTYs — remote/SSH terminals are interrupted despite the update saying they won't be (Fixes, OPEN); #9819 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Choose one implementation after a product and technical comparison; do not land alternatives together.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Not until one implementation is chosen.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Product and technical decision required.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15636 fix(ssh): retire orphaned relays during version GC instead of skipping them | Eric Tong Community · FIRST_TIME_CONTRIBUTOR | #13614 [Bug]: Relay upgrade orphans the previous relay and its PTYs — remote/SSH terminals are interrupted despite the update saying they won't be Fixes · OPEN | Alternative implementation | Fixes #13614 (expected behaviour #2: "Reap the old relay after migration"). ## Problem Each relay build lives in its own content-hashed directory with its own socket path, so when Orca upgrades, the new daemon can never | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +300/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15691 fix(ssh): preserve relay sessions across build updates | PeaceTis Community · FIRST_TIME_CONTRIBUTOR | #13614 [Bug]: Relay upgrade orphans the previous relay and its PTYs — remote/SSH terminals are interrupted despite the update saying they won't be Fixes · OPEN #9819 Title unavailable Unclear · Unknown | Alternative implementation | ## ELI5 When Orca updates, an older SSH relay can still own open terminal sessions. Orca now reconnects to that exact relay build instead of making those terminals unreachable while their processes continue running. ## W | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +600/−38. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire resume state after confirmed agent exit2 PRs · Related · Automated release pipeline#
Problem: retire resume state after confirmed agent exit.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Related. Linked issues: #14228 [Bug]: Cleanly exited Claude session is auto-resumed with `claude --resume` after an app restart (local macOS, hibernation off) (Fixes, OPEN); #14376 Title unavailable (Unclear, Unknown); #15166 Title unavailable (Unclear, Unknown); #14534 Title unavailable (Unclear, Unknown); #16900 Title unavailable (Unclear, Unknown); #16908 Title unavailable (Unclear, Unknown); #16926 Title unavailable (Unclear, Unknown); #16932 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14534 fix(terminal): retire resume state after confirmed agent exit | erish Community · CONTRIBUTOR | #14228 [Bug]: Cleanly exited Claude session is auto-resumed with `claude --resume` after an app restart (local macOS, hibernation off) Fixes · OPEN #14376 Title unavailable Unclear · Unknown #15166 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When a user exits Claude normally and later closes its shell, Orca should not bring that finished agent back after an app restart. ## What Changed - Clear the resolved pane resume record when foreground-process e | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +74/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15666 fix(terminal): retire resume authority after a confirmed agent exit | Brennan Benson Core team · MEMBER | #14228 [Bug]: Cleanly exited Claude session is auto-resumed with `claude --resume` after an app restart (local macOS, hibernation off) Fixes · OPEN #14534 Title unavailable Unclear · Unknown #16900 Title unavailable Unclear · Unknown #16908 Title unavailable Unclear · Unknown #16926 Title unavailable Unclear · Unknown #16932 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 30 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk79 files, +2900/−386. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reuse rich-mode eligibility per render1 PR · Standalone · Plugins#
Problem: reuse rich-mode eligibility per render.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7056 Title unavailable (Unclear, Unknown); #17159 Title unavailable (Unclear, Unknown); #17147 Title unavailable (Unclear, Unknown); #17158 Title unavailable (Unclear, Unknown); #17162 Title unavailable (Unclear, Unknown); #17134 Title unavailable (Unclear, Unknown); #16595 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17219 perf(markdown): reuse rich-mode eligibility per render | Neil Core team · MEMBER | #7056 Title unavailable Unclear · Unknown #17159 Title unavailable Unclear · Unknown #17147 Title unavailable Unclear · Unknown #17158 Title unavailable Unclear · Unknown #17162 Title unavailable Unclear · Unknown #17134 Title unavailable Unclear · Unknown #16595 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +355/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reveal local worktrees even when a remote runtime is active1 PR · Standalone · Plugins#
Problem: reveal local worktrees even when a remote runtime is active.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16539 [Bug]: 'Reveal in Finder' misidentifies local worktree as remote project after switching worktrees (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16559 fix(explorer): reveal local worktrees even when a remote runtime is active | Wooseong Kim Community · CONTRIBUTOR | #16539 [Bug]: 'Reveal in Finder' misidentifies local worktree as remote project after switching worktrees Fixes · OPEN | Standalone change | ## Description Reveal in Finder / Open in file manager was treating local worktrees as remote after a paired host had been used, because the guard read the globally focused runtime instead of the target worktree host. Fi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +268/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2roll up cancelled checks as their own muted aggregate verdict2 PRs · Related · Plugins#
Problem: roll up cancelled checks as their own muted aggregate verdict.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Related. Linked issues: #15847 [Bug]: Cancelled PR checks are colored and labeled as failed in aggregate status UI (Fixes, OPEN); #4077 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15858 fix(checks): roll up cancelled checks as their own muted aggregate verdict | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15847 [Bug]: Cancelled PR checks are colored and labeled as failed in aggregate status UI Fixes · OPEN #4077 Title unavailable Unclear · Unknown | Cluster contribution | ## What Cancelled PR checks now roll up into their own **cancelled** aggregate verdict instead of being presented as failures. The left worktree sidebar says `PR checks: Cancelled` on the muted grey tone, the Tasks check | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +216/−28. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15901 fix(checks): distinguish cancelled checks from failures | Mir Community · FIRST_TIME_CONTRIBUTOR | #15847 [Bug]: Cancelled PR checks are colored and labeled as failed in aggregate status UI Fixes · OPEN | Cluster contribution | ## ELI5 A cancelled CI run is still not passing, but it is not the same as a broken test or build. Orca now keeps cancellation non-passing for merge safety while showing it as muted “Cancelled” instead of red “Failed”. # | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk86 files, +1734/−271. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route packaged CLI launches before Electron1 PR · Standalone · Plugins#
Problem: route packaged CLI launches before Electron.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13719 [Bug]: Linux AppImage 1.4.148 — every CLI subcommand (incl. --version) SIGSEGVs in uv_close(); GUI mode unaffected (Fixes, OPEN); #13136 Title unavailable (Unclear, Unknown); #13289 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14006 fix(linux): route packaged CLI launches before Electron | Jinwoo Hong Core team · MEMBER | #13719 [Bug]: Linux AppImage 1.4.148 — every CLI subcommand (incl. --version) SIGSEGVs in uv_close(); GUI mode unaffected Fixes · OPEN #13136 Title unavailable Unclear · Unknown #13289 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes https://github.com/stablyai/orca/issues/13719 Linear: https://linear.app/stably/issue/STA-3860 Packaged Linux now transfers recognized CLI-only invocations to the unpacked CLI entrypoint before Electron | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +456/−96. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route reminted pane keys to canonical identity (STA-3993)1 PR · Standalone · Plugins#
Problem: route reminted pane keys to canonical identity (STA-3993).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14018 [Bug]: OMP agent status stuck at "working" in sidebar after turn completes — panes whose ORCA_PANE_KEY is a reminted "$$<hash>:L$$" never reach the hook pipeline (Fixes, OPEN); #15658 Title unavailable (Unclear, Unknown); #15695 Title unavailable (Unclear, Unknown); #13890 Title unavailable (Unclear, Unknown); #15674 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15714 fix(agent-hooks): route reminted pane keys to canonical identity (STA-3993) | Brennan Benson Core team · MEMBER | #14018 [Bug]: OMP agent status stuck at "working" in sidebar after turn completes — panes whose ORCA_PANE_KEY is a reminted "$$<hash>:L$$" never reach the hook pipeline Fixes · OPEN #15658 Title unavailable Unclear · Unknown #15695 Title unavailable Unclear · Unknown #13890 Title unavailable Unclear · Unknown #15674 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +515/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route self-hosted hosts through GITLAB_HOST for mr/issue commands1 PR · Standalone · Plugins#
Problem: route self-hosted hosts through GITLAB_HOST for mr/issue commands.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12193 [Bug]: GitLab MR merge passes unsupported --hostname to glab in SSH workspaces (Fixes, OPEN); #12556 [Bug]: GitLab MR creation and issue field edits pass unsupported --hostname to glab in SSH workspaces (Fixes, OPEN); #14704 Title unavailable (Unclear, Unknown); #14728 Title unavailable (Unclear, Unknown); #14447 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12310 fix(gitlab): route self-hosted hosts through GITLAB_HOST for mr/issue commands | makoto-developer Community · CONTRIBUTOR | #12193 [Bug]: GitLab MR merge passes unsupported --hostname to glab in SSH workspaces Fixes · OPEN #12556 [Bug]: GitLab MR creation and issue field edits pass unsupported --hostname to glab in SSH workspaces Fixes · OPEN #14704 Title unavailable Unclear · Unknown #14728 Title unavailable Unclear · Unknown #14447 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes #12193, fixes #12556 — GitLab write actions from a repository opened as an SSH-hosted workspace fail before Orca ever reaches GitLab: ``` glab mr merge 6 -R example-group/example-project --yes --hostname | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +265/−65. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route the status-bar popover scan to the workspace's host1 PR · Standalone · Plugins#
Problem: route the status-bar popover scan to the workspace's host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17046 [Bug]: Opening the Ports status-bar popover clears remote workspace ports on a paired runtime (Fixes, OPEN); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17048 fix(ports): route the status-bar popover scan to the workspace's host | iverJisty Community · FIRST_TIME_CONTRIBUTOR | #17046 [Bug]: Opening the Ports status-bar popover clears remote workspace ports on a paired runtime Fixes · OPEN #39 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca's status bar has a plug icon that counts the dev servers you have running. A background poll keeps that number fresh by asking every machine you use — your own computer and each paired remote Orca server — a | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +654/−55. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route zoom gestures to PDF viewer1 PR · Standalone · Plugins#
Problem: route zoom gestures to PDF viewer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17241 fix(editor): route zoom gestures to PDF viewer | Infinity_X Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 Zoom gestures and shortcuts now zoom the PDF itself instead of changing Orca’s editor font size. ## What Changed - Added cursor-centered Ctrl+scroll and trackpad-pinch zoom to the PDF viewer. - Added Command+scro | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +378/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2runtime-owned evidence for completion, gates, leases and worker identity1 PR · Standalone · Plugins#
Problem: runtime-owned evidence for completion, gates, leases and worker identity.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17038 fix(control-plane): runtime-owned evidence for completion, gates, leases and worker identity | SCL Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Package B — Orca Control Plane Every defect this package closes has one shape: **a caller-declared CLAIM was being read as runtime-owned EVIDENCE.** Each change moves the proof to the runtime. Head `de157d5` · base `o | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk238 files, +33892/−931. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Saving and editing files now works in a per-workspace environment1 PR · Standalone · Plugins#
Problem: Saving and editing files now works in a per-workspace environment.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11762 [Bug] File editing fails when using per-workspace environment (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12221 Saving and editing files now works in a per-workspace environment | Neil Core team · MEMBER | #11762 [Bug] File editing fails when using per-workspace environment Fixes · OPEN | Standalone change | ## Summary A per-workspace environment recipe that returns `connection.type: "ssh"` registers a **runtime-owned** SSH target id `runtime-ssh-<runtimeId>` (`src/main/ssh/ssh-connection-store.ts:55`, `src/main/ephemeral-vm | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +622/−47. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2say when empty check still has sibling-run unread1 PR · Standalone · Plugins#
Problem: say when empty check still has sibling-run unread.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13696 orchestration: check returns wrong empty success while product claims pending mail (cross-run unread + consumer_fenced) (Fixes, OPEN); #14979 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14751 fix(orchestration): say when empty check still has sibling-run unread | 686f6c61 Community · FIRST_TIME_CONTRIBUTOR | #13696 orchestration: check returns wrong empty success while product claims pending mail (cross-run unread + consumer_fenced) Fixes · OPEN #14979 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You finish one orchestration run, start another in the same terminal, and `orca orchestration check` says "nothing to do." The inbox still has unread mail from the old run. This makes `check` say so, instead of r | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +223/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2say why the runtime is unreachable instead of reporting "starting"1 PR · Standalone · Plugins#
Problem: say why the runtime is unreachable instead of reporting "starting".
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17164 fix(cli): say why the runtime is unreachable instead of reporting "starting" | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +811/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scale interactive-redraw windows by measured echo latency1 PR · Standalone · Plugins#
Problem: scale interactive-redraw windows by measured echo latency.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16265 [Bug]: Interactive-redraw windows are local-calibrated, so remote typing loses latency-sensitive classification above ~150ms RTT (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16268 fix(terminal): scale interactive-redraw windows by measured echo latency | gatsby74 Community · CONTRIBUTOR | #16265 [Bug]: Interactive-redraw windows are local-calibrated, so remote typing loses latency-sensitive classification above ~150ms RTT Fixes · OPEN | Standalone change | ## ELI5 When you type in a terminal, Orca tries to notice "the user is typing right now, paint immediately" and puts that output in a fast lane. It decides this with a stopwatch started the moment your keystroke is sent: | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +213/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scan SSH hosts owned by a paired runtime1 PR · Standalone · Plugins#
Problem: scan SSH hosts owned by a paired runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14171 fix(ai-vault): scan SSH hosts owned by a paired runtime | Brennan Benson Core team · MEMBER | None found | Standalone change | ## ELI5 When your laptop is paired to a always-on HUB (`orca serve`) that holds the SSH connections, Agent Session History can now ask that HUB to list sessions on those SSH machines. Before this, the HUB RPC could only | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +2329/−234. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scope optimistic echoes to the conversation they were sent into1 PR · Standalone · Plugins#
Problem: scope optimistic echoes to the conversation they were sent into.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11509 Title unavailable (Unclear, Unknown); #13513 Title unavailable (Unclear, Unknown); #11519 Title unavailable (Unclear, Unknown); #10102 Title unavailable (Unclear, Unknown); #10639 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15032 fix(native-chat): scope optimistic echoes to the conversation they were sent into | Brennan Benson Core team · MEMBER | #11509 Title unavailable Unclear · Unknown #13513 Title unavailable Unclear · Unknown #11519 Title unavailable Unclear · Unknown #10102 Title unavailable Unclear · Unknown #10639 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +732/−85. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2seed list preview from daemon snapshots after restart (STA-4326)1 PR · Standalone · Plugins#
Problem: seed list preview from daemon snapshots after restart (STA-4326).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14523 [Bug]: terminal list previews/activity are stale in both directions — only terminal read shows the truth (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15679 fix(terminal): seed list preview from daemon snapshots after restart (STA-4326) | Brennan Benson Core team · MEMBER | #14523 [Bug]: terminal list previews/activity are stale in both directions — only terminal read shows the truth Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +337/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2send a multi-line composer message as one paste1 PR · Standalone · Plugins#
Problem: send a multi-line composer message as one paste.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15205 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15206 fix(mobile-native-chat): send a multi-line composer message as one paste | Brennan Benson Core team · MEMBER | #15205 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +1133/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2send multi-line agent prompts from the launch paths as one paste1 PR · Standalone · Plugins#
Problem: send multi-line agent prompts from the launch paths as one paste.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15205 fix(mobile): send multi-line agent prompts from the launch paths as one pasteDraft | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +104/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2send the caller handle from dispatch-show1 PR · Standalone · Plugins#
Problem: send the caller handle from dispatch-show.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15952 [Other]: dispatch-show reaches the runtime with no caller identity, so Run-scoped enforcement cannot attach (Fixes, OPEN); #14898 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15965 fix(cli): send the caller handle from dispatch-show | Tauri-EPO Community · CONTRIBUTOR | #15952 [Other]: dispatch-show reaches the runtime with no caller identity, so Run-scoped enforcement cannot attach Fixes · OPEN #14898 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 `dispatch-show` never tells the runtime who is asking. That means any future rule of the form *"you may only inspect dispatches belonging to your own Run"* cannot work when the command is run from the CLI, howeve | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +273/−38. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2separate image attachment paths from following prompt text (STA-4847)1 PR · Standalone · Plugins#
Problem: separate image attachment paths from following prompt text (STA-4847).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15820 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15690 fix(mobile): separate image attachment paths from following prompt text (STA-4847) | Brennan Benson Core team · MEMBER | #15820 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +232/−100. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2separate session backfill baseline from launch updates1 PR · Standalone · Plugins#
Problem: separate session backfill baseline from launch updates.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16251 [Bug]: [Windows] Orca Codex session backfill re-scans full history on launch and can stall the app (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16252 fix(codex): separate session backfill baseline from launch updates | rumoii Community · FIRST_TIME_CONTRIBUTOR | #16251 [Bug]: [Windows] Orca Codex session backfill re-scans full history on launch and can stall the app Fixes · OPEN | Standalone change | ## ELI5 Orca copies Codex session history into its managed Home. Previously, a new Codex launch could make that historical copy look unfinished again, so Orca might revisit the entire history while the user was trying to | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1070/−160. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2serve favicon.ico and favicon.png from headless orca serve1 PR · Standalone · Plugins#
Problem: serve favicon.ico and favicon.png from headless orca serve.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14057 feat(serve): serve favicon.ico and favicon.png from headless orca serve | Aarav Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Allowlist `/favicon.ico` and `/favicon.png` in `static-web-client-handler.ts` with `image/x-icon` and `image/png` MIME so the bundled web client has a recognizable tab/bookmark icon. - Add `<link rel="icon" | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +71/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2set push.autoSetupRemote when claiming an existing local branch (#15645)1 PR · Standalone · Plugins#
Problem: set push.autoSetupRemote when claiming an existing local branch (#15645).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15645 Title unavailable (Unclear, Unknown); #15331 Title unavailable (Unclear, Unknown); #15868 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15796 fix: set push.autoSetupRemote when claiming an existing local branch (#15645)Draft | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15645 Title unavailable Unclear · Unknown #15331 Title unavailable Unclear · Unknown #15868 Title unavailable Unclear · Unknown | Standalone change | Fixes half of #15645 — the missing-upstream symptom. ## Root cause `performAddWorktree` has two branch-creation paths: a new-branch path (`--no-track -b`) and a claim-existing-branch path (`options.checkoutExistingBranch | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +737/−88. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2settle CLI prompts for cursor-agent1 PR · Standalone · Plugins#
Problem: settle CLI prompts for cursor-agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14525 terminal send --text --enter often leaves the message unsubmitted in TUI composers (codex / cursor-agent) — race between paste and Enter (Fixes, CLOSED); #14608 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14851 fix(terminal): settle CLI prompts for cursor-agent | Tauri-EPO Community · CONTRIBUTOR | #14525 terminal send --text --enter often leaves the message unsubmitted in TUI composers (codex / cursor-agent) — race between paste and Enter Fixes · CLOSED #14608 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 `orca terminal send --text … --enter` already waits for Claude and Codex composers to finish rendering before pressing Enter. After #14608, cursor-agent still used the old short delay, so long prompts could sit u | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +101/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2settle OMP status from agent-end contract3 PRs · Overlapping · Plugins#
Problem: settle OMP status from agent-end contract.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #14879 [Bug]: omp agnet active indicator (Fixes, CLOSED); #14278 Title unavailable (Unclear, Unknown); #14884 Title unavailable (Unclear, Unknown); #14018 Title unavailable (Unclear, Unknown); #13890 Title unavailable (Unclear, Unknown); #14605 Title unavailable (Unclear, Unknown); #15713 Title unavailable (Unclear, Unknown); #15711 Title unavailable (Unclear, Unknown); #15666 Title unavailable (Unclear, Unknown); #15658 Title unavailable (Unclear, Unknown); #17077 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14884 fix(pi): settle OMP status from agent-end contract | BingZ Community · CONTRIBUTOR | #14879 [Bug]: omp agnet active indicator Fixes · CLOSED | Cluster contribution | ## ELI5 OMP can emit `agent_end` both when a turn is truly finished and when it has already scheduled an automatic retry or continuation. Orca was guessing from `ctx.isIdle()`, which can remain false and leave the tab pe | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +48/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15658 fix(pi): settle OMP status from the agent-end contract | Brennan Benson Core team · MEMBER | #14879 [Bug]: omp agnet active indicator Fixes · CLOSED #14278 Title unavailable Unclear · Unknown #14884 Title unavailable Unclear · Unknown #14018 Title unavailable Unclear · Unknown #13890 Title unavailable Unclear · Unknown #14605 Title unavailable Unclear · Unknown #15713 Title unavailable Unclear · Unknown #15711 Title unavailable Unclear · Unknown #15666 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 14 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +1528/−218. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17209 fix(pi): settle OMP status from the agent_end contract | Brennan Benson Core team · MEMBER | #14278 Title unavailable Unclear · Unknown #15658 Title unavailable Unclear · Unknown #17077 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +294/−192. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2share Git fixture command1 PR · Standalone · Plugins#
Problem: share Git fixture command.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16155 refactor(e2e): share Git fixture command | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +13/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show Codex's effective model in the session picker (STA-4317)1 PR · Standalone · Plugins#
Problem: show Codex's effective model in the session picker (STA-4317).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14503 [Bug]: Orca UI and TUI show different models for the same session (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15688 fix(native-chat): show Codex's effective model in the session picker (STA-4317) | Brennan Benson Core team · MEMBER | #14503 [Bug]: Orca UI and TUI show different models for the same session Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +421/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Show remote host failure details in a submenu1 PR · Standalone · Plugins#
Problem: Show remote host failure details in a submenu.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17062 Show remote host failure details in a submenu | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +269/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show resumed sessions in the worktree sidebar before the first prompt1 PR · Standalone · Plugins#
Problem: show resumed sessions in the worktree sidebar before the first prompt.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15096 [Bug]: Resumed Codex sessions stay hidden under the worktree until the first prompt (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15097 fix(codex): show resumed sessions in the worktree sidebar before the first prompt | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #15096 [Bug]: Resumed Codex sessions stay hidden under the worktree until the first prompt Fixes · OPEN | Standalone change | ## ELI5 If you resume a Codex chat in Orca, the session is running, but it does not show up under the worktree on the left until you type something. This makes Orca notice the idle Codex window from its title (and from S | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +172/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show SSH labels in Run on picker1 PR · Standalone · Plugins#
Problem: show SSH labels in Run on picker.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16114 [Bug]: Mobile Run on picker shows internal SSH target id (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16115 fix(mobile): show SSH labels in Run on picker | GhostFlying Community · FIRST_TIME_CONTRIBUTOR | #16114 [Bug]: Mobile Run on picker shows internal SSH target id Fixes · OPEN | Standalone change | ## ELI5 Mobile now shows the recognizable SSH name from the user's SSH configuration in the Create Workspace `Run on` picker, matching desktop, instead of exposing Orca's generated target ID. ## What Changed - Load the h | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +123/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show the Active Server's usage in the rate-limit badges2 PRs · Overlapping · Automated release pipeline#
Problem: show the Active Server's usage in the rate-limit badges.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #15798 Usage / rate-limit badges are not environment-aware: `rateLimits.refresh*ForTarget` only accepts `host` / `wsl`, so a client with a remote Active Server shows local usage (Fixes, OPEN); #15880 Title unavailable (Unclear, Unknown); #15804 Title unavailable (Unclear, Unknown); #1467 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15804 fix(status-bar): show the Active Server's usage in the rate-limit badges | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15798 Usage / rate-limit badges are not environment-aware: `rateLimits.refresh*ForTarget` only accepts `host` / `wsl`, so a client with a remote Active Server shows local usage Fixes · OPEN #15880 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary **What** When a remote Active Server owns provider accounts (`hasRemoteProviderAccountOwner`), the status-bar usage badges now render the **server's** `RateLimitState` — taken from the provider-accounts snapsh | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +152/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15880 fix(status-bar): source rate-limit badges from the Active Server that owns usageDraft | Neil Core team · MEMBER | #15798 Usage / rate-limit badges are not environment-aware: `rateLimits.refresh*ForTarget` only accepts `host` / `wsl`, so a client with a remote Active Server shows local usage Fixes · OPEN #15804 Title unavailable Unclear · Unknown #1467 Title unavailable Unclear · Unknown | Cluster contribution | > ## 🛑 HELD — do not merge > > Held by maintainer decision (2026-08-22). CI is green and the branch merges clean; this is **not** a technical blocker. > Converted to draft and labelled `wip` so it cannot be merged by ac | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +1073/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show the cursor while a CJK preedit covers its cell3 PRs · Overlapping · Plugins#
Problem: show the cursor while a CJK preedit covers its cell.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #16949 [Bug]: No cursor is visible while a CJK syllable composes in a terminal pane (Fixes, OPEN); #17104 [Bug]: Korean IME preedit repeats the Codex placeholder on first input (Fixes, OPEN); #12545 Title unavailable (Unclear, Unknown); #17172 Title unavailable (Unclear, Unknown); #17178 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16951 fix(terminal): show the cursor while a CJK preedit covers its cell | klaatus Community · FIRST_TIME_CONTRIBUTOR | #16949 [Bug]: No cursor is visible while a CJK syllable composes in a terminal pane Fixes · OPEN | Cluster contribution | ## ELI5 While you are typing a Korean syllable in a terminal, the cursor used to vanish — it came back only when you finished the syllable, or when you clicked away. It was never gone, just hidden underneath the little b | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +292/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17105 Fix Korean IME composition over dim terminal placeholdersDraft | park sangjin Community · FIRST_TIME_CONTRIBUTOR | #17104 [Bug]: Korean IME preedit repeats the Codex placeholder on first input Fixes · OPEN #12545 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When Korean input is still being composed, Codex has not received it yet and cannot clear its initial hint. Orca was drawing that hint again after the composing syllable. This keeps the hint covered until the IME | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +248/−105. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #17170 fix(terminal): render the IME caret and mask dim placeholders | Neil Core team · MEMBER | #16949 [Bug]: No cursor is visible while a CJK syllable composes in a terminal pane Fixes · OPEN #17104 [Bug]: Korean IME preedit repeats the Codex placeholder on first input Fixes · OPEN #17172 Title unavailable Unclear · Unknown #17178 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 While an IME character is being assembled, Orca now draws a visible caret after it, keeps that caret on-screen at the final terminal cell, and hides placeholder ghost text without hiding ordinary terminal content | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +690/−201. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show unlimited Business usage1 PR · Standalone · Plugins#
Problem: show unlimited Business usage.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15764 Codex Business unlimited usage shows refresh failure (Fixes, OPEN); #15737 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16323 fix(codex): show unlimited Business usage | Hyeon-Gi Jeon Community · FIRST_TIME_CONTRIBUTOR | #15764 Codex Business unlimited usage shows refresh failure Fixes · OPEN #15737 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Codex Business accounts can report unlimited usage. Orca now shows `Unlimited` instead of treating missing percentage windows as a refresh failure. ## What Changed - Map plan and unlimited-usage metadata from app | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +342/−38. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2size issue list columns by panel width, not viewport1 PR · Standalone · Plugins#
Problem: size issue list columns by panel width, not viewport.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16625 [Bug]: Jira issue list columns crush the Issue title when the task panel is narrow (portrait screen) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16627 fix(jira): size issue list columns by panel width, not viewport | Leopold T Community · FIRST_TIME_CONTRIBUTOR | #16625 [Bug]: Jira issue list columns crush the Issue title when the task panel is narrow (portrait screen) Fixes · OPEN | Standalone change | ## ELI5 On a portrait screen the Jira task list squeezed the issue title down to a few characters because it was choosing its column widths based on how wide the *window* is, not how wide the *panel* is. It now measures | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +17/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2size the Windows launcher-compile test budget from measurement1 PR · Standalone · Plugins#
Problem: size the Windows launcher-compile test budget from measurement.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16900 Title unavailable (Unclear, Unknown); #16904 Title unavailable (Unclear, Unknown); #16915 Title unavailable (Unclear, Unknown); #16955 Title unavailable (Unclear, Unknown); #16979 Title unavailable (Unclear, Unknown); #17014 Title unavailable (Unclear, Unknown); #17085 Title unavailable (Unclear, Unknown); #8897 Title unavailable (Unclear, Unknown); #8909 Title unavailable (Unclear, Unknown); #17086 Title unavailable (Unclear, Unknown); #17088 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17116 fix(ci): size the Windows launcher-compile test budget from measurement | Brennan Benson Core team · MEMBER | #16900 Title unavailable Unclear · Unknown #16904 Title unavailable Unclear · Unknown #16915 Title unavailable Unclear · Unknown #16955 Title unavailable Unclear · Unknown #16979 Title unavailable Unclear · Unknown #17014 Title unavailable Unclear · Unknown #17085 Title unavailable Unclear · Unknown #8897 Title unavailable Unclear · Unknown #8909 Title unavailable Unclear · Unknown #17086 Title unavailable Unclear · Unknown #17088 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +11/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2skip Devin first-run workspace trust prompt1 PR · Standalone · Plugins#
Problem: skip Devin first-run workspace trust prompt.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15859 [Bug]: Devin exits on first-run workspace trust prompt when creating an agent in Orca (Fixes, OPEN); #11765 Title unavailable (Unclear, Unknown); #10666 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15860 fix(agents): skip Devin first-run workspace trust prompt | Dzmitry Bachko Community · CONTRIBUTOR | #15859 [Bug]: Devin exits on first-run workspace trust prompt when creating an agent in Orca Fixes · OPEN #11765 Title unavailable Unclear · Unknown #10666 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Creating a Devin agent in Orca was dying immediately. Devin asks "do you trust this folder?" with a numbered menu, and Orca's first keystrokes into the terminal were answering **No, exit**. This change tells Devi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +46/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2skip disabled diagnostic serialization1 PR · Standalone · Plugins#
Problem: skip disabled diagnostic serialization.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17176 perf(startup): skip disabled diagnostic serialization | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +86/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2skip missing Windows repo worktree spawns1 PR · Standalone · Plugins#
Problem: skip missing Windows repo worktree spawns.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13950 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17091 fix(git): skip missing Windows repo worktree spawns | jimmylee-cell Community · FIRST_TIME_CONTRIBUTOR | #13950 Title unavailable Unclear · Unknown | Standalone change | ## Summary - preflight native Windows drive-letter repo paths before running git worktree list - follow valid directory symlinks and junctions with stat - leave WSL, SSH, POSIX, and valid repo routing unchanged ## Eviden | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +57/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2skip unchanged cache rewrites1 PR · Standalone · Plugins#
Problem: skip unchanged cache rewrites.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16211 Title unavailable (Unclear, Unknown); #16219 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16220 perf(usage): skip unchanged cache rewrites | 叁笙早安 AI Community · FIRST_TIME_CONTRIBUTOR | #16211 Title unavailable Unclear · Unknown #16219 Title unavailable Unclear · Unknown | Standalone change | ## Summary - let each built-in usage scanner report whether any per-source projection was reparsed, added, removed, or reclaimed - skip the durable cache snapshot when all source projections were reused unchanged - still | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +73/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2spin the dot for an agent the user started by hand1 PR · Standalone · Plugins#
Problem: spin the dot for an agent the user started by hand.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15776 [Bug]: workspace dot shows Active while Claude is working, unless the session title happens to say "claude" (Fixes, OPEN); #9647 Title unavailable (Unclear, Unknown); #13925 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15777 fix(sidebar): spin the dot for an agent the user started by hand | Ramzi Community · CONTRIBUTOR | #15776 [Bug]: workspace dot shows Active while Claude is working, unless the session title happens to say "claude" Fixes · OPEN #9647 Title unavailable Unclear · Unknown #13925 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The sidebar dot only knew a Claude was working if Claude's own auto-generated session title happened to contain the word "claude". Now it asks the process table instead, which always knows. ## What Changed `title | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +331/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split relay Git handler responsibilities1 PR · Standalone · Plugins#
Problem: Split relay Git handler responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17215 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17217 Split relay Git handler responsibilities | Neil Core team · MEMBER | #17215 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +1623/−1407. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split runtime file client layers1 PR · Standalone · Plugins#
Problem: Split runtime file client layers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17181 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17188 Split runtime file client layers | Neil Core team · MEMBER | #17181 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 12 | $\co | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1619/−1519. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split Settings page responsibilities1 PR · Standalone · Plugins#
Problem: Split Settings page responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17270 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17271 Split Settings page responsibilities | Neil Core team · MEMBER | #17270 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +2563/−1927. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split speech session lifecycle1 PR · Standalone · Plugins#
Problem: Split speech session lifecycle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17123 Split speech session lifecycle | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 6 | $\col | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +527/−450. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stabilize E2E tests and document scheduled CI failures1 PR · Standalone · Plugins#
Problem: stabilize E2E tests and document scheduled CI failures.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16430 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16721 fix: stabilize E2E tests and document scheduled CI failures | Jinjing Core team · MEMBER | #16430 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +194/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2standardize Simplified Chinese product terminology1 PR · Standalone · Plugins#
Problem: standardize Simplified Chinese product terminology.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #8923 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15464 fix(i18n): standardize Simplified Chinese product terminologyDraft | ansonlotiniat Community · FIRST_TIME_CONTRIBUTOR | #8923 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca used several different Chinese words for the same core product concepts. This standardizes the existing Simplified Chinese UI glossary without adding a locale or changing the localization architecture. ## Wh | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +238/−100. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2start an agent with a prompt at workspace creation1 PR · Standalone · Plugins#
Problem: start an agent with a prompt at workspace creation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #7995 [Feature]: Start the agent immediately with a prompt entered at workspace creation (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15579 feat(workspace): start an agent with a prompt at workspace creationDraft | KyuJoo Han Community · CONTRIBUTOR | #7995 [Feature]: Start the agent immediately with a prompt entered at workspace creation Fixes · CLOSED | Standalone change | ## ELI5 Right now you can't tell Orca what to work on when you first create a workspace — you have to create it and then type your prompt. This lets you type the prompt (and optionally tick "Create & run") right in the N | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +159/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a failed delete showing Electron's IPC envelope1 PR · Standalone · Plugins#
Problem: stop a failed delete showing Electron's IPC envelope.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17237 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17230 fix(workspaces): stop a failed delete showing Electron's IPC envelope | Brennan Benson Core team · MEMBER | #17237 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +457/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop calling a readiness timeout a failed launch1 PR · Standalone · Plugins#
Problem: stop calling a readiness timeout a failed launch.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13653 Title unavailable (Unclear, Unknown); #13642 Title unavailable (Unclear, Unknown); #13661 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15268 fix(orchestration): stop calling a readiness timeout a failed launch | Taras Kornichuk Community · CONTRIBUTOR | #13653 Title unavailable Unclear · Unknown #13642 Title unavailable Unclear · Unknown #13661 Title unavailable Unclear · Unknown | Standalone change | A `worker-start` that times out at `agent_readiness` now reports `outcome_unknown` when the launched agent terminal is still running, instead of reporting `failed` for a lane whose agent is alive. Fixes the first half of | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +160/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop CLI commands from falling through to Chromium startup1 PR · Standalone · Plugins#
Problem: stop CLI commands from falling through to Chromium startup.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14229 Title unavailable (Unclear, Unknown); #13719 Title unavailable (Unclear, Unknown); #15081 Title unavailable (Unclear, Unknown); #11609 Title unavailable (Unclear, Unknown); #12530 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15083 fix(linux): stop CLI commands from falling through to Chromium startup | Neil Core team · MEMBER | #14229 Title unavailable Unclear · Unknown #13719 Title unavailable Unclear · Unknown #15081 Title unavailable Unclear · Unknown #11609 Title unavailable Unclear · Unknown #12530 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +634/−656. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop cutting a failed fetch/pull/push down to git's closing line1 PR · Standalone · Plugins#
Problem: stop cutting a failed fetch/pull/push down to git's closing line.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17275 fix(git): stop cutting a failed fetch/pull/push down to git's closing line | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +193/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop deleting a workspace after confirm when it turns out to be busy1 PR · Standalone · Plugins#
Problem: stop deleting a workspace after confirm when it turns out to be busy.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17024 Title unavailable (Unclear, Unknown); #17058 Title unavailable (Unclear, Unknown); #17044 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17074 fix(cleanup): stop deleting a workspace after confirm when it turns out to be busy | Brennan Benson Core team · MEMBER | #17024 Title unavailable Unclear · Unknown #17058 Title unavailable Unclear · Unknown #17044 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 14 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk28 files, +2637/−154. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Stop Escape interrupting the agent from a dashboard preview1 PR · Standalone · Plugins#
Problem: Stop Escape interrupting the agent from a dashboard preview.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16857 Stop Escape interrupting the agent from a dashboard preview | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | Escape in the Agent Dashboard preview was forwarded to the PTY as `\x1b`, so the agent read it as an interrupt. That is the wrong default for a glance surface. Escape is the key people press to back out of something they | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +100/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop leaking the Git credential guard into terminals Orca chose not to guard1 PR · Standalone · Plugins#
Problem: stop leaking the Git credential guard into terminals Orca chose not to guard.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16909 Title unavailable (Unclear, Unknown); #16915 Title unavailable (Unclear, Unknown); #17017 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17014 fix(terminal): stop leaking the Git credential guard into terminals Orca chose not to guard | Brennan Benson Core team · MEMBER | #16909 Title unavailable Unclear · Unknown #16915 Title unavailable Unclear · Unknown #17017 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1097/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop live output jumping off-screen1 PR · Standalone · Plugins#
Problem: stop live output jumping off-screen.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11638 [Bug]: scrolling chat on mobile (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16601 fix(mobile): stop live output jumping off-screen | baoer Community · FIRST_TIME_CONTRIBUTOR | #11638 [Bug]: scrolling chat on mobile Fixes · OPEN | Standalone change | ## ELI5 During a live agent response, the down-arrow could move the chat to the bottom without actually turning bottom-follow back on. The next streamed chunks could then push the newest output off-screen again. This cha | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +43/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop multi-host project-group headers from colliding2 PRs · Related · Automated release pipeline#
Problem: stop multi-host project-group headers from colliding.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Related. Linked issues: #12532 [Bug]: Project-group sidebar headers overlap and block clicks after expanding or collapsing a project (Fixes, OPEN); #13611 Title unavailable (Unclear, Unknown); #14112 Title unavailable (Unclear, Unknown); #14232 Title unavailable (Unclear, Unknown); #12300 [Bug]: Style collision across multiple host servers when collapsing/expanding a host server (Fixes, OPEN); #13947 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13599 fix(sidebar): stop multi-host project-group headers from colliding | Brennan Benson Core team · MEMBER | #12532 [Bug]: Project-group sidebar headers overlap and block clicks after expanding or collapsing a project Fixes · OPEN #13611 Title unavailable Unclear · Unknown #14112 Title unavailable Unclear · Unknown #14232 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk64 files, +5208/−646. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13611 fix(sidebar): stop multi-host header style collision on host collapse | Brennan Benson Core team · MEMBER | #12300 [Bug]: Style collision across multiple host servers when collapsing/expanding a host server Fixes · OPEN #12532 [Bug]: Project-group sidebar headers overlap and block clicks after expanding or collapsing a project Fixes · OPEN #13947 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +530/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop path resolution from creating ~/.claude1 PR · Standalone · Plugins#
Problem: stop path resolution from creating ~/.claude.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16257 fix(claude): stop path resolution from creating ~/.claude | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +153/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop path resolution from creating the config directory1 PR · Standalone · Plugins#
Problem: stop path resolution from creating the config directory.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12181 [Bug]: Orca creates ~/.claude during background usage refresh even when Claude is disabled (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12309 fix(claude-accounts): stop path resolution from creating the config directory | makoto-developer Community · CONTRIBUTOR | #12181 [Bug]: Orca creates ~/.claude during background usage refresh even when Claude is disabled Fixes · OPEN | Standalone change | ## Summary Fixes #12181 — Orca recreates `~/.claude` in the background even when Claude is disabled in `disabledTuiAgents`, there is no managed or active Claude account, and no Claude session has ever been launched. Dele | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review APPROVED | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: APPROVED. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +150/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop permission-denied runtimes reporting starting1 PR · Standalone · Plugins#
Problem: stop permission-denied runtimes reporting starting.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13539 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16697 fix(cli): stop permission-denied runtimes reporting starting | Brennan Benson Core team · MEMBER | #13539 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +177/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reading a missing worktree row as an empty tab list1 PR · Standalone · Plugins#
Problem: stop reading a missing worktree row as an empty tab list.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17223 test(e2e): stop reading a missing worktree row as an empty tab list | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +216/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop remote deletes from reappearing after path-spelling misses1 PR · Standalone · Plugins#
Problem: stop remote deletes from reappearing after path-spelling misses.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16753 [Bug]: Worktrees on a remote Mac reappear after deletion from a local Orca client (Fixes, OPEN); #16494 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16782 fix(worktrees): stop remote deletes from reappearing after path-spelling misses | Kaylee Community · CONTRIBUTOR | #16753 [Bug]: Worktrees on a remote Mac reappear after deletion from a local Orca client Fixes · OPEN #16494 Title unavailable Unclear · Unknown | Standalone change | Deleting a worktree on a remote Mac from a local Orca client could look like it worked, then the worktree came back because it was never actually removed. The client asked the host to delete one path spelling while Git o | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +170/−54. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reporting an unresumable delivery as a dead session1 PR · Standalone · Plugins#
Problem: stop reporting an unresumable delivery as a dead session.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14974 fix(ssh): stop reporting an unresumable delivery as a dead session | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 27 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk53 files, +3457/−330. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reporting Grok usage as 0% when the API omits the percent1 PR · Standalone · Plugins#
Problem: stop reporting Grok usage as 0% when the API omits the percent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15740 [Bug]: Grok usage always reports 0% when the billing API omits creditUsagePercent (Fixes, OPEN); #9214 Title unavailable (Unclear, Unknown); #9219 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15878 fix(rate-limits): stop reporting Grok usage as 0% when the API omits the percent | Neil Core team · MEMBER | #15740 [Bug]: Grok usage always reports 0% when the billing API omits creditUsagePercent Fixes · OPEN #9214 Title unavailable Unclear · Unknown #9219 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +258/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop runaway padding in serialized markdown tables1 PR · Standalone · Plugins#
Problem: stop runaway padding in serialized markdown tables.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13686 fix(editor): stop runaway padding in serialized markdown tables | Gimics Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary The rich markdown editor serializes tables through `@tiptap/extension-table`, whose serializer pads **every** column to the length of its longest cell. A single long cell therefore inflates every sibling cell | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +344/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop session scans stalling on stopped WSL distros1 PR · Standalone · Plugins#
Problem: stop session scans stalling on stopped WSL distros.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15453 [Bug]: Agent Session History scans stall for minutes and fail with "AI Vault service timed out after 130000ms" when a WSL distro is stopped (Fixes, CLOSED); #14924 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15475 fix(ai-vault): stop session scans stalling on stopped WSL distros | Suzano Community · FIRST_TIME_CONTRIBUTOR | #15453 [Bug]: Agent Session History scans stall for minutes and fail with "AI Vault service timed out after 130000ms" when a WSL distro is stopped Fixes · CLOSED #14924 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Agent Session History could get stuck loading forever and then fail with a timeout error, showing "0 shown" — because if you have WSL installed and one of your distros happens to be stopped, Orca was trying to re | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +957/−28. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop shadowing navigator.webdriver on the instance1 PR · Standalone · Plugins#
Problem: stop shadowing navigator.webdriver on the instance.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17196 fix(browser): stop shadowing navigator.webdriver on the instance | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +314/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop telling agents to detach worktree lineage1 PR · Standalone · Plugins#
Problem: stop telling agents to detach worktree lineage.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15461 docs(skills): stop telling agents to detach worktree lineage | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +75/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the pane error toast showing Electron's IPC envelope1 PR · Standalone · Plugins#
Problem: stop the pane error toast showing Electron's IPC envelope.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17237 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17255 fix(terminal): stop the pane error toast showing Electron's IPC envelope | Brennan Benson Core team · MEMBER | #17237 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +360/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the skill picker cap from erasing whole scopes1 PR · Standalone · Plugins#
Problem: stop the skill picker cap from erasing whole scopes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14690 [Bug]: Chat UI does not load all local and project skills (Fixes, OPEN); #16409 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16462 fix(native-chat): stop the skill picker cap from erasing whole scopes | Brennan Benson Core team · MEMBER | #14690 [Bug]: Chat UI does not load all local and project skills Fixes · OPEN #16409 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +125/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the update scheduler when the app quits1 PR · Standalone · Plugins#
Problem: stop the update scheduler when the app quits.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17130 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17221 fix(updater): stop the update scheduler when the app quits | Brennan Benson Core team · MEMBER | #17130 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +224/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the usage cards recommending orchestration for handoffs1 PR · Standalone · Plugins#
Problem: stop the usage cards recommending orchestration for handoffs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14104 Orchestration example cards and the orchestration skill guide give agents opposite handoff routing (Fixes, OPEN); #14842 Title unavailable (Unclear, Unknown); #14918 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14996 fix(orchestration): stop the usage cards recommending orchestration for handoffs | Tauri-EPO Community · CONTRIBUTOR | #14104 Orchestration example cards and the orchestration skill guide give agents opposite handoff routing Fixes · OPEN #14842 Title unavailable Unclear · Unknown #14918 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The orchestration Settings pane shows five example cards under "How to use it". The first two told agents to use orchestration to hand work off to another agent — which is the one thing the orchestration skill gu | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +39/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop treating waiting Actions as failures2 PRs · Overlapping · Plugins#
Problem: stop treating waiting Actions as failures.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #13327 [Bug]: GitHub actions requiring manual start reported as failing (Fixes, OPEN); #13566 Title unavailable (Unclear, Unknown); #13710 Title unavailable (Unclear, Unknown); #13692 Title unavailable (Unclear, Unknown); #13691 Title unavailable (Unclear, Unknown); #13536 Title unavailable (Unclear, Unknown); #13572 Title unavailable (Unclear, Unknown); #8072 Title unavailable (Unclear, Unknown); #13237 Title unavailable (Unclear, Unknown); #13570 Title unavailable (Unclear, Unknown); #13561 Title unavailable (Unclear, Unknown); #13255 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13609 fix(github): stop treating waiting Actions as failures | BingZ Community · CONTRIBUTOR | #13327 [Bug]: GitHub actions requiring manual start reported as failing Fixes · OPEN #13566 Title unavailable Unclear · Unknown #13710 Title unavailable Unclear · Unknown #13692 Title unavailable Unclear · Unknown #13691 Title unavailable Unclear · Unknown #13536 Title unavailable Unclear · Unknown #13572 Title unavailable Unclear · Unknown #8072 Title unavailable Unclear · Unknown #13237 Title unavailable Unclear · Unknown #13570 Title unavailable Unclear · Unknown #13561 Title unavailable Unclear · Unknown #13255 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 GitHub Actions that are still waiting or requested now show as pending instead of failed or unresolved. ## What Changed - Treat REST check-run `waiting`, `requested`, and `pending` statuses as queued/non-terminal | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +43/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16632 fix(checks): distinguish action-required PRs from failures | Luis Sebastian Urrutia Fuentes Community · CONTRIBUTOR | #13327 [Bug]: GitHub actions requiring manual start reported as failing Fixes · OPEN | Cluster contribution | ## ELI5 PRs waiting for someone to approve a GitHub Actions run could appear failed, passing, or unresolved depending on which Orca surface loaded first. Orca now keeps them merge-blocking but consistently labels them `A | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk61 files, +1926/−311. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop xterm.js version text leaking into Codex1 PR · Standalone · Plugins#
Problem: stop xterm.js version text leaking into Codex.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16489 [Bug]: Codex startup can consume the xterm.js XTVERSION reply as input (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16491 fix(terminal): stop xterm.js version text leaking into Codex | Luis Sebastian Urrutia Fuentes Community · CONTRIBUTOR | #16489 [Bug]: Codex startup can consume the xterm.js XTVERSION reply as input Fixes · OPEN | Standalone change | ## ELI5 When the terminal answered "what version are you?" during startup, Orca could hold that answer until Codex started and then hand it to Codex as if the user had typed it. XTVERSION replies now use Orca's existing | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +185/−42. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2submit Quick Commands in agent TUIs1 PR · Standalone · Plugins#
Problem: submit Quick Commands in agent TUIs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14525 Title unavailable (Unclear, Unknown); #14347 Title unavailable (Unclear, Unknown); #14608 Title unavailable (Unclear, Unknown); #14962 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16562 fix(terminal): submit Quick Commands in agent TUIs | Jinwoo Hong Core team · MEMBER | #14525 Title unavailable Unclear · Unknown #14347 Title unavailable Unclear · Unknown #14608 Title unavailable Unclear · Unknown #14962 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 21 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk50 files, +2880/−240. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2support raw HTML tags like <br> in markdown viewers1 PR · Standalone · Plugins#
Problem: support raw HTML tags like <br> in markdown viewers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13097 [Feature]: add html support to markdown viewer, such as <br> (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13122 fix(editor): support raw HTML tags like <br> in markdown viewers | jibin jose Community · FIRST_TIME_CONTRIBUTOR | #13097 [Feature]: add html support to markdown viewer, such as <br> Fixes · OPEN | Standalone change | ### Description Fixes #13097 This PR resolves an issue where raw HTML tags (such as `<br>`) inside markdown tables and comments were being rendered as literal text instead of acting as actual HTML elements. ### Cause Whi | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +3/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2support status authority without randomUUID1 PR · Standalone · Plugins#
Problem: support status authority without randomUUID.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16232 [Bug]: Web client white-screens over HTTP when crypto.randomUUID is unavailable (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16235 fix(renderer): support status authority without randomUUID | Seongho.Bak Community · CONTRIBUTOR | #16232 [Bug]: Web client white-screens over HTTP when crypto.randomUUID is unavailable Fixes · OPEN | Standalone change | ## ELI5 Plain-HTTP browsers can expose `crypto.getRandomValues` without exposing `crypto.randomUUID`. Orca created the renderer's agent-status authority ID while its module loaded, so that missing method could blank the | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +17/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2support strict bare repositories1 PR · Standalone · Plugins#
Problem: support strict bare repositories.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16445 [Bug]: bare repository inspection fails with safe.bareRepository=explicit (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16446 fix(git): support strict bare repositories | Luis Sebastian Urrutia Fuentes Community · CONTRIBUTOR | #16445 [Bug]: bare repository inspection fails with safe.bareRepository=explicit Fixes · OPEN | Standalone change | ## ELI5 Most Orca users will never enter this path. It applies only when Git is configured with `safe.bareRepository=explicit` and Orca opens an already registered bare repository. Git then rejects normal repository disc | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +1029/−153. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2suppress resume after relay replacement1 PR · Standalone · Plugins#
Problem: suppress resume after relay replacement.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16763 Title unavailable (Unclear, Unknown); #16989 Title unavailable (Unclear, Unknown); #16843 Title unavailable (Unclear, Unknown); #15172 Title unavailable (Unclear, Unknown); #16894 Title unavailable (Unclear, Unknown); #16895 Title unavailable (Unclear, Unknown); #16901 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16839 fix(ssh): suppress resume after relay replacement | Brennan Benson Core team · MEMBER | #16763 Title unavailable Unclear · Unknown #16989 Title unavailable Unclear · Unknown #16843 Title unavailable Unclear · Unknown #15172 Title unavailable Unclear · Unknown #16894 Title unavailable Unclear · Unknown #16895 Title unavailable Unclear · Unknown #16901 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk40 files, +1151/−140. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface an unverifiable worktree dot when agent hooks are missing1 PR · Standalone · Plugins#
Problem: surface an unverifiable worktree dot when agent hooks are missing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16101 [Bug]: Worktree dot shows a green "done" dot when Orca's managed agent hooks are missing (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16104 fix(sidebar): surface an unverifiable worktree dot when agent hooks are missing | gatsby74 Community · CONTRIBUTOR | #16101 [Bug]: Worktree dot shows a green "done" dot when Orca's managed agent hooks are missing Fixes · OPEN | Standalone change | ## ELI5 When Orca cannot receive status from a live managed agent because its hooks are missing or unreadable, the worktree now shows a muted dashed ring instead of the same green dot used for a finished agent. ## What C | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +1277/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface blocked Delivery backlogs1 PR · Standalone · Plugins#
Problem: surface blocked Delivery backlogs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15469 fix(orchestration): surface blocked Delivery backlogs | pinkiepromise33-glitch Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | [CODEX_AUTHORED @ msg_6f767d368b78/delivery-fifo-guard] ## Outcome REVIEW_READY — bound Run Delivery FIFO no longer hides an unacknowledged backlog silently. ## Contract - Preserve at-least-once delivery and explicit ACK | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +246/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface hidden command groups in root help1 PR · Standalone · Plugins#
Problem: surface hidden command groups in root help.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13201 Discoverability: ~19 served commands are missing from the visible help tree (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13205 fix(cli): surface hidden command groups in root help | BingZ Community · CONTRIBUTOR | #13201 Discoverability: ~19 served commands are missing from the visible help tree Fixes · OPEN | Standalone change | ## ELI5 Several Orca CLI commands worked when typed directly but were missing from `orca --help`. This PR makes those commands discoverable and locks every newly exposed help entry with a regression assertion. ## What Ch | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +89/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface host context labels on pinned worktree rows2 PRs · Related · Plugins#
Problem: surface host context labels on pinned worktree rows.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Related. Linked issues: #13353 Pinned worktree/project row may hide project name in sidebar (Fixes, OPEN); #13609 Title unavailable (Unclear, Unknown); #13566 Title unavailable (Unclear, Unknown); #13710 Title unavailable (Unclear, Unknown); #13692 Title unavailable (Unclear, Unknown); #13691 Title unavailable (Unclear, Unknown); #13536 Title unavailable (Unclear, Unknown); #8072 Title unavailable (Unclear, Unknown); #13237 Title unavailable (Unclear, Unknown); #13570 Title unavailable (Unclear, Unknown); #13561 Title unavailable (Unclear, Unknown); #13255 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13424 fix(sidebar): surface host context labels on pinned worktree rows | Pr1p Community · CONTRIBUTOR | #13353 Pinned worktree/project row may hide project name in sidebar Fixes · OPEN | Cluster contribution | ## ELI5 Pinned worktrees are shown under a generic "Pinned" section. If you pin worktrees from multiple hosts, the row itself needs to say which host it belongs to, otherwise different machines can look indistinguishable | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +60/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13572 fix(sidebar): keep project name visible on pinned worktree rows | BingZ Community · CONTRIBUTOR | #13353 Pinned worktree/project row may hide project name in sidebar Fixes · OPEN #13609 Title unavailable Unclear · Unknown #13566 Title unavailable Unclear · Unknown #13710 Title unavailable Unclear · Unknown #13692 Title unavailable Unclear · Unknown #13691 Title unavailable Unclear · Unknown #13536 Title unavailable Unclear · Unknown #8072 Title unavailable Unclear · Unknown #13237 Title unavailable Unclear · Unknown #13570 Title unavailable Unclear · Unknown #13561 Title unavailable Unclear · Unknown #13255 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - Pinning moves a worktree into the Pinned section without the project group header, so project identity was only an icon + aria-label/tooltip. - Show a visible project name chip when the card title is a workt | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +75/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface Pi tool approval requests as blocked1 PR · Standalone · Plugins#
Problem: surface Pi tool approval requests as blocked.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15145 Title unavailable (Unclear, Unknown); #10454 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17236 fix: surface Pi tool approval requests as blocked | Johnzell Community · FIRST_TIME_CONTRIBUTOR | #15145 Title unavailable Unclear · Unknown #10454 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Forward Pi `tool_approval_requested` from generated status extension. - Normalize Pi approval requests as `blocked` / action-required in Orca backend. - Preserve tool name and input preview for approval card | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +66/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface reserved-identity install errors for local forks1 PR · Standalone · Plugins#
Problem: surface reserved-identity install errors for local forks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12598 Local-path plugin install silently blocked for forks of official plugin templates (e.g. orca-portuguese) — no actionable error shown (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12606 fix(plugins): surface reserved-identity install errors for local forks | BingZ Community · CONTRIBUTOR | #12598 Local-path plugin install silently blocked for forks of official plugin templates (e.g. orca-portuguese) — no actionable error shown Fixes · OPEN | Standalone change | ## Summary Forking an official plugin template (for example `orca-portuguese`) and installing it from a local path failed with an error that never said what to change. The dialog now names the two fields to edit: `publis | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +73/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2survive a non-string repoId on hydrated setup rows1 PR · Standalone · Plugins#
Problem: survive a non-string repoId on hydrated setup rows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16718 fix(settings): survive a non-string repoId on hydrated setup rows | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +247/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2sweep descendants when tearing down hand-typed agent sessions1 PR · Standalone · Plugins#
Problem: sweep descendants when tearing down hand-typed agent sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16714 Hand-typed agent sessions (claude/codex in a plain shell) leak their process tree on tab close (Fixes, OPEN); #8459 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16713 fix(terminal): sweep descendants when tearing down hand-typed agent sessions | PeaceTis Community · FIRST_TIME_CONTRIBUTOR | #16714 Hand-typed agent sessions (claude/codex in a plain shell) leak their process tree on tab close Fixes · OPEN #8459 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If you open a plain terminal in Orca, type `claude` yourself, and later close the tab, the claude process and its MCP servers keep running forever. Orca only knew how to fully clean up agents it launched itself. | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +65/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2sync agent default launch settings to paired runtime1 PR · Standalone · Plugins#
Problem: sync agent default launch settings to paired runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16501 [Bug]: Paired Web saves agent settings locally but does not propagate them to the runtime (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16566 fix(web): sync agent default launch settings to paired runtime | Wooseong Kim Community · CONTRIBUTOR | #16501 [Bug]: Paired Web saves agent settings locally but does not propagate them to the runtime Fixes · OPEN | Standalone change | ## Description Paired Web settings updates for agent launch defaults were stored only in `orca.web.settings.v1`, so the connected runtime kept the previous `agentDefaultArgs`. `syncRuntimeBackedSettings` now forwards hos | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +56/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2take hook-server alias ownership before replay, not after1 PR · Standalone · Plugins#
Problem: take hook-server alias ownership before replay, not after.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17256 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17262 fix(persistence): take hook-server alias ownership before replay, not after | Brennan Benson Core team · MEMBER | #17256 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +125/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2tear down terminals on deletion1 PR · Standalone · Plugins#
Problem: tear down terminals on deletion.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13615 fix(folder-workspaces): tear down terminals on deletion | Neil Core team · MEMBER | None found | Standalone change | ## Description Deleting a folder workspace or project group used to remove its catalog/UI entry without proving that every owned terminal had stopped. Hidden, parked, direct-SSH, daemon, and paired-host PTYs could surviv | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk240 files, +24592/−2542. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2treat a dead status owner PID as claimable1 PR · Standalone · Plugins#
Problem: treat a dead status owner PID as claimable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16109 [Bug] pi-family agents stop reporting status permanently after an agent restart (dead-owner PID guard in orca-agent-status.ts) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16118 fix(pi): treat a dead status owner PID as claimable | Jason Brashear Community · CONTRIBUTOR | #16109 [Bug] pi-family agents stop reporting status permanently after an agent restart (dead-owner PID guard in orca-agent-status.ts) Fixes · OPEN | Standalone change | ## ELI5 When a pi/omp/prime agent starts in an Orca pane, it stamps its own process ID into an environment variable to say "this pane is mine, nobody else report status for it." That stops child agents from double-report | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +278/−189. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2trigger slash skill picker at any word boundary1 PR · Standalone · Plugins#
Problem: trigger slash skill picker at any word boundary.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16609 [Bug]: native chat slash (/) skill picker only triggers at the start of the input (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16610 fix(native-chat): trigger slash skill picker at any word boundary | Yunqian Fan Community · CONTRIBUTOR | #16609 [Bug]: native chat slash (/) skill picker only triggers at the start of the input Fixes · OPEN | Standalone change | ## Summary In native chat mode, the slash (`/`) skill/command picker only opened when `/` was the **first character** of the input — unlike the `$` (Codex skill) and `@` (file mention) pickers in the same composer, which | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +89/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2trust OS certificates for Linear API requests1 PR · Standalone · Plugins#
Problem: trust OS certificates for Linear API requests.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12189 [Bug]: Linear integration fails with "Fetch failed" when Cloudflare WARP is connected (Fixes, OPEN); #15208 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15450 fix(linear): trust OS certificates for Linear API requests | Joe Lyu Community · FIRST_TIME_CONTRIBUTOR | #12189 [Bug]: Linear integration fails with "Fetch failed" when Cloudflare WARP is connected Fixes · OPEN #15208 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On a corporate network that inspects TLS (Cloudflare WARP, Zscaler, a proxy at the office), the certificate Orca gets back for `api.linear.app` is signed by the company's own certificate authority instead of Line | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +195/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2unlink .asar files during host tree removal (#16958)1 PR · Standalone · Plugins#
Problem: unlink .asar files during host tree removal (#16958).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16958 [Bug]: Worktree trash deletion silently leaves every .asar file behind, accumulating forever (Fixes, OPEN); #11233 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16978 fix(worktrees): unlink .asar files during host tree removal (#16958) | BingZ Community · CONTRIBUTOR | #16958 [Bug]: Worktree trash deletion silently leaves every .asar file behind, accumulating forever Fixes · OPEN #11233 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Deleting a worktree is supposed to wipe the leftover folder in the background. If that folder contains `.asar` files (Electron apps ship them), those files stay forever in `.orca-worktree-trash/` and the next-lau | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +106/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2upload dropped files to remote Orca runtime worktrees1 PR · Standalone · Plugins#
Problem: upload dropped files to remote Orca runtime worktrees.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16558 [Bug]: Copy pasting files to remote orca server don't seem to work (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16567 fix(composer): upload dropped files to remote Orca runtime worktrees | Wooseong Kim Community · CONTRIBUTOR | #16558 [Bug]: Copy pasting files to remote orca server don't seem to work Fixes · OPEN | Standalone change | ## Description Drag-and-drop onto an agent prompt uploaded into `.orca/drops` over SSH, but a Remote Orca Server target fell through to pasting client-local paths. Composer drops now resolve the selected repo/worktree ow | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +158/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2use global history for floating terminals1 PR · Standalone · Plugins#
Problem: use global history for floating terminals.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15942 [Bug]: Floating terminal hides global shell history and its scoped history can be pruned (Fixes, OPEN); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15947 fix(terminal): use global history for floating terminals | dngur6344 Community · CONTRIBUTOR | #15942 [Bug]: Floating terminal hides global shell history and its scoped history can be pruned Fixes · OPEN #39 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Floating terminals now behave like a global shell: ArrowUp/history sees the user's normal shell history. Regular workspace terminal tabs remain isolated to their workspace history. ## What Changed - Added one ter | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +324/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2use the external display viewport1 PR · Standalone · Plugins#
Problem: use the external display viewport.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16641 fix(mobile): use the external display viewport | Adelin Berard Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem On an XREAL / Android external display, the mobile dashboard was constrained to a `720dp` max-width column even when Android reported a real `1920×1080` viewport. This left large unused side borders and made t | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +19/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2verify creates with a fresh listing1 PR · Standalone · Plugins#
Problem: verify creates with a fresh listing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16520 [Bug]: worktree.create fails with "Worktree created but not found in listing" although the worktree is actually created (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16700 fix(worktree): verify creates with a fresh listing | Brennan Benson Core team · MEMBER | #16520 [Bug]: worktree.create fails with "Worktree created but not found in listing" although the worktree is actually created Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +87/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2wait for Codex composer before paste1 PR · Standalone · Plugins#
Problem: wait for Codex composer before paste.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #14575 Title unavailable (Unclear, Unknown); #9976 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14888 fix(orchestration): wait for Codex composer before paste | BingZ Community · CONTRIBUTOR | #14575 Title unavailable Unclear · Unknown #9976 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Codex starts with several MCP servers, its prompt box can render late. Orca now waits for that prompt box before pasting worker instructions, so a startup redraw cannot erase the input. ## What Changed - Reu | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +210/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2wait for the host snapshot to hold the baseline before capturing it1 PR · Standalone · Plugins#
Problem: wait for the host snapshot to hold the baseline before capturing it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #17031 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17138 test(e2e): wait for the host snapshot to hold the baseline before capturing it | Brennan Benson Core team · MEMBER | #17031 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +46/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Windows suite: from 289 failures to zero, plus image-to-pet creation1 PR · Standalone · Plugins#
Problem: Windows suite: from 289 failures to zero, plus image-to-pet creation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16036 Title unavailable (Unclear, Unknown); #16037 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15994 Windows suite: from 289 failures to zero, plus image-to-pet creation | Sylen Community · FIRST_TIME_CONTRIBUTOR | #16036 Title unavailable Unclear · Unknown #16037 Title unavailable Unclear · Unknown | Standalone change | 78 commits, two things: **the Windows test suite goes from 289 failures to zero**, and the **image-to-pet creation feature** this branch originally existed for. The Windows work is the bulk of it. Full write-up, per-fail | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk230 files, +12648/−1488. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2withdraw unproven DOM spacing repair1 PR · Standalone · Plugins#
Problem: withdraw unproven DOM spacing repair.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #12944 Title unavailable (Unclear, Unknown); #11864 Title unavailable (Unclear, Unknown); #12622 Title unavailable (Unclear, Unknown); #12945 Title unavailable (Unclear, Unknown); #13159 Title unavailable (Unclear, Unknown); #11338 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13371 chore(terminal): withdraw unproven DOM spacing repair | Brennan Benson Core team · MEMBER | #12944 Title unavailable Unclear · Unknown #11864 Title unavailable Unclear · Unknown #12622 Title unavailable Unclear · Unknown #12945 Title unavailable Unclear · Unknown #13159 Title unavailable Unclear · Unknown #11338 Title unavailable Unclear · Unknown | Standalone change | ## Withdrawn after architectural and history review This PR now intentionally has no net code diff. The proposed repair was removed in d3c19c6a9b after two independent reviews found that its producer was not established: | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk0 files, +0/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2worktree create keeps slash-containing branch names1 PR · Standalone · Plugins#
Problem: worktree create keeps slash-containing branch names.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13011 [Bug]: `orca worktree create` can't create a branch containing `/` — sanitized worktree name leaks into the branch name (Fixes, OPEN); #6721 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13130 fix(cli): worktree create keeps slash-containing branch names | BingZ Community · CONTRIBUTOR | #13011 [Bug]: `orca worktree create` can't create a branch containing `/` — sanitized worktree name leaks into the branch name Fixes · OPEN #6721 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Add `--branch` to `orca worktree create`, forwarded as `branchNameOverride` so directory name and git branch can differ. - When `--name` contains `/` and `--branch` is omitted, keep the raw name as the branc | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +418/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2write runtime currentHash for mirrored hook trust1 PR · Standalone · Plugins#
Problem: write runtime currentHash for mirrored hook trust.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16428 [Bug]: mirrored user hooks reuse system trusted_hash and trigger review after runtime remap (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16568 fix(codex): write runtime currentHash for mirrored hook trust | Wooseong Kim Community · CONTRIBUTOR | #16428 [Bug]: mirrored user hooks reuse system trusted_hash and trigger review after runtime remap Fixes · OPEN | Standalone change | ## ELI5 Orca mirrors user Codex hooks into a managed `CODEX_HOME`. On Windows, the same approved hook can have a different runtime hash and slash spelling, so Codex repeatedly asks to review it. This change asks Codex fo | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1427/−42. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2yield terminal byte fallbacks to active app keybindings1 PR · Standalone · Plugins#
Problem: yield terminal byte fallbacks to active app keybindings.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15045 Terminal tab cycling shortcut silently dead after keyboard-only worktree switch until a tab is clicked (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15226 fix(terminal): yield terminal byte fallbacks to active app keybindings | Dandi Wong Community · FIRST_TIME_CONTRIBUTOR | #15045 Terminal tab cycling shortcut silently dead after keyboard-only worktree switch until a tab is clicked Fixes · OPEN | Standalone change | ## ELI5 When users customize shortcuts like `Command + Left/Right` to switch tabs or run plugin commands, the terminal previously intercepted those keystrokes and treated them as line-navigation bytes (`Ctrl+A` / `Ctrl+E | P2 Useful scoped improvement; aligned with Plugins but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +312/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[Fix] MiniMax: add CN endpoint selector + API key auth (#14264)1 PR · Standalone · Automated release pipeline#
Problem: [Fix] MiniMax: add CN endpoint selector + API key auth (#14264).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14264 [Bug]: Minimax quota check fails for platform.minimaxi.com due to hardcoded endpoints (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14929 [Fix] MiniMax: add CN endpoint selector + API key auth (#14264) | weekbin Community · FIRST_TIME_CONTRIBUTOR | #14264 [Bug]: Minimax quota check fails for platform.minimaxi.com due to hardcoded endpoints Fixes · OPEN | Standalone change | ## ELI5 The MiniMax provider's usage check was hardcoded to hit the overseas endpoint (platform.minimax.io), so anyone with a `www.minimaxi.com` (CN) account got 1004 "cookie is missing" and saw an empty chip. The fix le | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk41 files, +1797/−367. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[HOLD] fix(terminal): stop dropping renderer-bound bytes for hidden panes1 PR · Standalone · Automated release pipeline#
Problem: [HOLD] fix(terminal): stop dropping renderer-bound bytes for hidden panes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14241 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14250 [HOLD] fix(terminal): stop dropping renderer-bound bytes for hidden panesDraft | Brennan Benson Core team · MEMBER | #14241 Title unavailable Unclear · Unknown | Standalone change | > ## 🛑 ON HOLD — do not merge on the architecture argument alone > > **The bug this was written for is already fixed.** #14241 is merged and grounds the emulator pen at the choke point where a drop is announced, which c | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +39/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[perf-remote] perf(renderer): avoid duplicate remote session inventory1 PR · Standalone · Automated release pipeline#
Problem: [perf-remote] perf(renderer): avoid duplicate remote session inventory.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8098 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13577 [perf-remote] perf(renderer): avoid duplicate remote session inventory | Neil Core team · MEMBER | #8098 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Makes the remote `session.tabs.subscribeAll` bootstrap atomic: refresh inventory, install the listener, then capture the initial batch. - Uses that mandatory stream batch for normal renderer hydration instea | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +809/−189. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2abandon stuck relay recovery on revoked credentials1 PR · Standalone · Automated release pipeline#
Problem: abandon stuck relay recovery on revoked credentials.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14005 mobile: relay pairing recovery strands on "recovery pending" after desktop rotates QR (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13997 fix(mobile): abandon stuck relay recovery on revoked credentials | StillTogether Community · FIRST_TIME_CONTRIBUTOR | #14005 mobile: relay pairing recovery strands on "recovery pending" after desktop rotates QR Fixes · OPEN | Standalone change | ## ELI5 When you scan a QR to pair your phone with Orca and the pairing fails partway, the phone keeps a "to-do" note (journal) about it so it can finish up later. If you then make a new QR on your computer, the old note | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +65/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2accept an empty --value in fill and select commands1 PR · Standalone · Automated release pipeline#
Problem: accept an empty --value in fill and select commands.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16029 [Bug]: browser fill/select reject --value "" though the runtime accepts empty values (Fixes, OPEN); #15863 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16030 fix(browser): accept an empty --value in fill and select commands | 2sumtech Community · CONTRIBUTOR | #16029 [Bug]: browser fill/select reject --value "" though the runtime accepts empty values Fixes · OPEN #15863 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Typing "nothing" into a webpage box should empty it out. Right now Orca's CLI says "you forgot to type something" and refuses. This teaches `fill` and `select` that an empty value is a real value. ## What Changed | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +102/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2actionable error when file open path is outside worktree1 PR · Standalone · Automated release pipeline#
Problem: actionable error when file open path is outside worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13949 orca file open: absolute/outside-worktree paths rejected with invalid_relative_path — no way to open arbitrary files (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13967 fix(cli): actionable error when file open path is outside worktree | BingZ Community · CONTRIBUTOR | #13949 orca file open: absolute/outside-worktree paths rejected with invalid_relative_path — no way to open arbitrary files Fixes · OPEN | Standalone change | ## ELI5 `orca file open` now turns absolute or dotted paths inside the selected worktree into a clean relative path. If the target is the worktree directory itself or is outside that worktree, the CLI stops early with an | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +93/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2activate the window when a context menu opens while unfocused1 PR · Standalone · Automated release pipeline#
Problem: activate the window when a context menu opens while unfocused.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14545 [Bug]: Context menu opened while another app is focused has no hover or keyboard target (macOS) (Fixes, OPEN); #5128 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14546 fix(window): activate the window when a context menu opens while unfocused | Guyllaume Doyer Community · FIRST_TIME_CONTRIBUTOR | #14545 [Bug]: Context menu opened while another app is focused has no hover or keyboard target (macOS) Fixes · OPEN #5128 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Right-click a workspace card while you are working in another app, and the menu shows up but nothing lights up when you move the mouse over it — the menu is dead until you click Orca first, which closes it. macOS | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +220/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add a real profile-reset operation, wired to nothing1 PR · Standalone · Automated release pipeline#
Problem: add a real profile-reset operation, wired to nothing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15221 Title unavailable (Unclear, Unknown); #15481 Title unavailable (Unclear, Unknown); #15542 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15543 feat(browser): add a real profile-reset operation, wired to nothing | Brennan Benson Core team · MEMBER | #15221 Title unavailable Unclear · Unknown #15481 Title unavailable Unclear · Unknown #15542 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +231/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add collapse and expand all actions1 PR · Standalone · Automated release pipeline#
Problem: add collapse and expand all actions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13585 [Feature]: Collapse all / expand all for the sidebar sections (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13963 feat(sidebar): add collapse and expand all actions | 최재영 Community · FIRST_TIME_CONTRIBUTOR | #13585 [Feature]: Collapse all / expand all for the sidebar sections Fixes · OPEN | Standalone change | ## ELI5 The sidebar previously required users to collapse or expand each section one at a time. This adds two actions that collapse or expand all sidebar sections at once. ## What Changed - Added `Collapse all sections` | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +99/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add cross-protocol daemon reattach coverage1 PR · Standalone · Automated release pipeline#
Problem: Add cross-protocol daemon reattach coverage.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11789 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12403 Add cross-protocol daemon reattach coverage | Jinjing Core team · MEMBER | #11789 Title unavailable Unclear · Unknown | Standalone change | ## Summary Adds comprehensive testing of the current DaemonPtyAdapter against real daemons from every still-supported previous protocol version. Addresses the gap exposed in #11789, which shipped a total reattach failure | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +764/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add multi-agent Rooms1 PR · Standalone · Automated release pipeline#
Problem: Add multi-agent Rooms.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13888 Add multi-agent Rooms | embogomolov Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds Rooms, shared chats where multiple agents work together. Every agent sees the room history and decides whether to reply. Agents respond when they have something useful to add and can stay quiet otherwise, | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk419 files, +34478/−2534. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add Ukrainian README translation1 PR · Standalone · Automated release pipeline#
Problem: add Ukrainian README translation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16124 docs: add Ukrainian README translation | Ihor Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - add a Ukrainian translation of the README - link Ukrainian from every README language selector - preserve all documentation, download, and asset links ## Validation - verified translated README URLs match th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +276/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2adopt pty.attach viewport on reattach1 PR · Standalone · Automated release pipeline#
Problem: adopt pty.attach viewport on reattach.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7209 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13300 fix(relay): adopt pty.attach viewport on reattach | 오영택 Community · CONTRIBUTOR | #7209 Title unavailable Unclear · Unknown | Standalone change | Related to #7209 ## Scope This is bounded relay attach hardening. The SSH provider already includes the attaching pane's optional `cols` and `rows` in `pty.attach`; the relay now validates a complete finite numeric pair, | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +519/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2adopt robust Settings AUMID polling for UWP e2e test1 PR · Standalone · Automated release pipeline#
Problem: adopt robust Settings AUMID polling for UWP e2e test.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14894 [Bug]: Nightly computer-use e2e windows job fails - calc.exe launches as win32calc, not an ApplicationFrameHost UWP app, on windows-latest (Server 2025) (Fixes, OPEN); #13046 Title unavailable (Unclear, Unknown); #13038 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13048 test: adopt robust Settings AUMID polling for UWP e2e test | Zuz666 Community · CONTRIBUTOR | #14894 [Bug]: Nightly computer-use e2e windows job fails - calc.exe launches as win32calc, not an ApplicationFrameHost UWP app, on windows-latest (Server 2025) Fixes · OPEN #13046 Title unavailable Unclear · Unknown #13038 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes the UWP `computer-windows-store.e2e.ts` test failing on Windows Server 2025 runners. Fixes #14894. *Note: This PR is a clean, consolidated re-submission that replaces #13046 and #13038.* The original tes | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +1048/−88. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2after closing a tab, return to the previous one1 PR · Standalone · Automated release pipeline#
Problem: after closing a tab, return to the previous one.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15219 [Bug]: Closing a document on mobile jumps to the leftmost tab (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15220 fix(mobile): after closing a tab, return to the previous one | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #15219 [Bug]: Closing a document on mobile jumps to the leftmost tab Fixes · OPEN | Standalone change | ## ELI5 If you close a document on your phone, Orca used to jump to the leftmost tab. It now goes back to the tab you were looking at before, and only if you never visited another tab does it land on the newest remaining | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +238/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2align Agents sidebar badge with actual unread agent count2 PRs · Overlapping · Automated release pipeline#
Problem: align Agents sidebar badge with actual unread agent count.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #15445 [Bug]: Agents sidebar badge overcounts unread items (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15446 fix(activity): align Agents sidebar badge with actual unread agent count | Yunqian Fan Community · CONTRIBUTOR | #15445 [Bug]: Agents sidebar badge overcounts unread items Fixes · OPEN | Cluster contribution | ## Summary The Agents sidebar badge showed a non-zero unread count even after all agent threads were acknowledged, and could overcount due to non-agent terminal activity. ### Root cause The sidebar Agents badge (`sidebar | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +54/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15457 fix(sidebar): the Agents badge stops overcounting coarse unread flags (#15445) | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15445 [Bug]: Agents sidebar badge overcounts unread items Fixes · OPEN | Cluster contribution | Closes #15445 (items 1 and 2 of the suggested fix). ## The two defects 1. **Overcounting** — `sidebar-badge` mode summed `worktree.isUnread`, a coarse attention flag also set by terminal BELs and parked-terminal activity | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +103/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Allow editing Linear assignees and labels in list view1 PR · Standalone · Automated release pipeline#
Problem: Allow editing Linear assignees and labels in list view.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13435 Allow editing Linear assignees and labels in list view | Jinjing Core team · MEMBER | None found | Standalone change | ## Problem Users couldn't edit Linear assignees and labels directly from list and table views—they required navigation to detail views or alternate workflows to modify these fields. ## Solution Extracted assignee and lab | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +977/−93. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2allow repo-local OpenCode permissions1 PR · Standalone · Automated release pipeline#
Problem: allow repo-local OpenCode permissions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14433 chore: allow repo-local OpenCode permissionsDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## Summary - add repository-local `opencode.json` with allow-all permissions - allow exactly `opencode.json` through the existing new-root-entry guard - ensure every future worktree inherits the setting after this lands | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +23/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Allow worktree lineage across repo and project boundaries1 PR · Standalone · Automated release pipeline#
Problem: Allow worktree lineage across repo and project boundaries.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11007 [Bug] Child worktree grouping in sidebar (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12755 Allow worktree lineage across repo and project boundaries | Jinjing Core team · MEMBER | #11007 [Bug] Child worktree grouping in sidebar Fixes · OPEN | Standalone change | ## ELI5 Command-line coding agents often create a child workspace inside a different repository than its parent, but Orca refused those parent-child links unless both sides belonged to the same repo and project. Agent-cr | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +379/−80. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2always render the per-agent Environment field1 PR · Standalone · Automated release pipeline#
Problem: always render the per-agent Environment field.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17177 Settings → Agents: the Environment field only renders when an env value already exists (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17195 fix(settings): always render the per-agent Environment fieldDraft | ikitkwan Community · FIRST_TIME_CONTRIBUTOR | #17177 Settings → Agents: the Environment field only renders when an env value already exists Fixes · OPEN | Standalone change | ## ELI5 The Environment box in Settings → Agents only showed up if the agent already had an environment set. Nothing shipped one, so it never showed up, so you could never set one. This makes it always show. ## What Chan | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +80/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2answer a query in its own turn when the kernel is quiet (#13892)1 PR · Standalone · Automated release pipeline#
Problem: answer a query in its own turn when the kernel is quiet (#13892).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13892 [Bug]: OSC/DSR query replies are reordered behind CPR/DA1 by the POSIX echo-safe write path, stranding them into the next child's stdin (Fixes, OPEN); #12112 Title unavailable (Unclear, Unknown); #14609 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13998 fix(terminal): answer a query in its own turn when the kernel is quiet (#13892) | Neil Core team · MEMBER | #13892 [Bug]: OSC/DSR query replies are reordered behind CPR/DA1 by the POSIX echo-safe write path, stranding them into the next child's stdin Fixes · OPEN #12112 Title unavailable Unclear · Unknown #14609 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 fish asks the terminal "what colour is your background?" and, a moment later, "are you there?". Orca used to hold the colour answer back for a fraction of a second (to avoid a different bug) while sending the "ar | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1568/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2apply the app-wide HTTP proxy to embedded browser sessions1 PR · Standalone · Automated release pipeline#
Problem: apply the app-wide HTTP proxy to embedded browser sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15342 [Bug]: Embedded browser ignores the app-wide HTTP Proxy setting (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15536 fix(browser): apply the app-wide HTTP proxy to embedded browser sessions | Brennan Benson Core team · MEMBER | #15342 [Bug]: Embedded browser ignores the app-wide HTTP Proxy setting Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 11 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +2495/−218. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2arm PtyStartupIngress for non-agent panes to suppress OSC 10/11 reply echo on POSIX2 PRs · Related · Agent management and search#
Problem: arm PtyStartupIngress for non-agent panes to suppress OSC 10/11 reply echo on POSIX.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Agent management and search (stack rank 2).
Relationship: Related. Linked issues: #14306 OSC 10/11 color query reply echoes as visible text in non-agent panes on POSIX (macOS + Linux) (Fixes, OPEN); #12112 Title unavailable (Unclear, Unknown); #14490 Title unavailable (Unclear, Unknown); #14307 Title unavailable (Unclear, Unknown); #16542 Title unavailable (Unclear, Unknown); #9651 Title unavailable (Unclear, Unknown); #9500 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14307 fix(pty): arm PtyStartupIngress for non-agent panes to suppress OSC 10/11 reply echo on POSIX | Nguyen Thanh Tin Community · FIRST_TIME_CONTRIBUTOR | #14306 OSC 10/11 color query reply echoes as visible text in non-agent panes on POSIX (macOS + Linux) Fixes · OPEN #12112 Title unavailable Unclear · Unknown #14490 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - Non-agent terminal panes (plain shells with prompt themes like Oh My Posh, starship, powerlevel10k) leak OSC 10/11 color query reply echoes as visible text on POSIX (macOS + Linux/Ubuntu) - The fix for #1211 | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +212/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16123 fix(terminal): contain plain-shell startup color replies | Brennan Benson Core team · MEMBER | #14306 OSC 10/11 color query reply echoes as visible text in non-agent panes on POSIX (macOS + Linux) Fixes · OPEN #14307 Title unavailable Unclear · Unknown #16542 Title unavailable Unclear · Unknown #9651 Title unavailable Unclear · Unknown #9500 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +298/−149. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ask before closing the window when a terminal probe could not answer1 PR · Standalone · Automated release pipeline#
Problem: ask before closing the window when a terminal probe could not answer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17024 Title unavailable (Unclear, Unknown); #10142 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17044 fix(terminal): ask before closing the window when a terminal probe could not answer | Brennan Benson Core team · MEMBER | #17024 Title unavailable Unclear · Unknown #10142 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +932/−103. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2attribute each split pane's runtime title to its own leaf (STA-3264)1 PR · Standalone · Automated release pipeline#
Problem: attribute each split pane's runtime title to its own leaf (STA-3264).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11069 [Bug]: Split panes in one tab share a single sidebar agent-row name that flips to whichever pane was clicked last (Fixes, CLOSED); #12228 [Bug]: Split-pane agents remain jointly Running after one finishes (Fixes, OPEN); #11070 Title unavailable (Unclear, Unknown); #11372 Title unavailable (Unclear, Unknown); #14615 Title unavailable (Unclear, Unknown); #14650 Title unavailable (Unclear, Unknown); #14682 Title unavailable (Unclear, Unknown); #14486 Title unavailable (Unclear, Unknown); #14654 Title unavailable (Unclear, Unknown); #8711 Title unavailable (Unclear, Unknown); #8940 Title unavailable (Unclear, Unknown); #14707 Title unavailable (Unclear, Unknown); #14708 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14702 fix(sidebar): attribute each split pane's runtime title to its own leaf (STA-3264) | Brennan Benson Core team · MEMBER | #11069 [Bug]: Split panes in one tab share a single sidebar agent-row name that flips to whichever pane was clicked last Fixes · CLOSED #12228 [Bug]: Split-pane agents remain jointly Running after one finishes Fixes · OPEN #11070 Title unavailable Unclear · Unknown #11372 Title unavailable Unclear · Unknown #14615 Title unavailable Unclear · Unknown #14650 Title unavailable Unclear · Unknown #14682 Title unavailable Unclear · Unknown #14486 Title unavailable Unclear · Unknown #14654 Title unavailable Unclear · Unknown #8711 Title unavailable Unclear · Unknown #8940 Title unavailable Unclear · Unknown #14707 Title unavailable Unclear · Unknown #14708 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +176/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2avoid blocking cmd.exe agent launch on preflight CLI1 PR · Standalone · Automated release pipeline#
Problem: avoid blocking cmd.exe agent launch on preflight CLI.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16110 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16111 fix(windows): avoid blocking cmd.exe agent launch on preflight CLI | Jinjing Core team · MEMBER | #16110 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +72/−64. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2avoid garbled TUI frame after app restart1 PR · Standalone · Automated release pipeline#
Problem: avoid garbled TUI frame after app restart.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13464 fix(terminal): avoid garbled TUI frame after app restart | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## Summary - Prevent a live alternate-screen TUI from restoring a frame captured at a wider grid and then having xterm reflow it into detached rows when Orca restarts into a narrower window. - Keep the legacy merged snap | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +507/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2avoid quadratic terminal-tail whitespace trimming1 PR · Standalone · Automated release pipeline#
Problem: avoid quadratic terminal-tail whitespace trimming.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14331 [Bug]: Agent TUI redraws can block remote runtime RPCs (Fixes, OPEN); #15349 Title unavailable (Unclear, Unknown); #14770 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14329 perf(runtime): avoid quadratic terminal-tail whitespace trimming | Blueagle Community · FIRST_TIME_CONTRIBUTOR | #14331 [Bug]: Agent TUI redraws can block remote runtime RPCs Fixes · OPEN #15349 Title unavailable Unclear · Unknown #14770 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A terminal status line can contain thousands of spaces before its visible text. Orca checked those spaces repeatedly on every redraw, which could keep Electron's main thread busy and make a healthy remote runtime | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +32/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2back off host probes a wedged runtime never answers1 PR · Standalone · Automated release pipeline#
Problem: back off host probes a wedged runtime never answers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15039 Title unavailable (Unclear, Unknown); #15257 Title unavailable (Unclear, Unknown); #15060 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15293 fix(git): back off host probes a wedged runtime never answers | OrcaWin Unknown · COLLABORATOR | #15039 Title unavailable Unclear · Unknown #15257 Title unavailable Unclear · Unknown #15060 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +1192/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bind remote setup-hook execution to the exact approved content1 PR · Standalone · Automated release pipeline#
Problem: bind remote setup-hook execution to the exact approved content.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15087 fix(remote): bind remote setup-hook execution to the exact approved content | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 13 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk45 files, +2008/−241. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2block Cut Release on #14302 terminal goldens1 PR · Standalone · Automated release pipeline#
Problem: block Cut Release on #14302 terminal goldens.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14302 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14398 test(release): block Cut Release on #14302 terminal goldens | Jinjing Core team · MEMBER | #14302 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Make the #14302 fresh-profile terminal and shell-command goldens a hard `terminal-rendering-golden` gate for Cut Release on Linux, macOS, and Windows. - Compare the terminal cwd with Git's own toplevel so Wi | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +52/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2blur the file search input on Escape2 PRs · Overlapping · Automated release pipeline#
Problem: blur the file search input on Escape.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #12292 [Bug]: Escape in the sidebar file search input clears the query but never releases focus (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12293 fix(search): blur the file search input on Escape | JongHyeok Park Community · CONTRIBUTOR | #12292 [Bug]: Escape in the sidebar file search input clears the query but never releases focus Fixes · OPEN | Cluster contribution | ## Summary Pressing `Escape` in the sidebar file search cleared the query but left keyboard focus stuck in the input — and with an empty query it did nothing at all. The input now blurs on `Escape`, so the keyboard gets | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +128/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14283 fix(right-sidebar): release the file search field on Escape | Brennan Benson Core team · MEMBER | #12292 [Bug]: Escape in the sidebar file search input clears the query but never releases focus Fixes · OPEN | Cluster contribution | ## ELI5 You could type into the sidebar's file search box, but you could never get *out* of it with the keyboard. Pressing `Esc` wiped your text and then just sat there — every key you pressed next still went into the se | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +121/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound git grep fallback records1 PR · Standalone · Automated release pipeline#
Problem: bound git grep fallback records.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13476 fix(search): bound git grep fallback records | OrcaWin Unknown · COLLABORATOR | None found | Standalone change | ## Summary Bounds newline-free `git grep` fallback records at 8 MiB on both local/WSL and SSH relay search paths. Oversized records now stop the child, detach listeners, and return the existing `truncated: true` result i | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +94/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound host admission1 PR · Standalone · Automated release pipeline#
Problem: bound host admission.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14484 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14493 feat(browser): bound host admissionDraft | Jinwoo Hong Core team · MEMBER | #14484 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +332/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound local/WSL Cursor sidecar discovery1 PR · Standalone · Automated release pipeline#
Problem: bound local/WSL Cursor sidecar discovery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11525 Title unavailable (Unclear, Unknown); #11514 Title unavailable (Unclear, Unknown); #13611 Title unavailable (Unclear, Unknown); #14582 Title unavailable (Unclear, Unknown); #11370 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13617 perf(ai-vault): bound local/WSL Cursor sidecar discovery | Brennan Benson Core team · MEMBER | #11525 Title unavailable Unclear · Unknown #11514 Title unavailable Unclear · Unknown #13611 Title unavailable Unclear · Unknown #14582 Title unavailable Unclear · Unknown #11370 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Share the owning-host Cursor chats discovery algorithm between local/WSL and remote so ordinary unscoped scans apply the same ingress caps (buckets, sessions, scopes, sidecar bytes) instead of enumerating th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk35 files, +3421/−573. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bundle ripgrep so local search works without a user-installed rg1 PR · Standalone · Automated release pipeline#
Problem: bundle ripgrep so local search works without a user-installed rg.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9539 [Feature]: Bundle ripgrep so local Quick Open works without a user-installed rg (Fixes, OPEN); #9627 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13116 fix(quick-open): bundle ripgrep so local search works without a user-installed rg | manuaudio Community · CONTRIBUTOR | #9539 [Feature]: Bundle ripgrep so local Quick Open works without a user-installed rg Fixes · OPEN #9627 Title unavailable Unclear · Unknown | Standalone change | Closes #9539. ## Summary Quick Open now works on a machine with no user-installed `rg`. Previously, a local search on a host without ripgrep on `PATH` fell back to `git ls-files` / a `readdir` walk, and that fallback's b | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +439/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cancel in-flight ripgrep listings (STA-4310)1 PR · Standalone · Automated release pipeline#
Problem: cancel in-flight ripgrep listings (STA-4310).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14488 Windows: file explorer spinner hangs and lists no files (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14588 fix(file-explorer): cancel in-flight ripgrep listings (STA-4310) | OrcaWin Unknown · COLLABORATOR | #14488 Windows: file explorer spinner hangs and lists no files Fixes · OPEN | Standalone change | ## Summary - Cancel active local ripgrep passes when the File Explorer/Find Files request is superseded. - Reject with the typed file-list cancellation error, detach listeners, and use the existing process-tree-safe kill | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +61/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cancel superseded content scans1 PR · Standalone · Automated release pipeline#
Problem: cancel superseded content scans.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13525 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13587 perf(search): cancel superseded content scans | Neil Core team · MEMBER | #13525 Title unavailable Unclear · Unknown | Standalone change | ## Summary ### Description Cancel content searches as soon as they are superseded, cleared, hidden, moved to another worktree, or unmounted. Cancellation now propagates through native IPC, paired runtime subscriptions, d | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk52 files, +3651/−442. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Cap AI Vault history depth to 250 for performance1 PR · Standalone · Automated release pipeline#
Problem: Cap AI Vault history depth to 250 for performance.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13089 Cap AI Vault history depth to 250 for performance | Jinjing Core team · MEMBER | None found | Standalone change | ## Problem Deeper AI Vault histories slow the whole app, especially on remote hosts. Profiles that upgraded their history depth to 500, 1000, or unlimited can severely impact performance. We need to reset existing high-d | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +399/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cap remote project refresh concurrency1 PR · Standalone · Automated release pipeline#
Problem: cap remote project refresh concurrency.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14728 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13631 perf(renderer): cap remote project refresh concurrency | Neil Core team · MEMBER | #14728 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | +492 | 0 | +492 | | Prod | 2 | | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +622/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cap runtime file listings before SSH transport1 PR · Standalone · Automated release pipeline#
Problem: cap runtime file listings before SSH transport.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11884 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12025 fix(runtime): cap runtime file listings before SSH transport | Rod Boev Community · CONTRIBUTOR | #11884 Title unavailable Unclear · Unknown | Standalone change | ## Summary Refs #11884. An oversized remote `fs.listFiles` response can exceed the relay's 2,097,152-byte legacy lane and close the shared SSH connection. The diagnostic report from @bakabaka0613 at https://github.com/st | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +252/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2claim the status pane when the inherited owner PID is dead (STA-5245)1 PR · Standalone · Automated release pipeline#
Problem: claim the status pane when the inherited owner PID is dead (STA-5245).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16631 fix(pi): claim the status pane when the inherited owner PID is dead (STA-5245) | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +305/−191. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Clarify remote file mutation version mismatch messages1 PR · Standalone · Automated release pipeline#
Problem: Clarify remote file mutation version mismatch messages.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12443 Clarify remote file mutation version mismatch messages | Jinjing Core team · MEMBER | None found | Standalone change | ## Summary Improves error messages when remote file mutation operations fail due to version mismatches between Orca client and server. Messages now clearly explain which component is out of date and guide users to the re | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +16/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2close #16924 review P2s — degrade warn, reap comment, Windows claim-reap CI1 PR · Standalone · Automated release pipeline#
Problem: close #16924 review P2s — degrade warn, reap comment, Windows claim-reap CI.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16924 Title unavailable (Unclear, Unknown); #16946 Title unavailable (Unclear, Unknown); #16926 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16979 fix(daemon): close #16924 review P2s — degrade warn, reap comment, Windows claim-reap CI | Brennan Benson Core team · MEMBER | #16924 Title unavailable Unclear · Unknown #16946 Title unavailable Unclear · Unknown #16926 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +191/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2close browser tabs by page id1 PR · Standalone · Automated release pipeline#
Problem: close browser tabs by page id.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14052 [Feature]: Allow closing browser tabs by page ID from the CLI (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14369 feat(cli): close browser tabs by page id | erish Community · CONTRIBUTOR | #14052 [Feature]: Allow closing browser tabs by page ID from the CLI Fixes · OPEN | Standalone change | ## ELI5 Browser tab numbers can change while an integration is working. This lets integrations close the exact tab they created by using its stable page ID instead of a moving index. ## What Changed - Allowed --page on o | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +41/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2close headless terminal tabs whose persisted session record is missing1 PR · Standalone · Automated release pipeline#
Problem: close headless terminal tabs whose persisted session record is missing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10747 CLI `terminal close` can never close a background tab that failed reveal — headless close path throws `tab_not_found` for tabs that were never persisted (Fixes, OPEN); #12920 Closing a terminal tab with a missing persisted session record resurrects the tab — close aborts on tab_not_found before PTY kill and snapshot prune (Fixes, CLOSED); #12722 Title unavailable (Unclear, Unknown); #9585 Title unavailable (Unclear, Unknown); #11803 Title unavailable (Unclear, Unknown); #12721 Title unavailable (Unclear, Unknown); #14719 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12922 fix: close headless terminal tabs whose persisted session record is missing | Antonio Lourenco Community · CONTRIBUTOR | #10747 CLI `terminal close` can never close a background tab that failed reveal — headless close path throws `tab_not_found` for tabs that were never persisted Fixes · OPEN #12920 Closing a terminal tab with a missing persisted session record resurrects the tab — close aborts on tab_not_found before PTY kill and snapshot prune Fixes · CLOSED #12722 Title unavailable Unclear · Unknown #9585 Title unavailable Unclear · Unknown #11803 Title unavailable Unclear · Unknown #12721 Title unavailable Unclear · Unknown #14719 Title unavailable Unclear · Unknown | Standalone change | ## Summary A terminal tab that exists in the live mobile-session snapshot but has no persisted workspace-session record can never be closed: - CLI `terminal close` / `terminal closeTab` fail with `tab_not_found` (#10747) | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +92/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2close restored PTYs with missing tabs1 PR · Standalone · Automated release pipeline#
Problem: close restored PTYs with missing tabs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12905 fix(runtime): close restored PTYs with missing tabsDraft | jarbas-marco Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Fixes `orca terminal close` for restored live PTYs whose renderer tab no longer exists in persisted session state. - Falls back to closing only the addressed PTY when the durable close reports the exact `tab | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +75/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Close tab on mobile back to prev1 PR · Standalone · Automated release pipeline#
Problem: Close tab on mobile back to prev.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16146 Close tab on mobile back to prev | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +239/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2close terminal preview with pane shortcut1 PR · Standalone · Automated release pipeline#
Problem: close terminal preview with pane shortcut.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13958 [Bug]: Agent Dashboard terminal preview swallows the close shortcut (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13961 fix(dashboard): close terminal preview with pane shortcut | pstanton237 Community · CONTRIBUTOR | #13958 [Bug]: Agent Dashboard terminal preview swallows the close shortcut Fixes · OPEN | Standalone change | ## ELI5 Pressing the configured close-pane shortcut while a dashboard terminal preview is focused now closes the preview instead of doing nothing. The dashboard window and the underlying agent session stay open. ## What | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +40/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2collapse duplicate per-team status rows in the Tasks filter1 PR · Standalone · Automated release pipeline#
Problem: collapse duplicate per-team status rows in the Tasks filter.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16785 [Bug]: Tasks (Linear) - Duplicate Status values in Filters (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16879 fix(linear): collapse duplicate per-team status rows in the Tasks filter | Neil Core team · MEMBER | #16785 [Bug]: Tasks (Linear) - Duplicate Status values in Filters Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +323/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2compare workspace path prefixes with the cross-platform path helpers1 PR · Standalone · Automated release pipeline#
Problem: compare workspace path prefixes with the cross-platform path helpers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10832 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14890 fix(cleanup): compare workspace path prefixes with the cross-platform path helpers | Brennan Benson Core team · MEMBER | #10832 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +409/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2complete prime-agent title profiles and headless commit env1 PR · Standalone · Automated release pipeline#
Problem: complete prime-agent title profiles and headless commit env.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12892 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13707 feat(agents): complete prime-agent title profiles and headless commit env | Arnold Wang Community · FIRST_TIME_CONTRIBUTOR | #12892 Title unavailable Unclear · Unknown | Standalone change | ## Summary Refs #12892. Adds support for **Prime Agent** (github.com/PrimeIntellect-ai/prime-agent), the recently popular self-improving coding agent built as a fork of Pi. Most of the prime-agent integration is already | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +100/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2contain reattach to existing panes, quarantine orphans1 PR · Standalone · Automated release pipeline#
Problem: contain reattach to existing panes, quarantine orphans.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13111 Title unavailable (Unclear, Unknown); #12448 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12743 fix(ssh): contain reattach to existing panes, quarantine orphans | Jinjing Core team · MEMBER | #13111 Title unavailable Unclear · Unknown #12448 Title unavailable Unclear · Unknown | Standalone change | ## Summary SSH reattach now validates each remote PTY lease against durable pane state before restoring it, preventing cross-wiring to wrong panes or creating phantom entries. Unverified leases are quarantined to prevent | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +1757/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2contain WebGL context-loss churn and trace recovery declines (#12452)1 PR · Standalone · Automated release pipeline#
Problem: contain WebGL context-loss churn and trace recovery declines (#12452).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12452 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13027 fix(terminal): contain WebGL context-loss churn and trace recovery declines (#12452) | Antonio Lourenco Community · CONTRIBUTOR | #12452 Title unavailable Unclear · Unknown | Standalone change | ## Summary This is a bounded mitigation for repeated terminal WebGL context-loss churn reported alongside #12452. It does **not** reproduce or prove a fix for the reported presentation freeze. Two focused changes: 1. **C | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +623/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2correct cross-repository GitHub work-item pagination1 PR · Standalone · Automated release pipeline#
Problem: correct cross-repository GitHub work-item pagination.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12127 Redesign Tasks work-item pagination: the k-way merge model cannot produce a correct page count (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12139 fix(tasks): correct cross-repository GitHub work-item pagination | Hunter Veltri Community · FIRST_TIME_CONTRIBUTOR | #12127 Redesign Tasks work-item pagination: the k-way merge model cannot produce a correct page count Fixes · OPEN | Standalone change | ## Summary Fixes #12127. Tasks now use one scoped GitHub Search API request plan for compatible multi-repository selections. Results merge by GitHub creation timestamp, pagination remains globally ordered, and aggregate | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +2057/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cover editor reference-error paths1 PR · Standalone · Automated release pipeline#
Problem: cover editor reference-error paths.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16532 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16847 test(automations): cover editor reference-error paths | Brennan Benson Core team · MEMBER | #16532 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +20/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Cover the mobile approval card dropping on a live state transition1 PR · Standalone · Automated release pipeline#
Problem: Cover the mobile approval card dropping on a live state transition.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12206 Title unavailable (Unclear, Unknown); #11928 Title unavailable (Unclear, Unknown); #11933 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12237 Cover the mobile approval card dropping on a live state transition | giryun Community · FIRST_TIME_CONTRIBUTOR | #12206 Title unavailable Unclear · Unknown #11928 Title unavailable Unclear · Unknown #11933 Title unavailable Unclear · Unknown | Standalone change | ## Summary Follow-up to #12206, which landed the paused-state gate for the mobile native chat approval card. The six cases that shipped with it each mount a fresh probe and assert the card for one status. That pins the m | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +36/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Cursor/image cursor advance cf6c1 PR · Standalone · Automated release pipeline#
Problem: Cursor/image cursor advance cf6c.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14857 Cursor/image cursor advance cf6c | s546126 Community · CONTRIBUTOR | None found | Standalone change | ## ELI5 <!-- Simple high-level explanation --> ## What Changed <!-- Describe the change clearly and keep scope tight. --> ## Why <!-- What problem does this solve, and why is this approach right? --> ## Linked Issue <!-- | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +160/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2decouple notification host ownership1 PR · Standalone · Automated release pipeline#
Problem: decouple notification host ownership.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11642 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13000 fix(mobile): decouple notification host ownership | Jinwoo Hong Core team · MEMBER | #11642 Title unavailable Unclear · Unknown | Standalone change | ## Re-land status (updated) This is the **main / next-release re-land** of #11642. It is not a cherry-pick onto `prod-release-v1.4.177-rc.0`; that branch keeps its revert (`d2e8bbe109`). **Why the release branch reverted | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +1851/−192. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2dedupe PTY ownership at hydration instead of dropping rows (reland #13060)1 PR · Standalone · Automated release pipeline#
Problem: dedupe PTY ownership at hydration instead of dropping rows (reland #13060).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13060 Title unavailable (Unclear, Unknown); #13098 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13267 fix(terminal): dedupe PTY ownership at hydration instead of dropping rows (reland #13060) | Jinjing Core team · MEMBER | #13060 Title unavailable Unclear · Unknown #13098 Title unavailable Unclear · Unknown | Standalone change | ## Summary Relands #13060 (reverted by #13098) with a narrower fix. **Original bug:** the Grok pane restored at a stale width. A session can persist the same PTY id on more than one terminal row (a stale row left behind | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +486/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2default conflict-resolution agent to YOLO mode1 PR · Standalone · Automated release pipeline#
Problem: default conflict-resolution agent to YOLO mode.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15906 fix(source-control): default conflict-resolution agent to YOLO mode | Rozen Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 When you want to resolve merge conflicts with Gemini, the app used to open the dialog with completely blank arguments, overriding the default `--yolo` flag. Now, if you haven't saved a custom setup for that actio | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +354/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2defer a focus-cancelled paste instead of discarding it (STA-5272)1 PR · Standalone · Automated release pipeline#
Problem: defer a focus-cancelled paste instead of discarding it (STA-5272).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16170 Title unavailable (Unclear, Unknown); #13988 Title unavailable (Unclear, Unknown); #16926 Title unavailable (Unclear, Unknown); #16900 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17020 fix(terminal): defer a focus-cancelled paste instead of discarding it (STA-5272) | Brennan Benson Core team · MEMBER | #16170 Title unavailable Unclear · Unknown #13988 Title unavailable Unclear · Unknown #16926 Title unavailable Unclear · Unknown #16900 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +2083/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2design explicit owner admission follow-up1 PR · Standalone · Automated release pipeline#
Problem: design explicit owner admission follow-up.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12367 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12424 docs(ssh): design explicit owner admission follow-upDraft | Jinjing Core team · MEMBER | #12367 Title unavailable Unclear · Unknown | Standalone change | ## Summary Design-only follow-up to #12367 for making SSH PTY owner admission explicit and non-destructive. The design keeps the stable logical lease, per-admission generation fence, one pending publication, and bounded | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +164/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2detect agents for folder workspaces in the new-tab drawer1 PR · Standalone · Automated release pipeline#
Problem: detect agents for folder workspaces in the new-tab drawer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16215 Mobile: folder workspaces always show "Agent Presets Unavailable" in the New Tab drawer (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16216 fix(mobile): detect agents for folder workspaces in the new-tab drawer | iBakuman Community · FIRST_TIME_CONTRIBUTOR | #16215 Mobile: folder workspaces always show "Agent Presets Unavailable" in the New Tab drawer Fixes · OPEN | Standalone change | ## ELI5 On mobile, opening **New Tab** inside a folder workspace always said "Agent Presets Unavailable — Check the host connection", even though the connection was fine. The code was looking up a git repo for a workspac | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +200/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2detect Comet under its Perplexity vendor directory on Windows1 PR · Standalone · Automated release pipeline#
Problem: detect Comet under its Perplexity vendor directory on Windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14295 [Bug]: Comet cookie import never detects Comet on Windows - winRoot is missing the Perplexity vendor segment (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14300 fix(browser): detect Comet under its Perplexity vendor directory on Windows | Masaki Yamamoto Community · FIRST_TIME_CONTRIBUTOR | #14295 [Bug]: Comet cookie import never detects Comet on Windows - winRoot is missing the Perplexity vendor segment Fixes · OPEN | Standalone change | ## ELI5 On Windows, Orca was looking for Comet's data in the wrong folder, so Comet never appeared in the cookie-import menu no matter what you did. Comet actually installs one level deeper, inside a `Perplexity` folder. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +69/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2detect git D/F ref conflicts before create (STA-4762)1 PR · Standalone · Automated release pipeline#
Problem: detect git D/F ref conflicts before create (STA-4762).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15381 Title unavailable (Unclear, Unknown); #15402 Title unavailable (Unclear, Unknown); #15403 Title unavailable (Unclear, Unknown); #15404 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15383 fix(worktrees): detect git D/F ref conflicts before create (STA-4762) | Jinwoo Hong Core team · MEMBER | #15381 Title unavailable Unclear · Unknown #15402 Title unavailable Unclear · Unknown #15403 Title unavailable Unclear · Unknown #15404 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +646/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Diagnose Claude launches using Orca proxy1 PR · Standalone · Automated release pipeline#
Problem: Diagnose Claude launches using Orca proxy.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16833 Diagnose Claude launches using Orca proxy | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +108/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2disambiguate same-named projects in the repository filters (#6235)1 PR · Standalone · Automated release pipeline#
Problem: disambiguate same-named projects in the repository filters (#6235).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #6235 [Feature]: For projects with the same name, we need more information displayed to make them easily identifiable. (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12244 fix(sidebar): disambiguate same-named projects in the repository filters (#6235) | Neil Core team · MEMBER | #6235 [Feature]: For projects with the same name, we need more information displayed to make them easily identifiable. Fixes · OPEN | Standalone change | ## Description Both sidebar repository-filter surfaces — the **Projects** list inside the workspace-options dropdown (`SidebarFilter.tsx`) and the **repository filter section** (`SidebarRepositoryFilterSection.tsx`) — re | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +642/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2discover WSL Claude transcripts1 PR · Standalone · Automated release pipeline#
Problem: discover WSL Claude transcripts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11327 [Bug]: Native Chat UI cannot load Codex transcripts from WSL (Transcript unavailable) (Fixes, OPEN); #10639 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12154 fix(native-chat): discover WSL Claude transcripts | Wooseong Kim Community · CONTRIBUTOR | #11327 [Bug]: Native Chat UI cannot load Codex transcripts from WSL (Transcript unavailable) Fixes · OPEN #10639 Title unavailable Unclear · Unknown | Standalone change | ## Summary Resolve WSL-backed Claude Code transcripts in Native Chat instead of leaving desktop and mobile clients on `Transcript unavailable`. The main process now translates hook-reported Linux transcript paths to host | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +442/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2distinct guard when agent foreground cannot be read1 PR · Standalone · Automated release pipeline#
Problem: distinct guard when agent foreground cannot be read.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12946 Guarded sends refuse any agent when the foreground read is unavailable (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13162 fix(runtime): distinct guard when agent foreground cannot be read | BingZ Community · CONTRIBUTOR | #12946 Guarded sends refuse any agent when the foreground read is unavailable Fixes · OPEN | Standalone change | ## Summary - Guarded terminal sends rechecked agent presence, then refused with \`no-agent\` whenever \`getForegroundProcess\` was null. - Pre-v11 daemon sessions and other inspect-unavailable paths return null for the s | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +116/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2do not re-fire task-complete notifications for replayed agent statuses2 PRs · Related · Automated release pipeline#
Problem: do not re-fire task-complete notifications for replayed agent statuses.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Related. Linked issues: #12747 Reconnect replays of cached agent statuses re-fire task-complete notifications (Fixes, OPEN); #13974 Title unavailable (Unclear, Unknown); #14426 Title unavailable (Unclear, Unknown); #14610 Title unavailable (Unclear, Unknown); #12998 Title unavailable (Unclear, Unknown); #12750 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12750 fix(notifications): do not re-fire task-complete notifications for replayed agent statuses | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12747 Reconnect replays of cached agent statuses re-fire task-complete notifications Fixes · OPEN #13974 Title unavailable Unclear · Unknown | Cluster contribution | Fixes #12747 Reconnect replays re-deliver cached agent statuses with `isReplay: true`, but the flag was dropped from the `agentStatus:set` IPC payload, so the renderer treated each replayed `done` as a fresh completion a | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +89/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14635 fix(agent-status): keep the turn identity a disconnect clear removed (STA-3524) | Brennan Benson Core team · MEMBER | #12747 Reconnect replays of cached agent statuses re-fire task-complete notifications Fixes · OPEN #14426 Title unavailable Unclear · Unknown #14610 Title unavailable Unclear · Unknown #12998 Title unavailable Unclear · Unknown #12750 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When Orca loses an SSH connection it throws away everything it knew about the agents on that host. On reconnect the host re-sends ("replays") what it had. Orca had no memory of the turn it just threw away, so a j | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +390/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document terminal send --text as raw PTY bytes2 PRs · Overlapping · Automated release pipeline#
Problem: document terminal send --text as raw PTY bytes.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #14032 [Other]: terminal send --text is a raw byte channel, but nothing says so — integrators conclude Escape cannot be sent (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14037 docs(cli): document terminal send --text as raw PTY bytes | BingZ Community · CONTRIBUTOR | #14032 [Other]: terminal send --text is a raw byte channel, but nothing says so — integrators conclude Escape cannot be sent Fixes · OPEN | Cluster contribution | ## ELI5 `orca terminal send --text` can already send raw control bytes, but the help made its Bash/Zsh examples look portable to every shell. The help now keeps the useful examples while naming the shells that understand | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +62/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14073 docs: clarify terminal send raw text behavior | nyxst4ck Community · FIRST_TIME_CONTRIBUTOR | #14032 [Other]: terminal send --text is a raw byte channel, but nothing says so — integrators conclude Escape cannot be sent Fixes · OPEN | Cluster contribution | ## Summary Clarify that `orca terminal send --text` writes raw bytes to the PTY, including control bytes. Fixes #14032. ## Validation - Ran `git diff --check`. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +1/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drag the native-chat keyboard down with the swipe1 PR · Standalone · Automated release pipeline#
Problem: drag the native-chat keyboard down with the swipe.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15656 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15662 fix(mobile): drag the native-chat keyboard down with the swipe | Brennan Benson Core team · MEMBER | #15656 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +837/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drive the Git contract tests, and ban vi.mock keys that name no real export1 PR · Standalone · Automated release pipeline#
Problem: drive the Git contract tests, and ban vi.mock keys that name no real export.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17222 test: drive the Git contract tests, and ban vi.mock keys that name no real export | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 76 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk77 files, +578/−208. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop a third-party product name from a fit comment1 PR · Standalone · Automated release pipeline#
Problem: drop a third-party product name from a fit comment.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13258 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13259 chore(terminal): drop a third-party product name from a fit comment | Brennan Benson Core team · MEMBER | #13258 Title unavailable Unclear · Unknown | Standalone change | ## Summary A comment in `pane-fit-resize-observer.ts` justified coalescing drag-driven resizes by citing another product by name. The engineering reasoning stands on its own; the attribution does not belong in shipped so | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +2/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop completion notifications for worktrees the catalog no longer knows1 PR · Standalone · Automated release pipeline#
Problem: drop completion notifications for worktrees the catalog no longer knows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14806 [Bug] Delayed notifications for worktrees already deleted (Fixes, OPEN); #12916 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15001 fix(notifications): drop completion notifications for worktrees the catalog no longer knows | erish Community · CONTRIBUTOR | #14806 [Bug] Delayed notifications for worktrees already deleted Fixes · OPEN #12916 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A worktree is deleted, but Orca still pops an OS notification for it minutes later because the terminal/PTY bookkeeping behind that notification hadn't caught up yet, even though the worktree already vanished fro | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +35/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop unsupported Kimi recipe flags1 PR · Standalone · Automated release pipeline#
Problem: drop unsupported Kimi recipe flags.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14771 Source Control AI: Kimi recipe fails — baked-in `--quiet` flag unknown to kimi-code 0.36.x (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14790 fix(source-control): drop unsupported Kimi recipe flags | BingZ Community · CONTRIBUTOR | #14771 Source Control AI: Kimi recipe fails — baked-in `--quiet` flag unknown to kimi-code 0.36.x Fixes · OPEN | Standalone change | ## ELI5 Orca was starting Kimi with command-line options that current Kimi Code releases do not recognize, so commit-message generation stopped before Kimi could read the prompt. This keeps only the supported prompt and | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +17/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2emit neutral JSON from the managed Codex hook1 PR · Standalone · Automated release pipeline#
Problem: emit neutral JSON from the managed Codex hook.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16356 [Bug]: codex-hook.sh emits no stdout — every Codex session reports "invalid session start/stop hook JSON output" (Fixes, OPEN); #14818 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16439 fix(codex): emit neutral JSON from the managed Codex hook | Max Hsu Community · FIRST_TIME_CONTRIBUTOR | #16356 [Bug]: codex-hook.sh emits no stdout — every Codex session reports "invalid session start/stop hook JSON output" Fixes · OPEN #14818 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Codex refuses any hook whose output isn't JSON. Orca's Codex hook printed nothing, so Codex marked every session start and stop as failed — even though the hook's real work succeeded. This prints `{}` first, whic | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +53/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Enforce complete TypeScript coverage1 PR · Standalone · Automated release pipeline#
Problem: Enforce complete TypeScript coverage.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16532 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16849 Enforce complete TypeScript coverage | Brennan Benson Core team · MEMBER | #16532 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +4798/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2enforce Run-scoped dispatch inspection1 PR · Standalone · Automated release pipeline#
Problem: enforce Run-scoped dispatch inspection.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14898 [Bug]: orchestration.dispatchShow returns another Run's dispatch context without a caller check (Fixes, OPEN); #14891 Title unavailable (Unclear, Unknown); #14892 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14900 fix(orchestration): enforce Run-scoped dispatch inspection | BingZ Community · CONTRIBUTOR | #14898 [Bug]: orchestration.dispatchShow returns another Run's dispatch context without a caller check Fixes · OPEN #14891 Title unavailable Unclear · Unknown #14892 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A terminal in Run A could name a task from Run B and read Run B's dispatch metadata. Latest `main` still reproduces this: the byte-identical 12-case oracle passes only 2 cases. This PR makes the host verify the r | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +1155/−126. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2exit Windows hook guards instead of draining a foreign stdin1 PR · Standalone · Automated release pipeline#
Problem: exit Windows hook guards instead of draining a foreign stdin.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11549 [Bug]: Codex managed hook leaves persistent cmd.exe windows outside Orca on Windows (Fixes, CLOSED); #8430 Title unavailable (Unclear, Unknown); #9480 Title unavailable (Unclear, Unknown); #0 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12069 fix(agent-hooks): exit Windows hook guards instead of draining a foreign stdin | Neil Core team · MEMBER | #11549 [Bug]: Codex managed hook leaves persistent cmd.exe windows outside Orca on Windows Fixes · CLOSED #8430 Title unavailable Unclear · Unknown #9480 Title unavailable Unclear · Unknown #0 Title unavailable Unclear · Unknown | Standalone change | Fixes #11549 ## ELI5 On Windows, Orca installs little script files that AI coding tools run whenever something happens. Because those scripts are installed for the whole user account, tools launched *outside* Orca run th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +218/−77. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2expand symlinked directories that point outside the workspace1 PR · Standalone · Automated release pipeline#
Problem: expand symlinked directories that point outside the workspace.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13246 fix(file-explorer): expand symlinked directories that point outside the workspace | Zhao Zhen Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary A symlink inside a workspace could never be expanded in the File Explorer when it pointed outside the workspace roots — which is the normal case for links like `lems-web -> ../Hex/react-local-ems`. Clicking th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +239/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2extend GPU software-render fallback to Linux desktop1 PR · Standalone · Automated release pipeline#
Problem: extend GPU software-render fallback to Linux desktop.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14858 fix(linux): extend GPU software-render fallback to Linux desktop | s546126 Community · CONTRIBUTOR | None found | Standalone change | On Linux without a usable GPU, Chromium's GPU child process crashes repeatedly (ContextResult::kTransientFailure / GpuControl.CreateCommandBuffer), eventually taking the renderer down with it. The existing Windows-only f | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +130/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2extract WorktreeList into focused modules1 PR · Standalone · Automated release pipeline#
Problem: extract WorktreeList into focused modules.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14443 refactor(sidebar): extract WorktreeList into focused modules | Jinjing Core team · MEMBER | None found | Standalone change | ## Problem WorktreeList.tsx has grown to ~2000 lines, mixing concerns across hooks, utilities, components, and state logic. This makes the file hard to navigate, test, and maintain. ## Solution Extract WorktreeList into | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk40 files, +6745/−4856. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2failed worktree setup left the gated agent terminal silently waiting for two hours1 PR · Standalone · Automated release pipeline#
Problem: failed worktree setup left the gated agent terminal silently waiting for two hours.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16891 fix: failed worktree setup left the gated agent terminal silently waiting for two hours | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +901/−389. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fast-forward a checked-out existing branch inside its new worktree1 PR · Standalone · Automated release pipeline#
Problem: fast-forward a checked-out existing branch inside its new worktree.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15645 [Bug]: worktree create cannot fast-forward a local branch its own new worktree just claimed; branch is left with no upstream (Fixes, OPEN); #15868 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15815 fix(worktree): fast-forward a checked-out existing branch inside its new worktree | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15645 [Bug]: worktree create cannot fast-forward a local branch its own new worktree just claimed; branch is left with no upstream Fixes · OPEN #15868 Title unavailable Unclear · Unknown | Standalone change | ## Summary **What** `addWorktree`'s checkout-existing-branch path now runs the local-base refresh **after** the worktree add, reusing the existing `refreshLocalBaseRefForWorktreeCreate` machinery unchanged. **Why** #1564 | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +56/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fence mobile PR merges by exact head1 PR · Standalone · Automated release pipeline#
Problem: fence mobile PR merges by exact head.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12668 fix(github): fence mobile PR merges by exact head | zerator01 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Add optional `expectedHeadOid` to `github.mergePR`. - Validate a full 40-character GitHub object ID at the RPC boundary. - Pass it through the runtime to `gh pr merge --match-head-commit`. - Advertise `githu | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +499/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fence navigation on terminal host loss1 PR · Standalone · Automated release pipeline#
Problem: fence navigation on terminal host loss.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14753 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14754 fix(browser): fence navigation on terminal host lossDraft | Jinwoo Hong Core team · MEMBER | #14753 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +479/−94. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fetch linked PR and sub-issues progress field values1 PR · Standalone · Automated release pipeline#
Problem: fetch linked PR and sub-issues progress field values.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12649 [Bug] Linked pull requests" and "Sub-issues progress" columns always render empty (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12821 fix(github-project): fetch linked PR and sub-issues progress field values | Wooseong Kim Community · CONTRIBUTOR | #12649 [Bug] Linked pull requests" and "Sub-issues progress" columns always render empty Fixes · OPEN | Standalone change | ## Description Fetch and render ProjectV2 linked pull-request and sub-issues progress field values so those columns are no longer always blank. ## Focused fix - In scope: GraphQL fragments, normalizers, cell render for L | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +95/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2find and use the 1Password SSH agent (no more passphrase prompts for agent-held keys)1 PR · Standalone · Automated release pipeline#
Problem: find and use the 1Password SSH agent (no more passphrase prompts for agent-held keys).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12850 Title unavailable (Unclear, Unknown); #11707 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12765 fix(ssh): find and use the 1Password SSH agent (no more passphrase prompts for agent-held keys) | Vincent Colombo Community · FIRST_TIME_CONTRIBUTOR | #12850 Title unavailable Unclear · Unknown #11707 Title unavailable Unclear · Unknown | Standalone change | ## User-visible change Users who keep their SSH keys in the 1Password SSH agent no longer get passphrase prompts when Orca connects to remote hosts. GUI-launched Orca inherits launchd's environment on macOS, so `SSH_AUTH | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +621/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2finish the Windows command-override tokenizer fix1 PR · Standalone · Automated release pipeline#
Problem: finish the Windows command-override tokenizer fix.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14984 Title unavailable (Unclear, Unknown); #15014 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15051 fix(commit-message): finish the Windows command-override tokenizer fix | Neil Core team · MEMBER | #14984 Title unavailable Unclear · Unknown #15014 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +252/−35. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix Codex automation completion ordering1 PR · Standalone · Automated release pipeline#
Problem: Fix Codex automation completion ordering.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16975 Title unavailable (Unclear, Unknown); #16751 Title unavailable (Unclear, Unknown); #16863 Title unavailable (Unclear, Unknown); #16948 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16801 Fix Codex automation completion ordering | Brennan Benson Core team · MEMBER | #16975 Title unavailable Unclear · Unknown #16751 Title unavailable Unclear · Unknown #16863 Title unavailable Unclear · Unknown #16948 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +1775/−211. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix GitLab task resolution for sole nonstandard remotes1 PR · Standalone · Automated release pipeline#
Problem: Fix GitLab task resolution for sole nonstandard remotes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13816 [Bug]: GitLab task source only resolves projects via a remote named origin/upstream — silent empty issue list, ignores Orca's own stored gitRemoteIdentity.remoteName (Fixes, OPEN); #13886 Title unavailable (Unclear, Unknown); #13817 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13936 Fix GitLab task resolution for sole nonstandard remotes | Jinwoo Hong Core team · MEMBER | #13816 [Bug]: GitLab task source only resolves projects via a remote named origin/upstream — silent empty issue list, ignores Orca's own stored gitRemoteIdentity.remoteName Fixes · OPEN #13886 Title unavailable Unclear · Unknown #13817 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 GitLab Tasks used to look only for remotes literally named `upstream` or `origin`. A repository with one valid GitLab remote named `myremote` now resolves that project too, without changing which project wins whe | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1052/−131. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix macOS updater relaunch races across profiles1 PR · Standalone · Automated release pipeline#
Problem: Fix macOS updater relaunch races across profiles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9094 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14736 Fix macOS updater relaunch races across profiles | Jinwoo Hong Core team · MEMBER | #9094 Title unavailable Unclear · Unknown | Standalone change | ## Summary - persist a profile-independent, durable macOS install handoff before invoking Squirrel - reject installs that ShipIt cannot complete because another Orca main process is already running - stop racing old-vers | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +900/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix native chat IME composition lag1 PR · Standalone · Automated release pipeline#
Problem: Fix native chat IME composition lag.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15547 Fix native chat IME composition lag | liyang Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Prevent native chat preedit text from flowing into draft state during IME composition. - Keep composition start/end propagation intact so the parent composer still guards key handling and adopts the committe | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +251/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix remote agent terminal startup colors1 PR · Standalone · Automated release pipeline#
Problem: Fix remote agent terminal startup colors.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13865 Fix remote agent terminal startup colors | Garrett Johnson Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Forward the renderer terminal palette through host-authority agent create and resume RPCs so headless runtimes answer Codex startup OSC 10/11 queries with the selected theme instead of a light fallback. - Ad | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +97/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix retry ownership for rejected SSH split cleanup1 PR · Standalone · Automated release pipeline#
Problem: Fix retry ownership for rejected SSH split cleanup.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14101 Fix retry ownership for rejected SSH split cleanup | Jinwoo Hong Core team · MEMBER | None found | Standalone change | Addresses STA-4023. ## Problem and invariant A split can spawn an SSH PTY and then lose the source-pane persistence compare-and-swap. If immediate remote shutdown also fails, main previously deleted its routing owner, su | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +1432/−70. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix terminal federation recovery backoff1 PR · Standalone · Automated release pipeline#
Problem: Fix terminal federation recovery backoff.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14105 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14336 Fix terminal federation recovery backoffDraft | Jinwoo Hong Core team · MEMBER | #14105 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 A retired remote worker could make Orca knock on the same dead door every second forever. This change makes Orca remember recovery failures: proven permanent destinations stop retrying, while outages and unknown | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +737/−81. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2flush queued application input after IME commit1 PR · Standalone · Automated release pipeline#
Problem: flush queued application input after IME commit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12341 Title unavailable (Unclear, Unknown); #13128 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12436 fix(xterm): flush queued application input after IME commitDraft | Neil Core team · MEMBER | #12341 Title unavailable Unclear · Unknown #13128 Title unavailable Unclear · Unknown | Standalone change | ## Summary - flush application input queued before a native `insertText` commit - release application input queued during xterm's late-duplicate window - delete dead `_dataAlreadySent` bookkeeping This is separated from | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +112/−63. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2follow output when a pinned scroll anchor is trimmed away1 PR · Standalone · Automated release pipeline#
Problem: follow output when a pinned scroll anchor is trimmed away.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9079 Title unavailable (Unclear, Unknown); #11753 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12678 fix(terminal): follow output when a pinned scroll anchor is trimmed away | 5unnyWind Community · FIRST_TIME_CONTRIBUTOR | #9079 Title unavailable Unclear · Unknown #11753 Title unavailable Unclear · Unknown | Standalone change | ## Summary A terminal pane that the user had scrolled up in could suddenly jump to the very top of its scrollback during a long agent session, then keep snapping back there whenever the mouse moved over the pane. The pan | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +29/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2forward the client's resolved agent args to paired hosts1 PR · Standalone · Automated release pipeline#
Problem: forward the client's resolved agent args to paired hosts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15373 [Bug]: Remote Orca Server does not respect client's YOLO/Manual settings (Fixes, OPEN); #15867 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15611 fix(runtime): forward the client's resolved agent args to paired hosts | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15373 [Bug]: Remote Orca Server does not respect client's YOLO/Manual settings Fixes · OPEN #15867 Title unavailable Unclear · Unknown | Standalone change | ## Summary **What** `launchAgentInWebHostTab` now receives the client-resolved `effectiveAgentArgs` (empty string included) instead of the raw `agentArgs` launch parameter, so an agent quick-launch against a paired headl | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +31/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2frame alt-screen pastes when bracketed paste is on1 PR · Standalone · Automated release pipeline#
Problem: frame alt-screen pastes when bracketed paste is on.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13332 [Bug]: #5358 regression — long paste delivers only the final 1024-byte chunk; second paste appends the same fragment instead of expanding (Fixes, OPEN); #5358 Title unavailable (Unclear, Unknown); #10416 Title unavailable (Unclear, Unknown); #12502 Title unavailable (Unclear, Unknown); #14888 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13553 fix(mobile): frame alt-screen pastes when bracketed paste is on | Brennan Benson Core team · MEMBER | #13332 [Bug]: #5358 regression — long paste delivers only the final 1024-byte chunk; second paste appends the same fragment instead of expanding Fixes · OPEN #5358 Title unavailable Unclear · Unknown #10416 Title unavailable Unclear · Unknown #12502 Title unavailable Unclear · Unknown #14888 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +761/−95. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2gate bundled zod runtime integrity (STA-4316)1 PR · Standalone · Automated release pipeline#
Problem: gate bundled zod runtime integrity (STA-4316).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14502 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14587 fix(packaging): gate bundled zod runtime integrity (STA-4316) | OrcaWin Unknown · COLLABORATOR | #14502 Title unavailable Unclear · Unknown | Standalone change | ## Summary\n- add a post-pack oracle that requires representative public zod exports from the actual packaged resources tree\n- run it after runtime pruning for Windows, macOS, and Linux packages\n- add regression covera | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +87/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2gate OutputSpan frames behind a negotiated capability (STA-3482)1 PR · Standalone · Automated release pipeline#
Problem: gate OutputSpan frames behind a negotiated capability (STA-3482).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9500 Title unavailable (Unclear, Unknown); #11005 Title unavailable (Unclear, Unknown); #12834 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12788 fix(terminal): gate OutputSpan frames behind a negotiated capability (STA-3482)Draft | Jinwoo Hong Core team · MEMBER | #9500 Title unavailable Unclear · Unknown #11005 Title unavailable Unclear · Unknown #12834 Title unavailable Unclear · Unknown | Standalone change | Fixes STA-3482. ## Symptom: terminal output silently missing on mobile `OutputSpan` (opcode 15) was emitted on the legacy binary stream path with **no capability gate**. Mobile is the only consumer of `terminal.subscribe | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1071/−56. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2guard Add Project dialog dismissal while cloning1 PR · Standalone · Automated release pipeline#
Problem: guard Add Project dialog dismissal while cloning.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14265 Add Project: stray backdrop click or ESC during a long clone cancels the clone (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14266 fix(renderer): guard Add Project dialog dismissal while cloning | StillTogether Community · FIRST_TIME_CONTRIBUTOR | #14265 Add Project: stray backdrop click or ESC during a long clone cancels the clone Fixes · OPEN | Standalone change | ## ELI5 Cloning a big repo takes a while. If you accidentally click outside the Add Project dialog (or press ESC) while it's cloning, the dialog treats that as "cancel" and kills the clone. This PR makes those accidental | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +115/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2heal stuck permission wait after a denied Claude tool1 PR · Standalone · Automated release pipeline#
Problem: heal stuck permission wait after a denied Claude tool.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15078 fix(agent-hooks): heal stuck permission wait after a denied Claude tool | Alex Shan Community · CONTRIBUTOR | None found | Standalone change | ## Summary Denying a Claude Code permission request (Esc / "No") emits **no hook event**, so the pane's agent status stayed stuck in `waiting` ("needs permission") until the next prompt or the 30-minute staleness cutoff. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +737/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2hide bare repository backing stores from workspace list1 PR · Standalone · Automated release pipeline#
Problem: hide bare repository backing stores from workspace list.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16553 [Bug]: Bare repository backing stores are shown as primary workspaces in the sidebar (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16561 fix(sidebar): hide bare repository backing stores from workspace list | Wooseong Kim Community · CONTRIBUTOR | #16553 [Bug]: Bare repository backing stores are shown as primary workspaces in the sidebar Fixes · OPEN | Standalone change | ## Description Bare `GIT_COMMON_DIR` backing stores were rendered as primary sidebar workspaces because `git worktree list` reports them as the main worktree. The sidebar visibility pipeline now excludes `isBare` rows an | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +43/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2highlight the whole .env.* family as ini2 PRs · Overlapping · Automated release pipeline#
Problem: highlight the whole .env.* family as ini.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #13028 [Bug]: Non-standard .env files (.env.functions.local, .env.staging, …) render as plaintext (Fixes, OPEN); #11256 Title unavailable (Unclear, Unknown); #13239 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13029 fix(editor): highlight the whole .env.* family as ini | Willy Dallas Community · FIRST_TIME_CONTRIBUTOR | #13028 [Bug]: Non-standard .env files (.env.functions.local, .env.staging, …) render as plaintext Fixes · OPEN #11256 Title unavailable Unclear · Unknown #13239 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary Fixes #13028 `.env.functions.local`, `.env.staging`, and other non-standard dotenv names rendered as plaintext because language detection only exact-matched four names (`.env`, `.env.local`, `.env.development` | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +57/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13239 fix(editor): detect open-ended dotenv filenames | Wooseong Kim Community · CONTRIBUTOR | #13028 [Bug]: Non-standard .env files (.env.functions.local, .env.staging, …) render as plaintext Fixes · OPEN | Cluster contribution | ## Description Dotenv files with scoped names such as `.env.functions.local`, `.env.staging`, and `.env.test.example` now receive INI syntax highlighting when no more specific language mapping applies. The desktop and mo | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +35/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2hold route policy through page retirement1 PR · Standalone · Automated release pipeline#
Problem: hold route policy through page retirement.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14517 Title unavailable (Unclear, Unknown); #14471 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14518 feat(browser): hold route policy through page retirementDraft | Jinwoo Hong Core team · MEMBER | #14517 Title unavailable Unclear · Unknown #14471 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +325/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2hold the fabricated permission BEL for the Codex quiet window1 PR · Standalone · Automated release pipeline#
Problem: hold the fabricated permission BEL for the Codex quiet window.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13600 [Bug]: Codex “Approve for me” can still trigger false attention notifications after #8519 (Fixes, OPEN); #8519 Title unavailable (Unclear, Unknown); #11046 Title unavailable (Unclear, Unknown); #8387 Title unavailable (Unclear, Unknown); #13991 Title unavailable (Unclear, Unknown); #10947 Title unavailable (Unclear, Unknown); #11174 Title unavailable (Unclear, Unknown); #14611 Title unavailable (Unclear, Unknown); #14626 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14715 fix(codex): hold the fabricated permission BEL for the Codex quiet window | Brennan Benson Core team · MEMBER | #13600 [Bug]: Codex “Approve for me” can still trigger false attention notifications after #8519 Fixes · OPEN #8519 Title unavailable Unclear · Unknown #11046 Title unavailable Unclear · Unknown #8387 Title unavailable Unclear · Unknown #13991 Title unavailable Unclear · Unknown #10947 Title unavailable Unclear · Unknown #11174 Title unavailable Unclear · Unknown #14611 Title unavailable Unclear · Unknown #14626 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Codex pauses to ask permission, Orca fakes a terminal "ding" so the pane lights up. Under **"Approve for me"** Codex answers its own question a moment later — but the ding had already fired, so you got a fal | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +378/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2honor OS certificate trust for first-party traffic1 PR · Standalone · Automated release pipeline#
Problem: honor OS certificate trust for first-party traffic.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13736 Title unavailable (Unclear, Unknown); #13735 Title unavailable (Unclear, Unknown); #16399 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15208 fix(cloud): honor OS certificate trust for first-party traffic | Jinwoo Hong Core team · MEMBER | #13736 Title unavailable Unclear · Unknown #13735 Title unavailable Unclear · Unknown #16399 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +418/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ignore non-absolute env overrides for agent scan roots1 PR · Standalone · Automated release pipeline#
Problem: ignore non-absolute env overrides for agent scan roots.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13082 AI Vault: six env-derived scan roots accept relative values and walk the process cwd unbounded (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13118 fix(ai-vault): ignore non-absolute env overrides for agent scan roots | manuaudio Community · CONTRIBUTOR | #13082 AI Vault: six env-derived scan roots accept relative values and walk the process cwd unbounded Fixes · OPEN | Standalone change | Closes #13082. ## Summary A typo'd or relative agent-home environment variable no longer turns AI Vault session discovery into an unbounded walk of the disk. Six scan roots took a directory straight from an environment v | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +83/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Improve Agent Session History search: rg scopes and AI rank1 PR · Standalone · Automated release pipeline#
Problem: Improve Agent Session History search: rg scopes and AI rank.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #1234 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15354 Improve Agent Session History search: rg scopes and AI rank | s546126 Community · CONTRIBUTOR | #1234 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The right-sidebar Agent Session History search box now actually searches the transcript files. Type a word and Orca runs the real `rg` binary over the session logs it already discovered, instead of only matching | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk81 files, +7092/−795. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2infer worker identity in preambles1 PR · Standalone · Automated release pipeline#
Problem: infer worker identity in preambles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14570 Injected orchestration preambles can produce hybrid worker sender handles (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14567 fix(orchestration): infer worker identity in preambles | Jacky Zhang Community · FIRST_TIME_CONTRIBUTOR | #14570 Injected orchestration preambles can produce hybrid worker sender handles Fixes · OPEN | Standalone change | ## ELI5 Orca currently asks workers to copy a long terminal ID into lifecycle commands. When two similar IDs appear in the same prompt, a worker can splice them together and Orca correctly rejects the result. This change | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +22/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2install a selected agent from the onboarding step1 PR · Standalone · Automated release pipeline#
Problem: install a selected agent from the onboarding step.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14122 feat(onboarding): install a selected agent from the onboarding step | JTL Growth Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## The gap When no agent is on PATH, onboarding ends the thread rather than closing it. It names the selected agent, says it *"isn't on your PATH yet"*, and offers a link to install instructions — so a new user has to le | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +96/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a DA1 answerer for parked panes with raw-byte sidecars1 PR · Standalone · Automated release pipeline#
Problem: keep a DA1 answerer for parked panes with raw-byte sidecars.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14002 fix(terminal): keep a DA1 answerer for parked panes with raw-byte sidecars | Neil Core team · MEMBER | None found | Standalone change | ## ELI5 fish asks the terminal "what are you?" (DA1) every single time it draws a prompt, and it refuses to draw until someone answers — waiting up to 10 seconds. In a parked tab there is no visible terminal to answer, s | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +1404/−237. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a nested child hook's model off the fenced parent row1 PR · Standalone · Automated release pipeline#
Problem: keep a nested child hook's model off the fenced parent row.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13602 fix(agent-status): keep a nested child hook's model off the fenced parent row | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary When Claude runs \`codex exec\` (or any agent CLI nests another), the child's hooks fire on the inherited pane key. The identity fence already keeps the parent's \`agentType\`, but the child's **model** rode t | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +195/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep a quick command queued until its own spawn takes it (STA-4876)1 PR · Standalone · Automated release pipeline#
Problem: keep a quick command queued until its own spawn takes it (STA-4876).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15531 fix(terminal): keep a quick command queued until its own spawn takes it (STA-4876)Draft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +480/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep acknowledged completions in the Done column1 PR · Standalone · Automated release pipeline#
Problem: keep acknowledged completions in the Done column.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12168 Title unavailable (Unclear, Unknown); #11042 Title unavailable (Unclear, Unknown); #16201 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13780 fix(dashboard): keep acknowledged completions in the Done column | Jin Won, Park Community · FIRST_TIME_CONTRIBUTOR | #12168 Title unavailable Unclear · Unknown #11042 Title unavailable Unclear · Unknown #16201 Title unavailable Unclear · Unknown | Standalone change | ## Summary Agents that finish while you are watching them disappear from the Agent Dashboard instead of landing in **Done**. `buildDashboardSnapshot` chose each card's column with `dashboardBucketForDotState(dashboardCar | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +58/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep agent rows ordered by their session start once state history wraps1 PR · Standalone · Automated release pipeline#
Problem: keep agent rows ordered by their session start once state history wraps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13847 Agents list: manual order jumps when an agent receives new activity (Fixes, OPEN); #14284 Title unavailable (Unclear, Unknown); #14126 Title unavailable (Unclear, Unknown); #14084 Title unavailable (Unclear, Unknown); #14486 Title unavailable (Unclear, Unknown); #13776 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14654 fix(sidebar): keep agent rows ordered by their session start once state history wraps | Brennan Benson Core team · MEMBER | #13847 Agents list: manual order jumps when an agent receives new activity Fixes · OPEN #14284 Title unavailable Unclear · Unknown #14126 Title unavailable Unclear · Unknown #14084 Title unavailable Unclear · Unknown #14486 Title unavailable Unclear · Unknown #13776 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Each agent row in the sidebar is ordered by "when this agent session started". That start time was read off the agent's state-transition log — but that log is a rolling window that only keeps the last 20 entries. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +253/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep angle brackets inside consecutive code fences2 PRs · Overlapping · Automated release pipeline#
Problem: keep angle brackets inside consecutive code fences.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #13307 [Bug]: Rich editor encodes `<>` placeholders inside fenced code blocks into ORCA_RICH_MD transport tokens (Fixes, OPEN); #13609 Title unavailable (Unclear, Unknown); #13566 Title unavailable (Unclear, Unknown); #13710 Title unavailable (Unclear, Unknown); #13692 Title unavailable (Unclear, Unknown); #13536 Title unavailable (Unclear, Unknown); #13572 Title unavailable (Unclear, Unknown); #8072 Title unavailable (Unclear, Unknown); #13237 Title unavailable (Unclear, Unknown); #13570 Title unavailable (Unclear, Unknown); #13561 Title unavailable (Unclear, Unknown); #13255 Title unavailable (Unclear, Unknown); #13131 Title unavailable (Unclear, Unknown); #13919 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13691 fix(editor): keep angle brackets inside consecutive code fences | BingZ Community · CONTRIBUTOR | #13307 [Bug]: Rich editor encodes `<>` placeholders inside fenced code blocks into ORCA_RICH_MD transport tokens Fixes · OPEN #13609 Title unavailable Unclear · Unknown #13566 Title unavailable Unclear · Unknown #13710 Title unavailable Unclear · Unknown #13692 Title unavailable Unclear · Unknown #13536 Title unavailable Unclear · Unknown #13572 Title unavailable Unclear · Unknown #8072 Title unavailable Unclear · Unknown #13237 Title unavailable Unclear · Unknown #13570 Title unavailable Unclear · Unknown #13561 Title unavailable Unclear · Unknown #13255 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Rich Markdown must treat everything inside a fenced code block as code. Previously, a line that merely started with the active fence delimiter could close the block even when code followed it, allowing later text | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +242/−145. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13842 fix(rich-editor): consume closing fence line to prevent span bridging across fences | LavyaT Community · FIRST_TIME_CONTRIBUTOR | #13307 [Bug]: Rich editor encodes `<>` placeholders inside fenced code blocks into ORCA_RICH_MD transport tokens Fixes · OPEN #13131 Title unavailable Unclear · Unknown #13919 Title unavailable Unclear · Unknown | Cluster contribution | ## What Fixes #13307: Rich editor encodes `<>` placeholders inside fenced code blocks into ORCA_RICH_MD transport tokens. Two consecutive fenced blocks caused every even fence to become a spurious inline-code-span opener | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +75/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep bold distinct when font weight is 600+1 PR · Standalone · Automated release pipeline#
Problem: keep bold distinct when font weight is 600+.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14175 fix(terminal): keep bold distinct when font weight is 600+ | Brennan Benson Core team · MEMBER | None found | Standalone change | ## ELI5 Turning the terminal Font Weight slider up used to make bold and regular text look the same on the default Mac font. Bold is now kept as a separate face whenever the font can still show one. ## What Changed `reso | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +351/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep CJK panes from freezing on a half-built glyph atlas1 PR · Standalone · Automated release pipeline#
Problem: keep CJK panes from freezing on a half-built glyph atlas.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13765 fix(terminal): keep CJK panes from freezing on a half-built glyph atlas | Rayim Community · CONTRIBUTOR | None found | Standalone change | # Fix: CJK terminal panes garble mid-screen and stay garbled until a window resize ## User-visible change On panes rendering Hangul/Kana/Han-heavy output (e.g. Korean CLI agents, CJK build logs), glyphs would garble mid- | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +347/−99. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep client tab-group ratios on remote host snapshots1 PR · Standalone · Automated release pipeline#
Problem: keep client tab-group ratios on remote host snapshots.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13218 [Bug]: Tab group split ratio reverts to the host's layout on a remote runtime environment (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13224 fix(session): keep client tab-group ratios on remote host snapshots | BingZ Community · CONTRIBUTOR | #13218 [Bug]: Tab group split ratio reverts to the host's layout on a remote runtime environment Fixes · OPEN | Standalone change | ## ELI5 A remote client can resize its tab-group divider without the next host snapshot snapping it back. The host still controls which groups exist; each client keeps its own window geometry when it already lays out eve | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +148/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep Ctrl-W in Git Bash terminals1 PR · Standalone · Automated release pipeline#
Problem: keep Ctrl-W in Git Bash terminals.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13015 [Bug]: Ctrl+W closes tab in Windows Git Bash when "Terminal first" is enabled (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13232 fix(windows): keep Ctrl-W in Git Bash terminals | Wooseong Kim Community · CONTRIBUTOR | #13015 [Bug]: Ctrl+W closes tab in Windows Git Bash when "Terminal first" is enabled Fixes · OPEN | Standalone change | ## Description On native Windows, Git Bash now receives physical Ctrl+W when the terminal-first shortcut policy is enabled instead of Orca closing the active tab. The exception is fail-closed: it requires an active termi | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +445/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep direct-SSH projects when a cold start merges the local catalog1 PR · Standalone · Automated release pipeline#
Problem: keep direct-SSH projects when a cold start merges the local catalog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15112 [Bug]: Create New Workspace project picker is empty after sleep/wake — SSH host connection lost and project not selectable (Fixes, OPEN); #8268 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15115 fix(renderer): keep direct-SSH projects when a cold start merges the local catalog | Vlad Rafeev Community · FIRST_TIME_CONTRIBUTOR | #15112 [Bug]: Create New Workspace project picker is empty after sleep/wake — SSH host connection lost and project not selectable Fixes · OPEN #8268 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Orca starts up (or refreshes its project list after the Mac wakes from sleep), it was accidentally throwing away projects that live only on an SSH machine. The app still showed them in Settings, but the "Cre | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +126/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep draining a pty whose client has gone1 PR · Standalone · Automated release pipeline#
Problem: keep draining a pty whose client has gone.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15761 fix(relay): keep draining a pty whose client has gone | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +590/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep failed local/WSL scans non-authoritative1 PR · Standalone · Automated release pipeline#
Problem: keep failed local/WSL scans non-authoritative.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14003 Failed local/WSL worktree discovery can publish an authoritative empty catalog (Fixes, OPEN); #13556 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14183 fix(worktrees): keep failed local/WSL scans non-authoritative | OrcaWin Unknown · COLLABORATOR | #14003 Failed local/WSL worktree discovery can publish an authoritative empty catalog Fixes · OPEN #13556 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If Git or WSL fails while Orca is listing worktrees, Orca used to treat that as "this repo has no worktrees" and wipe the sidebar. Now a failed scan is treated as "I don't know," so the last known worktrees, tabs | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +533/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep folder workspaces on execution host1 PR · Standalone · Automated release pipeline#
Problem: keep folder workspaces on execution host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15404 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15685 fix(sidebar): keep folder workspaces on execution hostDraft | Jinwoo Hong Core team · MEMBER | #15404 Title unavailable Unclear · Unknown | Standalone change | ## Summary - keep runtime-owned folder workspaces grouped and routed by `executionHostId` - preserve legacy direct-SSH `connectionId` fallback and use the focused/default host only when neither owner exists - share one r | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk62 files, +2305/−328. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep gitless selected folders1 PR · Standalone · Automated release pipeline#
Problem: keep gitless selected folders.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13734 fix(workspaces): keep gitless selected folders | J-token Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 If you opened an ordinary folder that happens to sit somewhere inside a git repository, Orca silently opened the parent repository instead — the folder you actually picked was thrown away. Now Orca only treats yo | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +181/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep headless runtime alive on desktop Cmd+Q1 PR · Standalone · Automated release pipeline#
Problem: keep headless runtime alive on desktop Cmd+Q.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15537 [Bug]: macOS — ⌘Q on a serve-hosted desktop window kills the headless runtime (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15560 fix(serve): keep headless runtime alive on desktop Cmd+Q | Wooseong Kim Community · CONTRIBUTOR | #15537 [Bug]: macOS — ⌘Q on a serve-hosted desktop window kills the headless runtime Fixes · OPEN | Standalone change | ## Description On macOS, ⌘Q on a desktop window hosted by `orca serve` no longer tears down the headless runtime or drops paired remotes. `shouldQuitWhenAllWindowsClosed` already keeps serve mode alive for window close. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +66/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep heartbeats from waking coordinators1 PR · Standalone · Automated release pipeline#
Problem: keep heartbeats from waking coordinators.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13235 fix(orchestration): keep heartbeats from waking coordinatorsDraft | portrah Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - keep valid orchestration heartbeats out of push-on-idle wake batches - preserve rejected heartbeats as high-priority coordinator notifications - leave valid heartbeat rows unread so explicit heartbeat checks | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +65/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep hookless agents sendable via foreground process proof1 PR · Standalone · Automated release pipeline#
Problem: keep hookless agents sendable via foreground process proof.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14798 "Send notes to an agent" menu omits running agents (30-min hook staleness + current-worktree-only filter) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14810 fix(agent-send): keep hookless agents sendable via foreground process proof | Vincent Community · FIRST_TIME_CONTRIBUTOR | #14798 "Send notes to an agent" menu omits running agents (30-min hook staleness + current-worktree-only filter) Fixes · OPEN | Standalone change | ## ELI5 Orca decides "is there an agent in this pane I can send notes to?" by looking at the messages the agent sends it (hooks) and at the pane's title. An agent that has been running a long time stops sending hooks, an | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +218/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep image-path pastes tokenized after typed text1 PR · Standalone · Automated release pipeline#
Problem: keep image-path pastes tokenized after typed text.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9732 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12715 fix(terminal): keep image-path pastes tokenized after typed text | 5unnyWind Community · FIRST_TIME_CONTRIBUTOR | #9732 Title unavailable Unclear · Unknown | Standalone change | Cursor CLI only turns a pasted image path into `[Image #N]` when the path is a separate token. Prefix a space so prior prompt text cannot glue onto the path and leave a raw `orca-paste-*.png` string in the input. ## Summ | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +56/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep interrupted Stops working while background tasks run1 PR · Standalone · Automated release pipeline#
Problem: keep interrupted Stops working while background tasks run.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12382 [Bug]: Interrupted Stop discards running background_tasks, marking live workflows and shells as done (Fixes, OPEN); #11838 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12724 fix(agent-hooks): keep interrupted Stops working while background tasks run | Brennan Benson Core team · MEMBER | #12382 [Bug]: Interrupted Stop discards running background_tasks, marking live workflows and shells as done Fixes · OPEN #11838 Title unavailable Unclear · Unknown | Standalone change | ## Summary An interrupted Claude turn no longer discards evidence that background work is still running, so a pane holding a live Workflow or backgrounded shell stays `working` instead of flipping to `done`. Claude emits | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +85/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep OMP wrapper parse-safe under zsh global aliases1 PR · Standalone · Automated release pipeline#
Problem: keep OMP wrapper parse-safe under zsh global aliases.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14208 [Bug]: zsh global aliases break headless shell wrapper — 'parse error near '>'&''' in __orca_omp_should_skip_extension (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14215 fix(shell): keep OMP wrapper parse-safe under zsh global aliases | BingZ Community · CONTRIBUTOR | #14208 [Bug]: zsh global aliases break headless shell wrapper — 'parse error near '>'&''' in __orca_omp_should_skip_extension Fixes · OPEN | Standalone change | ## Summary User zsh global aliases whose name is a literal token in Orca's generated `shell-ready/zsh` wrapper (`--help`, `--version`) expand during interactive parse. HyDE's `alias -g -- --help='--help 2>&1 | bat …'` tu | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +51/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep one mounted session screen per worktree (supersedes #17068)1 PR · Standalone · Automated release pipeline#
Problem: keep one mounted session screen per worktree (supersedes #17068).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17068 Title unavailable (Unclear, Unknown); #16997 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17098 fix(mobile): keep one mounted session screen per worktree (supersedes #17068) | Brennan Benson Core team · MEMBER | #17068 Title unavailable Unclear · Unknown #16997 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +940/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep orchestration check help side-effect free1 PR · Standalone · Automated release pipeline#
Problem: keep orchestration check help side-effect free.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12985 [Bug]: `orca orchestration check --help` runs a real mailbox check instead of printing usage (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12996 fix(ssh): keep orchestration check help side-effect free | Wooseong Kim Community · CONTRIBUTOR | #12985 [Bug]: `orca orchestration check --help` runs a real mailbox check instead of printing usage Fixes · OPEN | Standalone change | ## Description Prevent the SSH legacy fallback from executing `orchestration check` when a user only asks for help. ## Focused fix - In scope: return the existing command usage before legacy RPC dispatch for `orca orches | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +113/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep owned agent panes visible when their title carries no agent frame (#14464)1 PR · Standalone · Automated release pipeline#
Problem: keep owned agent panes visible when their title carries no agent frame (#14464).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14464 [Bug]: Keep running Codex session tabs visible across Orca updates (Fixes, OPEN); #10258 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14650 fix(sidebar): keep owned agent panes visible when their title carries no agent frame (#14464) | OrcaWin Unknown · COLLABORATOR | #14464 [Bug]: Keep running Codex session tabs visible across Orca updates Fixes · OPEN #10258 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca decides "is this terminal an agent?" mostly by reading the terminal's title. Codex doesn't put its name in the title on Windows — it names the pane after the worktree (`gh-13695`), so Orca didn't recognise i | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +132/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Keep relay completion evidence live/unverifiable/exited, never coerced1 PR · Standalone · Automated release pipeline#
Problem: Keep relay completion evidence live/unverifiable/exited, never coerced.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16900 Title unavailable (Unclear, Unknown); #15420 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16926 Keep relay completion evidence live/unverifiable/exited, never coerced | Brennan Benson Core team · MEMBER | #16900 Title unavailable Unclear · Unknown #15420 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 13 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +2132/−488. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep retired names on an RPC error and route the host's created name (STA-4479, STA-4480)1 PR · Standalone · Automated release pipeline#
Problem: keep retired names on an RPC error and route the host's created name (STA-4479, STA-4480).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14350 Title unavailable (Unclear, Unknown); #14917 Title unavailable (Unclear, Unknown); #14919 Title unavailable (Unclear, Unknown); #14924 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14926 fix(mobile): keep retired names on an RPC error and route the host's created name (STA-4479, STA-4480) | Brennan Benson Core team · MEMBER | #14350 Title unavailable Unclear · Unknown #14917 Title unavailable Unclear · Unknown #14919 Title unavailable Unclear · Unknown #14924 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +85/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep session state for worktrees hidden from the sidebar (#15227)1 PR · Standalone · Automated release pipeline#
Problem: keep session state for worktrees hidden from the sidebar (#15227).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15227 [Bug]: Terminals created in worktrees hidden from the sidebar are dropped from session state, stranding live agent PTYs after a restart (Fixes, OPEN); #15313 Title unavailable (Unclear, Unknown); #14918 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15431 fix(session): keep session state for worktrees hidden from the sidebar (#15227) | OrcaWin Unknown · COLLABORATOR | #15227 [Bug]: Terminals created in worktrees hidden from the sidebar are dropped from session state, stranding live agent PTYs after a restart Fixes · OPEN #15313 Title unavailable Unclear · Unknown #14918 Title unavailable Unclear · Unknown | Standalone change | Fixes #15227. ## Repro verdict: reproduced Windows, dev build, isolated profile. A repo with one visible checkout plus a worktree created outside Orca (`git worktree add .claude/worktrees/lane-a`, classified `agent-scrat | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +155/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep system-default auth native when hooks are unavailable1 PR · Standalone · Automated release pipeline#
Problem: keep system-default auth native when hooks are unavailable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13746 [Bug]: System-default Codex can use stale managed credentials when status-hook trust is unavailable (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13755 fix(codex): keep system-default auth native when hooks are unavailable | Langning Zhang Community · CONTRIBUTOR | #13746 [Bug]: System-default Codex can use stale managed credentials when status-hook trust is unavailable Fixes · OPEN | Standalone change | ## Summary Fixes #13746. When Codex uses Orca's system-default account, keep it on the host's native `CODEX_HOME` even if the optional status-hook trust grant is unavailable. Previously, hook capability gated `isHostSyst | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +122/−60. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the chat viewport steady when history pages in (STA-3333)1 PR · Standalone · Automated release pipeline#
Problem: keep the chat viewport steady when history pages in (STA-3333).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12500 fix(mobile): keep the chat viewport steady when history pages in (STA-3333) | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary Paging older native-chat history now preserves the reader's viewport without relying on a timed hold or a render-observed loading transition. - `loadEarlier` returns an explicit `Promise<boolean> | null`, so t | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +971/−185. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the pane provider-session binding across a transient clear1 PR · Standalone · Automated release pipeline#
Problem: keep the pane provider-session binding across a transient clear.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11546 [Bug]: AI conversation context lost on renderer restart — SSH terminal reconnects but chat history is gone (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12070 fix(agent-hooks): keep the pane provider-session binding across a transient clear | Neil Core team · MEMBER | #11546 [Bug]: AI conversation context lost on renderer restart — SSH terminal reconnects but chat history is gone Fixes · OPEN | Standalone change | Fixes #11546 ## ELI5 When you chat with an agent in a pane, Orca doesn't keep the conversation in the window — it keeps a little sticky note saying "this pane is conversation #sess-1, whose transcript file lives here". T | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +347/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the reattach grid push past an exhausted fit budget1 PR · Standalone · Automated release pipeline#
Problem: keep the reattach grid push past an exhausted fit budget.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13155 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13194 fix(terminal): keep the reattach grid push past an exhausted fit budget | Brennan Benson Core team · MEMBER | #13155 Title unavailable Unclear · Unknown | Standalone change | ## Summary > **Stacked on #13155.** Review only the last commit. Retarget to `main` once #13155 merges. #13155 stopped a `display:none` pane from dropping the reattach grid push. The same continuation is still dropped by | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +38/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the shell wrapper parseable under zsh global aliases1 PR · Standalone · Automated release pipeline#
Problem: keep the shell wrapper parseable under zsh global aliases.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14538 fix(terminal): keep the shell wrapper parseable under zsh global aliases | Brennan Benson Core team · MEMBER | None found | Standalone change | ## ELI5 Some people put a shortcut in their zsh config that rewrites the word `--help` so long help text gets piped through a pretty pager. zsh applies that kind of shortcut to *every* `--help` on a line — including one | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +80/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the workspace selected when its last tab closes1 PR · Standalone · Automated release pipeline#
Problem: keep the workspace selected when its last tab closes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11699 [Bug]: Closing all terminals clears center panel file browser; must re-open workspace to browse files (Fixes, OPEN); #677 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12142 fix(workspace): keep the workspace selected when its last tab closes | Anddy Sahir Agudelo Community · CONTRIBUTOR | #11699 [Bug]: Closing all terminals clears center panel file browser; must re-open workspace to browse files Fixes · OPEN #677 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes #11699. Closing every tab in a workspace deselected the workspace itself. The file explorer fell back to *"Select a workspace to browse files"* and the Git panel emptied, so browsing files or using sourc | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +587/−103. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2land an account-switch restart on the newly selected account1 PR · Standalone · Automated release pipeline#
Problem: land an account-switch restart on the newly selected account.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12146 Title unavailable (Unclear, Unknown); #12098 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14877 fix(codex): land an account-switch restart on the newly selected account | Rayim Community · CONTRIBUTOR | #12146 Title unavailable Unclear · Unknown #12098 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You switch Codex to account B and press Restart on the card. The terminal comes back… still on account A. This PR makes that one press actually land on B, keeps your conversation going there (`codex resume`), and | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk32 files, +1322/−52. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2lazy-load source cache ledgers1 PR · Standalone · Automated release pipeline#
Problem: lazy-load source cache ledgers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16211 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16219 perf(usage): lazy-load source cache ledgers | 叁笙早安 AI Community · FIRST_TIME_CONTRIBUTOR | #16211 Title unavailable Unclear · Unknown | Standalone change | ## Summary - split each provider's cold source/ownership ledger into a schema- and worktree-bound sidecar cache - keep only hot scan state, sessions, and daily aggregates in the startup cache - load the cold ledger only | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +211/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let activate() tell a reconnected client from one that never left1 PR · Standalone · Automated release pipeline#
Problem: let activate() tell a reconnected client from one that never left.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15761 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15762 fix(relay): let activate() tell a reconnected client from one that never left | Neil Core team · MEMBER | #15761 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +286/−62. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let DevTools own Cmd+V instead of the focused terminal pane1 PR · Standalone · Automated release pipeline#
Problem: let DevTools own Cmd+V instead of the focused terminal pane.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16285 [Bug]: Cmd+V in DevTools pastes into the terminal instead of the console (Fixes, OPEN); #13388 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16288 fix(menu): let DevTools own Cmd+V instead of the focused terminal pane | gatsby74 Community · CONTRIBUTOR | #16285 [Bug]: Cmd+V in DevTools pastes into the terminal instead of the console Fixes · OPEN #13388 Title unavailable Unclear · Unknown | Standalone change | ## Problem On macOS, <kbd>Cmd</kbd>+<kbd>V</kbd> while the Chrome DevTools console has keyboard focus pastes into the focused **terminal pane** instead of the console input. <kbd>Cmd</kbd>+<kbd>C</kbd>, <kbd>Cmd</kbd>+<k | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +203/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let the model picker clear the persisted launch override1 PR · Standalone · Automated release pipeline#
Problem: let the model picker clear the persisted launch override.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13794 [Bug]: Claude Chat model picker permanently overrides the global default with no reset option (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13819 fix(native-chat): let the model picker clear the persisted launch override | 이수빈 Community · FIRST_TIME_CONTRIBUTOR | #13794 [Bug]: Claude Chat model picker permanently overrides the global default with no reset option Fixes · OPEN | Standalone change | Fixes #13794 ## Summary Once a model is picked in the native Chat composer, Orca persists it as `nativeChatSessionOptions.<agent>.model` and passes `--model` to every new launch — permanently overriding the model configu | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +204/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let users unpin main workspaces from the top of their group1 PR · Standalone · Automated release pipeline#
Problem: let users unpin main workspaces from the top of their group.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15770 [Feature] Any way to not pin primary worktrees to top? (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15811 feat(sidebar): let users unpin main workspaces from the top of their group | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15770 [Feature] Any way to not pin primary worktrees to top? Fixes · OPEN | Standalone change | ## Summary **What** A new Appearance → Window & Sidebar setting, **"Keep main workspaces at the top"** (default **on**, preserving today's behavior). Turned off, the user's chosen sort (Smart/Recent) ranks each project's | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +100/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2lift the closed-tab blackhole when a retracted tab comes back (STA-5679)1 PR · Standalone · Automated release pipeline#
Problem: lift the closed-tab blackhole when a retracted tab comes back (STA-5679).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14624 Title unavailable (Unclear, Unknown); #6095 Title unavailable (Unclear, Unknown); #16980 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16985 fix(agent-status): lift the closed-tab blackhole when a retracted tab comes back (STA-5679)Draft | Brennan Benson Core team · MEMBER | #14624 Title unavailable Unclear · Unknown #6095 Title unavailable Unclear · Unknown #16980 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +195/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2list default issues via REST so account mismatches surface errors (#16244)1 PR · Standalone · Automated release pipeline#
Problem: list default issues via REST so account mismatches surface errors (#16244).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16244 [Bug] Cannot load Github Issues when using multiple account on cli (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16294 fix(github): list default issues via REST so account mismatches surface errors (#16244) | Cal Community · CONTRIBUTOR | #16244 [Bug] Cannot load Github Issues when using multiple account on cli Fixes · OPEN | Standalone change | Closes #16244 After switching/re-logging-in gh accounts, the Tasks issues panel went silently empty: the Search API answers HTTP 200 with zero items when the active account cannot see the repo, which read as "no issues". | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +135/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2localize Artifacts feature strings to Korean1 PR · Standalone · Automated release pipeline#
Problem: localize Artifacts feature strings to Korean.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13810 feat(i18n): localize Artifacts feature strings to Korean | JeongSu Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary The Artifacts sidebar entry, settings pane, share flow, and publish dialogs shipped with no Korean translations (`ko.json` had 0 of the 82 `auto.components.artifacts.*` keys, plus related settings/sidebar keys | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +154/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2localize caffeinate controls in Chinese1 PR · Standalone · Automated release pipeline#
Problem: localize caffeinate controls in Chinese.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13480 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14772 fix(i18n): localize caffeinate controls in Chinese | Asurada Community · CONTRIBUTOR | #13480 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Display the Caffeinate status-bar controls in Chinese when Orca is using the Chinese locale. ## What Changed - Added Chinese labels for the On, Agent, and Off Caffeinate modes. - Added Chinese active and inactive | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +12/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2localize remaining Korean UI strings outside auto catalog1 PR · Standalone · Automated release pipeline#
Problem: localize remaining Korean UI strings outside auto catalog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13810 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14044 fix(i18n): localize remaining Korean UI strings outside auto catalog | JeongSu Community · FIRST_TIME_CONTRIBUTOR | #13810 Title unavailable Unclear · Unknown | Standalone change | ## Summary Follow-up to #13810 (which covered the Artifacts feature only). Several other UI surfaces were still shipping in English in `ko.json`: the worktree jump palette filter panel, the agent dashboard popout (map fi | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +94/−28. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2localize the source control dropdown hints1 PR · Standalone · Automated release pipeline#
Problem: localize the source control dropdown hints.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11826 Title unavailable (Unclear, Unknown); #12478 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14127 fix(i18n): localize the source control dropdown hints | Evgenii Community · CONTRIBUTOR | #11826 Title unavailable Unclear · Unknown #12478 Title unavailable Unclear · Unknown | Standalone change | ## Summary Three pieces of copy in the source control dropdown are built from bare literals inside `buildSourceControlDropdownItems`, so they stay English while the labels right beside them go through `translate()`: ```t | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +371/−65. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2long-press to select/copy sent Native Chat text (STA-4983)1 PR · Standalone · Automated release pipeline#
Problem: long-press to select/copy sent Native Chat text (STA-4983).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15652 fix(mobile): long-press to select/copy sent Native Chat text (STA-4983) | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +11/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make RC/perf update channels readable without hovering (#10590)1 PR · Standalone · Automated release pipeline#
Problem: make RC/perf update channels readable without hovering (#10590).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10590 RC/perf update channels are undiscoverable: the only hint is a native `title` tooltip (Fixes, OPEN); #10770 Title unavailable (Unclear, Unknown); #10598 Title unavailable (Unclear, Unknown); #10602 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12255 fix(updater): make RC/perf update channels readable without hovering (#10590) | Neil Core team · MEMBER | #10590 RC/perf update channels are undiscoverable: the only hint is a native `title` tooltip Fixes · OPEN #10770 Title unavailable Unclear · Unknown #10598 Title unavailable Unclear · Unknown #10602 Title unavailable Unclear · Unknown | Standalone change | ## Description Fixes #10590 The RC / perf / local-build update channels were only ever announced through a native `title` attribute on the "Check for Updates" button. That made them undiscoverable in practice: - A native | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +754/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Make terminal link action defaults switchable1 PR · Standalone · Automated release pipeline#
Problem: Make terminal link action defaults switchable.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14813 [Feature]: Terminal file-link hints and settings are inconsistent (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14814 Make terminal link action defaults switchable | Tor Arne Vestbø Community · FIRST_TIME_CONTRIBUTOR | #14813 [Feature]: Terminal file-link hints and settings are inconsistent Fixes · OPEN | Standalone change | ## ELI5 When you click a file link in the terminal, three things were off. The toggle that controls terminal link actions lived in the **Browser** settings even though it only ever affected the terminal. There was no way | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +717/−289. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the canonical envelope stripper the only one1 PR · Standalone · Automated release pipeline#
Problem: make the canonical envelope stripper the only one.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17230 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17237 refactor(ipc): make the canonical envelope stripper the only one | Brennan Benson Core team · MEMBER | #17230 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 15 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk36 files, +1141/−151. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the Electron install survive release-CDN blips1 PR · Standalone · Automated release pipeline#
Problem: make the Electron install survive release-CDN blips.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14110 fix(ci): make the Electron install survive release-CDN blips | OrcaWin Unknown · COLLABORATOR | None found | Standalone change | Two related fixes for CI jobs that red on transient GitHub release-CDN failures rather than on anything in the diff under test. ## 1. 5xx download failures were never retried `isTransientDownloadError` read only `error.s | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +91/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the software-rendering rescue reachable across launches1 PR · Standalone · Automated release pipeline#
Problem: make the software-rendering rescue reachable across launches.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10707 Title unavailable (Unclear, Unknown); #11295 Title unavailable (Unclear, Unknown); #15107 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15059 fix(gpu): make the software-rendering rescue reachable across launches | Neil Core team · MEMBER | #10707 Title unavailable Unclear · Unknown #11295 Title unavailable Unclear · Unknown #15107 Title unavailable Unclear · Unknown | Standalone change | ## What this fixes Orca has a rescue for machines whose GPU driver is unusable: after repeated GPU-child crashes it falls back to software rendering. **On the shape of failure that actually strands users — the GPU child | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +3230/−131. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2match external file changes across Windows path spellings1 PR · Standalone · Automated release pipeline#
Problem: match external file changes across Windows path spellings.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14801 Editor does not auto-refresh files written by agents (no banner, no unsaved edits — silent) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14812 fix(editor): match external file changes across Windows path spellings | Vincent Community · FIRST_TIME_CONTRIBUTOR | #14801 Editor does not auto-refresh files written by agents (no banner, no unsaved edits — silent) Fixes · OPEN | Standalone change | ## ELI5 On Windows the same file has several equally valid spellings: `C:\repo\src\a.ts` and `c:/repo/src/a.ts` are the same file. Orca filed your open tabs under one spelling and then looked them up under the other, so | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +111/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2migrate custom font weights to independent bold (STA-4236)1 PR · Standalone · Automated release pipeline#
Problem: migrate custom font weights to independent bold (STA-4236).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14368 Title unavailable (Unclear, Unknown); #14175 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14390 fix(terminal): migrate custom font weights to independent bold (STA-4236) | Brennan Benson Core team · MEMBER | #14368 Title unavailable Unclear · Unknown #14175 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 There used to be one Font Weight slider, and Orca worked bold out from it by adding 200. #14368 split bold into its own slider — but nobody told the profiles that were already saved. They arrive with no bold valu | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +165/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2mint PTY ids that carry the relay incarnation instead of a restarting counter1 PR · Standalone · Automated release pipeline#
Problem: mint PTY ids that carry the relay incarnation instead of a restarting counter.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16894 Title unavailable (Unclear, Unknown); #16895 Title unavailable (Unclear, Unknown); #16843 Title unavailable (Unclear, Unknown); #16763 Title unavailable (Unclear, Unknown); #16691 Title unavailable (Unclear, Unknown); #11003 Title unavailable (Unclear, Unknown); #16746 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16901 fix(relay): mint PTY ids that carry the relay incarnation instead of a restarting counter | Brennan Benson Core team · MEMBER | #16894 Title unavailable Unclear · Unknown #16895 Title unavailable Unclear · Unknown #16843 Title unavailable Unclear · Unknown #16763 Title unavailable Unclear · Unknown #16691 Title unavailable Unclear · Unknown #11003 Title unavailable Unclear · Unknown #16746 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 12 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +292/−143. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Move a rejected worker_done off ready instead of stranding its Dispatch1 PR · Standalone · Automated release pipeline#
Problem: Move a rejected worker_done off ready instead of stranding its Dispatch.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13364 [Bug]: rejected worker_done ("Dispatch capability is missing") leaves the dispatch at state=ready forever (Fixes, OPEN); #13655 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15265 Move a rejected worker_done off ready instead of stranding its Dispatch | Taras Kornichuk Community · CONTRIBUTOR | #13364 [Bug]: rejected worker_done ("Dispatch capability is missing") leaves the dispatch at state=ready forever Fixes · OPEN #13655 Title unavailable Unclear · Unknown | Standalone change | ## What changes A `worker_done` that Orca refuses now takes its worker Dispatch out of `ready`. A refused report **from the assigned pane** parks the lane at `state = stop_unknown`, `stage = worker_report_rejected`, with | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +291/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2name structured Codex chat tabs from their own session1 PR · Standalone · Automated release pipeline#
Problem: name structured Codex chat tabs from their own session.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17092 fix(native-chat): name structured Codex chat tabs from their own session | Brennan Benson Core team · MEMBER | #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +1029/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2native chat no longer claims an empty conversation while the agent is working1 PR · Standalone · Automated release pipeline#
Problem: native chat no longer claims an empty conversation while the agent is working.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16887 fix(mobile): native chat no longer claims an empty conversation while the agent is working | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +437/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2offer the host's real Claude model list in native chat1 PR · Standalone · Automated release pipeline#
Problem: offer the host's real Claude model list in native chat.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15086 fix(mobile): offer the host's real Claude model list in native chat | 0xnxxh Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem Mobile's native-chat model picker renders only the static seed catalog — the version-neutral `fable / opus / sonnet / haiku` family aliases in `src/shared/agent-session-option-catalog-claude-codex.ts`. A host | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +584/−83. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Omniroute baton integration1 PR · Standalone · Automated release pipeline#
Problem: Omniroute baton integration.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13526 Omniroute baton integration | Gagan Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Describe the user-visible change. ## Screenshots - Add screenshots or a screen recording for any new or changed UI behavior. - If there is no visual change, say `No visual change`. ## Testing - [ ] `pnpm lint` | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +1895/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open Create Workspace after its source drawer has closed1 PR · Standalone · Automated release pipeline#
Problem: open Create Workspace after its source drawer has closed.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13147 fix(mobile): open Create Workspace after its source drawer has closed | Zhou Jian Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Starting a workspace from a task on iOS did nothing and left the screen stuck. The Tasks screen asked the **Create Workspace** drawer to open while the sheet it was launched from was still on screen. Every `Bo | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +226/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open floating terminal when its notification is clicked1 PR · Standalone · Automated release pipeline#
Problem: open floating terminal when its notification is clicked.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11965 [Bug]: Notifications from the Floating Workspace (Global Terminal) never get a click handler — clicking them does nothing (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12110 fix(notifications): open floating terminal when its notification is clicked | Yuri Chukhlib Community · CONTRIBUTOR | #11965 [Bug]: Notifications from the Floating Workspace (Global Terminal) never get a click handler — clicking them does nothing Fixes · OPEN | Standalone change | ## Summary Clicking a native notification that comes from the **Floating Workspace** (the global floating terminal) does nothing — Orca isn't even brought to the front. Every repo-scoped notification (`worktreeId = "repo | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +68/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open project select with Cmd/Ctrl+.1 PR · Standalone · Automated release pipeline#
Problem: open project select with Cmd/Ctrl+..
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12989 feat(composer): open project select with Cmd/Ctrl+. | Dunz Koi Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - In the create-worktree / create-workspace composer modal, `⌘.` (macOS) / `Ctrl+.` (Linux/Windows) focuses and opens the project picker — the same habit as common IDEs. - Wired beside the existing screen-loca | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +132/−9. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open symlinked folders that point outside the workspace1 PR · Standalone · Automated release pipeline#
Problem: open symlinked folders that point outside the workspace.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13069 fix(file-explorer): open symlinked folders that point outside the workspace | KevinZhangv5 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary A symlinked folder whose target sits outside the workspace roots could not be opened from the file explorer, and every symlink rendered as a file until the user clicked it. Two independent causes: 1. **Every s | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +375/−38. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open the deep-linked project setup, not the host's first1 PR · Standalone · Automated release pipeline#
Problem: open the deep-linked project setup, not the host's first.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11689 Title unavailable (Unclear, Unknown); #8650 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12176 fix(settings): open the deep-linked project setup, not the host's first | Anddy Sahir Agudelo Community · CONTRIBUTOR | #11689 Title unavailable Unclear · Unknown #8650 Title unavailable Unclear · Unknown | Standalone change | ## Summary Addresses the reproducible half of #11689: *"Editing third project's properties shows first project's data."* **Precondition:** two setups sharing one identity on one host — two clones of the same remote, the | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +132/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open workers in the coordinator split pane1 PR · Standalone · Automated release pipeline#
Problem: open workers in the coordinator split pane.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13802 fix(orchestration): open workers in the coordinator split pane | rafly lesmana Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Orchestration workers created in an existing workspace now open in the same split pane as their coordinator, even when another pane is active during startup. Worker creation remains in the background without s | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +471/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2opening tmp files read-only breaks fsync on Windows1 PR · Standalone · Automated release pipeline#
Problem: opening tmp files read-only breaks fsync on Windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14168 fix: opening tmp files read-only breaks fsync on Windows | p75w4xt8mt-bit Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | fsyncFileSync opened the target with openSync(path, 'r') before calling fsyncSync. On Windows, FlushFileBuffers requires a write-access handle, so the read-only descriptor throws EPERM every time. This makes writeProfile | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +2/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2orchestration: launch argv-capable worker agents with the dispatch preamble embedded, instea1 PR · Standalone · Automated release pipeline#
Problem: orchestration: launch argv-capable worker agents with the dispatch preamble embedded, instea.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16095 Title unavailable (Unclear, Unknown); #15976 Title unavailable (Unclear, Unknown); #15920 Title unavailable (Unclear, Unknown); #15180 Title unavailable (Unclear, Unknown); #15190 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16425 orchestration: launch argv-capable worker agents with the dispatch preamble embedded, instead of paste + 5s submission verification | Florian Séran Community · FIRST_TIME_CONTRIBUTOR | #16095 Title unavailable Unclear · Unknown #15976 Title unavailable Unclear · Unknown #15920 Title unavailable Unclear · Unknown #15180 Title unavailable Unclear · Unknown #15190 Title unavailable Unclear · Unknown | Standalone change | ### Problem `orchestration.workerStart` currently delivers the dispatch preamble to a freshly created agent terminal by waiting for `tui-idle`, pasting, pressing Enter, and then requiring a `workingSequence` rise within | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +904/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2persist active workspace identity1 PR · Standalone · Automated release pipeline#
Problem: persist active workspace identity.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14474 [Bug]: Incremental session patches leave activeWorkspaceKey stale after switching worktrees (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14475 fix(workspace): persist active workspace identity | Yunqian Fan Community · CONTRIBUTOR | #14474 [Bug]: Incremental session patches leave activeWorkspaceKey stale after switching worktrees Fixes · OPEN | Standalone change | ## Summary - persist `activeWorkspaceKey` and `activeWorkspaceExecutionHostId` in incremental workspace-session patches - make same-worktree activation repair a stale workspace key instead of taking the no-op path - cove | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +48/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pin folder-workspace PTY cwd across paired and SSH topologies (STA-4746)1 PR · Standalone · Automated release pipeline#
Problem: pin folder-workspace PTY cwd across paired and SSH topologies (STA-4746).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10778 Title unavailable (Unclear, Unknown); #15381 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15385 test(relay): pin folder-workspace PTY cwd across paired and SSH topologies (STA-4746) | Jinwoo Hong Core team · MEMBER | #10778 Title unavailable Unclear · Unknown #15381 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +609/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pin OSC 11 reply before CPR (STA-5634)1 PR · Standalone · Automated release pipeline#
Problem: pin OSC 11 reply before CPR (STA-5634).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16672 Title unavailable (Unclear, Unknown); #15578 Title unavailable (Unclear, Unknown); #16862 Title unavailable (Unclear, Unknown); #15559 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16831 test(pty): pin OSC 11 reply before CPR (STA-5634) | Brennan Benson Core team · MEMBER | #16672 Title unavailable Unclear · Unknown #15578 Title unavailable Unclear · Unknown #16862 Title unavailable Unclear · Unknown #15559 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +77/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pin park verdict on slow notice-limit churn1 PR · Standalone · Automated release pipeline#
Problem: pin park verdict on slow notice-limit churn.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12596 [Bug]: terminal_park_verdict_churn reproduces in the field (12 flips/30s for 13.5 min), followed by a renderer reload loop (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13161 fix(terminal): pin park verdict on slow notice-limit churn | BingZ Community · CONTRIBUTOR | #12596 [Bug]: terminal_park_verdict_churn reproduces in the field (12 flips/30s for 13.5 min), followed by a renderer reload loop Fixes · OPEN | Standalone change | ## Summary - Park-verdict damping previously pinned only on **burst** flips (≈3+ flips in 1s). - Field #12596 recorded 12 flips / ~30s (≈2.5s period from the ~3s background measure lease) — too slow for the burst window, | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +25/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve ADF link marks as Markdown hyperlinks1 PR · Standalone · Automated release pipeline#
Problem: preserve ADF link marks as Markdown hyperlinks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11667 [Bug]: Jira issue description hyperlinks are rendered as plain text (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13604 fix(jira): preserve ADF link marks as Markdown hyperlinks | Brennan Benson Core team · MEMBER | #11667 [Bug]: Jira issue description hyperlinks are rendered as plain text Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +587/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve completed prompt dispatches1 PR · Standalone · Automated release pipeline#
Problem: preserve completed prompt dispatches.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15920 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15941 fix(orchestration): preserve completed prompt dispatches | Ray Community · FIRST_TIME_CONTRIBUTOR | #15920 Title unavailable Unclear · Unknown | Standalone change | ## Summary Prevent `orchestration dispatch --inject` from reporting `agent_prompt_stalled` after the dispatched worker has already completed the task through `worker_done`. ## Problem Prompt submission verification can t | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +30/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve iPad hardware keyboard focus1 PR · Standalone · Automated release pipeline#
Problem: preserve iPad hardware keyboard focus.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12706 [Bug] Cannot use external (e.g. magic) keyboard on ipad on terminal windows (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12772 fix(mobile): preserve iPad hardware keyboard focus | Ramiro Community · FIRST_TIME_CONTRIBUTOR | #12706 [Bug] Cannot use external (e.g. magic) keyboard on ipad on terminal windows Fixes · OPEN | Standalone change | ## ELI5 If you use Orca on an iPad with a physical keyboard attached, tapping a terminal to type could stop working: the app mistook "no on-screen keyboard" for "you dismissed the keyboard" and reset the hidden typing fi | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +67/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve project filter when importing or revealing a repo1 PR · Standalone · Automated release pipeline#
Problem: preserve project filter when importing or revealing a repo.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12691 fix: preserve project filter when importing or revealing a repo | Alejandro Madrazo Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Importing a new project used to reset the sidebar **Projects** filter: after adding a repo, *every* project reappeared instead of the ones the user had filtered to **plus** the newly imported one. Root cause: | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +151/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve remote task launch options1 PR · Standalone · Automated release pipeline#
Problem: preserve remote task launch options.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13412 Title unavailable (Unclear, Unknown); #13320 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13448 fix(workspaces): preserve remote task launch options | Jinwoo Hong Core team · MEMBER | #13412 Title unavailable Unclear · Unknown #13320 Title unavailable Unclear · Unknown | Standalone change | ## Summary Follow-up to #13412. Tasks-created paired workspaces already start the agent on the owning host; this PR also preserves the persisted per-agent launch defaults without claiming values that the host did not app | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +797/−67. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve run subcommand before launch flags1 PR · Standalone · Automated release pipeline#
Problem: preserve run subcommand before launch flags.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13065 fix(opencode): preserve run subcommand before launch flags | Isaque Coelho Community · CONTRIBUTOR | None found | Standalone change | ## Summary Fixes OpenCode AI commit-message generation when an `agentCmdOverrides` value includes launch flags, for example `opencode --auto`. Orca now produces `opencode run --auto ...` instead of `opencode --auto run . | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +54/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve sessions during uncertain Windows recovery1 PR · Standalone · Automated release pipeline#
Problem: preserve sessions during uncertain Windows recovery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14644 Daemon process is replaced repeatedly while the app keeps running; each replacement kills sessions and breaks orchestration bindings (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14959 fix(daemon): preserve sessions during uncertain Windows recoveryDraft | OrcaWin Unknown · COLLABORATOR | #14644 Daemon process is replaced repeatedly while the app keeps running; each replacement kills sessions and breaks orchestration bindings Fixes · OPEN | Standalone change | ## Summary - hold an unresponsive incumbent when daemon occupancy cannot be verified instead of treating unknown as permission to kill its PTYs - route fresh terminals locally while held and fence mutating operations who | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +380/−72. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve settled prompt authority1 PR · Standalone · Automated release pipeline#
Problem: preserve settled prompt authority.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14962 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15583 fix(terminal): preserve settled prompt authorityDraft | Jinwoo Hong Core team · MEMBER | #14962 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1380/−101. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve slashes in derived branch names1 PR · Standalone · Automated release pipeline#
Problem: preserve slashes in derived branch names.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15122 Worktree names with feature/ prefix lose the slash in the derived git branch name (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15104 feat(worktrees): preserve slashes in derived branch names | Matthew Yu Community · FIRST_TIME_CONTRIBUTOR | #15122 Worktree names with feature/ prefix lose the slash in the derived git branch name Fixes · OPEN | Standalone change | ## ELI5 When you name a new workspace `feature/tti_fix_1440`, Orca used to name the git branch `feature-tti_fix_1440` — the slash got flattened because the same sanitizer served both the folder name and the branch name. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +242/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve slow worktree removal responses1 PR · Standalone · Automated release pipeline#
Problem: preserve slow worktree removal responses.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11932 Title unavailable (Unclear, Unknown); #15663 Title unavailable (Unclear, Unknown); #15730 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16060 fix(runtime): preserve slow worktree removal responses | Jinwoo Hong Core team · MEMBER | #11932 Title unavailable Unclear · Unknown #15663 Title unavailable Unclear · Unknown #15730 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +412/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Preserve unverifiable terminal sessions and document PTY ownership redesign1 PR · Standalone · Automated release pipeline#
Problem: Preserve unverifiable terminal sessions and document PTY ownership redesign.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16152 Preserve unverifiable terminal sessions and document PTY ownership redesign | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +2277/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Preserve user-set workspace names across branch changes and collision retries1 PR · Standalone · Automated release pipeline#
Problem: Preserve user-set workspace names across branch changes and collision retries.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12742 Preserve user-set workspace names across branch changes and collision retries | Jinjing Core team · MEMBER | None found | Standalone change | ## Summary Enable workspace display names to persist across branch switches and collision retries by tracking name origin. User-authored names remain fixed with their exact trimmed text, while generated names (from issue | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk38 files, +984/−95. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve worktree forwarded host1 PR · Standalone · Automated release pipeline#
Problem: preserve worktree forwarded host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14535 [Bug]: Worktree proxy breaks Next.js Server Actions due to mismatched x-forwarded-host (Fixes, OPEN); #13318 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14562 fix(proxy): preserve worktree forwarded host | promptprobe Community · FIRST_TIME_CONTRIBUTOR | #14535 [Bug]: Worktree proxy breaks Next.js Server Actions due to mismatched x-forwarded-host Fixes · OPEN #13318 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Orca gives each workspace dev server a readable `*.orca.localhost` URL. It still needs to connect to the real localhost port, so it rewrites `Host` for the upstream server. It was not separately preserving the br | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +64/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve WSL federated worker lifecycle authority1 PR · Standalone · Automated release pipeline#
Problem: preserve WSL federated worker lifecycle authority.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15020 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15580 fix(orchestration): preserve WSL federated worker lifecycle authority | OrcaWin Unknown · COLLABORATOR | #15020 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 15 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +2396/−392. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prevent terminal font size value from clipping1 PR · Standalone · Automated release pipeline#
Problem: prevent terminal font size value from clipping.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12877 [Bug]: Terminal font size value is clipped in Settings (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12909 fix(settings): prevent terminal font size value from clipping | Soham Donode Community · FIRST_TIME_CONTRIBUTOR | #12877 [Bug]: Terminal font size value is clipped in Settings Fixes · CLOSED | Standalone change | ## Summary Widens the terminal Font Size input in Settings → Terminal → Terminal Typography so the numeric value is no longer clipped. Changed `w-14 text-center` to `w-16 text-center tabular-nums` — kept centered alignme | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +1/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prune nested ignored dirs on macOS and bound the flush fan-out1 PR · Standalone · Automated release pipeline#
Problem: prune nested ignored dirs on macOS and bound the flush fan-out.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11218 [Bug]: Sudden CPU/memory runaway with two worktrees in one workspace — Resource Manager reports 135 GB (211% of system RAM) on a 64 GB Mac, machine froze and required force power-off (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12067 fix(watcher): prune nested ignored dirs on macOS and bound the flush fan-out | Neil Core team · MEMBER | #11218 [Bug]: Sudden CPU/memory runaway with two worktrees in one workspace — Resource Manager reports 135 GB (211% of system RAM) on a 64 GB Mac, machine froze and required force power-off Fixes · OPEN | Standalone change | Fixes #11218 ## ELI5 Orca watches your project folder so the file tree updates when files change. On Macs it was told to skip the noisy folders — `node_modules`, `.git`, build output — but only the copies sitting at the | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +628/−57. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2push Dispatch mailbox mail to idle workers (STA-3105)1 PR · Standalone · Automated release pipeline#
Problem: push Dispatch mailbox mail to idle workers (STA-3105).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13717 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15249 fix(orchestration): push Dispatch mailbox mail to idle workers (STA-3105) | Jinwoo Hong Core team · MEMBER | #13717 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +244/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2qualify client page host capabilities1 PR · Standalone · Automated release pipeline#
Problem: qualify client page host capabilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14531 feat(browser): qualify client page host capabilitiesDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +150/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2re-probe tracked upstreams after SSH reconnect1 PR · Standalone · Automated release pipeline#
Problem: re-probe tracked upstreams after SSH reconnect.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14945 Title unavailable (Unclear, Unknown); #12977 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12979 test(github): re-probe tracked upstreams after SSH reconnect | dcieslak19973 Community · CONTRIBUTOR | #14945 Title unavailable Unclear · Unknown #12977 Title unavailable Unclear · Unknown | Standalone change | ## What Adds the missing regression coverage for tracked-upstream discovery across an SSH disconnect/reconnect. The test proves that a disconnected lookup does not invoke local Git and that the next lookup reaches the re | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +22/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2read live Windows env so packaged builds pick up setx tokens2 PRs · Overlapping · Automated release pipeline#
Problem: read live Windows env so packaged builds pick up setx tokens.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #14740 [Bug]: Packaged Windows build fails Gitea authentication while dev build connects with the same environment variables (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15435 fix(gitea): read live Windows env so packaged builds pick up setx tokens | Yuzhong Zhang Community · FIRST_TIME_CONTRIBUTOR | #14740 [Bug]: Packaged Windows build fails Gitea authentication while dev build connects with the same environment variables Fixes · OPEN | Cluster contribution | Packaged Windows builds launched from Explorer keep a stale `process.env` snapshot. After `setx` updates `ORCA_GITEA_TOKEN` / `ORCA_GITEA_API_BASE_URL`, Gitea auth still used the old values, so the same machine that work | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +369/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15734 fix(gitea): re-read Windows env credentials from the registry at check time | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #14740 [Bug]: Packaged Windows build fails Gitea authentication while dev build connects with the same environment variables Fixes · OPEN | Cluster contribution | ## Summary **What** The Gitea auth-status check and PR creation now overlay the **current** user + machine `Environment` values read from the Windows registry (via `reg query`; machine first, user wins, `%VAR%` expansion | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +267/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2read ssh host partitions so stranded tabs stop round-tripping as deletions1 PR · Standalone · Automated release pipeline#
Problem: read ssh host partitions so stranded tabs stop round-tripping as deletions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12721 SSH host session partitions are written but never read — tab lists round-trip as empty and remote sync permanently deletes them (Fixes, OPEN); #12671 Title unavailable (Unclear, Unknown); #13013 Title unavailable (Unclear, Unknown); #14844 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12722 fix(session): read ssh host partitions so stranded tabs stop round-tripping as deletions | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12721 SSH host session partitions are written but never read — tab lists round-trip as empty and remote sync permanently deletes them Fixes · OPEN #12671 Title unavailable Unclear · Unknown #13013 Title unavailable Unclear · Unknown #14844 Title unavailable Unclear · Unknown | Standalone change | Fixes #12721 ### What Session state persisted into `ssh:<targetId>` host partitions by main-process runtime flows is invisible to both readers of the workspace session — boot hydration reads only the local and `runtime:* | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +4048/−88. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2read SSH worktree transcripts on the host that owns them2 PRs · Overlapping · Automated release pipeline#
Problem: read SSH worktree transcripts on the host that owns them.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #13663 [Bug]: Native chat never loads for an agent in an SSH worktree (transcript resolved on the desktop, written on the remote host) (Fixes, OPEN); #8401 Title unavailable (Unclear, Unknown); #13687 Title unavailable (Unclear, Unknown); #15515 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13687 fix(native-chat): read SSH worktree transcripts on the host that owns them | Luis Felipe Cordeiro Sena Community · FIRST_TIME_CONTRIBUTOR | #13663 [Bug]: Native chat never loads for an agent in an SSH worktree (transcript resolved on the desktop, written on the remote host) Fixes · OPEN #8401 Title unavailable Unclear · Unknown | Cluster contribution | Fixes #13663. ## ELI5 When you run a coding agent in a worktree on a remote machine (over SSH) and open its native chat view, the chat just spins forever — no messages ever appear, on desktop or on mobile. That's because | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +2853/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15672 fix(native-chat): read SSH worktree transcripts on the execution host | Brennan Benson Core team · MEMBER | #13663 [Bug]: Native chat never loads for an agent in an SSH worktree (transcript resolved on the desktop, written on the remote host) Fixes · OPEN #13687 Title unavailable Unclear · Unknown #15515 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 30 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk81 files, +4359/−741. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2read the vi.mock factories that hand back a shared mock module, and report dead keys by mock1 PR · Standalone · Automated release pipeline#
Problem: read the vi.mock factories that hand back a shared mock module, and report dead keys by mock.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17222 Title unavailable (Unclear, Unknown); #17232 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17240 test: read the vi.mock factories that hand back a shared mock module, and report dead keys by mock shape | Brennan Benson Core team · MEMBER | #17222 Title unavailable Unclear · Unknown #17232 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +766/−65. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reap detached macOS helper processes on every teardown path1 PR · Standalone · Automated release pipeline#
Problem: reap detached macOS helper processes on every teardown path.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9141 computer-use spawns ~200 unmanaged helper processes/3h, causing 40-50GB+ memory usage and forced restarts (Fixes, OPEN); #13767 Title unavailable (Unclear, Unknown); #11425 Title unavailable (Unclear, Unknown); #11441 Title unavailable (Unclear, Unknown); #11481 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14494 fix(computer-use): reap detached macOS helper processes on every teardown path | 박주홍 Community · FIRST_TIME_CONTRIBUTOR | #9141 computer-use spawns ~200 unmanaged helper processes/3h, causing 40-50GB+ memory usage and forced restarts Fixes · OPEN #13767 Title unavailable Unclear · Unknown #11425 Title unavailable Unclear · Unknown #11441 Title unavailable Unclear · Unknown #11481 Title unavailable Unclear · Unknown | Standalone change | Fixes #9141. ## Summary On macOS, `computer-use` leaks helper processes until the machine runs out of memory. #9141 reports ~200 `orca-computer-use-macos` processes in 3 hours and 40-50 GB of memory, ending in the "syste | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +249/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reap owned PTYs when the daemon dies on an uncaught exception (STA-5697)1 PR · Standalone · Automated release pipeline#
Problem: reap owned PTYs when the daemon dies on an uncaught exception (STA-5697).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16895 Title unavailable (Unclear, Unknown); #16901 Title unavailable (Unclear, Unknown); #16843 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16894 fix(relay): reap owned PTYs when the daemon dies on an uncaught exception (STA-5697) | Brennan Benson Core team · MEMBER | #16895 Title unavailable Unclear · Unknown #16901 Title unavailable Unclear · Unknown #16843 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +315/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reclaim idle headless browser tab renderers (STA-4341)1 PR · Standalone · Automated release pipeline#
Problem: reclaim idle headless browser tab renderers (STA-4341).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12137 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15254 fix(browser): reclaim idle headless browser tab renderers (STA-4341) | Jinwoo Hong Core team · MEMBER | #12137 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 14 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +4119/−197. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reconcile completed Claude background tasks1 PR · Standalone · Automated release pipeline#
Problem: reconcile completed Claude background tasks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15317 Title unavailable (Unclear, Unknown); #15558 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15591 fix(agent-status): reconcile completed Claude background tasksDraft | OrcaWin Unknown · COLLABORATOR | #15317 Title unavailable Unclear · Unknown #15558 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1084/−61. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reconcile every hydrated workspace's tab model1 PR · Standalone · Automated release pipeline#
Problem: reconcile every hydrated workspace's tab model.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15710 [Bug]: Remote-runtime tab bar omits live Host sessions — `unifiedTabs` holds 31 of 105 persisted tabs and misses 5 of 11 live PTYs (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15845 fix(startup): reconcile every hydrated workspace's tab model | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15710 [Bug]: Remote-runtime tab bar omits live Host sessions — `unifiedTabs` holds 31 of 105 persisted tabs and misses 5 of 11 live PTYs Fixes · OPEN | Standalone change | ## Summary **What** Boot hydration now runs `reconcileWorktreeTabModel` for **every workspace the session loaded** (via a small pure helper, `reconcileHydratedWorkspaceTabModels`), instead of only the active worktree rec | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +51/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Recover agents stalled by a login or network failure1 PR · Standalone · Automated release pipeline#
Problem: Recover agents stalled by a login or network failure.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16738 Recover agents stalled by a login or network failure | Elad Kishon Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 When a coding agent loses its login or the network blips mid-task, the CLI prints an error and goes back to its prompt. The turn is over and the work is half-done — but nothing in Orca knows that, because agent h | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk36 files, +3679/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover browser host admission fairly1 PR · Standalone · Automated release pipeline#
Problem: recover browser host admission fairly.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14738 Title unavailable (Unclear, Unknown); #14694 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14747 fix(browser): recover browser host admission fairlyDraft | Jinwoo Hong Core team · MEMBER | #14738 Title unavailable Unclear · Unknown #14694 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +587/−65. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover Codex subagent state after restart (STA-5329)1 PR · Standalone · Automated release pipeline#
Problem: recover Codex subagent state after restart (STA-5329).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16751 Title unavailable (Unclear, Unknown); #16979 Title unavailable (Unclear, Unknown); #17012 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16336 fix(agent-status): recover Codex subagent state after restart (STA-5329) | Brennan Benson Core team · MEMBER | #16751 Title unavailable Unclear · Unknown #16979 Title unavailable Unclear · Unknown #17012 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 16 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk41 files, +2935/−293. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover dispatch completion capability1 PR · Standalone · Automated release pipeline#
Problem: recover dispatch completion capability.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12769 [Bug]: supervised Hermes worker receives placeholder instead of dispatch preamble and cannot send worker_done (Fixes, OPEN); #13364 Title unavailable (Unclear, Unknown); #13927 Title unavailable (Unclear, Unknown); #12630 Title unavailable (Unclear, Unknown); #12824 Title unavailable (Unclear, Unknown); #12551 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14026 fix(orchestration): recover dispatch completion capability | Jinwoo Hong Core team · MEMBER | #12769 [Bug]: supervised Hermes worker receives placeholder instead of dispatch preamble and cannot send worker_done Fixes · OPEN #13364 Title unavailable Unclear · Unknown #13927 Title unavailable Unclear · Unknown #12630 Title unavailable Unclear · Unknown #12824 Title unavailable Unclear · Unknown #12551 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes #12769. Linear: https://linear.app/stably/issue/STA-3539 An accepted supervised start must deliver a complete, non-placeholder task and lifecycle preamble, including completion authority, to the exact as | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1706/−192. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover hidden remote agent alerts after resubscription1 PR · Standalone · Automated release pipeline#
Problem: recover hidden remote agent alerts after resubscription.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16102 [Bug]: Paired remote hosts drop completion and permission-prompt notifications raised while the Orca window is hidden (Fixes, OPEN); #16280 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16103 fix(notifications): recover hidden remote agent alerts after resubscriptionDraft | gatsby74 Community · CONTRIBUTOR | #16102 [Bug]: Paired remote hosts drop completion and permission-prompt notifications raised while the Orca window is hidden Fixes · OPEN #16280 Title unavailable Unclear · Unknown | Standalone change | > **Draft — implementation and reproduction are green; final independent review is still running. Do not merge yet.** Fixes #16102 ## ELI5 When Orca hid its window, it parked remote workspace subscriptions. If a paired r | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · L Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk39 files, +3702/−351. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover Linux headless runtime after main crashes1 PR · Standalone · Automated release pipeline#
Problem: recover Linux headless runtime after main crashes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14074 [Bug]: headless serve cannot recover a stale singleton after main-process failure (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14096 fix(serve): recover Linux headless runtime after main crashes | Langning Zhang Community · CONTRIBUTOR | #14074 [Bug]: headless serve cannot recover a stale singleton after main-process failure Fixes · OPEN | Standalone change | ## ELI5 Linux `orca serve` now keeps a small foreground supervisor around the Electron main process. If the main process crashes, the supervisor verifies the runtime is actually unavailable, preserves the detached daemon | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +2856/−195. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Recover native chat messages when terminal delivery is unconfirmed1 PR · Standalone · Automated release pipeline#
Problem: Recover native chat messages when terminal delivery is unconfirmed.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12643 Recover native chat messages when terminal delivery is unconfirmed | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary - confirm native-chat delivery from exact live `UserPromptSubmit` acknowledgements, with transcript fallback, instead of inferring terminal UI state or matching provider-specific strings - after 8 seconds with | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk51 files, +1939/−176. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover overlay hit-test after pane-column snap1 PR · Standalone · Automated release pipeline#
Problem: recover overlay hit-test after pane-column snap.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13297 [Bug]: Cursor hit-test desyncs from visual position after dragging a terminal pane to snap it side-by-side (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14014 fix(renderer): recover overlay hit-test after pane-column snap | OrcaWin Unknown · COLLABORATOR | #13297 [Bug]: Cursor hit-test desyncs from visual position after dragging a terminal pane to snap it side-by-side Fixes · OPEN | Standalone change | ## Summary - After dragging a terminal tab/pane to snap side-by-side, worktree-level overlays (CSS `position-anchor`) can keep a full-area hit-test box while the body only occupies half the layout — clicks land off the c | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +1167/−97. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2release completed run observers1 PR · Standalone · Automated release pipeline#
Problem: release completed run observers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13641 perf(automations): release completed run observers | Neil Core team · MEMBER | None found | Standalone change | ## Summary - Abort remote `terminal.wait` calls and close terminal-data streams as soon as an automation run stops being observed. - Register the fresh-launch observer with the same completion cleanup already used for re | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +184/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2release preserved cleanup routes with reviews1 PR · Standalone · Automated release pipeline#
Problem: release preserved cleanup routes with reviews.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13941 fix(worktrees): release preserved cleanup routes with reviews | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## Summary Preserved-branch force-delete routing now lives only as long as its toast or batch review UI. Dismissal, cancellation, replacement, unselected branches, completed deletion, and dismissed retry surfaces release | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk25 files, +1346/−94. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2release the occurrence a cancelled send would have taken1 PR · Standalone · Automated release pipeline#
Problem: release the occurrence a cancelled send would have taken.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11509 Title unavailable (Unclear, Unknown); #11519 Title unavailable (Unclear, Unknown); #11511 Title unavailable (Unclear, Unknown); #15032 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13513 fix(native-chat): release the occurrence a cancelled send would have taken | grboy6770 Community · CONTRIBUTOR | #11509 Title unavailable Unclear · Unknown #11519 Title unavailable Unclear · Unknown #11511 Title unavailable Unclear · Unknown #15032 Title unavailable Unclear · Unknown | Standalone change | > **Stacked on #11509 — review the last commit only** (`fix(native-chat): release the occurrence a cancelled send would have taken`). > > The fix lives in `use-native-chat-pending-echoes.ts`, a file #11509 creates, so th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +655/−82. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reload Jira and Linear state files when another process rewrites them1 PR · Standalone · Automated release pipeline#
Problem: reload Jira and Linear state files when another process rewrites them.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13126 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13125 fix(integrations): reload Jira and Linear state files when another process rewrites them | Minho Yi Community · FIRST_TIME_CONTRIBUTOR | #13126 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Connect Jira or Linear in one Orca window, and any other Orca running on the same machine keeps saying "not connected" until you restart it. This makes the other one notice. ## What Changed Jira and Linear both m | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +288/−27. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2remove 4px lip above the active terminal tab when not split1 PR · Standalone · Automated release pipeline#
Problem: remove 4px lip above the active terminal tab when not split.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13053 fix(tab-group): remove 4px lip above the active terminal tab when not split | Aex Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem With a single (unsplit) terminal, the **active** tab looks clipped — a bright 4px lip sits between the tab and the window top, so the tab floats instead of sitting flush against the top edge (aligned with the | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +58/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2remove the project on its own host, not another host's row1 PR · Standalone · Automated release pipeline#
Problem: remove the project on its own host, not another host's row.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13071 removeProject without a hostId can delete the wrong host's project when repo IDs are duplicated across hosts (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13117 fix(sidebar): remove the project on its own host, not another host's row | manuaudio Community · CONTRIBUTOR | #13071 removeProject without a hostId can delete the wrong host's project when repo IDs are duplicated across hosts Fixes · OPEN | Standalone change | Closes #13071. ## Summary Removing a project from the sidebar can no longer destroy a *different* host's project. When a repo id exists on two hosts and the owning host's row has dropped out of the renderer catalog, the | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +176/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2render Mermaid HTML labels without stripping foreignObject1 PR · Standalone · Automated release pipeline#
Problem: render Mermaid HTML labels without stripping foreignObject.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12414 [Bug]: Mermaid node labels show HTML tags literally — htmlLabels can be enabled safely while keeping securityLevel "strict" (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12581 fix(editor): render Mermaid HTML labels without stripping foreignObject | BingZ Community · CONTRIBUTOR | #12414 [Bug]: Mermaid node labels show HTML tags literally — htmlLabels can be enabled safely while keeping securityLevel "strict" Fixes · OPEN | Standalone change | ## Summary Security answer first: `securityLevel: "strict"` is unchanged, and Mermaid still runs its own DOMPurify pass over every HTML label. The only change to Orca's second, defense-in-depth pass in `MermaidBlock` is | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +137/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2render the vertical scrollbar again while keeping the gutter transparent1 PR · Standalone · Automated release pipeline#
Problem: render the vertical scrollbar again while keeping the gutter transparent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12635 [Bug]: Terminal vertical scrollbar does not render on any theme (regression, xterm viewport) (Fixes, OPEN); #7876 Title unavailable (Unclear, Unknown); #12826 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12806 fix(terminal): render the vertical scrollbar again while keeping the gutter transparent | BingZ Community · CONTRIBUTOR | #12635 [Bug]: Terminal vertical scrollbar does not render on any theme (regression, xterm viewport) Fixes · OPEN #7876 Title unavailable Unclear · Unknown #12826 Title unavailable Unclear · Unknown | Standalone change | ## Summary The terminal vertical scrollbar no longer rendered on any theme after #7876 folded the xterm viewport into both standard `scrollbar-*` properties and `::-webkit-scrollbar*` rules. Fixes #12635. ## Screenshots | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +47/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2repaint after scrollback replay settles on fresh mount1 PR · Standalone · Automated release pipeline#
Problem: repaint after scrollback replay settles on fresh mount.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12047 [Bug]: Mobile terminal renders garbled/misaligned after tab switch back (OpenCode TUI) (Fixes, OPEN); #7058 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12927 fix(terminal): repaint after scrollback replay settles on fresh mount | Aashish Tamsya Community · FIRST_TIME_CONTRIBUTOR | #12047 [Bug]: Mobile terminal renders garbled/misaligned after tab switch back (OpenCode TUI) Fixes · OPEN #7058 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes #12047: mobile terminal renders garbled/misaligned (stale ghost cells) after tab reveal, and also on first launch of a background/cold-mounted tab. Root cause: a freshly-mounted terminal pane's restored | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +198/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Repair E2E test failures with relay build and fixture updates1 PR · Standalone · Automated release pipeline#
Problem: Repair E2E test failures with relay build and fixture updates.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15231 Repair E2E test failures with relay build and fixture updates | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +49/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2repair NSIS upgrade metadata that reports cannot-close1 PR · Standalone · Automated release pipeline#
Problem: repair NSIS upgrade metadata that reports cannot-close.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13924 [Bug]: v1.4.180 Windows NSIS installer reports “Orca cannot be closed” and hangs after 7z-out (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14172 fix(win): repair NSIS upgrade metadata that reports cannot-close | OrcaWin Unknown · COLLABORATOR | #13924 [Bug]: v1.4.180 Windows NSIS installer reports “Orca cannot be closed” and hangs after 7z-out Fixes · CLOSED | Standalone change | ## ELI5 If an older Windows install left broken uninstall registry text (the literal `$installDir`), the next official installer thinks Orca is still running, says it cannot be closed, and then sits on Installing after i | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +1044/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2replace React 185 timers with structural handoffs1 PR · Standalone · Automated release pipeline#
Problem: replace React 185 timers with structural handoffs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12600 Title unavailable (Unclear, Unknown); #12596 Title unavailable (Unclear, Unknown); #185 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12634 fix(renderer): replace React 185 timers with structural handoffs | Neil Core team · MEMBER | #12600 Title unavailable Unclear · Unknown #12596 Title unavailable Unclear · Unknown #185 Title unavailable Unclear · Unknown | Standalone change | ## Summary Follow-up to #12600. That PR was a defensible emergency circuit breaker for two independent React 185 cascades, but its behavioral brakes were not free: - Activity's true sliding 8-flip/500ms budget could turn | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk67 files, +4864/−2227. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report a partly-sent ask answer honestly (STA-3333)1 PR · Standalone · Automated release pipeline#
Problem: report a partly-sent ask answer honestly (STA-3333).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12373 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12503 fix(mobile): report a partly-sent ask answer honestly (STA-3333) | Brennan Benson Core team · MEMBER | #12373 Title unavailable Unclear · Unknown | Standalone change | ## Summary Split from #12373 (fix 7 of that PR's list) — this PR is independent and targets `main`; #12373 stays open and untouched. A mobile ask-answer send for Claude/Codex is a paced sequence of keystroke groups, not | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +143/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report app-bound encrypted cookies instead of a silent zero1 PR · Standalone · Automated release pipeline#
Problem: report app-bound encrypted cookies instead of a silent zero.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13192 [Bug] Browser cookie import silently imports 0 cookies on Chrome/Edge 140+ on Windows (v20 app-bound encryption) (Fixes, OPEN); #14683 Title unavailable (Unclear, Unknown); #14181 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13193 fix(browser): report app-bound encrypted cookies instead of a silent zero | manuaudio Community · CONTRIBUTOR | #13192 [Bug] Browser cookie import silently imports 0 cookies on Chrome/Edge 140+ on Windows (v20 app-bound encryption) Fixes · OPEN #14683 Title unavailable Unclear · Unknown #14181 Title unavailable Unclear · Unknown | Standalone change | Closes #13192. ## Summary Importing cookies from Chrome/Edge 140+ on Windows now says why it failed instead of reporting a clean zero. Before, the summary read `importedCookies: 0` with `totalCookies > 0` and no error — | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +217/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report expired sessions terminate cannot reach while the relay is offline1 PR · Standalone · Automated release pipeline#
Problem: report expired sessions terminate cannot reach while the relay is offline.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12661 P2: ssh:terminateSessions with only expired leases is a silent no-op when relay is offline (Fixes, OPEN); #2626 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12797 fix(ssh): report expired sessions terminate cannot reach while the relay is offline | dcieslak19973 Community · CONTRIBUTOR | #12661 P2: ssh:terminateSessions with only expired leases is a silent no-op when relay is offline Fixes · OPEN #2626 Title unavailable Unclear · Unknown | Standalone change | **What:** Offline terminate with only expired leases no longer masquerades as a successful remote kill — the handler reports the sessions it couldn't reach and the settings pane says so, with reconnect guidance. **Risk:* | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +170/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report hook status per host, and stop remote Codex reusing an env-less app-server (#8711, #11 PR · Standalone · Automated release pipeline#
Problem: report hook status per host, and stop remote Codex reusing an env-less app-server (#8711, #1.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8711 Codex status hooks are dead in SSH worktrees — CODEX_HOME is injected only by the local PTY provider, while `orca agent hooks status` still reports `codex: installed` (Fixes, OPEN); #11941 Title unavailable (Unclear, Unknown); #7282 Title unavailable (Unclear, Unknown); #8848 Title unavailable (Unclear, Unknown); #14982 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14621 fix(agent-hooks): report hook status per host, and stop remote Codex reusing an env-less app-server (#8711, #11941) | Brennan Benson Core team · MEMBER | #8711 Codex status hooks are dead in SSH worktrees — CODEX_HOME is injected only by the local PTY provider, while `orca agent hooks status` still reports `codex: installed` Fixes · OPEN #11941 Title unavailable Unclear · Unknown #7282 Title unavailable Unclear · Unknown #8848 Title unavailable Unclear · Unknown #14982 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 27 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk57 files, +2169/−385. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2require identity for braille guarded sends (STA-4048)1 PR · Standalone · Automated release pipeline#
Problem: require identity for braille guarded sends (STA-4048).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14092 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14169 fix(terminal): require identity for braille guarded sends (STA-4048) | Brennan Benson Core team · MEMBER | #14092 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Some programs draw a little braille spinner (`⠋ ⠙ ⠸`) in their terminal title while they work. Orca treated that spinner as proof an agent owns the pane, which was enough to type a prompt into it and press Enter. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +386/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2require placement retirement before replacement1 PR · Standalone · Automated release pipeline#
Problem: require placement retirement before replacement.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14536 feat(browser): require placement retirement before replacementDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +121/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve Grok auth from configured WSL runtime1 PR · Standalone · Automated release pipeline#
Problem: resolve Grok auth from configured WSL runtime.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13784 [Bug]: Grok usage tracking ignores configured WSL account runtime (Fixes, OPEN); #13276 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13839 fix(rate-limits): resolve Grok auth from configured WSL runtime | euclodius Community · FIRST_TIME_CONTRIBUTOR | #13784 [Bug]: Grok usage tracking ignores configured WSL account runtime Fixes · OPEN #13276 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Resolve Grok authentication from Orca's configured local account runtime. - Preserve host `GROK_HOME`; on Windows with a WSL runtime, resolve the selected or default distro home and read `.grok/auth.json` th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +763/−181. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve project ref from non-origin remotes1 PR · Standalone · Automated release pipeline#
Problem: resolve project ref from non-origin remotes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13816 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13886 fix(gitlab): resolve project ref from non-origin remotes | BingZ Community · CONTRIBUTOR | #13816 Title unavailable Unclear · Unknown | Standalone change | ## Summary - GitLab Tasks only probed remotes named `origin` or `upstream`, so repositories with a sole non-conventional GitLab remote could show an empty Issues list (#13816). - Preserve the existing `upstream` and `ori | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +351/−112. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve VS Code CLI from standard app installs1 PR · Standalone · Automated release pipeline#
Problem: resolve VS Code CLI from standard app installs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14008 [Bug]: Open SSH worktree in VS Code fails with `spawn code ENOENT` on macOS (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14010 fix(shell): resolve VS Code CLI from standard app installs | BingZ Community · CONTRIBUTOR | #14008 [Bug]: Open SSH worktree in VS Code fails with `spawn code ENOENT` on macOS Fixes · OPEN | Standalone change | ## Summary - GUI-launched Orca often has a minimal `PATH`, so `spawn code` fails with `ENOENT` even when VS Code is installed under `/Applications`. - After PATH/version-manager resolution, fall back to known VS Code (an | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +219/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore agent homes and the attribution PATH shim after config.fish1 PR · Standalone · Automated release pipeline#
Problem: restore agent homes and the attribution PATH shim after config.fish.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13875 Title unavailable (Unclear, Unknown); #13906 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13978 fix(fish): restore agent homes and the attribution PATH shim after config.fish | Neil Core team · MEMBER | #13875 Title unavailable Unclear · Unknown #13906 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If you use fish as your shell, Orca was quietly losing two things every time it opened a terminal: the agent account it routed you to, and the little wrapper that stamps commits as coming from Orca. Your own `con | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +647/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore DECTCEM from tracked mode state on live-agent reattach1 PR · Standalone · Automated release pipeline#
Problem: restore DECTCEM from tracked mode state on live-agent reattach.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14632 [Bug]: Hardware cursor reappears below the input box after pane reattach for hide-once TUIs (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14638 fix(terminal): restore DECTCEM from tracked mode state on live-agent reattach | Dallas Crilley Community · FIRST_TIME_CONTRIBUTOR | #14632 [Bug]: Hardware cursor reappears below the input box after pane reattach for hide-once TUIs Fixes · OPEN | Standalone change | ## ELI5 Some TUIs hide the real terminal cursor once and draw their own caret. Orca could replay a newer screen image but then apply an older “cursor visible” value, turning the hardware cursor back on below the input bo | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +190/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore paired snapshots at the source grid1 PR · Standalone · Automated release pipeline#
Problem: restore paired snapshots at the source grid.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7279 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12768 fix(terminal): restore paired snapshots at the source grid | Brennan Benson Core team · MEMBER | #7279 Title unavailable Unclear · Unknown | Standalone change | ## Summary - carry the host snapshot's optional `cols` / `rows` through the paired-runtime multiplexer and transport - replay authoritative ANSI at the source grid, then fit to the destination viewport and report the res | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +374/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore remote replay grid on reveal1 PR · Standalone · Automated release pipeline#
Problem: restore remote replay grid on reveal.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14206 fix(terminal): restore remote replay grid on reveal | Brennan Benson Core team · MEMBER | None found | Standalone change | ## ELI5 A remote terminal could reopen in a wide pane while its host still believed it was narrow. Orca now replays the saved screen at the grid that produced it, returns the pane to its live grid, and tells the host tha | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +445/−49. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore scroll position when returning to a tab1 PR · Standalone · Automated release pipeline#
Problem: restore scroll position when returning to a tab.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8715 [Bug] OMP: Scroll position resets to top when switching tabs (Fixes, CLOSED); #11915 Title unavailable (Unclear, Unknown); #1298 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12464 fix(terminal): restore scroll position when returning to a tab | Neil Core team · MEMBER | #8715 [Bug] OMP: Scroll position resets to top when switching tabs Fixes · CLOSED #11915 Title unavailable Unclear · Unknown #1298 Title unavailable Unclear · Unknown | Standalone change | `hideTerminalVisibility` captured a marker-anchored scroll snapshot per pane, but nothing ever consumed it. On reveal the live post-`display:none` viewport was resampled instead, and a viewport that collapsed to line 0 w | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +462/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore shell integration after startup exec1 PR · Standalone · Automated release pipeline#
Problem: restore shell integration after startup exec.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13767 Title unavailable (Unclear, Unknown); #13869 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14176 fix(terminal): restore shell integration after startup exec | Neil Core team · MEMBER | #13767 Title unavailable Unclear · Unknown #13869 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Route zsh startup-file replacements through a just-in-time `exec` shim, so command arguments and redirections expand against the user's `ZDOTDIR` before only the replacement process inherits Orca's wrapper. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +894/−53. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resume a provider session in the directory the agent reported, not the pane's worktree (STA-1 PR · Standalone · Automated release pipeline#
Problem: resume a provider session in the directory the agent reported, not the pane's worktree (STA-.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16960 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17087 fix(agent-resume): resume a provider session in the directory the agent reported, not the pane's worktree (STA-5804) | Brennan Benson Core team · MEMBER | #16960 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 21 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk52 files, +2221/−85. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire a superseded daemon that owns no sessions1 PR · Standalone · Automated release pipeline#
Problem: retire a superseded daemon that owns no sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13063 fix(daemon): retire a superseded daemon that owns no sessions | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary The daemon endpoint name embeds the wire protocol version, so every `PROTOCOL_VERSION` bump creates a new daemon and leaves the previous one running. On Windows there is no retirement path at all — `checkEndpo | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +387/−28. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire agent resume records when a shell exit closes its tab1 PR · Standalone · Automated release pipeline#
Problem: retire agent resume records when a shell exit closes its tab.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14228 Title unavailable (Unclear, Unknown); #14534 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15545 fix(terminal): retire agent resume records when a shell exit closes its tab | Daniel Lafraia Community · FIRST_TIME_CONTRIBUTOR | #14228 Title unavailable Unclear · Unknown #14534 Title unavailable Unclear · Unknown | Standalone change | ## Problem A tab closed by its own shell exit (Ctrl+D, `exit`) comes back. Returning to the workspace, or restarting the app, reopens it running `claude --resume <old session>`. The chain: 1. `App.tsx` runs `captureAllSl | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +160/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire direct-SSH tabs on publisher retraction instead of snapshot absence (STA-4719)1 PR · Standalone · Automated release pipeline#
Problem: retire direct-SSH tabs on publisher retraction instead of snapshot absence (STA-4719).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14844 Title unavailable (Unclear, Unknown); #1876 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15348 fix(remote): retire direct-SSH tabs on publisher retraction instead of snapshot absence (STA-4719) | Neil Core team · MEMBER | #14844 Title unavailable Unclear · Unknown #1876 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Say you have Orca open on your laptop **and** your desktop, both connected to the same server. You close a terminal tab on the laptop. The desktop should notice and close it too — but it didn't. Worse, the deskto | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +1624/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire placements on host lease fence1 PR · Standalone · Automated release pipeline#
Problem: retire placements on host lease fence.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14747 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14753 fix(browser): retire placements on host lease fenceDraft | Jinwoo Hong Core team · MEMBER | #14747 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +261/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire removed-workspace snapshot tombstones once their holders release (STA-4451)1 PR · Standalone · Automated release pipeline#
Problem: retire removed-workspace snapshot tombstones once their holders release (STA-4451).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13413 Title unavailable (Unclear, Unknown); #14930 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14933 fix(workspace): retire removed-workspace snapshot tombstones once their holders release (STA-4451) | Brennan Benson Core team · MEMBER | #13413 Title unavailable Unclear · Unknown #14930 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +1001/−304. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire the unpublished-title fallback that minted an agent row and both dots (STA-2926)1 PR · Standalone · Automated release pipeline#
Problem: retire the unpublished-title fallback that minted an agent row and both dots (STA-2926).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #9040 [Bug] No processing indicators (Fixes, CLOSED); #11372 [Bug]: Title-derived agent rows recycle after split pane close (Fixes, OPEN); #8569 Title unavailable (Unclear, Unknown); #9647 Title unavailable (Unclear, Unknown); #14650 Title unavailable (Unclear, Unknown); #14615 Title unavailable (Unclear, Unknown); #14702 Title unavailable (Unclear, Unknown); #11069 Title unavailable (Unclear, Unknown); #11070 Title unavailable (Unclear, Unknown); #14486 Title unavailable (Unclear, Unknown); #14654 Title unavailable (Unclear, Unknown); #14682 Title unavailable (Unclear, Unknown); #8711 Title unavailable (Unclear, Unknown); #8940 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14708 fix(sidebar): retire the unpublished-title fallback that minted an agent row and both dots (STA-2926) | Brennan Benson Core team · MEMBER | #9040 [Bug] No processing indicators Fixes · CLOSED #11372 [Bug]: Title-derived agent rows recycle after split pane close Fixes · OPEN #8569 Title unavailable Unclear · Unknown #9647 Title unavailable Unclear · Unknown #14650 Title unavailable Unclear · Unknown #14615 Title unavailable Unclear · Unknown #14702 Title unavailable Unclear · Unknown #11069 Title unavailable Unclear · Unknown #11070 Title unavailable Unclear · Unknown #14486 Title unavailable Unclear · Unknown #14654 Title unavailable Unclear · Unknown #14682 Title unavailable Unclear · Unknown #8711 Title unavailable Unclear · Unknown #8940 Title unavailable Unclear · Unknown | Standalone change | ## What this actually is — read this first **This is not a live user-facing fix, and the original framing of it was wrong.** Live validation established that the symptom STA-2926 describes — closing a split pane and havi | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +277/−134. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retry snapshot tabs whose worktree paths resolve after apply1 PR · Standalone · Automated release pipeline#
Problem: retry snapshot tabs whose worktree paths resolve after apply.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12902 Direct-SSH snapshot tabs are silently dropped when the worktree catalog resolves their paths late (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12903 fix(remote-workspace): retry snapshot tabs whose worktree paths resolve after apply | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12902 Direct-SSH snapshot tabs are silently dropped when the worktree catalog resolves their paths late Fixes · OPEN | Standalone change | Fixes #12902 ## Problem `applyDirectSshRemoteWorkspaceSnapshot` imports a pulled snapshot through `importRemoteWorkspaceSession`, whose resolver is built from the worktree catalog at apply time. Any snapshot path the cat | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +983/−136. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reveal agents through worktree-activation so slept agents wake1 PR · Standalone · Automated release pipeline#
Problem: reveal agents through worktree-activation so slept agents wake.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14646 fix(agent-map): reveal agents through worktree-activation so slept agents wake | Brennan Benson Core team · MEMBER | None found | Standalone change | ## ELI5 The Agent Map could show a finished Claude/Codex card as **Idle** with “No live terminal — this agent’s pane has closed,” but **Open worktree** only navigated to the workspace. It did not recreate the selected ag | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk26 files, +1283/−92. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reveal remote agent sessions from the dashboard1 PR · Standalone · Automated release pipeline#
Problem: reveal remote agent sessions from the dashboard.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16731 [Bug]: Agent dashboard cannot open remote (SSH) sessions — shows "terminal closed" (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16732 fix(dashboard): reveal remote agent sessions from the dashboard | Yunqian Fan Community · CONTRIBUTOR | #16731 [Bug]: Agent dashboard cannot open remote (SSH) sessions — shows "terminal closed" Fixes · OPEN | Standalone change | ## Summary Fixes #16731. Clicking an agent in the Agent Dashboard (pop-out window or in-window drawer) failed to open **remote/SSH** sessions: the terminal preview falsely reported *"this agent's pane has closed"*, and " | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +297/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2revert: feat(native-chat): Codex structured native chat restructure (revert #16729)1 PR · Standalone · Automated release pipeline#
Problem: revert: feat(native-chat): Codex structured native chat restructure (revert #16729).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16729 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17242 revert: feat(native-chat): Codex structured native chat restructure (revert #16729) | Jinjing Core team · MEMBER | #16729 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 234 | $\color{#1a7f37}{\Huge{\math | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk615 files, +1642/−64508. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2revive retired panes on live new turns1 PR · Standalone · Automated release pipeline#
Problem: revive retired panes on live new turns.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14624 Title unavailable (Unclear, Unknown); #14236 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14560 fix(pi): revive retired panes on live new turns | euclodius Community · FIRST_TIME_CONTRIBUTOR | #14624 Title unavailable Unclear · Unknown #14236 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 #14624 fixes the normal detach/reattach path by lifting pane-retirement fences when a live PTY binds again. This PR adds the secondary safety net: if that attach signal was not observed on both sides, a real live | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +367/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2roll review notes back to the persisted list1 PR · Standalone · Automated release pipeline#
Problem: roll review notes back to the persisted list.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14112 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14125 fix: roll review notes back to the persisted list | Jinjing Core team · MEMBER | #14112 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 If saving a review note to disk fails twice in a row, the app used to keep showing a note that was never actually saved. Now it always falls back to what is really on disk. Plus, the note schema now rejects junk | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +425/−107. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route page-scoped keyboard input through CDP1 PR · Standalone · Automated release pipeline#
Problem: route page-scoped keyboard input through CDP.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12912 [Bug]: orca type/keypress ignore --page and deliver keystrokes to the focused window, while reporting typed:true (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13231 fix(browser): route page-scoped keyboard input through CDP | Wooseong Kim Community · CONTRIBUTOR | #12912 [Bug]: orca type/keypress ignore --page and deliver keystrokes to the focused window, while reporting typed:true Fixes · OPEN | Standalone change | ## Description Browser `type` and `keypress` commands now deliver page-scoped input to the requested browser `webContents` instead of the OS-focused window. The bridge uses direct CDP input dispatch for targeted pages an | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +299/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route task issues, MRs, and detail actions to the owning host1 PR · Standalone · Automated release pipeline#
Problem: route task issues, MRs, and detail actions to the owning host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14603 [Bug]: GitLab Tasks fail with "Access denied: unknown repository path" for repos on a remote host (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14604 fix(gitlab): route task issues, MRs, and detail actions to the owning host | Matt Delmarter Community · FIRST_TIME_CONTRIBUTOR | #14603 [Bug]: GitLab Tasks fail with "Access denied: unknown repository path" for repos on a remote host Fixes · OPEN | Standalone change | ## ELI5 When you run Orca on one machine and connect to your projects living on another (a remote server), the GitLab Tasks panel talked to the wrong machine. It asked your local machine about repos that only exist on th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +639/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2route WSL transcripts by PTY provenance1 PR · Standalone · Automated release pipeline#
Problem: route WSL transcripts by PTY provenance.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13789 [Bug]: wsl can not use chatui feature (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13934 fix(native-chat): route WSL transcripts by PTY provenance | OrcaWin Unknown · COLLABORATOR | #13789 [Bug]: wsl can not use chatui feature Fixes · OPEN | Standalone change | ## ELI5 Orca knew a conversation file was missing from Windows, but it did not know whether the terminal was Windows or WSL. The old patch reacted to a Windows miss by searching every WSL distro. This revision carries th | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk40 files, +2018/−533. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2say what the liveness vocabulary actually fixes, and dedupe the observation status1 PR · Standalone · Automated release pipeline#
Problem: say what the liveness vocabulary actually fixes, and dedupe the observation status.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16926 Title unavailable (Unclear, Unknown); #16932 Title unavailable (Unclear, Unknown); #16953 Title unavailable (Unclear, Unknown); #17024 Title unavailable (Unclear, Unknown); #17003 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17029 refactor(pty): say what the liveness vocabulary actually fixes, and dedupe the observation statusDraft | Brennan Benson Core team · MEMBER | #16926 Title unavailable Unclear · Unknown #16932 Title unavailable Unclear · Unknown #16953 Title unavailable Unclear · Unknown #17024 Title unavailable Unclear · Unknown #17003 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 3 | $\col | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +26/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scan Claude transcripts from WSL homes1 PR · Standalone · Automated release pipeline#
Problem: scan Claude transcripts from WSL homes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15487 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16933 fix(usage): scan Claude transcripts from WSL homes | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15487 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 On Windows, Orca now reads Claude usage from the same host or WSL runtime and account-selected config directory that Claude uses. It no longer combines unrelated WSL Claude accounts into one usage total. ## What | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +499/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scan configured Codex session home (#12186)1 PR · Standalone · Automated release pipeline#
Problem: scan configured Codex session home (#12186).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12186 [Bug]: Agent history from custom paths cannot be displayed in the Agent History (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12733 fix(ai-vault): scan configured Codex session home (#12186) | haazz Community · CONTRIBUTOR | #12186 [Bug]: Agent history from custom paths cannot be displayed in the Agent History Fixes · OPEN | Standalone change | ## Summary - Fix Agent History session discovery when Orca is configured with a custom Codex session home. - Pass the configured host Codex session source through both desktop IPC and headless `orca serve` runtime paths. | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +993/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scope capability state to the distro that runs git1 PR · Standalone · Automated release pipeline#
Problem: scope capability state to the distro that runs git.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15293 Title unavailable (Unclear, Unknown); #15039 Title unavailable (Unclear, Unknown); #15040 Title unavailable (Unclear, Unknown); #15060 Title unavailable (Unclear, Unknown); #15257 Title unavailable (Unclear, Unknown); #15290 Title unavailable (Unclear, Unknown); #14335 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15297 fix(git): scope capability state to the distro that runs git | OrcaWin Unknown · COLLABORATOR | #15293 Title unavailable Unclear · Unknown #15039 Title unavailable Unclear · Unknown #15040 Title unavailable Unclear · Unknown #15060 Title unavailable Unclear · Unknown #15257 Title unavailable Unclear · Unknown #15290 Title unavailable Unclear · Unknown #14335 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +351/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scope Git Bash capacity retention1 PR · Standalone · Automated release pipeline#
Problem: scope Git Bash capacity retention.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16045 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16662 fix(terminal): scope Git Bash capacity retentionDraft | Jinjing Core team · MEMBER | #16045 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +84/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scope PTY inventory by exact workspace owner1 PR · Standalone · Automated release pipeline#
Problem: scope PTY inventory by exact workspace owner.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16180 perf(runtime): scope PTY inventory by exact workspace owner | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +2079/−208. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2scope the worktree-visibility toggle to its own host1 PR · Standalone · Automated release pipeline#
Problem: scope the worktree-visibility toggle to its own host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13071 Title unavailable (Unclear, Unknown); #13117 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13211 fix(sidebar): scope the worktree-visibility toggle to its own host | manuaudio Community · CONTRIBUTOR | #13071 Title unavailable Unclear · Unknown #13117 Title unavailable Unclear · Unknown | Standalone change | Same defect class as #13071 (P1), in a different flow. No separate issue filed — happy to open one if you'd rather track it on its own. ## Summary The worktree-visibility toggle could show you one host's state and write | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +127/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2seed the spawn-window agent status from launch metadata1 PR · Standalone · Automated release pipeline#
Problem: seed the spawn-window agent status from launch metadata.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #6643 Codex agent status missing until first user message (Fixes, OPEN); #6829 Title unavailable (Unclear, Unknown); #14222 Title unavailable (Unclear, Unknown); #8292 Title unavailable (Unclear, Unknown); #11941 Title unavailable (Unclear, Unknown); #7950 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14611 fix(codex): seed the spawn-window agent status from launch metadata | Brennan Benson Core team · MEMBER | #6643 Codex agent status missing until first user message Fixes · OPEN #6829 Title unavailable Unclear · Unknown #14222 Title unavailable Unclear · Unknown #8292 Title unavailable Unclear · Unknown #11941 Title unavailable Unclear · Unknown #7950 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When you start a Codex agent in Orca, the agent row in the status surface used to be missing entirely until you sent your first message. That's because Codex's CLI doesn't tell Orca anything while it's sitting at | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +839/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2send a composing cursor chord once, not twice1 PR · Standalone · Automated release pipeline#
Problem: send a composing cursor chord once, not twice.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12871 [Bug]: Cmd/Option+Arrow during IME composition moves the composing character to the cursor destination (Korean & Japanese, macOS) (Fixes, CLOSED); #12732 Title unavailable (Unclear, Unknown); #14730 Title unavailable (Unclear, Unknown); #13282 Title unavailable (Unclear, Unknown); #12171 Title unavailable (Unclear, Unknown); #13033 Title unavailable (Unclear, Unknown); #13253 Title unavailable (Unclear, Unknown); #11094 Title unavailable (Unclear, Unknown); #15017 Title unavailable (Unclear, Unknown); #14743 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14742 fix(terminal): send a composing cursor chord once, not twice | 이건상 Community · CONTRIBUTOR | #12871 [Bug]: Cmd/Option+Arrow during IME composition moves the composing character to the cursor destination (Korean & Japanese, macOS) Fixes · CLOSED #12732 Title unavailable Unclear · Unknown #14730 Title unavailable Unclear · Unknown #13282 Title unavailable Unclear · Unknown #12171 Title unavailable Unclear · Unknown #13033 Title unavailable Unclear · Unknown #13253 Title unavailable Unclear · Unknown #11094 Title unavailable Unclear · Unknown #15017 Title unavailable Unclear · Unknown #14743 Title unavailable Unclear · Unknown | Standalone change | ## Summary Supersedes #12732, which GitHub will not let me reopen — I force-pushed the rebase before reopening it, and that is a one-way door. Same branch, same author, one commit now. Fixes #12871. Rebased onto #14730 a | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +3153/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2send Native Chat on hardware Enter1 PR · Standalone · Automated release pipeline#
Problem: send Native Chat on hardware Enter.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14744 feat(mobile): Support hardware keyboard shortcut to send messages in Native Chat (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14782 fix(mobile): send Native Chat on hardware Enter | Wooseong Kim Community · CONTRIBUTOR | #14744 feat(mobile): Support hardware keyboard shortcut to send messages in Native Chat Fixes · OPEN | Standalone change | ## Description Hardware Enter/Return in mobile Native Chat now sends the message. Shift+Enter still inserts a newline. ## Focused fix - In scope: hardware Enter → existing `handleSend()`. - Out of scope: removing multili | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +149/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2send one atomic mouseClick on the legacy remote pane1 PR · Standalone · Automated release pipeline#
Problem: send one atomic mouseClick on the legacy remote pane.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15402 perf(browser): send one atomic mouseClick on the legacy remote pane | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +976/−106. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2separate worktree issue metadata1 PR · Standalone · Automated release pipeline#
Problem: separate worktree issue metadata.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13119 refactor(jira): separate worktree issue metadata | Jinjing Core team · MEMBER | None found | Standalone change | ## Summary - Add a dedicated JiraIssueLink model with key, title, and canonical URL, stored as linkedJiraIssue with its matching linkedJiraIssueSourceContext. - Write new Jira-created worktrees through the dedicated fiel | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +1161/−41. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2serialize agent-prompt submits per PTY so overlapping sends stop gluing1 PR · Standalone · Automated release pipeline#
Problem: serialize agent-prompt submits per PTY so overlapping sends stop gluing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14935 Title unavailable (Unclear, Unknown); #14936 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14980 fix(terminal): serialize agent-prompt submits per PTY so overlapping sends stop gluingDraft | Brennan Benson Core team · MEMBER | #14935 Title unavailable Unclear · Unknown #14936 Title unavailable Unclear · Unknown | Standalone change | > **Status: DRAFT pending an independent review loop.** This change qualified for Orca's plan-first gate on > three counts (it changes ordering and failure handling, it crosses a client/host version boundary, and it > si | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks Unknown · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +295/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2serialize desktop viewport ownership1 PR · Standalone · Automated release pipeline#
Problem: serialize desktop viewport ownership.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8252 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16065 fix(terminal): serialize desktop viewport ownership | Jinwoo Hong Core team · MEMBER | #8252 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 20 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +2008/−64. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2settle exited headless terminal closes1 PR · Standalone · Automated release pipeline#
Problem: settle exited headless terminal closes.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #5788 Title unavailable (Unclear, Unknown); #8845 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15572 fix(runtime): settle exited headless terminal closes | OrcaWin Unknown · COLLABORATOR | #5788 Title unavailable Unclear · Unknown #8845 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +536/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2settle OMP status on terminal agent_end via willContinue1 PR · Standalone · Automated release pipeline#
Problem: settle OMP status on terminal agent_end via willContinue.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14278 Title unavailable (Unclear, Unknown); #14279 Title unavailable (Unclear, Unknown); #13891 Title unavailable (Unclear, Unknown); #13890 Title unavailable (Unclear, Unknown); #13923 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14330 fix(pi): settle OMP status on terminal agent_end via willContinue | Vlad Rafeev Community · FIRST_TIME_CONTRIBUTOR | #14278 Title unavailable Unclear · Unknown #14279 Title unavailable Unclear · Unknown #13891 Title unavailable Unclear · Unknown #13890 Title unavailable Unclear · Unknown #13923 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When an OMP agent finished its turn, the Orca pane could stay stuck showing "working" forever. Orca was waiting for OMP to report itself idle, but OMP never does that — instead it says on each `agent_end` whether | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +51/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ship the appearance-aware macOS icon catalog1 PR · Standalone · Automated release pipeline#
Problem: ship the appearance-aware macOS icon catalog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16495 [Bug]: macOS Clear and Tinted icon styles are ignored because the packaged app only contains a legacy ICNS (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16507 fix(packaging): ship the appearance-aware macOS icon catalog | Han Community · CONTRIBUTOR | #16495 [Bug]: macOS Clear and Tinted icon styles are ignored because the packaged app only contains a legacy ICNS Fixes · OPEN | Standalone change | ## Summary - `resources/icon-source/generate.sh` compiles the Icon Composer project twice: the original `10.12` target keeps feeding the legacy `icon.icns` pipeline (16/32px slot trimming, PNG and ICO derivations), and a | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +174/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show Codex compaction markers1 PR · Standalone · Automated release pipeline#
Problem: show Codex compaction markers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14188 [Bug]: Show Codex auto-compaction markers in native Chat transcripts (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14765 fix(native-chat): show Codex compaction markers | erish Community · CONTRIBUTOR | #14188 [Bug]: Show Codex auto-compaction markers in native Chat transcripts Fixes · OPEN | Standalone change | ## ELI5 When Codex automatically compresses an older conversation to free context space, Native Chat should show where that happened instead of silently jumping to a smaller context. ## What Changed - Decode completed Co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +19/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show Codex goal-mode digests (mobile empty transcript)1 PR · Standalone · Automated release pipeline#
Problem: show Codex goal-mode digests (mobile empty transcript).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13629 Mobile: Codex goal mode shows only “agent is working” (no transcript content) (Fixes, OPEN); #13494 Title unavailable (Unclear, Unknown); #13663 Title unavailable (Unclear, Unknown); #13687 Title unavailable (Unclear, Unknown); #13320 Title unavailable (Unclear, Unknown); #13393 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13985 fix(native-chat): show Codex goal-mode digests (mobile empty transcript) | OrcaWin Unknown · COLLABORATOR | #13629 Mobile: Codex goal mode shows only “agent is working” (no transcript content) Fixes · OPEN #13494 Title unavailable Unclear · Unknown #13663 Title unavailable Unclear · Unknown #13687 Title unavailable Unclear · Unknown #13320 Title unavailable Unclear · Unknown #13393 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Codex goal mode writes Active-goal / handoff digests as `response_item` messages with `phase: final_answer` and Response-API `output_text` blocks. Those never had an `event_msg` twin, and the shared Claude c | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +214/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show Fable remaining time in compact usage mode3 PRs · Overlapping · Profile and resource management#
Problem: show Fable remaining time in compact usage mode.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Profile and resource management (stack rank 2).
Relationship: Overlapping. Linked issues: #13041 [Bug] Compact mode show Fable instead time left (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13134 fix(status-bar): show Fable remaining time in compact usage mode | BingZ Community · CONTRIBUTOR | #13041 [Bug] Compact mode show Fable instead time left Fixes · OPEN | Cluster contribution | ## Summary - Compact usage chips for Claude's Fable window showed the fixed word **Fable** instead of remaining time (unlike Codex/Grok/Kimi). - Prefer `formatRateLimitWindowChipLabel` for every window when building the | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +20/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13141 fix(status-bar): show the Fable reset countdown beside its usage percent | manuaudio Community · CONTRIBUTOR | #13041 [Bug] Compact mode show Fable instead time left Fixes · OPEN | Cluster contribution | Closes #13041. ## Summary The Fable chip in the status bar now shows its reset countdown, like every chip beside it. Before, the provider segment read: ``` 10% used 3h 59m · 20% used 1d 23h · 30% used Fable ``` The sessi | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +99/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13226 fix(status-bar): show remaining duration for Claude Fable window in compact mode | left-to-right Community · FIRST_TIME_CONTRIBUTOR | #13041 [Bug] Compact mode show Fable instead time left Fixes · OPEN | Cluster contribution | ## Summary In compact usage mode, the Claude Fable 7-day window was labeled with the hardcoded window name "Fable" instead of the reset countdown every other window shows. `getTightestUsageSection` calls `shortLabel(..., | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +51/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show PR line totals in detail header1 PR · Standalone · Automated release pipeline#
Problem: show PR line totals in detail header.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13773 [Feature]: Show pull request line changes in the detail header (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13781 feat(tasks): show PR line totals in detail header | Killua AI Community · FIRST_TIME_CONTRIBUTOR | #13773 [Feature]: Show pull request line changes in the detail header Fixes · OPEN | Standalone change | ## Summary - Show GitHub-like `+additions` and `-deletions` totals beside the base/head branch pair in the pull request detail header. - Hydrate totals from the existing PR detail response, with the list item retained as | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +262/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show project name on status/PR-status grouped cards1 PR · Standalone · Automated release pipeline#
Problem: show project name on status/PR-status grouped cards.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13937 Sidebar: project name not shown on status/PR-status grouped cards (all read as main/master) (Fixes, OPEN); #13830 Title unavailable (Unclear, Unknown); #13828 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13938 fix(sidebar): show project name on status/PR-status grouped cards | Yunqian Fan Community · CONTRIBUTOR | #13937 Sidebar: project name not shown on status/PR-status grouped cards (all read as main/master) Fixes · OPEN #13830 Title unavailable Unclear · Unknown #13828 Title unavailable Unclear · Unknown | Standalone change | ## Summary Follow-on to #13830, extending its board fix to the **sidebar**. Closes #13937. When the sidebar is grouped by **workspace-status** or **PR-status** (or ungrouped), cards from different projects interleave wit | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +221/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show project name on Workspace board cards1 PR · Standalone · Automated release pipeline#
Problem: show project name on Workspace board cards.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13828 Workspace board: project name not shown on cards without a session (all read as main/master) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13830 fix(board): show project name on Workspace board cards | Yunqian Fan Community · CONTRIBUTOR | #13828 Workspace board: project name not shown on cards without a session (all read as main/master) Fixes · OPEN | Standalone change | Closes #13828 ## Summary On the Workspace board, cards with no descriptive title didn't show which **project** they belong to. Board lanes group by workspace status and mix projects, so each card is the only place its pr | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +206/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show prompts Claude queued while the agent was busy2 PRs · Overlapping · Automated release pipeline#
Problem: show prompts Claude queued while the agent was busy.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #14308 [Bug]: Prompts sent while Claude is busy disappear from native chat, and reappear out of order (Fixes, OPEN); #14446 Title unavailable (Unclear, Unknown); #14309 Title unavailable (Unclear, Unknown); #43 Title unavailable (Unclear, Unknown); #16972 Title unavailable (Unclear, Unknown); #16977 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14309 fix(native-chat): show prompts Claude queued while the agent was busy | Dalton Haksu Lee Community · FIRST_TIME_CONTRIBUTOR | #14308 [Bug]: Prompts sent while Claude is busy disappear from native chat, and reappear out of order Fixes · OPEN #14446 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 When you message a coworker who's busy, they finish what they're doing, *then* read your message. Claude Code does the same: a prompt sent mid-turn gets queued, and its transcript record is stamped when you sent | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +884/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #16121 fix(native-chat): preserve queued Claude prompts | Brennan Benson Core team · MEMBER | #14308 [Bug]: Prompts sent while Claude is busy disappear from native chat, and reappear out of order Fixes · OPEN #14309 Title unavailable Unclear · Unknown #43 Title unavailable Unclear · Unknown #16972 Title unavailable Unclear · Unknown #16977 Title unavailable Unclear · Unknown | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +628/−241. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Speed up worktree creation with a gated early terminal1 PR · Standalone · Automated release pipeline#
Problem: Speed up worktree creation with a gated early terminal.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13704 Speed up worktree creation with a gated early terminalDraft | Neil Core team · MEMBER | None found | Standalone change | ## Summary - parallelize independent username, base/ref, shared-path, include-file, and terminal-preparation work during worktree creation - split ordinary creation into `git worktree add --no-checkout` plus explicit mat | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk86 files, +10384/−1082. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split Codex hook service responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split Codex hook service responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17253 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17260 Split Codex hook service responsibilities | Neil Core team · MEMBER | #17253 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 16 | $\co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +2024/−1742. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split daemon initialization lifecycle1 PR · Standalone · Automated release pipeline#
Problem: Split daemon initialization lifecycle.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17157 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17161 Split daemon initialization lifecycle | Neil Core team · MEMBER | #17157 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 13 | $\co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +1622/−1402. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2split dispatch-liveness tests out of db.test.ts1 PR · Standalone · Automated release pipeline#
Problem: split dispatch-liveness tests out of db.test.ts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14907 Title unavailable (Unclear, Unknown); #8452 Title unavailable (Unclear, Unknown); #14918 Title unavailable (Unclear, Unknown); #15165 Title unavailable (Unclear, Unknown); #15869 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14889 test(orchestration): split dispatch-liveness tests out of db.test.ts | Tauri-EPO Community · CONTRIBUTOR | #14907 Title unavailable Unclear · Unknown #8452 Title unavailable Unclear · Unknown #14918 Title unavailable Unclear · Unknown #15165 Title unavailable Unclear · Unknown #15869 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 `db.test.ts` is nearly at the 800-line lint ceiling, so there is no room to add coverage to it. This moves one coherent group of tests into their own file. Nothing else changes. ## What Changed Moved the `recordH | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +142/−122. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split external automation manager1 PR · Standalone · Automated release pipeline#
Problem: Split external automation manager.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17146 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17149 Split external automation manager | Neil Core team · MEMBER | #17146 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 8 | $\col | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +491/−444. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split Git worktree responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split Git worktree responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17248 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17253 Split Git worktree responsibilities | Neil Core team · MEMBER | #17248 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 17 | $\co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1828/−1694. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split GitHub project view read path1 PR · Standalone · Automated release pipeline#
Problem: Split GitHub project view read path.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17263 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17266 Split GitHub project view read path | Neil Core team · MEMBER | #17263 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 13 | $\co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +1873/−1781. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split GitLab item dialog1 PR · Standalone · Automated release pipeline#
Problem: Split GitLab item dialog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17161 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17165 Split GitLab item dialog | Neil Core team · MEMBER | #17161 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +1885/−1488. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split Linear item drawer responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split Linear item drawer responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17231 Split Linear item drawer responsibilities | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1715/−1475. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split local PTY provider responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split local PTY provider responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17198 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17206 Split local PTY provider responsibilities | Neil Core team · MEMBER | #17198 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +2110/−1473. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split main window service attachments1 PR · Standalone · Automated release pipeline#
Problem: Split main window service attachments.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17149 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17151 Split main window service attachments | Neil Core team · MEMBER | #17149 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 4 | $\col | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +380/−359. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split mobile host screen layers1 PR · Standalone · Automated release pipeline#
Problem: Split mobile host screen layers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17174 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17181 Split mobile host screen layers | Neil Core team · MEMBER | #17174 Title unavailable Unclear · Unknown | Standalone change | ## Summary - split the mobile host route into focused state, synchronization, catalog, action, controller, and view modules - preserve the phone and embedded tablet host-list UI, route behavior, transport lifecycle, and | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +1875/−1423. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split ports panel layers1 PR · Standalone · Automated release pipeline#
Problem: Split ports panel layers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17188 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17194 Split ports panel layers | Neil Core team · MEMBER | #17188 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1546/−1504. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split relay dispatcher layers1 PR · Standalone · Automated release pipeline#
Problem: Split relay dispatcher layers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17165 Title unavailable (Unclear, Unknown); #17159 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17174 Split relay dispatcher layers | Neil Core team · MEMBER | #17165 Title unavailable Unclear · Unknown #17159 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +1636/−1513. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split remote terminal multiplexer responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split remote terminal multiplexer responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17244 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17248 Split remote terminal multiplexer responsibilities | Neil Core team · MEMBER | #17244 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 12 | $\co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1828/−1640. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split runtime environments pane layers1 PR · Standalone · Automated release pipeline#
Problem: Split runtime environments pane layers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17194 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17198 Split runtime environments pane layers | Neil Core team · MEMBER | #17194 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 12 | $\co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1930/−1461. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split runtime RPC server responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split runtime RPC server responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17268 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17270 Split runtime RPC server responsibilities | Neil Core team · MEMBER | #17268 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +2017/−1890. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split settings navigation metadata1 PR · Standalone · Automated release pipeline#
Problem: Split settings navigation metadata.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17155 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17157 Split settings navigation metadata | Neil Core team · MEMBER | #17155 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 7 | $\col | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +736/−636. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split telemetry event schema responsibilities1 PR · Standalone · Automated release pipeline#
Problem: Split telemetry event schema responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17231 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17235 Split telemetry event schema responsibilities | Neil Core team · MEMBER | #17231 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 12 | $\co | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1899/−1654. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split terminal output scheduler pipeline1 PR · Standalone · Automated release pipeline#
Problem: Split terminal output scheduler pipeline.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17123 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17131 Split terminal output scheduler pipeline | Neil Core team · MEMBER | #17123 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 7 | $\col | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +938/−773. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2STA-5296: keep Claude startup queries answerable on mobile1 PR · Standalone · Automated release pipeline#
Problem: STA-5296: keep Claude startup queries answerable on mobile.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16242 Title unavailable (Unclear, Unknown); #16917 Title unavailable (Unclear, Unknown); #16887 Title unavailable (Unclear, Unknown); #16850 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16825 STA-5296: keep Claude startup queries answerable on mobile | Brennan Benson Core team · MEMBER | #16242 Title unavailable Unclear · Unknown #16917 Title unavailable Unclear · Unknown #16887 Title unavailable Unclear · Unknown #16850 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 You open a Claude Code session from your phone. The very first thing Claude does is ask the terminal a question — how wide are you, where is the cursor — and it will not start until something answers. Two things | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +210/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stabilize scroll through grid resize1 PR · Standalone · Automated release pipeline#
Problem: stabilize scroll through grid resize.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12059 fix(terminal): stabilize scroll through grid resize | Neil Core team · MEMBER | None found | Standalone change | ## Summary - bottom-lock normal-buffer terminals only when a fit actually changes columns - preserve pinned scroll for row-only, failed, and grid-identical fits - prevent delayed split settlement from overwriting newer u | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +1100/−223. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop --json throwing a TypeError on a primitive result1 PR · Standalone · Automated release pipeline#
Problem: stop --json throwing a TypeError on a primitive result.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14508 [Bug]: three defects in the iOS emulator exec passthrough (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14735 fix(cli): stop --json throwing a TypeError on a primitive result | Vincent Community · FIRST_TIME_CONTRIBUTOR | #14508 [Bug]: three defects in the iOS emulator exec passthrough Fixes · OPEN | Standalone change | ## ELI5 If a CLI command answers with a plain piece of text instead of a structured object, `--json` crashed while printing the successful answer. This makes it print the text. ## What Changed `prepareComputerCliJsonResu | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +28/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a failed relay --connect from orphaning the live relay (STA-1756)1 PR · Standalone · Automated release pipeline#
Problem: stop a failed relay --connect from orphaning the live relay (STA-1756).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8585 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15250 fix(ssh): stop a failed relay --connect from orphaning the live relay (STA-1756) | Jinwoo Hong Core team · MEMBER | #8585 Title unavailable Unclear · Unknown | Standalone change | Fixes STA-1756 (#8585). ## What was broken `launchRelay` probes for an existing relay socket and, when `--connect` to it fails, it removed the socket and launched a fresh detached relay over the same path: ```ts // Why: | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +1627/−122. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a leaked hook-server listener from making the 130k-leaf migration test load-decided1 PR · Standalone · Automated release pipeline#
Problem: stop a leaked hook-server listener from making the 130k-leaf migration test load-decided.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17240 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17256 test(persistence): stop a leaked hook-server listener from making the 130k-leaf migration test load-decided | Brennan Benson Core team · MEMBER | #17240 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +6/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a leaked real timer from failing the updater scheduling test1 PR · Standalone · Automated release pipeline#
Problem: stop a leaked real timer from failing the updater scheduling test.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17086 fix(test): stop a leaked real timer from failing the updater scheduling test | Brennan Benson Core team · MEMBER | #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +5/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a recovery snapshot erasing scrollback it cannot replace1 PR · Standalone · Automated release pipeline#
Problem: stop a recovery snapshot erasing scrollback it cannot replace.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14593 Recovery snapshot erases terminal scrollback it cannot replace (desktop snapshots are screen-only) (Fixes, OPEN); #7329 Title unavailable (Unclear, Unknown); #9562 Title unavailable (Unclear, Unknown); #6106 Title unavailable (Unclear, Unknown); #14202 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14594 fix(terminal): stop a recovery snapshot erasing scrollback it cannot replace | Brennan Benson Core team · MEMBER | #14593 Recovery snapshot erases terminal scrollback it cannot replace (desktop snapshots are screen-only) Fixes · OPEN #7329 Title unavailable Unclear · Unknown #9562 Title unavailable Unclear · Unknown #6106 Title unavailable Unclear · Unknown #14202 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When a remote terminal recovers from a hiccup, the server sends back just what is on screen—not the terminal history. We were erasing the history before painting that screen, so scrollback vanished and the recove | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +200/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a relay leaking its own pane identity into every pane it spawns1 PR · Standalone · Automated release pipeline#
Problem: stop a relay leaking its own pane identity into every pane it spawns.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17243 Title unavailable (Unclear, Unknown); #10188 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17257 fix(pty): stop a relay leaking its own pane identity into every pane it spawns | Brennan Benson Core team · MEMBER | #17243 Title unavailable Unclear · Unknown #10188 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | Stacked on #17243. Base: `fix/unmanaged-omp-status-extension`. ## What broke The relay builds every PTY's environment from its own `process.env`, stripping only build-mode keys: ```ts // src/relay/pty-handler.ts — buildS | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk21 files, +1110/−44. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a removed worktree from breaking every spawn for the session1 PR · Standalone · Automated release pipeline#
Problem: stop a removed worktree from breaking every spawn for the session.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16463 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16702 fix(wsl): stop a removed worktree from breaking every spawn for the session | Brennan Benson Core team · MEMBER | #16463 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +554/−40. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a tab close reading "could not tell" as "nothing running"1 PR · Standalone · Automated release pipeline#
Problem: stop a tab close reading "could not tell" as "nothing running".
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17076 Title unavailable (Unclear, Unknown); #17077 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17079 fix(terminal): stop a tab close reading "could not tell" as "nothing running" | Brennan Benson Core team · MEMBER | #17076 Title unavailable Unclear · Unknown #17077 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +694/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop an unverified PTY loss from deleting tab records1 PR · Standalone · Automated release pipeline#
Problem: stop an unverified PTY loss from deleting tab records.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15549 [Bug][Windows] Ghost terminal registry entries: no UI tab, no OS process, but terminal list reports connected: true and terminal close succeeds without removing them (Fixes, OPEN); #16391 [Bug][Windows/WSL] A WSL distro shutdown deletes the tab records of every worktree that had a live PTY — 23 tabs gone, no close requested (Fixes, OPEN); #16463 [Bug]: Removing the worktree Orca was launched from breaks every wsl.exe spawn for the rest of the session (tabs stop rendering, new tab fails, agent detection empty) (Fixes, OPEN); #15710 Title unavailable (Unclear, Unknown); #15845 Title unavailable (Unclear, Unknown); #16307 Title unavailable (Unclear, Unknown); #16563 Title unavailable (Unclear, Unknown); #16551 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16585 fix(windows): stop an unverified PTY loss from deleting tab records | Neil Core team · MEMBER | #15549 [Bug][Windows] Ghost terminal registry entries: no UI tab, no OS process, but terminal list reports connected: true and terminal close succeeds without removing them Fixes · OPEN #16391 [Bug][Windows/WSL] A WSL distro shutdown deletes the tab records of every worktree that had a live PTY — 23 tabs gone, no close requested Fixes · OPEN #16463 [Bug]: Removing the worktree Orca was launched from breaks every wsl.exe spawn for the rest of the session (tabs stop rendering, new tab fails, agent detection empty) Fixes · OPEN #15710 Title unavailable Unclear · Unknown #15845 Title unavailable Unclear · Unknown #16307 Title unavailable Unclear · Unknown #16563 Title unavailable Unclear · Unknown #16551 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +421/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop Antigravity treating --sandbox as the commit prompt1 PR · Standalone · Automated release pipeline#
Problem: stop Antigravity treating --sandbox as the commit prompt.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14059 [Bug]: Antigravity receives --sandbox as the prompt when generating commit messages (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14157 fix(commit-message): stop Antigravity treating --sandbox as the commit prompt | Brennan Benson Core team · MEMBER | #14059 [Bug]: Antigravity receives --sandbox as the prompt when generating commit messages Fixes · OPEN | Standalone change | ## ELI5 When Orca asked Antigravity to write a commit message, it accidentally told the CLI that the job was `--sandbox` instead of the real prompt. This change puts the commit-message text in the flag Antigravity actual | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +48/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop background panes rendering blank after a system wake1 PR · Standalone · Automated release pipeline#
Problem: stop background panes rendering blank after a system wake.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #4480 Title unavailable (Unclear, Unknown); #9115 Title unavailable (Unclear, Unknown); #7240 Title unavailable (Unclear, Unknown); #5345 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13833 fix(terminal): stop background panes rendering blank after a system wake | Aesop Community · FIRST_TIME_CONTRIBUTOR | #4480 Title unavailable Unclear · Unknown #9115 Title unavailable Unclear · Unknown #7240 Title unavailable Unclear · Unknown #5345 Title unavailable Unclear · Unknown | Standalone change | ## The bug: a blank terminal over an intact buffer Wake the machine from sleep, switch to a workspace that was in the background, and its terminal panes can paint nothing at all. The xterm buffer is fine — scrollback is | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +170/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop chasing chunk recovery during a committed update install1 PR · Standalone · Automated release pipeline#
Problem: stop chasing chunk recovery during a committed update install.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13171 Title unavailable (Unclear, Unknown); #12950 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13172 fix(renderer): stop chasing chunk recovery during a committed update install | Jinwoo Hong Core team · MEMBER | #13171 Title unavailable Unclear · Unknown #12950 Title unavailable Unclear · Unknown | Standalone change | ## Summary When an update install is committed, Orca's installer replaces `app.asar` underneath the still-running renderer. Lazy chunks are read **by byte offset** out of that archive, so an import that would have succee | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +1077/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop Claude TUI remounts on Linux resize restreams (STA-3992)1 PR · Standalone · Automated release pipeline#
Problem: stop Claude TUI remounts on Linux resize restreams (STA-3992).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14017 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14164 fix(mobile): stop Claude TUI remounts on Linux resize restreams (STA-3992) | Brennan Benson Core team · MEMBER | #14017 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes [STA-3992](https://linear.app/stably/issue/STA-3992/bug-claude-code-keeps-rendering-on-orca-mobile) / #14017: switching to a Claude Code terminal on Orca Mobile remounts the TUI when the paired desktop/r | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +310/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop deleting the branch a worktree drifted onto1 PR · Standalone · Automated release pipeline#
Problem: stop deleting the branch a worktree drifted onto.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13877 fix(worktrees): stop deleting the branch a worktree drifted onto | Charles Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem Deleting a worktree pruned whatever branch it had checked out, and nothing in the local, relay, or runtime paths refused to prune the repo's default branch. That is reachable through an ordinary workflow. Ask | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +781/−128. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop foreground ConPTY helper fanout1 PR · Standalone · Automated release pipeline#
Problem: stop foreground ConPTY helper fanout.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10857 Title unavailable (Unclear, Unknown); #15749 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16074 fix(windows): stop foreground ConPTY helper fanoutDraft | OrcaWin Unknown · COLLABORATOR | #10857 Title unavailable Unclear · Unknown #15749 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 To work out *which program is currently in the foreground of a Windows terminal pane* — is Claude still running, or has it exited back to the shell? — Orca asked Windows for the list of processes attached to that | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +192/−191. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop Hide sleeping dropping a remote workspace row on a transient PTY gap1 PR · Standalone · Automated release pipeline#
Problem: stop Hide sleeping dropping a remote workspace row on a transient PTY gap.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15996 [Bug]: Hide sleeping transiently drops a remote workspace row from the sidebar for one frame when switching workspaces (Fixes, OPEN); #7197 Title unavailable (Unclear, Unknown); #15999 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16001 fix(sidebar): stop Hide sleeping dropping a remote workspace row on a transient PTY gap | gatsby74 Community · CONTRIBUTOR | #15996 [Bug]: Hide sleeping transiently drops a remote workspace row from the sidebar for one frame when switching workspaces Fixes · OPEN #7197 Title unavailable Unclear · Unknown #15999 Title unavailable Unclear · Unknown | Standalone change | Fixes #15996. ## What this changes With **Hide sleeping workspaces** on, a remote workspace's sidebar row could vanish for a single frame when a *different* workspace was activated. Every row below it — including the nex | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +434/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Stop keep reconnecting to remote1 PR · Standalone · Automated release pipeline#
Problem: Stop keep reconnecting to remote.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12155 Stop keep reconnecting to remote | Jinjing Core team · MEMBER | None found | Standalone change | ## Summary - Bound automatic SSH reconnect attempts to a 60-second wall-clock budget per target. - Keep that budget outside individual connection objects so pane remounts, automation dispatch, and replacement connections | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk22 files, +1085/−43. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop lazy-chunk recovery reloads from killing the user's terminals1 PR · Standalone · Automated release pipeline#
Problem: stop lazy-chunk recovery reloads from killing the user's terminals.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12950 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12943 fix(pty): stop lazy-chunk recovery reloads from killing the user's terminalsDraft | Jinwoo Hong Core team · MEMBER | #12950 Title unavailable Unclear · Unknown | Standalone change | ## Summary When the renderer fails to load a lazy-loaded code chunk, Orca attempts a recovery reload. Two separate defects meant that recovery **could not succeed**, and that attempting it **killed the user's running ter | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk37 files, +1385/−151. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop losing a startup command when the shell-ready marker is late1 PR · Standalone · Automated release pipeline#
Problem: stop losing a startup command when the shell-ready marker is late.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13642 Title unavailable (Unclear, Unknown); #14551 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15275 fix(daemon): stop losing a startup command when the shell-ready marker is late | Taras Kornichuk Community · CONTRIBUTOR | #13642 Title unavailable Unclear · Unknown #14551 Title unavailable Unclear · Unknown | Standalone change | Supersedes #13642, which @Jinwoo-H closed pending a deterministic reproduction. **That reproduction exists and is what this PR adds.** A new pull request rather than a reopen, for a mechanical reason worth stating: I pus | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +498/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop matching pending echoes across clock domains1 PR · Standalone · Automated release pipeline#
Problem: stop matching pending echoes across clock domains.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11519 [Bug]: Chat UI matches pending echoes across two clock domains — renderer send time vs remote transcript timestamps (Fixes, OPEN); #11509 Title unavailable (Unclear, Unknown); #13513 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13613 fix(native-chat): stop matching pending echoes across clock domains | Brennan Benson Core team · MEMBER | #11519 [Bug]: Chat UI matches pending echoes across two clock domains — renderer send time vs remote transcript timestamps Fixes · OPEN #11509 Title unavailable Unclear · Unknown #13513 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +2192/−576. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop painting every project on launch, then walking the list back1 PR · Standalone · Automated release pipeline#
Problem: stop painting every project on launch, then walking the list back.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16247 [Bug]: Sidebar paints every imported project on launch, then spends ~7s walking the list back (Fixes, OPEN); #7197 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16255 fix(sidebar): stop painting every project on launch, then walking the list back | gatsby74 Community · CONTRIBUTOR | #16247 [Bug]: Sidebar paints every imported project on launch, then spends ~7s walking the list back Fixes · OPEN #7197 Title unavailable Unclear · Unknown | Standalone change | ## What this fixes On cold launch the sidebar painted **every imported project** as a header row — including projects with nothing but sleeping workspaces — and then spent several seconds withdrawing them as data arrived | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +335/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop PTY layout writes from re-rendering every tab strip (STA-3328)1 PR · Standalone · Automated release pipeline#
Problem: stop PTY layout writes from re-rendering every tab strip (STA-3328).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12359 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12371 perf(tabs): stop PTY layout writes from re-rendering every tab strip (STA-3328) | Brennan Benson Core team · MEMBER | #12359 Title unavailable Unclear · Unknown | Standalone change | ## Summary Second installment of the STA-3328 typing-lag work (first: #12359, the spinner clock). This removes the tab-group render amplifiers confirmed by the terminal-pane React audit — the fan-out path that turns ever | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +336/−85. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reading an unreachable terminal as an idle one1 PR · Standalone · Automated release pipeline#
Problem: stop reading an unreachable terminal as an idle one.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16926 Title unavailable (Unclear, Unknown); #16955 Title unavailable (Unclear, Unknown); #17003 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17024 fix(cleanup): stop reading an unreachable terminal as an idle one | Brennan Benson Core team · MEMBER | #16926 Title unavailable Unclear · Unknown #16955 Title unavailable Unclear · Unknown #17003 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +1168/−163. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reconnect from grafting ghost terminal panes (STA-3077)1 PR · Standalone · Automated release pipeline#
Problem: stop reconnect from grafting ghost terminal panes (STA-3077).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11729 Title unavailable (Unclear, Unknown); #217 Title unavailable (Unclear, Unknown); #11860 Title unavailable (Unclear, Unknown); #13111 Title unavailable (Unclear, Unknown); #12448 Title unavailable (Unclear, Unknown); #11006 Title unavailable (Unclear, Unknown); #12699 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12264 fix(ssh): stop reconnect from grafting ghost terminal panes (STA-3077) | Jinjing Core team · MEMBER | #11729 Title unavailable Unclear · Unknown #217 Title unavailable Unclear · Unknown #11860 Title unavailable Unclear · Unknown #13111 Title unavailable Unclear · Unknown #12448 Title unavailable Unclear · Unknown #11006 Title unavailable Unclear · Unknown #12699 Title unavailable Unclear · Unknown | Standalone change | Fixes STA-3077 / #11729. > **On the line numbers below.** Cites in *Root cause* and *RC0* describe the code **as it was on > `main`** — they are the diagnosis, and they stop being findable at those offsets once this bran | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +3114/−104. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop remote terminals before project removal1 PR · Standalone · Automated release pipeline#
Problem: stop remote terminals before project removal.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13072 Remote-runtime agents survive project removal: terminal.stop runs after repo.rm, so its selector always fails (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13229 fix(workspace): stop remote terminals before project removal | Wooseong Kim Community · CONTRIBUTOR | #13072 Remote-runtime agents survive project removal: terminal.stop runs after repo.rm, so its selector always fails Fixes · OPEN | Standalone change | ## Summary Fixes #13072 by making project removal host-authoritative instead of relying on renderer-only terminal hints. - Route removal to the owning runtime and preserve duplicate project IDs on sibling hosts. - Reject | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +1389/−157. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reorder drags from selecting header labels1 PR · Standalone · Automated release pipeline#
Problem: stop reorder drags from selecting header labels.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13849 fix(sidebar): stop reorder drags from selecting header labels | Mike Bannister Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Dragging a project header in the sidebar to reorder it left the project's name partially highlighted, with the amount of text selected depending on where in the label you grabbed it. The three reorderable side | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +90/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reporting permission-denied worktrees as deleted1 PR · Standalone · Automated release pipeline#
Problem: stop reporting permission-denied worktrees as deleted.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13760 [Bug]: Command DaemonProtocolError: Working directory "/media/happy/6A82508782505A21/WebApps/MJH Hospital" does not exist. It may have been deleted or is on an unmounted volume. If this persists, please file an issue. (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13826 fix(pty): stop reporting permission-denied worktrees as deleted | 이수빈 Community · FIRST_TIME_CONTRIBUTOR | #13760 [Bug]: Command DaemonProtocolError: Working directory "/media/happy/6A82508782505A21/WebApps/MJH Hospital" does not exist. It may have been deleted or is on an unmounted volume. If this persists, please file an issue. Fixes · OPEN | Standalone change | Fixes #13760 ## Summary When spawning a terminal, `validateWorkingDirectory` decided "missing" with `existsSync`, which returns `false` for **every** stat failure — not just `ENOENT`. An existing directory Orca merely ca | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +109/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop retained output slices pinning whole parent strings1 PR · Standalone · Automated release pipeline#
Problem: stop retained output slices pinning whole parent strings.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12939 fix(terminal): stop retained output slices pinning whole parent stringsDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## Summary The terminal output scheduler re-slices partially-consumed output chunks back into its queue. V8 represents `String.prototype.slice` as a **SlicedString that retains a pointer to the entire parent string**, so | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +723/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop rewriting the engine user agent so Cloudflare challenges pass (STA-3905)1 PR · Standalone · Automated release pipeline#
Problem: stop rewriting the engine user agent so Cloudflare challenges pass (STA-3905).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12884 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17189 fix(browser): stop rewriting the engine user agent so Cloudflare challenges pass (STA-3905) | Brennan Benson Core team · MEMBER | #12884 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +71/−55. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop sibling session rows indenting when a lineage expands1 PR · Standalone · Automated release pipeline#
Problem: stop sibling session rows indenting when a lineage expands.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14084 [Bug]: Projects sidebar: expanding a session with sub-agents indents every other session in that project (Fixes, OPEN); #11796 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14126 fix(sidebar): stop sibling session rows indenting when a lineage expands | BingZ Community · CONTRIBUTOR | #14084 [Bug]: Projects sidebar: expanding a session with sub-agents indents every other session in that project Fixes · OPEN #11796 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Expanding a session with sub-agents reserved a 16px disclosure gutter on **every sibling root** (`anyRootHasChildren && !hasChildAgents`) so state-dots lined up with the parent chevron. - That is the measure | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +152/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop silently deleting workspaces of groups without a parentPath on load1 PR · Standalone · Automated release pipeline#
Problem: stop silently deleting workspaces of groups without a parentPath on load.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13344 fix(folder-workspace): stop silently deleting workspaces of groups without a parentPath on load | Eugenio Jesus Jose Valeiras Community · CONTRIBUTOR | None found | Standalone change | ## Summary `normalizeFolderWorkspaces` (src/shared/folder-workspaces.ts) only accepts persisted folder workspaces whose project group has a `parentPath`. A workspace created in a **manual group** (no `parentPath`) — reac | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +597/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the agent row's tool step from flickering on every hook (#11075)1 PR · Standalone · Automated release pipeline#
Problem: stop the agent row's tool step from flickering on every hook (#11075).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11075 [Bug]: Cursor tab/sidebar title flickers while agent is working (Fixes, OPEN); #5294 Title unavailable (Unclear, Unknown); #12466 Title unavailable (Unclear, Unknown); #14626 Title unavailable (Unclear, Unknown); #11127 Title unavailable (Unclear, Unknown); #12686 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14682 fix(sidebar): stop the agent row's tool step from flickering on every hook (#11075) | Brennan Benson Core team · MEMBER | #11075 [Bug]: Cursor tab/sidebar title flickers while agent is working Fixes · OPEN #5294 Title unavailable Unclear · Unknown #12466 Title unavailable Unclear · Unknown #14626 Title unavailable Unclear · Unknown #11127 Title unavailable Unclear · Unknown #12686 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 While a Cursor agent works, it tells Orca what it's doing several times a second — "reading this file", "running that command". The sidebar row printed every single one of those onto the same line as the workspac | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +389/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the titlebar spinner on settlement and idle compaction1 PR · Standalone · Automated release pipeline#
Problem: stop the titlebar spinner on settlement and idle compaction.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16470 [Bug]: OMP idle compaction leaves the tab spinner running after completion (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16880 fix(pi): stop the titlebar spinner on settlement and idle compaction | Neil Core team · MEMBER | #16470 [Bug]: OMP idle compaction leaves the tab spinner running after completion Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks PENDING · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: PENDING. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +357/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the WebRTC egress probe timing out its own startup1 PR · Standalone · Automated release pipeline#
Problem: stop the WebRTC egress probe timing out its own startup.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17071 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17125 fix(test): stop the WebRTC egress probe timing out its own startup | Brennan Benson Core team · MEMBER | #17071 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +211/−165. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop titlebar spinner from crashing on stale session ctx2 PRs · Overlapping · Automated release pipeline#
Problem: stop titlebar spinner from crashing on stale session ctx.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #14400 [Bug]: orca-titlebar-spinner extension crashes pi with uncaughtException on stale ctx after session replacement (Fixes, OPEN); #14412 Title unavailable (Unclear, Unknown); #14605 Title unavailable (Unclear, Unknown); #14664 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14412 fix(pi): stop titlebar spinner from crashing on stale session ctx | BingZ Community · CONTRIBUTOR | #14400 [Bug]: orca-titlebar-spinner extension crashes pi with uncaughtException on stale ctx after session replacement Fixes · OPEN | Cluster contribution | ## ELI5 Pi can die mid-turn if you replace the session while Orca's spinner is still ticking. The spinner now swallows that stale-handle error and stops instead of taking the process down. ## What Changed `orca-titlebar- | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +167/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14618 fix(pi): bind the titlebar spinner to its session incarnation (STA-4246) | Brennan Benson Core team · MEMBER | #14400 [Bug]: orca-titlebar-spinner extension crashes pi with uncaughtException on stale ctx after session replacement Fixes · OPEN #14412 Title unavailable Unclear · Unknown #14605 Title unavailable Unclear · Unknown #14664 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 Orca's π spinner asked pi "what's this session called?" 12 times a second. If you forked or switched sessions mid-turn, the next tick asked a session that no longer existed, pi threw, and because the question was | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +376/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop Windows checks from reporting a false latest version1 PR · Standalone · Automated release pipeline#
Problem: stop Windows checks from reporting a false latest version.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14325 fix(updater): stop Windows checks from reporting a false latest version | Jinjing Core team · MEMBER | None found | Standalone change | ## Problem A Windows user on `1.4.178-rc.2` clicked **Settings → General → Check for Updates** after `v1.4.182` shipped (with `latest.yml` + `orca-windows-setup.exe` on the release) and got *"You're on the latest version | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +540/−81. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop Windows teardown failing a passed rebuild-native-deps test1 PR · Standalone · Automated release pipeline#
Problem: stop Windows teardown failing a passed rebuild-native-deps test.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16955 Title unavailable (Unclear, Unknown); #17077 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17088 fix(test): stop Windows teardown failing a passed rebuild-native-deps test | Brennan Benson Core team · MEMBER | #16955 Title unavailable Unclear · Unknown #17077 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +30/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop workspace delete from waking a sleeping sibling1 PR · Standalone · Automated release pipeline#
Problem: stop workspace delete from waking a sleeping sibling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7197 Title unavailable (Unclear, Unknown); #10205 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14705 fix(sidebar): stop workspace delete from waking a sleeping sibling | JeongUk Park Community · CONTRIBUTOR | #7197 Title unavailable Unclear · Unknown #10205 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When you delete the workspace you're looking at, Orca moves you to another workspace in the same project so you don't end up staring at nothing. It just wasn't checking whether that other workspace was asleep. So | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +106/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2strip Electron's invoke envelope at the preload boundary1 PR · Standalone · Automated release pipeline#
Problem: strip Electron's invoke envelope at the preload boundary.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17259 Title unavailable (Unclear, Unknown); #17255 Title unavailable (Unclear, Unknown); #17237 Title unavailable (Unclear, Unknown); #17230 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17264 fix(ipc): strip Electron's invoke envelope at the preload boundary | Brennan Benson Core team · MEMBER | #17259 Title unavailable Unclear · Unknown #17255 Title unavailable Unclear · Unknown #17237 Title unavailable Unclear · Unknown #17230 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +1195/−859. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2strip Kimi hook-result envelopes2 PRs · Overlapping · Automated release pipeline#
Problem: strip Kimi hook-result envelopes.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Overlapping. Linked issues: #14789 Branch auto-name ingests agent hook envelopes (`<hook_result>`, system wrappers) — names anchor on noise (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14791 fix(agent-hooks): strip Kimi hook-result envelopes | BingZ Community · CONTRIBUTOR | #14789 Branch auto-name ingests agent hook envelopes (`<hook_result>`, system wrappers) — names anchor on noise Fixes · OPEN | Cluster contribution | ## ELI5 Kimi can place internal hook output next to the user's request. Orca treated that internal XML-like wrapper as if the user had typed it, so automatic branch and workspace names could describe the hook instead of | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +76/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14807 fix(agent-hooks): treat Kimi <hook_result> envelopes as harness-injected | Vincent Community · FIRST_TIME_CONTRIBUTOR | #14789 Branch auto-name ingests agent hook envelopes (`<hook_result>`, system wrappers) — names anchor on noise Fixes · OPEN | Cluster contribution | ## ELI5 When you type a request to Kimi, its hook sends Orca a second, robot-written message right after yours: `<hook_result hook_event="UserPromptSubmit">{}</hook_result>`. Orca already knows how to ignore robot messag | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +44/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2support helper on macOS 121 PR · Standalone · Automated release pipeline#
Problem: support helper on macOS 12.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15720 fix(computer-use): support helper on macOS 12Draft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +591/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2support non-secure web contexts1 PR · Standalone · Automated release pipeline#
Problem: support non-secure web contexts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #8804 Title unavailable (Unclear, Unknown); #11525 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13142 fix(ai-vault): support non-secure web contexts | BLUEAT Community · FIRST_TIME_CONTRIBUTOR | #8804 Title unavailable Unclear · Unknown #11525 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Prevent Agent Session History from crashing the right sidebar on plain HTTP web clients. - Use the existing `createBrowserUuid()` fallback for the AI Vault scan request token. - Add a regression test that mo | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +21/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface API auth error messages in Settings1 PR · Standalone · Automated release pipeline#
Problem: surface API auth error messages in Settings.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #13786 [Feature]: Surface the actual Gitea API error when integration auth fails (Fixes, OPEN); #14403 Title unavailable (Unclear, Unknown); #14728 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14045 fix(gitea): surface API auth error messages in Settings | BingZ Community · CONTRIBUTOR | #13786 [Feature]: Surface the actual Gitea API error when integration auth fails Fixes · OPEN #14403 Title unavailable Unclear · Unknown #14728 Title unavailable Unclear · Unknown | Standalone change | ## Summary - **Bug:** Gitea Settings card shows only a generic "could not authenticate" string when a configured token fails auth — even when Gitea returns an actionable body (e.g. missing `read:user` scope). - **Root ca | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +250/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface clipboard copy failures and make verify advisory1 PR · Standalone · Automated release pipeline#
Problem: surface clipboard copy failures and make verify advisory.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #5611 Title unavailable (Unclear, Unknown); #8977 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12779 fix(terminal): surface clipboard copy failures and make verify advisoryDraft | Brandon Bennett Community · CONTRIBUTOR | #5611 Title unavailable Unclear · Unknown #8977 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When you copied selected text from a terminal, Orca sometimes showed success but the paste came out empty — mostly on Windows, where clipboard managers can tweak text behind the scenes and trip Orca's own double- | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +93/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface load-earlier failures and stop retry storms (STA-3333)1 PR · Standalone · Automated release pipeline#
Problem: surface load-earlier failures and stop retry storms (STA-3333).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12499 fix(native-chat): surface load-earlier failures and stop retry storms (STA-3333) | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary Fixes native-chat history paging failures on both desktop and mobile without duplicating the behavior between clients. - Uses one shared load-earlier controller for request deduplication, stale-result invalida | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1119/−183. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2syntax highlighting for Glimmer and Handlebars1 PR · Standalone · Automated release pipeline#
Problem: syntax highlighting for Glimmer and Handlebars.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13236 feat(editor): syntax highlighting for Glimmer and Handlebars | Jorge Albarracín Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Adds Monaco syntax highlighting for the Ember/Glimmer stack, which previously fell back to plaintext in Orca's editor/diff viewer: - `.gjs` / `.gts` — Glimmer JS/TS components. A parametrized Monarch tokenizer | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +280/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2syntax-highlight VHDL and SystemVerilog1 PR · Standalone · Automated release pipeline#
Problem: syntax-highlight VHDL and SystemVerilog.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12123 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12124 feat(mobile): syntax-highlight VHDL and SystemVerilog | Nickel Liang Community · FIRST_TIME_CONTRIBUTOR | #12123 Title unavailable Unclear · Unknown | Standalone change | ## What Mobile's extension map (`mobile/src/session/mobile-file-language.ts`) carried no HDL at all, so `.vhd` **and** `.sv` files rendered flat in both the file viewer and the diff review pane. Companion to #12123, whic | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +57/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2teach dispatched workers the status message for progress1 PR · Standalone · Automated release pipeline#
Problem: teach dispatched workers the status message for progress.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14311 Title unavailable (Unclear, Unknown); #14764 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14762 fix(orchestration): teach dispatched workers the status message for progress | Rayim Community · CONTRIBUTOR | #14311 Title unavailable Unclear · Unknown #14764 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When Orca dispatches a worker, it injects a preamble listing the commands that worker may use to talk back. For a worker that is midway through a task and wants to say "phase one is done, starting phase two", non | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +144/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2tell a settled worker what happened instead of that it is revoked1 PR · Standalone · Automated release pipeline#
Problem: tell a settled worker what happened instead of that it is revoked.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14311 Title unavailable (Unclear, Unknown); #14762 Title unavailable (Unclear, Unknown); #12528 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14764 fix(orchestration): tell a settled worker what happened instead of that it is revoked | Rayim Community · CONTRIBUTOR | #14311 Title unavailable Unclear · Unknown #14762 Title unavailable Unclear · Unknown #12528 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When a worker's dispatch has been settled, its next `worker_done` or `heartbeat` comes back as: ``` Dispatch ctx_… capability is revoked. ``` That sentence names a mechanism. It does not say what settled the disp | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +224/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2tell a watched local exit apart from a lost route1 PR · Standalone · Automated release pipeline#
Problem: tell a watched local exit apart from a lost route.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17024 Title unavailable (Unclear, Unknown); #17044 Title unavailable (Unclear, Unknown); #17076 Title unavailable (Unclear, Unknown); #17079 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17058 fix(pty): tell a watched local exit apart from a lost route | Brennan Benson Core team · MEMBER | #17024 Title unavailable Unclear · Unknown #17044 Title unavailable Unclear · Unknown #17076 Title unavailable Unclear · Unknown #17079 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 14 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk33 files, +1799/−53. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2treat SYSTEMROOT as optional in the Git Bash hook wrapper1 PR · Standalone · Automated release pipeline#
Problem: treat SYSTEMROOT as optional in the Git Bash hook wrapper.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14794 [Bug]: Grok skips managed hooks on macOS because $SYSTEMROOT is required (Fixes, CLOSED); #14994 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14793 fix(agent-hooks): treat SYSTEMROOT as optional in the Git Bash hook wrapper | Miguel Angel Flores Community · FIRST_TIME_CONTRIBUTOR | #14794 [Bug]: Grok skips managed hooks on macOS because $SYSTEMROOT is required Fixes · CLOSED #14994 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 The hook command Orca installs for Claude/Grok already treats `HOME` and `OSTYPE` as optional. `SYSTEMROOT` was left as a required `$VAR`. On macOS and Linux that variable does not exist, so Grok refuses to spawn | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +5/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2trim trailing PROMPT_COMMAND separator in the daemon bash wrapper1 PR · Standalone · Automated release pipeline#
Problem: trim trailing PROMPT_COMMAND separator in the daemon bash wrapper.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14448 [Bug]: daemon bash shell-ready wrapper builds ';;' in PROMPT_COMMAND (breaks OSC 133 with zoxide) (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14451 fix(shell-ready): trim trailing PROMPT_COMMAND separator in the daemon bash wrapper | Oliver Mee Community · CONTRIBUTOR | #14448 [Bug]: daemon bash shell-ready wrapper builds ';;' in PROMPT_COMMAND (breaks OSC 133 with zoxide) Fixes · CLOSED | Standalone change | ## ELI5 If your shell config leaves `PROMPT_COMMAND` ending in a `;`, Orca's daemon wrapper glues its own hooks on and you end up with `;;`, which bash refuses to run. This trims that stray `;` first. The relay wrapper a | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +23/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2update watcher targets incrementally1 PR · Standalone · Automated release pipeline#
Problem: update watcher targets incrementally.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16176 perf(repos): update watcher targets incrementally | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 5 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +1765/−175. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2use a codex-specific 3s managed hook timeout, and cover the EOF pipe-break signature in the 1 PR · Standalone · Automated release pipeline#
Problem: use a codex-specific 3s managed hook timeout, and cover the EOF pipe-break signature in the .
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11549 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13900 fix(codex): use a codex-specific 3s managed hook timeout, and cover the EOF pipe-break signature in the Windows hook lifecycle tests | SiwenPz Community · FIRST_TIME_CONTRIBUTOR | #11549 Title unavailable Unclear · Unknown | Standalone change | ### Summary Two focused improvements on top of the recently merged missing-env guard fix (#11549): 1. **Codex-specific hook timeout.** All agents currently share `MANAGED_HOOK_TIMEOUT_SECONDS = 10`. Codex now uses its ow | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +25/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2use createBrowserUuid for cross-platform UUID generation1 PR · Standalone · Automated release pipeline#
Problem: use createBrowserUuid for cross-platform UUID generation.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13101 fix(right-sidebar): use createBrowserUuid for cross-platform UUID generation | Kevin Ku Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Fixes a renderer crash in the AiVault panel when connecting to a remote Orca backend through a web browser served over plain HTTP (non-secure context). `crypto.randomUUID` is a [secure-context-only](https:// | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +30/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2use launch agent for first auto-name1 PR · Standalone · Automated release pipeline#
Problem: use launch agent for first auto-name.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14428 [Bug]: First-work auto-name ignores the selected launch agent (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14431 fix(workspaces): use launch agent for first auto-name | Leo(오영택) Community · FIRST_TIME_CONTRIBUTOR | #14428 [Bug]: First-work auto-name ignores the selected launch agent Fixes · OPEN | Standalone change | ## ELI5 When a workspace is opened with a launch agent that supports Source Control AI text generation, Orca now asks that same agent to create the first automatic workspace or branch name. Previously, this path could ca | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +187/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2use native monospace font on iOS1 PR · Standalone · Automated release pipeline#
Problem: use native monospace font on iOS.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14093 fix(mobile): use native monospace font on iOS | Yongqi Zhuo Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## ELI5 The iOS app asked React Native for a font named `monospace`. iOS does not recognize that name in native text, so it silently displayed the proportional system font. This change asks iOS for its built-in monospace | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +19/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2verify derived-sort drops don't accidentally switch to manual1 PR · Standalone · Automated release pipeline#
Problem: verify derived-sort drops don't accidentally switch to manual.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12762 test: verify derived-sort drops don't accidentally switch to manual | Jinjing Core team · MEMBER | None found | Standalone change | ## Problem When dragging a card within a derived-sort mode (like 'recent'), a minor repositioning that returns the card to its original position or a nearby slot was incorrectly triggering a switch to manual sort. This c | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +96/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2wait out a disconnected PTY owner's full grace instead of failing the connect1 PR · Standalone · Automated release pipeline#
Problem: wait out a disconnected PTY owner's full grace instead of failing the connect.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12745 SSH reconnect death-loops when a disconnected PTY owner keeps its full grace ('local' disconnect cause) (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12749 fix(ssh): wait out a disconnected PTY owner's full grace instead of failing the connect | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12745 SSH reconnect death-loops when a disconnected PTY owner keeps its full grace ('local' disconnect cause) Fixes · CLOSED | Standalone change | ## Summary Fixes #12745. Use monotonic duration accounting for relay owner grace and client reconnect retry budgets so wall-clock adjustments cannot distort either interval. When the disconnected-holder budget expires, p | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +475/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2wake a restored idle pane that never speaks again1 PR · Standalone · Automated release pipeline#
Problem: wake a restored idle pane that never speaks again.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13203 fix(orchestration): wake a restored idle pane that never speaks again | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## The report A coordinator was left idle overnight. Eight worker messages arrived and none reached it. When the user came back and sent an unrelated prompt, all eight surfaced at once — making it look like delivery is t | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +636/−24. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2warn before closing SSH work1 PR · Standalone · Automated release pipeline#
Problem: warn before closing SSH work.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #17044 Title unavailable (Unclear, Unknown); #17076 Title unavailable (Unclear, Unknown); #17085 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17077 fix(terminal): warn before closing SSH work | Brennan Benson Core team · MEMBER | #17044 Title unavailable Unclear · Unknown #17076 Title unavailable Unclear · Unknown #17085 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk23 files, +1204/−154. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2watch the directory of open files outside every worktree root1 PR · Standalone · Automated release pipeline#
Problem: watch the directory of open files outside every worktree root.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #15612 [Bug]: Files opened from outside a worktree root never auto-reload and show no changed-on-disk banner (Fixes, OPEN); #15512 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15627 fix(editor): watch the directory of open files outside every worktree root | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15612 [Bug]: Files opened from outside a worktree root never auto-reload and show no changed-on-disk banner Fixes · OPEN #15512 Title unavailable Unclear · Unknown | Standalone change | ## Summary **What** `getEditorExternalWatchTargets` now emits one additional watch target per distinct containing directory (per owner) for open files that resolve outside their worktree/folder-workspace root. **Why** #1 | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +211/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2watch the whole worktree so nested external edits reach open editors1 PR · Standalone · Automated release pipeline#
Problem: watch the whole worktree so nested external edits reach open editors.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #7792 [Bug]: Windows/WSL open Markdown files stay stale until close, refresh, and reopen (Fixes, OPEN); #7968 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12472 fix(wsl): watch the whole worktree so nested external edits reach open editorsDraft | Neil Core team · MEMBER | #7792 [Bug]: Windows/WSL open Markdown files stay stale until close, refresh, and reopen Fixes · OPEN #7968 Title unavailable Unclear · Unknown | Standalone change | The WSL in-distro poll scan was capped at `-maxdepth 2`, so external edits to any file nested deeper never produced an `fs:changed` event. An open editor tab kept its in-memory content until it was closed and reopened — | P2 Useful scoped improvement; aligned with Automated release pipeline but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +126/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add GPT Transcribe model1 PR · Standalone · Agent management and search#
Problem: add GPT Transcribe model.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12116 feat(speech): add GPT Transcribe model | YulHeon Kim Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - register GPT Transcribe in the shared speech model catalog so desktop and paired mobile settings can surface it - map the catalog ID to OpenAI's gpt-transcribe Audio API model - add regression coverage for t | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +69/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Add native Plane task tracker integration1 PR · Standalone · Agent management and search#
Problem: Add native Plane task tracker integration.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #8009 [Feature]: Add native Plane task tracker integration (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14692 Add native Plane task tracker integration | Ugo Enyioha Community · FIRST_TIME_CONTRIBUTOR | #8009 [Feature]: Add native Plane task tracker integration Fixes · OPEN | Standalone change | ## ELI5 Plane work items can now be used in Orca the same way Linear and Jira tasks are used: connect a Plane workspace, search or list work items, and create linked Orca workspaces from them. Plane can be connected with | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk105 files, +8155/−98. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2add the macOS blur surface for Background Opacity and Window Blur (partial)1 PR · Standalone · Agent management and search#
Problem: add the macOS blur surface for Background Opacity and Window Blur (partial).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #8797 [Bug]: "Background Opacity" and "Window Blur" have no visible effect on macOS (Fixes, OPEN); #8482 Title unavailable (Unclear, Unknown); #10349 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12470 fix(window): add the macOS blur surface for Background Opacity and Window Blur (partial) | Neil Core team · MEMBER | #8797 [Bug]: "Background Opacity" and "Window Blur" have no visible effect on macOS Fixes · OPEN #8482 Title unavailable Unclear · Unknown #10349 Title unavailable Unclear · Unknown | Standalone change | macOS configured no vibrancy surface at all, and an opaque fill sat between the desktop and the terminal, so Background Opacity and Window Blur both looked like no-ops. ## Fix Adds a platform-gated blur surface (`resolve | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +205/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2allow zero-message agent sessions1 PR · Standalone · Agent management and search#
Problem: allow zero-message agent sessions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14200 fix(native-chat): allow zero-message agent sessions | Brennan Benson Core team · MEMBER | None found | Standalone change | ## Summary - admit native Chat from pane-local launch identity before the first hook or transcript message - share pane identity precedence across the pane button/session gate, keyboard shortcut, and tab context menu - f | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +469/−59. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2block delete on branch-attributed shared stash (partial)1 PR · Standalone · Agent management and search#
Problem: block delete on branch-attributed shared stash (partial).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13695 Title unavailable (Unclear, Unknown); #11571 Title unavailable (Unclear, Unknown); #13930 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13979 fix(worktree): block delete on branch-attributed shared stash (partial) | OrcaWin Unknown · COLLABORATOR | #13695 Title unavailable Unclear · Unknown #11571 Title unavailable Unclear · Unknown #13930 Title unavailable Unclear · Unknown | Standalone change | ## Summary **Partial only.** Addresses the **worktree-removal adjacency** in #13695. Does **not** solve agent terminal/tool `git stash` pop/drop/clear across worktrees. - Shared `refs/stash` has no worktree ownership. No | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +519/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound Windows Claude hook stdin before curl1 PR · Standalone · Agent management and search#
Problem: bound Windows Claude hook stdin before curl.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13285 [Bug]: Managed hook scripts block unbounded on stdin — neither the `more.com` drain nor curl's `payload@-` is covered by a timeout (~12s stall per fire; residual of #7323) (Fixes, CLOSED); #14837 Title unavailable (Unclear, Unknown); #8419 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13560 fix(agent-hooks): bound Windows Claude hook stdin before curl | Brennan Benson Core team · MEMBER | #13285 [Bug]: Managed hook scripts block unbounded on stdin — neither the `more.com` drain nor curl's `payload@-` is covered by a timeout (~12s stall per fire; residual of #7323) Fixes · CLOSED #14837 Title unavailable Unclear · Unknown #8419 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Bound local Windows Claude hook stdin in the existing PowerShell launcher instead of shortening the provider host timeout. - Detect and validate a complete top-level JSON payload without waiting for EOF, cap | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +356/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cache legacy worktree clean fallback1 PR · Standalone · Agent management and search#
Problem: cache legacy worktree clean fallback.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14555 Title unavailable (Unclear, Unknown); #15297 Title unavailable (Unclear, Unknown); #10408 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17213 perf(ssh): cache legacy worktree clean fallback | Neil Core team · MEMBER | #14555 Title unavailable Unclear · Unknown #15297 Title unavailable Unclear · Unknown #10408 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +247/−47. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2closeTerminalTab must not orphan a runtime-owned pty behind tab_not_found (#14719)1 PR · Standalone · Agent management and search#
Problem: closeTerminalTab must not orphan a runtime-owned pty behind tab_not_found (#14719).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14719 [Bug]: `terminal close --tab` returns tab_not_found but leaves the terminal running (Antigravity/agy TUI); plain terminals close fine (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14726 fix: closeTerminalTab must not orphan a runtime-owned pty behind tab_not_found (#14719) | nomuvan Community · FIRST_TIME_CONTRIBUTOR | #14719 [Bug]: `terminal close --tab` returns tab_not_found but leaves the terminal running (Antigravity/agy TUI); plain terminals close fine Fixes · OPEN | Standalone change | ## Problem `orca terminal close --tab <handle>` (RPC `terminal.closeTab`) can fail with `tab_not_found` while the addressed terminal stays `running` (#14719). `closeTerminalTab()` resolves a runtime-owned pty by handle a | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +94/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2consolidate agent prompt and mailbox PTY delivery ownership1 PR · Standalone · Agent management and search#
Problem: consolidate agent prompt and mailbox PTY delivery ownership.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16198 fix: consolidate agent prompt and mailbox PTY delivery ownership | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 13 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk34 files, +2915/−502. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2count a client-initiated ping as proof of life1 PR · Standalone · Agent management and search#
Problem: count a client-initiated ping as proof of life.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12327 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12548 fix(runtime): count a client-initiated ping as proof of life | Daniel (Danai) Rudaev Community · CONTRIBUTOR | #12327 Title unavailable Unclear · Unknown | Standalone change | `handleConnection` in `src/main/runtime/rpc/ws-transport.ts` registers `pong` and `message` as proof of life, but not `ping`. Clients run their own liveness probe every 10s (`REMOTE_RUNTIME_SOCKET_PING_INTERVAL_MS` in `s | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +9/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cover paired Windows ownership races1 PR · Standalone · Agent management and search#
Problem: cover paired Windows ownership races.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15575 test(agent-session): cover paired Windows ownership racesDraft | OrcaWin Unknown · COLLABORATOR | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +785/−21. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Daemon terminal-host inspection: a degraded read is unverifiable, never an agent exit1 PR · Standalone · Agent management and search#
Problem: Daemon terminal-host inspection: a degraded read is unverifiable, never an agent exit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #16926 Title unavailable (Unclear, Unknown); #16955 Title unavailable (Unclear, Unknown); #16900 Title unavailable (Unclear, Unknown); #16908 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17003 Daemon terminal-host inspection: a degraded read is unverifiable, never an agent exit | Brennan Benson Core team · MEMBER | #16926 Title unavailable Unclear · Unknown #16955 Title unavailable Unclear · Unknown #16900 Title unavailable Unclear · Unknown #16908 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +1962/−235. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2defer the sleeping-agent sweep until a direct-SSH workspace merges its snapshot1 PR · Standalone · Agent management and search#
Problem: defer the sleeping-agent sweep until a direct-SSH workspace merges its snapshot.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12701 SSH: sleeping-agent sweep races the remote workspace snapshot merge — every restart cold-resumes live remote sessions and destroys their records (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12704 fix(agents): defer the sleeping-agent sweep until a direct-SSH workspace merges its snapshot | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12701 SSH: sleeping-agent sweep races the remote workspace snapshot merge — every restart cold-resumes live remote sessions and destroys their records Fixes · OPEN | Standalone change | ## Summary Fixes #12701. For direct-SSH workspaces the worktree tab lists arrive with the remote snapshot merge, after connect; the sleeping-agent sweep runs earlier (its only gate, `workspaceSessionReady`, means local h | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +1454/−175. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2deliver agent completion notifications from serve hosts1 PR · Standalone · Agent management and search#
Problem: deliver agent completion notifications from serve hosts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12044 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12045 fix(remote): deliver agent completion notifications from serve hosts | gal064 Community · FIRST_TIME_CONTRIBUTOR | #12044 Title unavailable Unclear · Unknown | Standalone change | > **Stacked on #12044.** Branched off it, so its diff appears here too. Review/merge that one first; this PR's own change is the last commit (`fix(remote): deliver agent completion notifications from serve hosts`). ## Pr | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +358/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2design durable bounded shutdown follow-up1 PR · Standalone · Agent management and search#
Problem: design durable bounded shutdown follow-up.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12367 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12425 docs(ssh): design durable bounded shutdown follow-upDraft | Jinjing Core team · MEMBER | #12367 Title unavailable Unclear · Unknown | Standalone change | ## Summary Design-only follow-up to #12367 for making SSH quit snapshots durable and transport teardown bounded. The design introduces one synchronous shutdown entry point that marks recovery leases detached before the f | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +193/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2detect new-tab agents on runtime execution owner1 PR · Standalone · Agent management and search#
Problem: detect new-tab agents on runtime execution owner.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13752 [Bug][Mobile]: New-tab agent menu resolves detection from repo.connectionId only, so runtime-hosted workspaces list the paired host's agents (Fixes, OPEN); #5832 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13977 fix(mobile): detect new-tab agents on runtime execution owner | OrcaWin Unknown · COLLABORATOR | #13752 [Bug][Mobile]: New-tab agent menu resolves detection from repo.connectionId only, so runtime-hosted workspaces list the paired host's agents Fixes · OPEN #5832 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Mobile new-tab agent menu previously resolved detection from `repo.connectionId` only, so runtime-hosted repos (`connectionId: null`) probed the **paired host** instead of the runtime execution owner. - Adds | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +379/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2disambiguate same-named projects by host role1 PR · Standalone · Agent management and search#
Problem: disambiguate same-named projects by host role.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13221 [Bug]: Sidebar shows project by full path (and duplicated) when a Local project and a remote-runtime project share the same repo — no Local/Remote indicator (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13222 fix(sidebar): disambiguate same-named projects by host role | BingZ Community · CONTRIBUTOR | #13221 [Bug]: Sidebar shows project by full path (and duplicated) when a Local project and a remote-runtime project share the same repo — no Local/Remote indicator Fixes · OPEN | Standalone change | ## Summary - Cross-host project name collisions now render as `foo · Local` / `foo · Remote` / `foo · SSH` instead of expanding into a near-full absolute path. - Same-host basename collisions still use minimal parent pat | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +79/−25. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2dismiss the keyboard after sending to an agent1 PR · Standalone · Agent management and search#
Problem: dismiss the keyboard after sending to an agent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14819 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17059 fix(mobile): dismiss the keyboard after sending to an agent | Brennan Benson Core team · MEMBER | #14819 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 17 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk34 files, +1755/−64. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document status --json runtime capability flags1 PR · Standalone · Agent management and search#
Problem: document status --json runtime capability flags.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13202 Capability flags: 31 names are served bare by status --json with no documented semantics (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13212 docs(cli): document status --json runtime capability flags | BingZ Community · CONTRIBUTOR | #13202 Capability flags: 31 names are served bare by status --json with no documented semantics Fixes · OPEN | Standalone change | ## Summary - Adds a one-line semantics map for every static runtime capability flag (`RUNTIME_CAPABILITY_DOCS`). - `orca status --json` now includes `runtime.capabilityDocs` for the advertised flags (client-side enrichme | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +218/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document terminal read --json result schema1 PR · Standalone · Agent management and search#
Problem: document terminal read --json result schema.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #7433 [Other]: `terminal read --help` does not document the `--json` result schema (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13173 docs(cli): document terminal read --json result schema | BingZ Community · CONTRIBUTOR | #7433 [Other]: `terminal read --help` does not document the `--json` result schema Fixes · OPEN | Standalone change | ## Summary - `orca terminal read --help` documented flags but not the `--json` result shape (#7433). - Agents misread `latestCursor` as the paging token; only `nextCursor` should feed a later `--cursor`. - Add Notes cove | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +39/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2don't tear down terminals when a scan lists no worktrees1 PR · Standalone · Agent management and search#
Problem: don't tear down terminals when a scan lists no worktrees.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12913 [Bug]: Agent pane sessions torn down repeatedly (session-exited code 0) — moving .git aside kills the session within ~1s (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12916 fix(worktrees): don't tear down terminals when a scan lists no worktrees | 이강은 Community · FIRST_TIME_CONTRIBUTOR | #12913 [Bug]: Agent pane sessions torn down repeatedly (session-exited code 0) — moving .git aside kills the session within ~1s Fixes · OPEN | Standalone change | Fixes #12913 ## Problem `listWorktrees` maps git's "not a git repository" failure to `[]`: ```ts // src/main/git/worktree.ts — listWorktreesUnshared if (isNotGitRepositoryError(err)) { return [] } ``` So a repo whose `.g | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +307/−20. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop residual per-PTY map entries on teardown1 PR · Standalone · Agent management and search#
Problem: drop residual per-PTY map entries on teardown.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15286 fix(runtime): drop residual per-PTY map entries on teardown | kseungyong Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary A full memory-leak audit of the desktop app (main process, renderer, remote/SSH/relay, terminal/PTY lifecycle), the mobile app, and the CLI found three small unbounded-growth leaks, all the same shape: a per-e | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +57/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop the ssh-pty-provider mock key that names no export1 PR · Standalone · Agent management and search#
Problem: drop the ssh-pty-provider mock key that names no export.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17222 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17232 test(ipc): drop the ssh-pty-provider mock key that names no export | Brennan Benson Core team · MEMBER | #17222 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 1 | 0 | $ | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +0/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2drop the standalone Chat session launcher1 PR · Standalone · Agent management and search#
Problem: drop the standalone Chat session launcher.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15372 feat(native-chat): drop the standalone Chat session launcher | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 1 | $\col | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +1/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2emit a typed exited frame before the terminal stream ends1 PR · Standalone · Agent management and search#
Problem: emit a typed exited frame before the terminal stream ends.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #9433 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12836 fix(runtime): emit a typed exited frame before the terminal stream ends | BingZ Community · CONTRIBUTOR | #9433 Title unavailable Unclear · Unknown | Standalone change | ## Summary Remote clients that opt in can distinguish “the terminal process exited” from “the stream disconnected.” The host emits a typed `{ type: 'exited', exitCode }` frame immediately before the terminal stream's `en | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +214/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2expire the app-wide WebGL DOM suggestion at recovery boundaries1 PR · Standalone · Agent management and search#
Problem: expire the app-wide WebGL DOM suggestion at recovery boundaries.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15455 fix(terminal): expire the app-wide WebGL DOM suggestion at recovery boundaries | Brennan Benson Core team · MEMBER | None found | Standalone change | ## What One failed WebGL attach in `auto` mode — the shipped default — sets the module-global `suggestedRendererType` to `'dom'`. Nothing clears it for the rest of the app session except the user toggling the GPU setting | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +152/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2expose terminal agent status1 PR · Standalone · Agent management and search#
Problem: expose terminal agent status.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12844 [Feature]: Expose terminal agent status through the public CLI (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12994 feat(cli): expose terminal agent status | Wooseong Kim Community · CONTRIBUTOR | #12844 [Feature]: Expose terminal agent status through the public CLI Fixes · OPEN | Standalone change | ## Description Expose the existing terminal agent-status RPC through a public non-blocking CLI command. ## Focused fix - In scope: add `orca terminal agent-status`, its human-readable and JSON formatters, and focused CLI | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +110/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fail closed on wedged cookie CDP mutations1 PR · Standalone · Agent management and search#
Problem: fail closed on wedged cookie CDP mutations.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15684 fix(browser): fail closed on wedged cookie CDP mutationsDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | ## Summary - give a CDP command a 10-second deadline and a bounded 1-second settlement grace - treat only a fulfilled reply during that grace as proven completion; rejection or silence retires the exclusively owned debug | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Draft/early · M Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +904/−101. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fire Marker dispose before clearing line1 PR · Standalone · Agent management and search#
Problem: fire Marker dispose before clearing line.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #10879 perf: scrollback trim is O(k²) when evicting decorated lines (search highlights) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13178 fix(xterm): fire Marker dispose before clearing line | BingZ Community · CONTRIBUTOR | #10879 perf: scrollback trim is O(k²) when evicting decorated lines (search highlights) Fixes · OPEN | Standalone change | ## Summary - Scrollback trim while search decorations were live was **O(k²)** (#10879): \`Marker.dispose\` set \`line = -1\` before \`onDispose\`, so every \`SortedList.delete\` walked the growing \`-1\` key group. - Fir | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +114/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fix dead links for Goose quickstart and Continue CLI guides1 PR · Standalone · Agent management and search#
Problem: fix dead links for Goose quickstart and Continue CLI guides.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14574 docs: fix dead links for Goose quickstart and Continue CLI guides | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | Two integration links in the IDE integrations section return 404 in all README languages: Goose quickstart and Continue CLI guides. Replaced with verified live URLs (official Goose site and Continue docs root). Fixed in | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +14/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2focus multi-agent rows across sibling worktree keys1 PR · Standalone · Agent management and search#
Problem: focus multi-agent rows across sibling worktree keys.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12739 [Bug]: Agent rows cannot open their tabs when multiple remote agents share a project (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13156 fix(sidebar): focus multi-agent rows across sibling worktree keys | BingZ Community · CONTRIBUTOR | #12739 [Bug]: Agent rows cannot open their tabs when multiple remote agents share a project Fixes · OPEN | Standalone change | ## Summary - Clicking a sidebar agent row only looked for the tab in `tabsByWorktree[cardWorktreeId]`. - Remote multi-agent layouts can host the tab under a sibling worktree key (same project), so activation called `acti | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +114/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2focus the live pane when resuming an already-running session from the sidebar1 PR · Standalone · Agent management and search#
Problem: focus the live pane when resuming an already-running session from the sidebar.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12700 AI Vault: sidebar Resume duplicates an already-running session (no liveness check; Jump affordance hidden post-restart) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12703 fix(agents): focus the live pane when resuming an already-running session from the sidebar | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12700 AI Vault: sidebar Resume duplicates an already-running session (no liveness check; Jump affordance hidden post-restart) Fixes · OPEN | Standalone change | ## Summary Fixes #12700. The Agents sidebar's Resume action launches a new tab + `claude --resume` unconditionally, starting a second process on a transcript whose session may still be running in an existing pane. This P | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +437/−98. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2give an SSH pane binding one home — the 2→19→20 mechanism (STA-3077 P)1 PR · Standalone · Agent management and search#
Problem: give an SSH pane binding one home — the 2→19→20 mechanism (STA-3077 P).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #217 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13324 fix(ssh): give an SSH pane binding one home — the 2→19→20 mechanism (STA-3077 P) | Neil Core team · MEMBER | #217 Title unavailable Unclear · Unknown | Standalone change | Design step **P**. Goalpost **S4**. **This is the mechanism behind the reported 2 → 19 → 20.** > Second of a 4-PR stack; base is the E-0 PR. ## The defect An SSH pane's durable binding lived in **two** persisted partitio | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +138/−95. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2guard SshConnection's SFTP calls against protocol-layer errors (#15479)1 PR · Standalone · Agent management and search#
Problem: guard SshConnection's SFTP calls against protocol-layer errors (#15479).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15479 SSH remote: Uncaught Exception crashes connection when SFTP subsystem is sandboxed by a jump host (relay deploy hits SSH_FX_NO_SUCH_FILE) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15800 fix: guard SshConnection's SFTP calls against protocol-layer errors (#15479) | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15479 SSH remote: Uncaught Exception crashes connection when SFTP subsystem is sandboxed by a jump host (relay deploy hits SSH_FX_NO_SUCH_FILE) Fixes · OPEN | Standalone change | Fixes #15479 — uncaught exception crashes the app when relay deployment hits a fatal SFTP protocol error (e.g. `SSH_FX_NO_SUCH_FILE` from a bastion whose SFTP subsystem is sandboxed to a different filesystem view than it | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +389/−56. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2hide Codex home-level scratch capsules1 PR · Standalone · Agent management and search#
Problem: hide Codex home-level scratch capsules.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #9388 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15253 fix(worktree): hide Codex home-level scratch capsules | dev-vet Community · FIRST_TIME_CONTRIBUTOR | #9388 Title unavailable Unclear · Unknown | Standalone change | ## Why Running OMO/Codex inside Orca creates git worktrees at `~/.codex/worktrees/<id>/<repo>`. The built-in scratch matcher only knew `.claude/worktrees` and `.gsd-workspaces` **under a registered checkout**, so those c | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +81/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2i18n: localize keep-awake / caffeinate status segment for zh, ja, ko, es1 PR · Standalone · Agent management and search#
Problem: i18n: localize keep-awake / caffeinate status segment for zh, ja, ko, es.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14490 Keep-awake / prevent-sleep control is not localized (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14820 i18n: localize keep-awake / caffeinate status segment for zh, ja, ko, es | Nguyen Thanh Tin Community · FIRST_TIME_CONTRIBUTOR | #14490 Keep-awake / prevent-sleep control is not localized Fixes · CLOSED | Standalone change | ## Summary - Add 13 missing i18n keys per locale (52 total) for the keep-awake corner chip and settings panel - Previously these showed English fallback text on Chinese, Japanese, Korean, and Spanish UIs - CaffeinateStat | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +212/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2isolate late retired tunnel frames1 PR · Standalone · Agent management and search#
Problem: isolate late retired tunnel frames.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14691 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14694 fix(browser): isolate late retired tunnel framesDraft | Jinwoo Hong Core team · MEMBER | #14691 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +151/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep archived Codex sessions out of the real-home backfill1 PR · Standalone · Agent management and search#
Problem: keep archived Codex sessions out of the real-home backfill.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #16411 [Bug]: Orca restores archived/deleted ChatGPT sessions and desynchronizes them from worktrees (Fixes, OPEN); #14029 Title unavailable (Unclear, Unknown); #14028 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16882 fix(codex): keep archived Codex sessions out of the real-home backfill | Neil Core team · MEMBER | #16411 [Bug]: Orca restores archived/deleted ChatGPT sessions and desynchronizes them from worktrees Fixes · OPEN #14029 Title unavailable Unclear · Unknown #14028 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +465/−115. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep attachments on multi-image sends1 PR · Standalone · Agent management and search#
Problem: keep attachments on multi-image sends.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #16972 [Bug]: Native chat drops image attachments when a send carries two or more images (Fixes, OPEN); #14939 Title unavailable (Unclear, Unknown); #11712 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16977 fix(native-chat): keep attachments on multi-image sends | Gideon Community · CONTRIBUTOR | #16972 [Bug]: Native chat drops image attachments when a send carries two or more images Fixes · OPEN #14939 Title unavailable Unclear · Unknown #11712 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Attach one image to a chat message and it shows up. Attach two and both disappear, and the raw `[Image: source: /path]` text Claude uses to record them shows up as if you had typed it. The fold that turns those m | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +102/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep COMMITS expand and height across worktrees1 PR · Standalone · Agent management and search#
Problem: keep COMMITS expand and height across worktrees.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12591 [Feature]: Remember the Source Control COMMITS section's expanded state and height (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12814 fix(source-control): keep COMMITS expand and height across worktrees | Wooseong Kim Community · CONTRIBUTOR | #12591 [Feature]: Remember the Source Control COMMITS section's expanded state and height Fixes · OPEN | Standalone change | ## Description Remember the Source Control **COMMITS** section expanded state and panel height across worktree/project switches within a session. Previously every switch reset the section to collapsed + default height. # | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +112/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep completed run sessions visible1 PR · Standalone · Agent management and search#
Problem: keep completed run sessions visible.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15570 fix(automations): keep completed run sessions visible | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1167/−460. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep default cookie clearing available2 PRs · Overlapping · Profile and resource management#
Problem: keep default cookie clearing available.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Profile and resource management (stack rank 3).
Relationship: Overlapping. Linked issues: #14678 [Bug]: Google cookies become permanently unremovable after a cookie import (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15044 fix(browser): keep default cookie clearing available | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #14678 [Bug]: Google cookies become permanently unremovable after a cookie import Fixes · OPEN | Cluster contribution | ## Summary - keep the default-profile cookie-clear action enabled after import metadata is cleared - add unit and Electron E2E coverage for clearing default cookies repeatedly Closes #14678 ## Validation - `pnpm exec vit | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +72/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15676 fix(browser): add a repeatable Google cookie clear (STA-4398) | Brennan Benson Core team · MEMBER | #14678 [Bug]: Google cookies become permanently unremovable after a cookie import Fixes · OPEN | Cluster contribution | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +604/−69. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep tab order and titles stable on a headless host1 PR · Standalone · Agent management and search#
Problem: keep tab order and titles stable on a headless host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12042 fix(remote): keep tab order and titles stable on a headless host | gal064 Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem On a remote `orca serve` host the tab bar is unstable: - **Order rotates.** Whichever tab you click jumps to the rightmost slot, so repeated clicking permutes the tab bar. - **Idle tabs get relabelled** to the | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +284/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep worker-start RPC alive past the 30s socket idle cap1 PR · Standalone · Agent management and search#
Problem: keep worker-start RPC alive past the 30s socket idle cap.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12126 fix(orchestration): keep worker-start RPC alive past the 30s socket idle cap | ElNelyo Community · CONTRIBUTOR | None found | Standalone change | ## Problem Orchestration mode did not work on a remote server (`orca serve` / slow SSH host): `orchestration worker-start` returned `runtime_unavailable` — _"The Orca runtime closed the connection before responding"_ — a | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +232/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let a deliberate agent /rename win the tab label mid-session1 PR · Standalone · Agent management and search#
Problem: let a deliberate agent /rename win the tab label mid-session.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12319 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12481 fix(tabs): let a deliberate agent /rename win the tab label mid-session | Neil Core team · MEMBER | #12319 Title unavailable Unclear · Unknown | Standalone change | ## What was broken (ELI5) When you ask Claude to rename your session with `/rename`, the name is supposed to show up on the Orca tab. It only worked if renaming was the very first thing you did. Once you had sent a messa | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk27 files, +1027/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let a respawned pane's status come back on any provider1 PR · Standalone · Agent management and search#
Problem: let a respawned pane's status come back on any provider.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17257 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17267 fix(agent-hooks): let a respawned pane's status come back on any provider | Brennan Benson Core team · MEMBER | #17257 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +525/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let an agent's own /rename win the tab label1 PR · Standalone · Agent management and search#
Problem: let an agent's own /rename win the tab label.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12481 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12319 fix(tabs): let an agent's own /rename win the tab label | Daniel Lafraia Community · FIRST_TIME_CONTRIBUTOR | #12481 Title unavailable Unclear · Unknown | Standalone change | ## Problem Claude's `/rename` only reached the tab label when it was the first thing you did in a session. After any prompt, the tab kept a name derived from that opening message and every later `/rename` was ignored. Th | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk34 files, +1758/−140. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make check log excerpts readable before they reach the UI and prompts1 PR · Standalone · Agent management and search#
Problem: make check log excerpts readable before they reach the UI and prompts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14871 fix(github): make check log excerpts readable before they reach the UI and prompts | Seong Gil Je Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | GitHub check log excerpts skipped the readability pipeline that GitLab job traces already go through, so escape sequences and carriage-return progress output reached both the log excerpt UI and the fix-checks agent promp | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +149/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make the published group->tab invariant true for terminals1 PR · Standalone · Agent management and search#
Problem: make the published group->tab invariant true for terminals.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17100 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17106 fix(mobile-sync): make the published group->tab invariant true for terminals | Brennan Benson Core team · MEMBER | #17100 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +547/−45. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2map Salesforce Apex extensions to the apex language id1 PR · Standalone · Agent management and search#
Problem: map Salesforce Apex extensions to the apex language id.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13835 Title unavailable (Unclear, Unknown); #11215 Title unavailable (Unclear, Unknown); #11313 Title unavailable (Unclear, Unknown); #10363 Title unavailable (Unclear, Unknown); #13028 Title unavailable (Unclear, Unknown); #8093 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14287 fix(editor): map Salesforce Apex extensions to the apex language id | Brooks Johnson Community · FIRST_TIME_CONTRIBUTOR | #13835 Title unavailable Unclear · Unknown #11215 Title unavailable Unclear · Unknown #11313 Title unavailable Unclear · Unknown #10363 Title unavailable Unclear · Unknown #13028 Title unavailable Unclear · Unknown #8093 Title unavailable Unclear · Unknown | Standalone change | Apex files (`.cls`, `.trigger`) open as plaintext in the editor, with no syntax highlighting. ## Cause Monaco already ships an `apex` language and registers it for `.cls`: ```js { id: "apex", extensions: [".cls"], aliase | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +14/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2one bind producer, so the superseded-pane fence is live on reattach (STA-3077 F)1 PR · Standalone · Agent management and search#
Problem: one bind producer, so the superseded-pane fence is live on reattach (STA-3077 F).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13325 fix(ssh): one bind producer, so the superseded-pane fence is live on reattach (STA-3077 F) | Neil Core team · MEMBER | None found | Standalone change | Design step **F**. Goalpost **S5**. Closes a defect in already-shipped work. > Stacked on the P PR. ## The defect The superseded-PTY fence refuses a keystroke queued for a shell whose pane has since bound a different one | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +152/−30. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2only skip the quit warning when the work actually survives1 PR · Standalone · Agent management and search#
Problem: only skip the quit warning when the work actually survives.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17044 Title unavailable (Unclear, Unknown); #17077 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17085 fix(terminal): only skip the quit warning when the work actually survives | Brennan Benson Core team · MEMBER | #17044 Title unavailable Unclear · Unknown #17077 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +1010/−99. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open files from PR comments1 PR · Standalone · Agent management and search#
Problem: open files from PR comments.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12980 [Feature]: Open file from PR comments (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13230 feat(source-control): open files from PR comments | Wooseong Kim Community · CONTRIBUTOR | #12980 [Feature]: Open file from PR comments Fixes · OPEN | Standalone change | ## Description PR comment file references can now be activated to open the referenced file at its reported line in the active workspace. The Checks panel passes the selected review location through the existing file-open | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +210/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Open right sidebar by default for new web profiles1 PR · Standalone · Agent management and search#
Problem: Open right sidebar by default for new web profiles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13731 Open right sidebar by default for new web profiles | Jinjing Core team · MEMBER | None found | Standalone change | ## Problem New web profiles had the right sidebar closed by default, while desktop opened it by default. This inconsistency meant new users on web didn't discover the explorer panel. ## Solution Remove the explicit `righ | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +16/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open the host editor deterministically via a route action1 PR · Standalone · Agent management and search#
Problem: open the host editor deterministically via a route action.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #11635 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12554 fix(mobile): open the host editor deterministically via a route action | Programming Zombie Community · FIRST_TIME_CONTRIBUTOR | #11635 Title unavailable Unclear · Unknown | Standalone change | ## What this fixes **Edit host** could still strand the user on the host worktree list screen instead of opening the edit form — the symptom #11635 addressed, still reproducible on `mobile-android-v0.0.37` (Galaxy Z Fold | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +55/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open working-tree file from a change row1 PR · Standalone · Agent management and search#
Problem: open working-tree file from a change row.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14487 [Feature]: Open the working-tree file from a Source Control change row (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14778 fix(source-control): open working-tree file from a change row | Wooseong Kim Community · CONTRIBUTOR | #14487 [Feature]: Open the working-tree file from a Source Control change row Fixes · OPEN | Standalone change | ## Description Source Control change rows now have an Open file hover action that opens the working-tree file in a regular editor tab. ## Focused fix - In scope: one Open file action on uncommitted rows. - Out of scope: | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +146/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2park a remote pty only for the worktree that owns it1 PR · Standalone · Agent management and search#
Problem: park a remote pty only for the worktree that owns it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #16138 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13253 fix(terminals): park a remote pty only for the worktree that owns it | 이건상 Community · CONTRIBUTOR | #16138 Title unavailable Unclear · Unknown | Standalone change | ## What Remote terminal parking now requires authoritative PTY ownership across ordinary per-tab parking, retention force-parking, and parked watcher coverage. A worktree can park a tagged SSH or paired-runtime PTY only | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk31 files, +2313/−382. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pin the relay re-establish budget to the deadlines it covers1 PR · Standalone · Agent management and search#
Problem: pin the relay re-establish budget to the deadlines it covers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15760 test(ssh): pin the relay re-establish budget to the deadlines it covers | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +48/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2pipeline live terminal input instead of awaiting each RPC (STA-3199)1 PR · Standalone · Agent management and search#
Problem: pipeline live terminal input instead of awaiting each RPC (STA-3199).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12071 [Bug]: Mobile terminal input serializes every live delta behind a full RPC round trip (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15708 fix(mobile): pipeline live terminal input instead of awaiting each RPC (STA-3199) | Brennan Benson Core team · MEMBER | #12071 [Bug]: Mobile terminal input serializes every live delta behind a full RPC round trip Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk20 files, +813/−52. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve live agent on readiness timeout1 PR · Standalone · Agent management and search#
Problem: preserve live agent on readiness timeout.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13642 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15215 fix(orchestration): preserve live agent on readiness timeoutDraft | Jinwoo Hong Core team · MEMBER | #13642 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +232/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve SSH hook launch context (STA-3147)1 PR · Standalone · Agent management and search#
Problem: preserve SSH hook launch context (STA-3147).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #11941 [Bug]: SSH Codex sessions emit no Orca hooks when the TUI reuses an existing app-server (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16062 fix(codex): preserve SSH hook launch context (STA-3147)Draft | Jinwoo Hong Core team · MEMBER | #11941 [Bug]: SSH Codex sessions emit no Orca hooks when the TUI reuses an existing app-server Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 10 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Draft/early · L Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk24 files, +943/−34. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve the exact preview source group1 PR · Standalone · Agent management and search#
Problem: preserve the exact preview source group.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15716 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16129 fix(remote): preserve the exact preview source group | Brennan Benson Core team · MEMBER | #15716 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +292/−72. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preview remote terminal HTML taps1 PR · Standalone · Agent management and search#
Problem: preview remote terminal HTML taps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13144 Support opening/previewing HTML files on Orca Mobile (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13234 fix(mobile): preview remote terminal HTML taps | Wooseong Kim Community · CONTRIBUTOR | #13144 Support opening/previewing HTML files on Orca Mobile Fixes · OPEN | Standalone change | ## Description HTML files opened from a remote or hosted terminal on Orca Mobile now use the mobile file-preview surface instead of falling through to a desktop-style file tab. The existing local worktree `file://` brows | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +34/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2re-attach on restoreRequired instead of expiring the live session1 PR · Standalone · Agent management and search#
Problem: re-attach on restoreRequired instead of expiring the live session.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12448 [Bug]: SSH reattach treats sourceRecovery restoreRequired as SSH_SESSION_EXPIRED — live PTY abandoned and agent duplicate-resumed into a fresh PTY (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12456 fix(ssh): re-attach on restoreRequired instead of expiring the live session | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12448 [Bug]: SSH reattach treats sourceRecovery restoreRequired as SSH_SESSION_EXPIRED — live PTY abandoned and agent duplicate-resumed into a fresh PTY Fixes · OPEN | Standalone change | ## Summary Fixes #12448. `SshPtyProvider.spawn` treats a successful `pty.attach` whose `sourceRecovery` is `restoreRequired` as `SSH_SESSION_EXPIRED`. `restoreRequired` is the relay's stream-recovery verdict — "the stale | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +188/−52. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reap empty macOS TCC login wrappers after shell exit1 PR · Standalone · Agent management and search#
Problem: reap empty macOS TCC login wrappers after shell exit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13764 macOS: TCC login-shell wrapper leaks PTYs (session-kill-failed, session-closed never fires) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13973 fix(daemon): reap empty macOS TCC login wrappers after shell exit | OrcaWin Unknown · COLLABORATOR | #13764 macOS: TCC login-shell wrapper leaks PTYs (session-kill-failed, session-closed never fires) Fixes · OPEN | Standalone change | ## Summary - On macOS TCC-wrapped PTYs the node-pty root is `/usr/bin/login`, so an exited inner shell can leave `login` holding the master with no `onExit` (#13764). - Death watch uses **bounded async** `ps` (not `execF | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +1007/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2reconcile hook relays on startup1 PR · Standalone · Agent management and search#
Problem: reconcile hook relays on startup.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13491 fix(wsl): reconcile hook relays on startup | OrcaWin Unknown · COLLABORATOR | None found | Standalone change | ## Summary - reconcile WSL hook relays from authoritative live-daemon inventory after daemon and hook authority are ready - use one non-booting running-distro snapshot, dedupe by normalized distro, and guard exceptional | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk17 files, +1024/−148. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2recover provider-only terminal state safely1 PR · Standalone · Agent management and search#
Problem: recover provider-only terminal state safely.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16267 fix(runtime): recover provider-only terminal state safely | Jinjing Core team · MEMBER | None found | Standalone change | ## Summary - recover visible terminal output from provider snapshots for recovered and never-attached sessions - avoid stale provider frames and retry storms after snapshot timeouts - require provider-backed idle probing | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk343 files, +39942/−3008. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2refresh desktop TUI after mobile-fit ends1 PR · Standalone · Agent management and search#
Problem: refresh desktop TUI after mobile-fit ends.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14321 After mobile session, desktop terminal restores size but does not refresh until scroll (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14787 fix(terminal): refresh desktop TUI after mobile-fit ends | Wooseong Kim Community · CONTRIBUTOR | #14321 After mobile session, desktop terminal restores size but does not refresh until scroll Fixes · OPEN | Standalone change | ## Description After a mobile session ends, the desktop TUI now fit+refreshes instead of only restoring geometry. ## Focused fix - In scope: refresh/repaint when mobile-fit lifts. - Out of scope: changing mobile-fit hold | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +234/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2refuse a self-addressed ask instead of blocking1 PR · Standalone · Agent management and search#
Problem: refuse a self-addressed ask instead of blocking.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13362 Title unavailable (Unclear, Unknown); #13659 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15266 fix(orchestration): refuse a self-addressed ask instead of blocking | Taras Kornichuk Community · CONTRIBUTOR | #13362 Title unavailable Unclear · Unknown #13659 Title unavailable Unclear · Unknown | Standalone change | `orca orchestration ask` now refuses, with a typed error, when the question it would post could only be answered by the terminal that is about to block on it. ## What we saw A dispatched terminal that had taken over the | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +365/−29. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report when a remote's node-pty has no native job control1 PR · Standalone · Agent management and search#
Problem: report when a remote's node-pty has no native job control.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #1693 Title unavailable (Unclear, Unknown); #9902 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17042 fix(relay): report when a remote's node-pty has no native job control | Brennan Benson Core team · MEMBER | #1693 Title unavailable Unclear · Unknown #9902 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +542/−33. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2resolve Devin transcripts under APPDATA on Windows1 PR · Standalone · Agent management and search#
Problem: resolve Devin transcripts under APPDATA on Windows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15768 [Bug]: Devin session history never appears on Windows — scanner uses Linux-only transcript path with no platform fallback (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15818 fix(ai-vault): resolve Devin transcripts under APPDATA on Windows | Brennan Benson Core team · MEMBER | #15768 [Bug]: Devin session history never appears on Windows — scanner uses Linux-only transcript path with no platform fallback Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +441/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore terminal modes when a pane reattaches to a relay-hosted SSH pty1 PR · Standalone · Agent management and search#
Problem: restore terminal modes when a pane reattaches to a relay-hosted SSH pty.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #8291 Title unavailable (Unclear, Unknown); #7329 Title unavailable (Unclear, Unknown); #12101 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13043 fix(terminal): restore terminal modes when a pane reattaches to a relay-hosted SSH pty | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #8291 Title unavailable Unclear · Unknown #7329 Title unavailable Unclear · Unknown #12101 Title unavailable Unclear · Unknown | Standalone change | ## Problem The relay replays a raw bounded byte tail (`REPLAY_BUFFER_MAX`) when a pane attaches to a long-lived SSH pty. A TUI's mode-setting sequences — mouse reporting (`?1000/?1002/?1006`), alternate screen (`?1049`), | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk29 files, +1339/−217. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2serve an omp native-chat scenario1 PR · Standalone · Agent management and search#
Problem: serve an omp native-chat scenario.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14859 test(mock-server): serve an omp native-chat scenario | netrunner Community · CONTRIBUTOR | None found | Standalone change | ## Summary The mock server's native-chat scenario is hardcoded to `claude`, so mobile's omp support can only be exercised against a live runtime. `MOCK_CHAT_AGENT=omp` switches the scenario's agent tab to omp with the tw | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +61/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Show agent names and lineage in dashboard map1 PR · Standalone · Agent management and search#
Problem: Show agent names and lineage in dashboard map.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14991 Show agent names and lineage in dashboard map | Adelin Berard Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - Show stable agent names across dashboard cards, sidebar rows, and map nodes. - Render readable agent labels, tooltips, and orchestration lineage without overlap at dense map scales. - Keep pane lineage scope | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · L Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk53 files, +3577/−518. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show phone-launched agent tabs before desktop mounts them1 PR · Standalone · Agent management and search#
Problem: show phone-launched agent tabs before desktop mounts them.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15203 [Bug]: Agent sessions started from the phone do not appear in the desktop sidebar (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15204 fix(sidebar): show phone-launched agent tabs before desktop mounts them | Galaxy Roaming Community · FIRST_TIME_CONTRIBUTOR | #15203 [Bug]: Agent sessions started from the phone do not appear in the desktop sidebar Fixes · OPEN | Standalone change | ## ELI5 If you start an agent from your phone, the desktop already knows the tab exists, but the left sidebar Agents list waited for a live terminal or a hook ping. That wait never finished for a background phone launch, | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +241/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show tooltip for truncated shortcut titles in shortcut…1 PR · Standalone · Agent management and search#
Problem: show tooltip for truncated shortcut titles in shortcut….
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #16805 [Feature]: Show tooltip on hover for truncated shortcut titles in Settings → Shortcuts (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16806 fix(settings): show tooltip for truncated shortcut titles in shortcut… | hwantage Community · CONTRIBUTOR | #16805 [Feature]: Show tooltip on hover for truncated shortcut titles in Settings → Shortcuts Fixes · OPEN | Standalone change | ## ELI5 In **Settings → Shortcuts**, long shortcut titles like `Worktree History Back` get truncated with `...`, but hovering over them didn't reveal the full name. This PR wraps the title in Orca's standard Tooltip so y | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +47/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2slow certified terminal inventory sweeps1 PR · Standalone · Agent management and search#
Problem: slow certified terminal inventory sweeps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17182 perf(mobile): slow certified terminal inventory sweeps | Neil Core team · MEMBER | None found | Standalone change | ## ELI5 A focused phone session already hears terminal and tab changes through live streams, but it still asked the host for a full terminal census every two seconds. Healthy sessions now ask once per minute. When a term | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +1237/−108. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2soft-skip migrated non-GitLab projects in Tasks1 PR · Standalone · Agent management and search#
Problem: soft-skip migrated non-GitLab projects in Tasks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #13817 [Bug]: GitLab task source keeps querying a project that migrated off GitLab, and one project's error replaces the whole view (Fixes, OPEN); #6263 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13962 fix(gitlab): soft-skip migrated non-GitLab projects in Tasks | OrcaWin Unknown · COLLABORATOR | #13817 [Bug]: GitLab task source keeps querying a project that migrated off GitLab, and one project's error replaces the whole view Fixes · OPEN #6263 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Soft-skip GitLab task projects that are no longer GitLab after migration, using **per-repo backend `not_found`** as host-correct evidence (no renderer-wide host allowlist). - Keep **local cwd `glab mr list` | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +810/−113. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split automation dispatch event handling1 PR · Standalone · Agent management and search#
Problem: Split automation dispatch event handling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17152 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17155 Split automation dispatch event handling | Neil Core team · MEMBER | #17152 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 5 | $\col | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +765/−683. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split CDP bridge responsibilities1 PR · Standalone · Agent management and search#
Problem: Split CDP bridge responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17206 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17215 Split CDP bridge responsibilities | Neil Core team · MEMBER | #17206 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 14 | $\co | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +1823/−1382. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2split Codex account service modules1 PR · Standalone · Agent management and search#
Problem: split Codex account service modules.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17277 refactor: split Codex account service modules | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 14 | $\co | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk14 files, +2176/−1875. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split mobile browser pane modules1 PR · Standalone · Agent management and search#
Problem: Split mobile browser pane modules.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17131 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17141 Split mobile browser pane modules | Neil Core team · MEMBER | #17131 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 11 | $\co | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1668/−1026. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split resource usage status responsibilities1 PR · Standalone · Agent management and search#
Problem: Split resource usage status responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17235 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17244 Split resource usage status responsibilities | Neil Core team · MEMBER | #17235 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +2089/−1619. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split web runtime session responsibilities1 PR · Standalone · Agent management and search#
Problem: Split web runtime session responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17260 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17263 Split web runtime session responsibilities | Neil Core team · MEMBER | #17260 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +2026/−1788. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2STA-5061: restore Cmd-J host badges1 PR · Standalone · Agent management and search#
Problem: STA-5061: restore Cmd-J host badges.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15891 STA-5061: restore Cmd-J host badges | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +108/−31. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2STA-5496: offer Orca Browser for SSH terminal links1 PR · Standalone · Agent management and search#
Problem: STA-5496: offer Orca Browser for SSH terminal links.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16503 STA-5496: offer Orca Browser for SSH terminal links | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 7 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +298/−99. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop bash alias collision from crashing codex/omp shell wrappers1 PR · Standalone · Agent management and search#
Problem: stop bash alias collision from crashing codex/omp shell wrappers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15830 [Bug]: bash alias on `codex`/`omp` breaks headless shell wrapper — 'syntax error near unexpected token (' at the generated function definition (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15844 fix(pty): stop bash alias collision from crashing codex/omp shell wrappers | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15830 [Bug]: bash alias on `codex`/`omp` breaks headless shell wrapper — 'syntax error near unexpected token (' at the generated function definition Fixes · OPEN | Standalone change | ## Summary Fixes #15830. When a user's `~/.bashrc` defines `alias codex=...` or `alias omp=...`, Orca's managed shell rc injects `codex() { ... }` / `omp() { ... }` wrapper function definitions later in the same file. Ba | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +143/−32. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop deleting page annotations on navigate/reload1 PR · Standalone · Agent management and search#
Problem: stop deleting page annotations on navigate/reload.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15019 fix(browser): stop deleting page annotations on navigate/reload | Emirhan Celik Sahin Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Browser annotations (the click-to-comment feedback tool on a live page in the browser pane) were being deleted outright any time the page's URL changed, and again on every reload — even though `browserPageId` | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +82/−35. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop duplicating rows in the status-bar popover after Stop Process1 PR · Standalone · Agent management and search#
Problem: stop duplicating rows in the status-bar popover after Stop Process.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15626 fix(ports): stop duplicating rows in the status-bar popover after Stop Process | heslanx Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Reported: after killing a process holding a port from the Ports status-bar popover, the killed port's row keeps showing (duplicated many times over) for a few seconds before self-clearing. Root cause is a one- | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +151/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop host snapshots yanking the phone off its current tab1 PR · Standalone · Agent management and search#
Problem: stop host snapshots yanking the phone off its current tab.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #8364 [Bug]: iOS mobile — browser tab switches back to Agent tab on refresh or route change (Fixes, CLOSED); #8700 [Bug] Bug: interacting with Browser tab on mobile hides the tab (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12471 fix(mobile): stop host snapshots yanking the phone off its current tab | Neil Core team · MEMBER | #8364 [Bug]: iOS mobile — browser tab switches back to Agent tab on refresh or route change Fixes · CLOSED #8700 [Bug] Bug: interacting with Browser tab on mobile hides the tab Fixes · CLOSED | Standalone change | The phone re-derived its active tab from every incoming host snapshot. Any republication — an agent turn, a desktop focus change, or the browser-activation bootstrap that a mobile browser tap itself triggers — moved the | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk30 files, +6253/−839. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop publishing an active group the phone was never sent1 PR · Standalone · Agent management and search#
Problem: stop publishing an active group the phone was never sent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17100 fix(mobile-sync): stop publishing an active group the phone was never sent | Brennan Benson Core team · MEMBER | #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +373/−181. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop reconnect grafting panes, stacking leases, and respawning live shells (STA-3077)1 PR · Standalone · Agent management and search#
Problem: stop reconnect grafting panes, stacking leases, and respawning live shells (STA-3077).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #11729 Title unavailable (Unclear, Unknown); #12448 Title unavailable (Unclear, Unknown); #11006 Title unavailable (Unclear, Unknown); #12699 Title unavailable (Unclear, Unknown); #12683 Title unavailable (Unclear, Unknown); #10208 Title unavailable (Unclear, Unknown); #12264 Title unavailable (Unclear, Unknown); #12743 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13111 fix(terminal): stop reconnect grafting panes, stacking leases, and respawning live shells (STA-3077) | Neil Core team · MEMBER | #11729 Title unavailable Unclear · Unknown #12448 Title unavailable Unclear · Unknown #11006 Title unavailable Unclear · Unknown #12699 Title unavailable Unclear · Unknown #12683 Title unavailable Unclear · Unknown #10208 Title unavailable Unclear · Unknown #12264 Title unavailable Unclear · Unknown #12743 Title unavailable Unclear · Unknown | Standalone change | Fixes STA-3077 / #11729. Also addresses the duplicate-agent family: #12448, #11006, #12699, #12683, #10208. ## Symptoms Two distinct failures, one shared shape — *something absent was treated as something dead*, and a re | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk104 files, +12910/−591. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop remote workspace pulls from resurrecting closed tabs1 PR · Standalone · Agent management and search#
Problem: stop remote workspace pulls from resurrecting closed tabs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #10342 Phantom terminal tabs survive close and are restored from persisted layout state (SSH host) (Fixes, CLOSED); #2323 Title unavailable (Unclear, Unknown); #9352 Title unavailable (Unclear, Unknown); #11729 Title unavailable (Unclear, Unknown); #12264 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12339 fix(ssh): stop remote workspace pulls from resurrecting closed tabs | Dzmitry Bachko Community · CONTRIBUTOR | #10342 Phantom terminal tabs survive close and are restored from persisted layout state (SSH host) Fixes · CLOSED #2323 Title unavailable Unclear · Unknown #9352 Title unavailable Unclear · Unknown #11729 Title unavailable Unclear · Unknown #12264 Title unavailable Unclear · Unknown | Standalone change | Fixes #10342. Related: #2323 (item C2), #9352 (paired-viewer sibling), #11729 / #12264 (complementary main-process lease path — no file overlap). ## Summary On a direct-SSH workspace, closing terminal tabs doesn't stick: | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +476/−49. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop separator-variant worktree ids purging live checkouts1 PR · Standalone · Agent management and search#
Problem: stop separator-variant worktree ids purging live checkouts.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15598 [Bug]: Duplicate worktreeMeta entries differing only by path separator force-kill a live agent pane when a child worktree is created (Fixes, OPEN); #10832 Title unavailable (Unclear, Unknown); #16494 Title unavailable (Unclear, Unknown); #16243 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15616 fix(worktrees): stop separator-variant worktree ids purging live checkouts | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15598 [Bug]: Duplicate worktreeMeta entries differing only by path separator force-kill a live agent pane when a child worktree is created Fixes · OPEN #10832 Title unavailable Unclear · Unknown #16494 Title unavailable Unclear · Unknown #16243 Title unavailable Unclear · Unknown | Standalone change | ## Summary **What** Two exact-string worktree-id membership checks now compare through a new shared `worktreeIdComparisonKey` (`src/shared/worktree/id.ts`), which folds separator and drive-letter spelling via the existin | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +204/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop snapshot applies from erasing worktrees outside the hydration validity set1 PR · Standalone · Agent management and search#
Problem: stop snapshot applies from erasing worktrees outside the hydration validity set.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13030 fix(remote-workspace): stop snapshot applies from erasing worktrees outside the hydration validity set | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem `applyDirectSshRemoteWorkspaceSnapshot` hydrates the merged session with `replaceWorkspaceKeys` derived from `resolveDirectSshTargetScope`, whose scope includes `detectedWorktreesByRepo`. The hydrators indepen | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +152/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop the wake sweep from forking sessions that live SSH panes still own1 PR · Standalone · Agent management and search#
Problem: stop the wake sweep from forking sessions that live SSH panes still own.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12699 SSH: sleeping-agent wake sweep forks live remote sessions (disconnected panes judged dead; stale worktreeId; per-worktree dedupe) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12702 fix(agents): stop the wake sweep from forking sessions that live SSH panes still own | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #12699 SSH: sleeping-agent wake sweep forks live remote sessions (disconnected panes judged dead; stale worktreeId; per-worktree dedupe) Fixes · OPEN | Standalone change | ## Summary Fixes #12699. The sleeping-agent wake sweep forks live remote sessions into duplicate `claude --resume` tabs through three ownership misjudgments. This PR closes all three in `recordPaneIsOwnedByPreservedPane` | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +196/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop untyped tool-hook agent_ids from minting phantom subagent rows1 PR · Standalone · Agent management and search#
Problem: stop untyped tool-hook agent_ids from minting phantom subagent rows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15325 [Bug]: Long-lived async agents mint dozens of phantom "Working - Agent" roster rows (Fixes, OPEN); #15591 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15326 fix(agent-hooks): stop untyped tool-hook agent_ids from minting phantom subagent rows | Matthew Yu Community · FIRST_TIME_CONTRIBUTOR | #15325 [Bug]: Long-lived async agents mint dozens of phantom "Working - Agent" roster rows Fixes · OPEN #15591 Title unavailable Unclear · Unknown | Standalone change | Fixes #15325. ## Problem When a dispatched worker runs long-lived async background agents, the agent status tree accumulates dozens of phantom `Working - Agent` rows. Observed: 4 real async agents displayed as **32 roste | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +158/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stream an idle-agent reply below the prompt that caused it1 PR · Standalone · Agent management and search#
Problem: stream an idle-agent reply below the prompt that caused it.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #15608 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15617 fix(native-chat): stream an idle-agent reply below the prompt that caused it | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15608 Title unavailable Unclear · Unknown | Standalone change | ## Summary **What** The desktop native-chat view now renders the streaming reply bubble **below** an optimistic user echo that was sent while the agent was idle, and keeps it **above** echoes that were queued while the a | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +92/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2strip the invoke envelope from the discard and GitLab list errors1 PR · Standalone · Agent management and search#
Problem: strip the invoke envelope from the discard and GitLab list errors.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #17255 Title unavailable (Unclear, Unknown); #17237 Title unavailable (Unclear, Unknown); #17230 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17259 fix(ipc): strip the invoke envelope from the discard and GitLab list errors | Brennan Benson Core team · MEMBER | #17255 Title unavailable Unclear · Unknown #17237 Title unavailable Unclear · Unknown #17230 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +269/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2submit large agent-prompt pastes after TUI ingest (STA-2912)1 PR · Standalone · Agent management and search#
Problem: submit large agent-prompt pastes after TUI ingest (STA-2912).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #11343 [Bug]: dispatch --inject to Codex never submits large payloads — trailing Enter is concatenated into the bracketed-paste PTY write (v1.4.159) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15698 fix(terminal): submit large agent-prompt pastes after TUI ingest (STA-2912) | Brennan Benson Core team · MEMBER | #11343 [Bug]: dispatch --inject to Codex never submits large payloads — trailing Enter is concatenated into the bracketed-paste PTY write (v1.4.159) Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +929/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Support Kagi private-session navigation without token persistence1 PR · Standalone · Agent management and search#
Problem: Support Kagi private-session navigation without token persistence.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13943 Support Kagi private-session navigation without token persistence | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk19 files, +502/−57. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface failed attach-only orphan retire for support1 PR · Standalone · Agent management and search#
Problem: surface failed attach-only orphan retire for support.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12662 P2: Pre-v31 attach-only accidental spawn leave orphan if kill fails (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13143 fix(daemon): surface failed attach-only orphan retire for support | BingZ Community · CONTRIBUTOR | #12662 P2: Pre-v31 attach-only accidental spawn leave orphan if kill fails Fixes · OPEN | Standalone change | ## Summary - Extract attach-only accidental-spawn retire into a small helper. - On kill failure: `console.error` with structured fields + `daemon_attach_only_orphan_risk` telemetry (enum-only). - One kill only (not incar | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +202/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2track closed PTY inventory incrementally1 PR · Standalone · Agent management and search#
Problem: track closed PTY inventory incrementally.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16174 perf(resource-usage): track closed PTY inventory incrementally | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 6 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +849/−208. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2treat an absent worktree and an empty tab list as different answers1 PR · Standalone · Agent management and search#
Problem: treat an absent worktree and an empty tab list as different answers.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #12751 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12987 fix(remote): treat an absent worktree and an empty tab list as different answers | Jinwoo Hong Core team · MEMBER | #12751 Title unavailable Unclear · Unknown | Standalone change | ## Problem The direct-SSH workspace snapshot merge deleted a worktree's local tabs whenever the imported remote session reported no tabs for it. Two very different situations reach that point: - **present, empty array** | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +195/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2use the entered group name when opening a folder1 PR · Standalone · Agent management and search#
Problem: use the entered group name when opening a folder.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #16355 [Bug]: Open as Folder ignores the entered group name and uses the parent-folder basename (Fixes, OPEN); #737373 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16881 fix(add-project): use the entered group name when opening a folder | Neil Core team · MEMBER | #16355 [Bug]: Open as Folder ignores the entered group name and uses the parent-folder basename Fixes · OPEN #737373 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 3 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +158/−22. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2verify a sleeping session's tab is gone from every session partition before resuming into a 1 PR · Standalone · Agent management and search#
Problem: verify a sleeping session's tab is gone from every session partition before resuming into a .
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13037 fix(agents): verify a sleeping session's tab is gone from every session partition before resuming into a fresh tab | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Problem `resumeSleepingAgentSessionsForWorktree` resumes a sleeping-agent record into a fresh tab whenever the record's wake tab is absent from `tabsByWorktree` and no preserved pane owns the session. `tabsByWorktree` | P2 Useful scoped improvement; aligned with Agent management and search but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +638/−44. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2accept an empty --value in cookie set and --pass in set credentials1 PR · Standalone · SSH/remote re-architecture#
Problem: accept an empty --value in cookie set and --pass in set credentials.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #17225 [Bug]: cookie set --value "" and set credentials --pass "" are rejected though the runtime accepts empty values (Fixes, OPEN); #15863 Title unavailable (Unclear, Unknown); #16030 Title unavailable (Unclear, Unknown); #15810 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17226 fix(browser): accept an empty --value in cookie set and --pass in set credentials | 2sumtech Community · CONTRIBUTOR | #17225 [Bug]: cookie set --value "" and set credentials --pass "" are rejected though the runtime accepts empty values Fixes · OPEN #15863 Title unavailable Unclear · Unknown #16030 Title unavailable Unclear · Unknown #15810 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Setting a cookie to "nothing" and using a blank password are both real things the browser runtime already allows. The CLI was saying "you forgot to type something" and refusing. This teaches both commands that an | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +128/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ask before a tab close kills a pty the app cannot vouch for1 PR · Standalone · SSH/remote re-architecture#
Problem: ask before a tab close kills a pty the app cannot vouch for.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #17058 Title unavailable (Unclear, Unknown); #17044 Title unavailable (Unclear, Unknown); #17024 Title unavailable (Unclear, Unknown); #17003 Title unavailable (Unclear, Unknown); #16955 Title unavailable (Unclear, Unknown); #16926 Title unavailable (Unclear, Unknown); #39 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17076 fix(terminal): ask before a tab close kills a pty the app cannot vouch for | Brennan Benson Core team · MEMBER | #17058 Title unavailable Unclear · Unknown #17044 Title unavailable Unclear · Unknown #17024 Title unavailable Unclear · Unknown #17003 Title unavailable Unclear · Unknown #16955 Title unavailable Unclear · Unknown #16926 Title unavailable Unclear · Unknown #39 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +155/−35. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound git response-stream reassembly on the host1 PR · Standalone · SSH/remote re-architecture#
Problem: bound git response-stream reassembly on the host.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14160 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14510 fix(ssh): bound git response-stream reassembly on the host | Neil Core team · MEMBER | #14160 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +143/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2bound stalled setup-split grid polling1 PR · Standalone · SSH/remote re-architecture#
Problem: bound stalled setup-split grid polling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15241 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17228 perf(terminal): bound stalled setup-split grid polling | Neil Core team · MEMBER | #15241 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +39/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2cap distinct error surface growth2 PRs · Overlapping · SSH/remote re-architecture#
Problem: cap distinct error surface growth.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Overlapping. Linked issues: #12685 terminal: error surface still has no hard cap on distinct messages (Fixes, OPEN); #12650 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12809 fix(terminal): cap distinct error surface growth | Wooseong Kim Community · CONTRIBUTOR | #12685 terminal: error surface still has no hard cap on distinct messages Fixes · OPEN #12650 Title unavailable Unclear · Unknown | Cluster contribution | ## Description Cap the aggregated terminal error surface so a storm of **distinct** messages cannot grow without bound. #12650 added whole-line dedup; this adds a closed line + character budget preferring newest content. | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +68/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13145 fix(terminal): hard-cap aggregated error surface length | BingZ Community · CONTRIBUTOR | #12685 terminal: error surface still has no hard cap on distinct messages Fixes · OPEN | Cluster contribution | ## Summary - Cap the newline-joined terminal error toast at 2000 characters. - Prefer the newest complete lines; a single oversized line keeps its head so SSH reconnect ownership prefixes still match. Fixes #12685 ## Tes | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +83/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2defer mail pointer when user is actively typing1 PR · Standalone · SSH/remote re-architecture#
Problem: defer mail pointer when user is actively typing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14832 [Bug]: orchestration mail pointer still auto-submits into a prompt the user is typing in (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14836 fix(orchestration): defer mail pointer when user is actively typing | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #14832 [Bug]: orchestration mail pointer still auto-submits into a prompt the user is typing in Fixes · OPEN | Standalone change | Fixes #14832. The orchestration push-on-idle pointer (and its delayed Enter) injected into a prompt the user was actively typing in, then auto-submitted it. The fix: 1. **RuntimePtyController** gains an optional `lastUse | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +22/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2do not inherit nice -8 into integrated PTYs1 PR · Standalone · SSH/remote re-architecture#
Problem: do not inherit nice -8 into integrated PTYs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14639 Integrated terminals inherit the app's nice -8, so builds starve the desktop (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14786 fix(terminal): do not inherit nice -8 into integrated PTYs | Wooseong Kim Community · CONTRIBUTOR | #14639 Integrated terminals inherit the app's nice -8, so builds starve the desktop Fixes · OPEN | Standalone change | ## Description Linux integrated terminals no longer inherit Electron's nice -8. Child PTY PIDs are reset to `PRIORITY_NORMAL` after spawn. ## Focused fix - In scope: Linux PTY child niceness only. - Out of scope: changin | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +280/−17. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2document client pairing and port 6768 collision1 PR · Standalone · SSH/remote re-architecture#
Problem: document client pairing and port 6768 collision.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #11318 [Feature]: Document the client half of remote-server setup (pairing flow, port collision with the desktop app, separate profile) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13175 docs(headless): document client pairing and port 6768 collision | BingZ Community · CONTRIBUTOR | #11318 [Feature]: Document the client half of remote-server setup (pairing flow, port collision with the desktop app, separate profile) Fixes · OPEN | Standalone change | ## Summary - Headless serve guide printed a pairing URL and stopped; the client half lived only in a UI placeholder (#11318). - Add **Connect a client to your server**: decision table (SSH vs serve vs mobile/web), deskto | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +97/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2don't report a connected Codex account as unconfigured when its usage read fails1 PR · Standalone · SSH/remote re-architecture#
Problem: don't report a connected Codex account as unconfigured when its usage read fails.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17167 fix(rate-limits): don't report a connected Codex account as unconfigured when its usage read fails | Brennan Benson Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +464/−43. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fence client page placements1 PR · Standalone · SSH/remote re-architecture#
Problem: fence client page placements.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14529 feat(browser): fence client page placementsDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Draft/early · M Draft · checks FAILURE · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +336/−36. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2find cross-fork pull requests when the fork is not `origin`2 PRs · Related · SSH/remote re-architecture#
Problem: find cross-fork pull requests when the fork is not `origin`.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Related. Linked issues: #12956 [Bug]: Source Control blade offers "Create PR" for a branch that already has one — branch lookup assumes the fork is `origin` (Fixes, OPEN); #7331 Title unavailable (Unclear, Unknown); #9384 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12957 fix(github): find cross-fork pull requests when the fork is not `origin` | dcieslak19973 Community · CONTRIBUTOR | #12956 [Bug]: Source Control blade offers "Create PR" for a branch that already has one — branch lookup assumes the fork is `origin` Fixes · OPEN #7331 Title unavailable Unclear · Unknown #9384 Title unavailable Unclear · Unknown | Cluster contribution | **What:** A branch whose pull request lives on a fork that isn't `origin` now resolves correctly, so the Source Control blade shows the PR instead of offering "Create PR" for a branch that already has one. **Risk:** Call | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +554/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13227 fix(github): fall back when branch PR lookup is empty | Wooseong Kim Community · CONTRIBUTOR | #12956 [Bug]: Source Control blade offers "Create PR" for a branch that already has one — branch lookup assumes the fork is `origin` Fixes · OPEN | Cluster contribution | ## Description Branches hosted on a separately named fork now fall back to the existing CLI PR lookup when the inferred REST head-owner query returns an empty result. The branch lookup no longer treats an empty response | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +120/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Fix Jira connector routing in Web UI1 PR · Standalone · SSH/remote re-architecture#
Problem: Fix Jira connector routing in Web UI.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #16802 Jira connector crashes in Web UI because Jira RPC namespace is missing (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16803 Fix Jira connector routing in Web UI | JasonJarvan Community · FIRST_TIME_CONTRIBUTOR | #16802 Jira connector crashes in Web UI because Jira RPC namespace is missing Fixes · OPEN | Standalone change | ### Summary - expose the Jira runtime namespace from the Web preload API - route Web UI Jira connector calls through runtime RPC, matching Linear and hosted review connectors - add a regression test for `jira.connect` an | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +61/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2ignore a fit hold with no dimensions1 PR · Standalone · SSH/remote re-architecture#
Problem: ignore a fit hold with no dimensions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13951 fix(terminal): ignore a fit hold with no dimensions | PP Community · CONTRIBUTOR | None found | Standalone change | ## Problem `getRemoteDesktopFitHold` falls back to `{ cols: 0, rows: 0 }` when the host cannot read a pty's size: ```ts // src/main/runtime/orca-runtime.ts const size = this.getTerminalSize(ptyId) ?? { cols: 0, rows: 0 } | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +29/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep the project selection per task source1 PR · Standalone · SSH/remote re-architecture#
Problem: keep the project selection per task source.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15784 [Bug]: Shared project filter in Tasks generates errors (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15848 fix(tasks): keep the project selection per task source | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15784 [Bug]: Shared project filter in Tasks generates errors Fixes · OPEN | Standalone change | ## Summary **What** Switching task sources (GitHub / GitLab / Linear / Jira) now stashes the outgoing source's project selection and restores the incoming source's own stash — or the page's initial selection the first ti | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +102/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keepalive slow non-long-poll dispatches past the idle reaper1 PR · Standalone · SSH/remote re-architecture#
Problem: keepalive slow non-long-poll dispatches past the idle reaper.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15663 [Bug]: `orca worktree rm` drops runtime connection during batch deletes (`runtime_unavailable`) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15730 fix(runtime): keepalive slow non-long-poll dispatches past the idle reaper | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15663 [Bug]: `orca worktree rm` drops runtime connection during batch deletes (`runtime_unavailable`) Fixes · OPEN | Standalone change | ## Summary **What** Non-long-poll RPC dispatches now arm transport keepalive **lazily**: a single `setTimeout` (cleared on reply) that starts the keepalive interval if the dispatch is still silent after 10 seconds — well | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +73/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let a dual-role terminal read its Dispatch mailbox1 PR · Standalone · SSH/remote re-architecture#
Problem: let a dual-role terminal read its Dispatch mailbox.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #13362 Title unavailable (Unclear, Unknown); #13648 Title unavailable (Unclear, Unknown); #13639 Title unavailable (Unclear, Unknown); #13660 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15267 feat(orchestration): let a dual-role terminal read its Dispatch mailbox | Taras Kornichuk Community · CONTRIBUTOR | #13362 Title unavailable Unclear · Unknown #13648 Title unavailable Unclear · Unknown #13639 Title unavailable Unclear · Unknown #13660 Title unavailable Unclear · Unknown | Standalone change | A terminal that is both a dispatched worker and a bound coordinator can now read either of its two mailboxes, and is told when one of them was shadowed. ## The problem In a nested wave, the middle layer holds two roles: | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +430/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2let a new QR supersede deferred pairing recovery1 PR · Standalone · SSH/remote re-architecture#
Problem: let a new QR supersede deferred pairing recovery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #12708 [Bug]: Mobile relay pairing fails with "mobile relay pairing recovery pending" (Fixes, CLOSED).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13174 fix(mobile): let a new QR supersede deferred pairing recovery | BingZ Community · CONTRIBUTOR | #12708 [Bug]: Mobile relay pairing fails with "mobile relay pairing recovery pending" Fixes · CLOSED | Standalone change | ## Summary - After a partial relay pair stamped `winner`/`authorizationMode`, a later QR scan with a **different** invite hit `mobile relay pairing recovery pending` forever while recovery only deferred (#12708). - Keep | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +49/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2make src/shared the only terminal stream wire definition (STA-3482)1 PR · Standalone · SSH/remote re-architecture#
Problem: make src/shared the only terminal stream wire definition (STA-3482).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #12788 Title unavailable (Unclear, Unknown); #12675 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12834 fix(mobile): make src/shared the only terminal stream wire definition (STA-3482) | Jinwoo Hong Core team · MEMBER | #12788 Title unavailable Unclear · Unknown #12675 Title unavailable Unclear · Unknown | Standalone change | Root-cause half of STA-3482. Pairs with #12788, which handles the installed base. ## The real defect: a hand-copied wire definition that drifted `mobile/src/transport/terminal-stream-protocol.ts` was a **hand-copied dupl | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +262/−81. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2name the transport failure sign-in and Relay swallow1 PR · Standalone · SSH/remote re-architecture#
Problem: name the transport failure sign-in and Relay swallow.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #13735 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13736 fix(cloud): name the transport failure sign-in and Relay swallow | 오영택 Community · CONTRIBUTOR | #13735 Title unavailable Unclear · Unknown | Standalone change | Related to #13735 ## Scope Diagnostics only. No transport, TLS policy, or trust store changes here, and nothing that fails today starts succeeding. #13735 describes the underlying trust-store split and asks which directi | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +305/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2never finalize a hidden-output loss where nobody can see it (STA-4869)1 PR · Standalone · SSH/remote re-architecture#
Problem: never finalize a hidden-output loss where nobody can see it (STA-4869).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15504 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15534 fix(terminal): never finalize a hidden-output loss where nobody can see it (STA-4869)Draft | Jinwoo Hong Core team · MEMBER | #15504 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Draft/early · L Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk16 files, +2078/−72. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2note that active/current worktree selectors are local-runtime only2 PRs · Overlapping · SSH/remote re-architecture#
Problem: note that active/current worktree selectors are local-runtime only.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Overlapping. Linked issues: #14030 [Other]: terminal create --help headlines --worktree active, which is rejected against a remote runtime (Fixes, OPEN); #7432 Title unavailable (Unclear, Unknown); #7892 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14035 docs(cli): note that active/current worktree selectors are local-runtime only | Jesper Vang Community · FIRST_TIME_CONTRIBUTOR | #14030 [Other]: terminal create --help headlines --worktree active, which is rejected against a remote runtime Fixes · OPEN #7432 Title unavailable Unclear · Unknown #7892 Title unavailable Unclear · Unknown | Cluster contribution | Fixes #14030. `orca terminal create --help` uses `--worktree active` as its headline example (`src/cli/help.ts`), and `orca worktree set --help` does the same. Against a remote runtime that argument always fails — `asser | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +8/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14072 docs: clarify remote worktree selectors | nyxst4ck Community · FIRST_TIME_CONTRIBUTOR | #14030 [Other]: terminal create --help headlines --worktree active, which is rejected against a remote runtime Fixes · OPEN | Cluster contribution | ## Summary Clarify that `active` and `current` are local-cwd shortcuts and provide the selector forms required for remote runtime calls. Fixes #14030. ## Validation - Ran `git diff --check`. | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +2/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2offer Remove on path-bound host setups, behind a confirm1 PR · Standalone · SSH/remote re-architecture#
Problem: offer Remove on path-bound host setups, behind a confirm.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15281 [Bug]: No way to delete/edit available host configuration (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15610 fix(settings): offer Remove on path-bound host setups, behind a confirm | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15281 [Bug]: No way to delete/edit available host configuration Fixes · OPEN | Standalone change | ## Summary **What** The "Available Hosts" section in Settings → Repository now offers **Remove** on host setups that are bound to a folder path, not only on "Path pending" rows. Deleting a bound setup goes through a conf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +183/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2open WSL Claude sign-in in Windows browser1 PR · Standalone · SSH/remote re-architecture#
Problem: open WSL Claude sign-in in Windows browser.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #11823 [Bug]: WSL "Add Account" hangs 180s when the distro has no xdg-open — Claude CLI falls back to the paste-code flow and its output is never surfaced (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12023 fix(accounts): open WSL Claude sign-in in Windows browser | Rod Boev Community · CONTRIBUTOR | #11823 [Bug]: WSL "Add Account" hangs 180s when the distro has no xdg-open — Claude CLI falls back to the paste-code flow and its output is never surfaced Fixes · OPEN | Standalone change | ## Summary Give WSL Claude sign-in a private, temporary browser opener when the selected distro has no opener on PATH. The shim writes one atomic URL handoff into the existing temporary config directory; the main process | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +642/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve standing host reconnect intent1 PR · Standalone · SSH/remote re-architecture#
Problem: preserve standing host reconnect intent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #5341 Title unavailable (Unclear, Unknown); #9774 Title unavailable (Unclear, Unknown); #8255 Title unavailable (Unclear, Unknown); #11513 Title unavailable (Unclear, Unknown); #7718 Title unavailable (Unclear, Unknown); #7329 Title unavailable (Unclear, Unknown); #9993 Title unavailable (Unclear, Unknown); #12112 Title unavailable (Unclear, Unknown); #13137 Title unavailable (Unclear, Unknown); #15559 Title unavailable (Unclear, Unknown); #15578 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17067 fix(remote): preserve standing host reconnect intent | Brennan Benson Core team · MEMBER | #5341 Title unavailable Unclear · Unknown #9774 Title unavailable Unclear · Unknown #8255 Title unavailable Unclear · Unknown #11513 Title unavailable Unclear · Unknown #7718 Title unavailable Unclear · Unknown #7329 Title unavailable Unclear · Unknown #9993 Title unavailable Unclear · Unknown #12112 Title unavailable Unclear · Unknown #13137 Title unavailable Unclear · Unknown #15559 Title unavailable Unclear · Unknown #15578 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 16 | $\color{#1a7f37}{\Huge{\mathb | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk39 files, +2213/−380. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve WebGL atlas on tab reveal1 PR · Standalone · SSH/remote re-architecture#
Problem: preserve WebGL atlas on tab reveal.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #7951 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13339 fix(terminal): preserve WebGL atlas on tab reveal | Victor Demonchy Community · FIRST_TIME_CONTRIBUTOR | #7951 Title unavailable Unclear · Unknown | Standalone change | ## Summary Refs #7951. Switching back to a terminal tab could leave the pane showing gray or black blocks until a window resize or another layout change forced a repaint. The light tab-resume path was clearing the shared | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · S Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +28/−52. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Prune resolved max-lines suppressions1 PR · Standalone · SSH/remote re-architecture#
Problem: Prune resolved max-lines suppressions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #17141 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17142 Prune resolved max-lines suppressions | Neil Core team · MEMBER | #17141 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 3 | 0 | $ | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +0/−10. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2raise viewport column cap from 240 to 10241 PR · Standalone · SSH/remote re-architecture#
Problem: raise viewport column cap from 240 to 1024.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #16354 [Feature]: Let PTY width follow the pane width — remove the 240-column terminal cap (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16578 fix(terminal): raise viewport column cap from 240 to 1024 | Wooseong Kim Community · CONTRIBUTOR | #16354 [Feature]: Let PTY width follow the pane width — remove the 240-column terminal cap Fixes · OPEN | Standalone change | ## Description A full-width terminal pane was clamped at 240 columns, so wide monitors wrapped early and left a blank right pad. Split panes already sized to the real width. The viewport clamp now allows up to 1024 colum | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +69/−18. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2remember last GitHub Start vs Open-in-browser choice1 PR · Standalone · SSH/remote re-architecture#
Problem: remember last GitHub Start vs Open-in-browser choice.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14480 [Feature]: Save 'Open in browser' choice in Tasks>GitHub when selected instead of 'Start' by default (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14779 fix(tasks): remember last GitHub Start vs Open-in-browser choice | Wooseong Kim Community · CONTRIBUTOR | #14480 [Feature]: Save 'Open in browser' choice in Tasks>GitHub when selected instead of 'Start' by default Fixes · OPEN | Standalone change | ## Description Tasks → GitHub remembers the last Start vs Open in browser choice and shows it as the primary action next time. ## Focused fix - In scope: persist one UI preference. Default remains Start. - Out of scope: | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +291/−125. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report counterbalanced WSL Git medians1 PR · Standalone · SSH/remote re-architecture#
Problem: report counterbalanced WSL Git medians.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #9300 Title unavailable (Unclear, Unknown); #11261 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13474 fix(bench): report counterbalanced WSL Git medians | OrcaWin Unknown · COLLABORATOR | #9300 Title unavailable Unclear · Unknown #11261 Title unavailable Unclear · Unknown | Standalone change | ## Summary - factor the WSL Git benchmark's ABBA order into a tested counterbalanced schedule - reject odd `--samples` counts before starting WSL work - report the conventional midpoint median for even sample sets while | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +163/−19. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2report real exitCode from terminal wait --for exit1 PR · Standalone · SSH/remote re-architecture#
Problem: report real exitCode from terminal wait --for exit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14739 [Bug]: terminal wait --for exit reports exitCode: 0 for commands that exited non-zero (and the exec-prefix requirement is undocumented) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14774 fix(cli): report real exitCode from terminal wait --for exit | Wooseong Kim Community · CONTRIBUTOR | #14739 [Bug]: terminal wait --for exit reports exitCode: 0 for commands that exited non-zero (and the exec-prefix requirement is undocumented) Fixes · OPEN | Standalone change | ## Description `orca terminal wait --for exit` now reports the command's real exit code instead of always `0`. Help text notes that `--command` needs `exec` so wait tracks the pane process. ## Focused fix - In scope: plu | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +297/−26. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Report the failing command and PATH when a POSIX setup runner fails1 PR · Standalone · SSH/remote re-architecture#
Problem: Report the failing command and PATH when a POSIX setup runner fails.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #13688 Title unavailable (Unclear, Unknown); #13689 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15271 Report the failing command and PATH when a POSIX setup runner fails | Taras Kornichuk Community · CONTRIBUTOR | #13688 Title unavailable Unclear · Unknown #13689 Title unavailable Unclear · Unknown | Standalone change | ## What changes A POSIX setup (or issue-command) runner that fails now says which command failed and, when the command was not found, which `PATH` it ran with. ## Why A setup hook is unattended automation: the runner is | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +182/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2restore retained tail when host snapshot is empty1 PR · Standalone · SSH/remote re-architecture#
Problem: restore retained tail when host snapshot is empty.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14182 Host serves an empty snapshot for an exited-but-preserved PTY although the retained scrollback survives (Fixes, OPEN); #7329 Title unavailable (Unclear, Unknown); #14095 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14184 fix(terminal): restore retained tail when host snapshot is empty | Brennan Benson Core team · MEMBER | #14182 Host serves an empty snapshot for an exited-but-preserved PTY although the retained scrollback survives Fixes · OPEN #7329 Title unavailable Unclear · Unknown #14095 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 When a preserved terminal has exited, Orca can still retain its text even if the screen serializer answers with an empty object. The host now sends that retained text instead of authoritatively telling the client | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +303/−23. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2retire timed-out provider snapshot acquisitions1 PR · Standalone · SSH/remote re-architecture#
Problem: retire timed-out provider snapshot acquisitions.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #16531 [Bug]: readVisibleTerminalState() doesn't forward retireOnTimeout, leaving wedged provider acquisitions active (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16560 fix(runtime): retire timed-out provider snapshot acquisitions | Wooseong Kim Community · CONTRIBUTOR | #16531 [Bug]: readVisibleTerminalState() doesn't forward retireOnTimeout, leaving wedged provider acquisitions active Fixes · OPEN | Standalone change | ## Description Visible terminal snapshot reads timed out without retiring the in-flight provider buffer acquisition, so the next read rejoined the same hung promise. `readVisibleTerminalState` now passes `retireOnTimeout | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +37/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2show relay grace period in two units1 PR · Standalone · SSH/remote re-architecture#
Problem: show relay grace period in two units.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13838 fix(settings): show relay grace period in two units | PP Community · CONTRIBUTOR | None found | Standalone change | ## Problem The SSH relay grace period is entered in **seconds**. A milliseconds-shaped entry stays inside the `MIN_SSH_RELAY_GRACE_PERIOD_SECONDS`..`MAX_SSH_RELAY_GRACE_PERIOD_SECONDS` bounds, so nothing rejects it — and | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +72/−14. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2skip unchanged review-note reflows1 PR · Standalone · SSH/remote re-architecture#
Problem: skip unchanged review-note reflows.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #16400 [Bug]: Editing a review note's content is severely laggy when a document has many review notes (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17212 perf(editor): skip unchanged review-note reflows | Neil Core team · MEMBER | #16400 [Bug]: Editing a review note's content is severely laggy when a document has many review notes Fixes · OPEN | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +62/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split Claude runtime auth responsibilities1 PR · Standalone · SSH/remote re-architecture#
Problem: Split Claude runtime auth responsibilities.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #17266 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17268 Split Claude runtime auth responsibilities | Neil Core team · MEMBER | #17266 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 15 | $\co | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · L Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk15 files, +1829/−1730. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split hosted review creation checks1 PR · Standalone · SSH/remote re-architecture#
Problem: Split hosted review creation checks.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #17151 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17152 Split hosted review creation checks | Neil Core team · MEMBER | #17151 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 5 | $\col | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +432/−409. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Split pane tree equalization logic1 PR · Standalone · SSH/remote re-architecture#
Problem: Split pane tree equalization logic.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #17142 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17145 Split pane tree equalization logic | Neil Core team · MEMBER | #17142 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 3 | $\col | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +60/−62. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stagger and bound metadata polling1 PR · Standalone · SSH/remote re-architecture#
Problem: stagger and bound metadata polling.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16175 perf(git): stagger and bound metadata polling | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · L Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk11 files, +1176/−491. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop a failed diff load from being saved over the file1 PR · Standalone · SSH/remote re-architecture#
Problem: stop a failed diff load from being saved over the file.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #14160 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14509 fix(editor): stop a failed diff load from being saved over the file | Neil Core team · MEMBER | #14160 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +668/−37. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop rescanning persisted pane tabs1 PR · Standalone · SSH/remote re-architecture#
Problem: stop rescanning persisted pane tabs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17179 perf(startup): stop rescanning persisted pane tabs | Neil Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +247/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop writing hook events Claude Code's schema rejects1 PR · Standalone · SSH/remote re-architecture#
Problem: stop writing hook events Claude Code's schema rejects.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15548 Claude Code hooks: `StopFailure` is not a valid hook event — causes entire settings.json to be skipped (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15558 fix(claude): stop writing hook events Claude Code's schema rejects | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15548 Claude Code hooks: `StopFailure` is not a valid hook event — causes entire settings.json to be skipped Fixes · OPEN | Standalone change | Fixes #15548. ## What changed Claude Code validates `hooks` event names against its settings schema and **skips the entire `settings.json`** when it meets an unknown key. Four events Orca injects are OpenClaude-only (`St | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +113/−15. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2surface Git dubious ownership instead of empty imports1 PR · Standalone · SSH/remote re-architecture#
Problem: surface Git dubious ownership instead of empty imports.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #12627 [Bug]: Windows repo import silently creates zero worktrees when safe.directory is required (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13151 fix(repos): surface Git dubious ownership instead of empty imports | BingZ Community · CONTRIBUTOR | #12627 [Bug]: Windows repo import silently creates zero worktrees when safe.directory is required Fixes · OPEN | Standalone change | ## Summary - On Windows (and other hosts), Git may refuse checkouts owned by another principal (`detected dubious ownership` / `safe.directory`). - `isGitRepo` can still accept a `.git` marker after `rev-parse` fails, so | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +252/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2track Windows performance work1 PR · Standalone · SSH/remote re-architecture#
Problem: track Windows performance work.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #9300 Title unavailable (Unclear, Unknown); #9284 Title unavailable (Unclear, Unknown); #9768 Title unavailable (Unclear, Unknown); #9372 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13167 docs: track Windows performance work | OrcaWin Unknown · COLLABORATOR | #9300 Title unavailable Unclear · Unknown #9284 Title unavailable Unclear · Unknown #9768 Title unavailable Unclear · Unknown #9372 Title unavailable Unclear · Unknown | Standalone change | ## Summary - add a durable Windows/WSL performance tracker linked to umbrella issue #9300 - record completed fixes and their deterministic benchmark evidence - prioritize the WSL Git hot path (#9284 / #9768 / #9372) as t | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +183/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2treat existing WSL Codex runtime home as ready on EISDIR mkdir1 PR · Standalone · SSH/remote re-architecture#
Problem: treat existing WSL Codex runtime home as ready on EISDIR mkdir.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15441 [Bug]: Windows host mkdir of existing WSL Codex runtime home throws EISDIR (\\wsl.localhost\...\codex-runtime-home\home) (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15444 fix(windows): treat existing WSL Codex runtime home as ready on EISDIR mkdir | 1bok2 Community · FIRST_TIME_CONTRIBUTOR | #15441 [Bug]: Windows host mkdir of existing WSL Codex runtime home throws EISDIR (\\wsl.localhost\...\codex-runtime-home\home) Fixes · OPEN | Standalone change | ## Summary Windows Orca creates the WSL Codex runtime home with host `fs.mkdirSync(..., { recursive: true })` on a `\\wsl.localhost\...` UNC path. When that guest directory already exists — or 9P is mid-attach after `wsl | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +164/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2wait for queued writes in park snapshots1 PR · Standalone · SSH/remote re-architecture#
Problem: wait for queued writes in park snapshots.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16141 fix(runtime): wait for queued writes in park snapshots | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Blocked · S Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +126/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2warn implementers that internal subagents must not send worker_done (#15634)1 PR · Standalone · SSH/remote re-architecture#
Problem: warn implementers that internal subagents must not send worker_done (#15634).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: SSH/remote re-architecture (stack rank 4).
Relationship: Standalone. Linked issues: #15634 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15795 fix: warn implementers that internal subagents must not send worker_done (#15634) | kaluli123123 Community · FIRST_TIME_CONTRIBUTOR | #15634 Title unavailable Unclear · Unknown | Standalone change | ## Summary - A Codex worker's internal cold-review subagent inherited enough of the parent dispatch protocol to emit `worker_done` for the parent task/dispatch. Orca accepted it because the capability/pane/process-incarn | P2 Useful scoped improvement; aligned with SSH/remote re-architecture but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +75/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2apply terminal line height to Monaco1 PR · Standalone · Profile and resource management#
Problem: apply terminal line height to Monaco.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #14257 File editor ignores line height: Monaco lineHeight is never set, so file view can't match terminal spacing (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14783 fix(editor): apply terminal line height to Monaco | Wooseong Kim Community · CONTRIBUTOR | #14257 File editor ignores line height: Monaco lineHeight is never set, so file view can't match terminal spacing Fixes · OPEN | Standalone change | ## Description The file editor now passes Monaco `lineHeight` from the terminal Line Height setting so file view can match terminal spacing. ## Focused fix - In scope: one Monaco option derived from the existing setting. | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +133/−5. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Extract mobile troubleshoot screen styles1 PR · Standalone · Profile and resource management#
Problem: Extract mobile troubleshoot screen styles.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #17145 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17146 Extract mobile troubleshoot screen styles | Neil Core team · MEMBER | #17145 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 4 | $\col | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +137/−149. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2fix broken Continue CLI link in README1 PR · Standalone · Profile and resource management#
Problem: fix broken Continue CLI link in README.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14226 docs: fix broken Continue CLI link in README | EdgeMLHacker Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | The Continue badge in the README points at `https://docs.continue.dev/guides/cli`, which currently 404s. The CLI docs now live under `/cli`, so I've pointed it at the overview page (`https://docs.continue.dev/cli/overvie | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +1/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2isolate unparseable schedules per tick and reject over-range cron steps1 PR · Standalone · Profile and resource management#
Problem: isolate unparseable schedules per tick and reject over-range cron steps.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #15895 [Bug]: an over-range cron step degrades silently and still validates — `5/90 * * * *` runs hourly (Fixes, OPEN); #15723 Title unavailable (Unclear, Unknown); #15864 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15902 fix(automations): isolate unparseable schedules per tick and reject over-range cron steps | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15895 [Bug]: an over-range cron step degrades silently and still validates — `5/90 * * * *` runs hourly Fixes · OPEN #15723 Title unavailable Unclear · Unknown #15864 Title unavailable Unclear · Unknown | Standalone change | ## What Two halves of the #15895 fix, in the order the issue prescribes: 1. **Per-automation error isolation.** `evaluateDueRuns` wraps each `evaluateAutomation` in its own `try`/`catch` (log + continue), and `evaluateAu | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +149/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2join wrapped PowerShell URLs before opening1 PR · Standalone · Profile and resource management#
Problem: join wrapped PowerShell URLs before opening.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #14291 PowerShell terminal: file paths and multi-line URLs are not clickable/openable (Fixes, OPEN); #8832 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14784 fix(terminal): join wrapped PowerShell URLs before opening | Wooseong Kim Community · CONTRIBUTOR | #14291 PowerShell terminal: file paths and multi-line URLs are not clickable/openable Fixes · OPEN #8832 Title unavailable Unclear · Unknown | Standalone change | ## Description Wrapped PowerShell URLs are joined before open so a hard line break no longer 404s the first line only. ## Focused fix - In scope: join wrapped HTTP URL remainders in the terminal link opener. - Out of sco | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +125/−16. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2prompt before opening custom app protocol links1 PR · Standalone · Profile and resource management#
Problem: prompt before opening custom app protocol links.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #12719 Title unavailable (Unclear, Unknown); #13225 Title unavailable (Unclear, Unknown); #13237 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13240 feat(browser): prompt before opening custom app protocol links | BingZ Community · CONTRIBUTOR | #12719 Title unavailable Unclear · Unknown #13225 Title unavailable Unclear · Unknown #13237 Title unavailable Unclear · Unknown | Standalone change | ## Summary - Embedded browser `will-navigate` / `setWindowOpenHandler` now detect custom app schemes (`oktaverify://`, etc.). - In-guest load is denied; a trusted confirm dialog shows the full URL and requesting origin, | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Blocked · M Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +465/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2stop re-wiping the shared glyph atlas on every reveal shot1 PR · Standalone · Profile and resource management#
Problem: stop re-wiping the shared glyph atlas on every reveal shot.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #4480 Title unavailable (Unclear, Unknown); #6354 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13836 perf(terminal): stop re-wiping the shared glyph atlas on every reveal shot | PP Community · CONTRIBUTOR | #4480 Title unavailable Unclear · Unknown #6354 Title unavailable Unclear · Unknown | Standalone change | ## What A reveal fires the shared WebGL glyph atlas wipe more times than it needs to. Each wipe clears the atlas shared by every same-config terminal and repaints all of them, so the cost scales with how many terminals a | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +257/−38. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2syntax-highlight VHDL files1 PR · Standalone · Profile and resource management#
Problem: syntax-highlight VHDL files.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #5427 Title unavailable (Unclear, Unknown); #12124 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12123 feat(editor): syntax-highlight VHDL files | Nickel Liang Community · FIRST_TIME_CONTRIBUTOR | #5427 Title unavailable Unclear · Unknown #12124 Title unavailable Unclear · Unknown | Standalone change | ## What `.vhd` files open as plaintext in the file preview and both diff panes — Monaco ships no VHDL grammar. This adds one. SystemVerilog and Verilog were **already fine**: Monaco 0.55.1 registers `systemverilog` for ` | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Ready · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +676/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2validate in-process serve flags like the CLI1 PR · Standalone · Profile and resource management#
Problem: validate in-process serve flags like the CLI.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #13006 In-process CLI-form serve skips the CLI's flag validation and cross-flag guards (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13133 fix(serve): validate in-process serve flags like the CLI | BingZ Community · CONTRIBUTOR | #13006 In-process CLI-form serve skips the CLI's flag validation and cross-flag guards Fixes · OPEN | Standalone change | ## Summary - Extract `getServeOptions` to `src/main/startup/serve-options.ts` and share cross-flag guards with `orca serve` via `src/shared/serve-option-guards.ts`. - Reject contradictory combinations (`--no-pairing` + ` | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +431/−70. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2warn that bare brew cask orca is Plotly, not Orca ADE1 PR · Standalone · Profile and resource management#
Problem: warn that bare brew cask orca is Plotly, not Orca ADE.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Profile and resource management (stack rank 6).
Relationship: Standalone. Linked issues: #14591 Cask token collision: bare `orca` upgrades install the deprecated Plotly Orca cask (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14777 docs: warn that bare brew cask orca is Plotly, not Orca ADE | Wooseong Kim Community · CONTRIBUTOR | #14591 Cask token collision: bare `orca` upgrades install the deprecated Plotly Orca cask Fixes · OPEN | Standalone change | ## Description Install docs now tell users to use the fully qualified Homebrew token `stablyai/orca/orca`. Bare `brew upgrade --cask orca` installs deprecated Plotly Orca. ## Focused fix - In scope: README and localized | P2 Useful scoped improvement; aligned with Profile and resource management but no verified emergency. | Unclear · M Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +14/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2preserve ANSI background under IME preedit1 PR · Standalone · Chat UI#
Problem: preserve ANSI background under IME preedit.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Chat UI (stack rank 8).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16230 fix(terminal): preserve ANSI background under IME preedit | Noobear Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary - paint xterm's opaque IME composition overlay with the cursor cell's effective ANSI background instead of the terminal-wide theme background - resolve RGB, indexed palette, default, and inverse cell colors wh | P2 Useful scoped improvement; aligned with Chat UI but no verified emergency. | Minor changes needed · M Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +304/−107. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2correct zh-CN translation for editor view toggle buttons1 PR · Standalone · Enterprise governance#
Problem: correct zh-CN translation for editor view toggle buttons.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Enterprise governance (stack rank 9).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13723 fix(i18n): correct zh-CN translation for editor view toggle buttons | Maxon Phong Community · CONTRIBUTOR | None found | Standalone change | ## Problem When previewing/editing a Markdown file, the top-right toggle buttons show incorrect Simplified Chinese translations: | Key | English | Before (zh-CN) | After (zh-CN) | |---|---|---|---| | `aff15f94f5` | Rich | P2 Useful scoped improvement; aligned with Enterprise governance but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +3/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2order Issues board columns Backlog -> Done1 PR · Standalone · Enterprise governance#
Problem: order Issues board columns Backlog -> Done.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Enterprise governance (stack rank 9).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12096 fix(linear): order Issues board columns Backlog -> Done | ElNelyo Community · CONTRIBUTOR | None found | Standalone change | ## What Tasks → Linear → Issues → **Board** mode now shows status columns in workflow order (**Backlog … Done**) instead of the previous **Done → Backlog** artifact. ## Why Board columns were rendered in the order their | P2 Useful scoped improvement; aligned with Enterprise governance but no verified emergency. | Blocked · S Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +117/−7. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2upgrade nanoid to 3.3.18, 5.1.6 (CVE-2026-67213)1 PR · Standalone · Enterprise governance#
Problem: upgrade nanoid to 3.3.18, 5.1.6 (CVE-2026-67213).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Enterprise governance (stack rank 9).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14521 fix: upgrade nanoid to 3.3.18, 5.1.6 (CVE-2026-67213) | Anupam Mediratta Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary Upgrade nanoid from 3.3.17 to 3.3.18, 5.1.6 to fix CVE-2026-67213. ## Vulnerability | Field | Value | |-------|-------| | **ID** | CVE-2026-67213 | | **Severity** | HIGH | | **Scanner** | trivy | | **Rule** | | P2 Useful scoped improvement; aligned with Enterprise governance but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +18/−48. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[TEST] Stacked PR UI validation — API1 PR · Standalone · Inbound and outbound endpoints#
Problem: [TEST] Stacked PR UI validation — API.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Inbound and outbound endpoints (stack rank 12).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Merge
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13721 [TEST] Stacked PR UI validation — API | Jinwoo Hong Core team · MEMBER | None found | Standalone change | Disposable draft for Orca stacked PR UI validation. Do not merge. | P2 Useful scoped improvement; aligned with Inbound and outbound endpoints but no verified emergency. | Ready · S Open · checks SUCCESS · review None | Merge |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +1/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2keep underscores visible when ligatures are enabled (#13473)1 PR · Standalone · Inbound and outbound endpoints#
Problem: keep underscores visible when ligatures are enabled (#13473).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Inbound and outbound endpoints (stack rank 12).
Relationship: Standalone. Linked issues: #13473 [Bug] Underscore is invisible in orca terminals and CLIs opened there (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14055 fix(terminal): keep underscores visible when ligatures are enabled (#13473) | LavyaT Community · FIRST_TIME_CONTRIBUTOR | #13473 [Bug] Underscore is invisible in orca terminals and CLIs opened there Fixes · OPEN | Standalone change | ## Summary Fixes #13473 — underscores are invisible in terminals when ligatures are enabled. Some programming fonts (e.g. JetBrains Mono) ship a `calt` feature that connects runs of underscores into a single glyph. The ` | P2 Useful scoped improvement; aligned with Inbound and outbound endpoints but no verified emergency. | Minor changes needed · S Open · checks SUCCESS · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +30/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2key cron day restriction off the literal star, matching vixie1 PR · Standalone · Inbound and outbound endpoints#
Problem: key cron day restriction off the literal star, matching vixie.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Inbound and outbound endpoints (stack rank 12).
Relationship: Standalone. Linked issues: #15896 [Bug]: cron day restriction is inferred from set size, not a literal `*` — OR/AND day matching diverges from vixie (Fixes, OPEN); #15864 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review soon
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15900 fix(automations): key cron day restriction off the literal star, matching vixie | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15896 [Bug]: cron day restriction is inferred from set size, not a literal `*` — OR/AND day matching diverges from vixie Fixes · OPEN #15864 Title unavailable Unclear · Unknown | Standalone change | ## What `parseCronExpression` now keys day-of-month/day-of-week restriction off the field **literally starting with `*`** — vixie's `DOM_STAR`/`DOW_STAR` — instead of inferring it from the size of the parsed set. `cronDa | P2 Useful scoped improvement; aligned with Inbound and outbound endpoints but no verified emergency. | Unclear · S Open · checks Unknown · review None | Review soon |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +69/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[TEST] Stacked PR creation — child1 PR · Standalone · Other product work#
Problem: [TEST] Stacked PR creation — child.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Other product work.
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13741 [TEST] Stacked PR creation — childDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | Disposable draft for Orca stacked PR creation validation. Do not merge. | P2 Useful scoped improvement; aligned with Other product work but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk0 files, +0/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[TEST] Stacked PR creation — parent1 PR · Standalone · Other product work#
Problem: [TEST] Stacked PR creation — parent.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Other product work.
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13740 [TEST] Stacked PR creation — parentDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | Disposable draft for Orca stacked PR creation validation. Do not merge. | P2 Useful scoped improvement; aligned with Other product work but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk0 files, +0/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2[TEST] Stacked PR creation — UI layer1 PR · Standalone · Other product work#
Problem: [TEST] Stacked PR creation — UI layer.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Other product work.
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13738 [TEST] Stacked PR creation — UI layerDraft | Jinwoo Hong Core team · MEMBER | None found | Standalone change | Disposable draft for Orca stacked PR creation validation. Do not merge. | P2 Useful scoped improvement; aligned with Other product work but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk0 files, +0/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P2Windows PR menu reproduction1 PR · Standalone · Other product work#
Problem: Windows PR menu reproduction.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Other product work.
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Defer
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16844 test: Windows PR menu reproductionDraft | OrcaWin Unknown · COLLABORATOR | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 0 | 0 | 0 | 0 | | Prod | 0 | 0 | 0 | P2 Useful scoped improvement; aligned with Other product work but no verified emergency. | Draft/early · S Draft · checks SUCCESS · review None | Defer |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk0 files, +0/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3batch-prune stale local metadata1 PR · Standalone · Plugins#
Problem: batch-prune stale local metadata.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15412 [Bug]: Main process reaches 100% CPU after terminal/worktree churn and retains thousands of removed worktrees (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17278 perf(worktrees): batch-prune stale local metadata | Neil Core team · MEMBER | #15412 [Bug]: Main process reaches 100% CPU after terminal/worktree churn and retains thousands of removed worktrees Fixes · OPEN | Standalone change | ## ELI5 Orca keeps a metadata card for each worktree so it can remember names, pins, links, and activity. Deleted worktrees could leave thousands of cards behind, and cleaning them one at a time repeatedly rescanned Git | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Ready · L Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk38 files, +3382/−46. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3clear stale mobile ws fallback port1 PR · Standalone · Plugins#
Problem: clear stale mobile ws fallback port.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #15490 [Bug]: persisted mobile-ws fallback port flip-flops with Windows Hyper-V excluded port ranges, repeatedly stranding paired devices (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15509 fix(runtime): clear stale mobile ws fallback port | Siddiqui Qamar Community · CONTRIBUTOR | #15490 [Bug]: persisted mobile-ws fallback port flip-flops with Windows Hyper-V excluded port ranges, repeatedly stranding paired devices Fixes · OPEN | Standalone change | ## Summary On Windows, Orca could alternate between a stale mobile WebSocket fallback port and the default port after restarts, disconnecting paired devices. This change removes the stale fallback after it fails and the | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk4 files, +86/−6. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3complete OMP stale cwd recovery1 PR · Standalone · Plugins#
Problem: complete OMP stale cwd recovery.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16457 [Bug] OMP Unknown error (Fixes, CLOSED); #17128 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #17154 fix(terminal): complete OMP stale cwd recovery | Neil Core team · MEMBER | #16457 [Bug] OMP Unknown error Fixes · CLOSED #17128 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 An Orca terminal can keep standing in an old folder object after the project path is deleted and recreated. The prompt still shows the familiar path, but OMP cannot determine its current directory and exits befor | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Ready · M Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk9 files, +137/−55. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3discard a stale authorized-roots rebuild instead of marking the cache clean2 PRs · Competing · Plugins#
Problem: discard a stale authorized-roots rebuild instead of marking the cache clean.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Competing. Linked issues: #15667 [Bug]: Worktree created during an authorized-roots rebuild gets "Access denied" in File Explorer; removed repos can be re-authorized (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Choose one implementation after a product and technical comparison; do not land alternatives together.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Not until one implementation is chosen.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Product and technical decision required.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15668 fix(filesystem-auth): discard a stale authorized-roots rebuild instead of marking the cache clean | 2sumtech Community · CONTRIBUTOR | #15667 [Bug]: Worktree created during an authorized-roots rebuild gets "Access denied" in File Explorer; removed repos can be re-authorized Fixes · OPEN | Alternative implementation | ## ELI5 Orca keeps a little allow-list of folders that File Explorer and Quick Open may touch. When that list is being recomputed (it asks git, which takes a moment) and you create or remove a workspace in that moment, t | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +116/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #15726 fix(filesystem-auth): stop an overtaken rebuild writing stale authorized roots | yzxcj797 Community · FIRST_TIME_CONTRIBUTOR | #15667 [Bug]: Worktree created during an authorized-roots rebuild gets "Access denied" in File Explorer; removed repos can be re-authorized Fixes · OPEN | Alternative implementation | ## Summary **What** The filesystem-auth authorized-roots cache now carries an invalidation epoch. A rebuild captures the epoch before snapshotting and **discards itself** (no writes, dirty stays set) when an invalidation | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Needs product decision |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +92/−8. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3drop the stale Settings > Experimental prerequisite2 PRs · Overlapping · Plugins#
Problem: drop the stale Settings > Experimental prerequisite.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Plugins (stack rank 1).
Relationship: Overlapping. Linked issues: #14031 [Other]: bundled orchestration skill guide tells agents to enable a Settings > Experimental toggle that no longer exists (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14034 docs(orchestration): drop the stale Settings > Experimental prerequisite | Jesper Vang Community · FIRST_TIME_CONTRIBUTOR | #14031 [Other]: bundled orchestration skill guide tells agents to enable a Settings > Experimental toggle that no longer exists Fixes · OPEN | Cluster contribution | Fixes #14031. `skill-guides/orchestration.md` lists this as a precondition: > - The orchestration experimental feature must be enabled in Settings > Experimental. No such setting exists — `experimentalOrchestration`/`orc | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +1/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14069 docs: remove stale orchestration toggle requirement | nyxst4ck Community · FIRST_TIME_CONTRIBUTOR | #14031 [Other]: bundled orchestration skill guide tells agents to enable a Settings > Experimental toggle that no longer exists Fixes · OPEN | Cluster contribution | ## Summary Remove the stale prerequisite that asks users to enable an orchestration toggle which no longer exists. Fixes #14031. ## Validation - Confirmed `skill-guides/orchestration.md` no longer references Settings > E | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +0/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3handle static WSL titles and clear stale spinners3 PRs · Overlapping · Automated release pipeline#
Problem: handle static WSL titles and clear stale spinners.
Combined impact: Coordinates 3 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 1).
Relationship: Overlapping. Linked issues: #13890 [Bug]: OMP 17.2.12+ loses working status and can leave a spinner stuck on WSL (Fixes, OPEN); #13749 Title unavailable (Unclear, Unknown); #13776 Title unavailable (Unclear, Unknown); #14279 Title unavailable (Unclear, Unknown); #14330 Title unavailable (Unclear, Unknown); #14278 Title unavailable (Unclear, Unknown); #13923 Title unavailable (Unclear, Unknown); #13891 Title unavailable (Unclear, Unknown); #15658 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Review together; if diffs do not conflict, land the smallest foundation first, then rerun CI before each follow-up.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Potentially, after overlap and CI validation.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Elevated.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Not established.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13891 fix(omp): handle static WSL titles and clear stale spinners | euclodius Community · FIRST_TIME_CONTRIBUTOR | #13890 [Bug]: OMP 17.2.12+ loses working status and can leave a spinner stuck on WSL Fixes · OPEN #13749 Title unavailable Unclear · Unknown #13776 Title unavailable Unclear · Unknown #14279 Title unavailable Unclear · Unknown #14330 Title unavailable Unclear · Unknown #14278 Title unavailable Unclear · Unknown #13923 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary - Classify bare and wrapper-prefixed OMP 17.2.12+ WSL/ConPTY titles as `working`, `idle`, or `permission`. - Preserve the legacy no-space `π:` title as idle. - Stop a pane's synthetic title spinner when its or | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Unclear · M Open · checks Unknown · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk7 files, +97/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #13923 fix(omp): preserve native WSL status and clear stale spinners | OrcaWin Unknown · COLLABORATOR | #13890 [Bug]: OMP 17.2.12+ loses working status and can leave a spinner stuck on WSL Fixes · OPEN #13891 Title unavailable Unclear · Unknown #14279 Title unavailable Unclear · Unknown #14330 Title unavailable Unclear · Unknown #14278 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 OMP changed the terminal-title punctuation it uses on Windows/WSL. Orca read every new title as idle and could leave its fallback spinner running after the live hook row disappeared. This teaches the shared title | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · M Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +202/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #14602 fix(omp): read Pi/OMP static state-title markers and retire stale spinners | Brennan Benson Core team · MEMBER | #13890 [Bug]: OMP 17.2.12+ loses working status and can leave a spinner stuck on WSL Fixes · OPEN #13891 Title unavailable Unclear · Unknown #13923 Title unavailable Unclear · Unknown #13749 Title unavailable Unclear · Unknown #13776 Title unavailable Unclear · Unknown #15658 Title unavailable Unclear · Unknown | Cluster contribution | ## ELI5 OMP used to spin a little braille animation in the terminal title while it worked. On Windows/WSL it can't animate any more, so as of 17.2.12 it writes a static punctuation marker instead: `π : cwd` means working | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · M Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk10 files, +330/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3let live conversation names outrank a stale first-prompt title (STA-2848)1 PR · Standalone · Plugins#
Problem: let live conversation names outrank a stale first-prompt title (STA-2848).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #11167 [Bug]: Generated tab title is pinned to the tab's first prompt and outranks the live title after /clear (Fixes, OPEN); #15659 Title unavailable (Unclear, Unknown); #15701 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15703 fix(tabs): let live conversation names outrank a stale first-prompt title (STA-2848) | Brennan Benson Core team · MEMBER | #11167 [Bug]: Generated tab title is pinned to the tab's first prompt and outranks the live title after /clear Fixes · OPEN #15659 Title unavailable Unclear · Unknown #15701 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 4 | $\color{#1a7f37}{\Huge{\mathbf | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +383/−50. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3refuse stale same-identity credential overwrites1 PR · Standalone · Plugins#
Problem: refuse stale same-identity credential overwrites.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #13165 Title unavailable (Unclear, Unknown); #9754 Title unavailable (Unclear, Unknown); #9582 Title unavailable (Unclear, Unknown); #12002 Title unavailable (Unclear, Unknown); #6864 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13568 fix(claude-auth): refuse stale same-identity credential overwrites | Brennan Benson Core team · MEMBER | #13165 Title unavailable Unclear · Unknown #9754 Title unavailable Unclear · Unknown #9582 Title unavailable Unclear · Unknown #12002 Title unavailable Unclear · Unknown #6864 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 9 | $\color{#1a7f37}{\Huge{\mathbf | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · L Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +2448/−98. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3stop a stale scan from pruning lineage created mid-scan1 PR · Standalone · Plugins#
Problem: stop a stale scan from pruning lineage created mid-scan.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #16654 [Bug]: A worktree created while a scan is in flight has its lineage pruned as missing (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16656 fix(worktrees): stop a stale scan from pruning lineage created mid-scan | Skyler Shaw Community · FIRST_TIME_CONTRIBUTOR | #16654 [Bug]: A worktree created while a scan is in flight has its lineage pruned as missing Fixes · OPEN | Standalone change | ## Author X: [@skythediver](https://x.com/skythediver) ## In short When several Orca worktrees are created back to back, one of them can silently lose its parent and jump to the top level of the sidebar. The worktree its | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · M Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk6 files, +122/−11. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3stop WSL API-key Codex defaults reading as stale sign-ins1 PR · Standalone · Plugins#
Problem: stop WSL API-key Codex defaults reading as stale sign-ins.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Plugins (stack rank 1).
Relationship: Standalone. Linked issues: #9313 Title unavailable (Unclear, Unknown); #9501 Title unavailable (Unclear, Unknown); #8765 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13254 fix(settings): stop WSL API-key Codex defaults reading as stale sign-ins | dcieslak19973 Community · CONTRIBUTOR | #9313 Title unavailable Unclear · Unknown #9501 Title unavailable Unclear · Unknown #8765 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes the remaining path in #9313 where a valid API-key Codex login is reported as needing re-authentication. The originally reported case — a **host** system default with an API-key `auth.json` — was already | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Unclear · S Open · checks Unknown · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk3 files, +59/−2. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3fix a README typo and drop a stale RC cron note1 PR · Standalone · Automated release pipeline#
Problem: fix a README typo and drop a stale RC cron note.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #14568 [Other]: typo in README + two broken relative links in CONTRIBUTING (Fixes, OPEN); #1362 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14569 docs: fix a README typo and drop a stale RC cron note | Grit Community · FIRST_TIME_CONTRIBUTOR | #14568 [Other]: typo in README + two broken relative links in CONTRIBUTING Fixes · OPEN #1362 Title unavailable Unclear · Unknown | Standalone change | ## ELI5 Two tiny docs fixes: a typo in the `README.md` and a stale sentence in `CONTRIBUTING.md` ## What Changed - Fixed a typo in `README.md` (`sponored` → `sponsored`) - Removed a sentence from `.github/CONTRIBUTING.md | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Unclear · S Open · checks Unknown · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +2/−4. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3make the stale terminal artifact grant assertion deterministic1 PR · Standalone · Automated release pipeline#
Problem: make the stale terminal artifact grant assertion deterministic.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #16002 [Bug]: Flaky test — stale terminal artifact grant is undetectable when the replacement is the same size (Fixes, OPEN).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16004 fix(test): make the stale terminal artifact grant assertion deterministic | gatsby74 Community · CONTRIBUTOR | #16002 [Bug]: Flaky test — stale terminal artifact grant is undetectable when the replacement is the same size Fixes · OPEN | Standalone change | ## Summary `orca-runtime-files-terminal-artifact-io.test.ts > rejects stale absolute terminal artifact previews before returning changed content` fails intermittently — **4 of 6 runs** on a clean tree at `5651662494`, wi | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +6/−1. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3mute stale agent status and disable Stop while disconnected (STA-3333)1 PR · Standalone · Automated release pipeline#
Problem: mute stale agent status and disable Stop while disconnected (STA-3333).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #12373 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12496 fix(mobile): mute stale agent status and disable Stop while disconnected (STA-3333) | Brennan Benson Core team · MEMBER | #12373 Title unavailable Unclear · Unknown | Standalone change | ## Summary When the mobile transport drops, the last agent status is cached and Stop cannot reach the terminal. This PR makes that state honest: - After a continuous 600 ms connection loss, **Agent is working** becomes * | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk18 files, +454/−47. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3preserve host PTY binding over stale renderer replay1 PR · Standalone · Automated release pipeline#
Problem: preserve host PTY binding over stale renderer replay.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #217 Title unavailable (Unclear, Unknown); #16751 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #16795 fix(terminal): preserve host PTY binding over stale renderer replay | Brennan Benson Core team · MEMBER | #217 Title unavailable Unclear · Unknown #16751 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 1 | $\color{#1a7f37}{\Huge{\mathbf | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +242/−3. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3refresh stale capabilities before pairing1 PR · Standalone · Automated release pipeline#
Problem: refresh stale capabilities before pairing.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #11871 [Bug]: Stale Orca Cloud capabilities show signed-in but Relay offline; no in-app re-sign-in path in packaged builds (Fixes, CLOSED); #11714 Title unavailable (Unclear, Unknown); #12129 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12134 fix(relay): refresh stale capabilities before pairing | aaraujoe Community · FIRST_TIME_CONTRIBUTOR | #11871 [Bug]: Stale Orca Cloud capabilities show signed-in but Relay offline; no in-app re-sign-in path in packaged builds Fixes · CLOSED #11714 Title unavailable Unclear · Unknown #12129 Title unavailable Unclear · Unknown | Standalone change | ## Summary - refresh Orca Cloud capabilities before treating cached `relay.use=false` as authoritative - single-flight and rate-limit capability refreshes, with cooldown eviction after 60 seconds - offer a production-acc | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Unclear · M Open · checks Unknown · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +269/−12. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3release an abandoned synchronized-output latch on reveal (~1s stale-pane window)1 PR · Standalone · Automated release pipeline#
Problem: release an abandoned synchronized-output latch on reveal (~1s stale-pane window).
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: #10907 Title unavailable (Unclear, Unknown); #11338 Title unavailable (Unclear, Unknown); #10692 Title unavailable (Unclear, Unknown); #10794 Title unavailable (Unclear, Unknown); #10871 Title unavailable (Unclear, Unknown); #4480 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15021 fix(terminal): release an abandoned synchronized-output latch on reveal (~1s stale-pane window) | Brennan Benson Core team · MEMBER | #10907 Title unavailable Unclear · Unknown #11338 Title unavailable Unclear · Unknown #10692 Title unavailable Unclear · Unknown #10794 Title unavailable Unclear · Unknown #10871 Title unavailable Unclear · Unknown #4480 Title unavailable Unclear · Unknown | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 2 | $\color{#1a7f37}{\Huge{\mathbf | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · M Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk5 files, +272/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3retire superseded dispatch authority2 PRs · Duplicate · Automated release pipeline#
Problem: retire superseded dispatch authority.
Combined impact: Coordinates 2 proposals for the same narrowly inferred outcome.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Duplicate. Linked issues: #11499 [Bug]: Completed orchestration task reverts to ready when a superseded dispatch's terminal exits (Fixes, OPEN); #9001 Title unavailable (Unclear, Unknown); #9832 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Confirm the preferred implementation and supersede redundant work.
Landing/consolidation: Review together. Resolve overlap and conflicts first; land foundations before follow-ups, with CI between merges.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
Cluster review plan
- Review together: Yes.
- Can multiple land: Not until one implementation is chosen.
- Order: smallest required foundation, then follow-ups.
- Conflict risk: Verify in diff review.
- Preferred implementation: choose the most complete, tested, architecture-aligned option.
- Redundancy: Likely.
- Decision first: Only if deep review reveals incompatible direction.
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12024 fix(orchestration): retire superseded dispatch authority | Rod Boev Community · CONTRIBUTOR | #11499 [Bug]: Completed orchestration task reverts to ready when a superseded dispatch's terminal exits Fixes · OPEN #9001 Title unavailable Unclear · Unknown #9832 Title unavailable Unclear · Unknown | Cluster contribution | ## Summary Fixes an orchestration lifecycle race where closing a superseded worker's terminal can reopen a completed task. The exit still settles the dispatch tied to that terminal, but task mutation now requires the dis | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · L Open · checks SUCCESS · review None | Supersede |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk12 files, +1773/−262. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
| #12312 fix(orchestration): keep completed tasks closed when a superseded dispatch's terminal exits | Brennan Benson Core team · MEMBER | #11499 [Bug]: Completed orchestration task reverts to ready when a superseded dispatch's terminal exits Fixes · OPEN | Cluster contribution | ## Summary A completed orchestration task silently flipped back to `ready` when a superseded dispatch's terminal exited (#11499, Linear STA-2978). `OrchestrationDb.failDispatch` applied its task transition unconditionall | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · S Open · checks SUCCESS · review None | Supersede |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk2 files, +137/−13. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3stop a stale scan from pruning freshly recorded lineage1 PR · Standalone · Automated release pipeline#
Problem: stop a stale scan from pruning freshly recorded lineage.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #12631 fix(worktrees): stop a stale scan from pruning freshly recorded lineage | eezy Community · FIRST_TIME_CONTRIBUTOR | None found | Standalone change | ## Summary A newly created child workspace nests correctly under its parent, then jumps to the top level once creation finishes. It reproduced on roughly half of consecutive creates, with no error and no warning in the l | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · M Open · checks SUCCESS · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk13 files, +793/−47. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3update stale E2E test contracts and fake Codex fixtures1 PR · Standalone · Automated release pipeline#
Problem: update stale E2E test contracts and fake Codex fixtures.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Automated release pipeline (stack rank 2).
Relationship: Standalone. Linked issues: None found.
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one latest check rollup is failing. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #15432 test(e2e): update stale E2E test contracts and fake Codex fixtures | Jinjing Core team · MEMBER | None found | Standalone change | <!-- orca-pr-loc --> <!-- Programmatic LoC summary. Do not edit by hand; rewritten on every commit. --> | | Files | Added | Deleted | Net | | :--- | ---: | ---: | ---: | ---: | | Test | 8 | $\color{#1a7f37}{\Huge{\mathbf | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · M Open · checks FAILURE · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: FAILURE. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk8 files, +57/−42. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3stop stale snapshot applies from erasing freshly created terminal tabs1 PR · Standalone · Agent management and search#
Problem: stop stale snapshot applies from erasing freshly created terminal tabs.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14607 Title unavailable (Unclear, Unknown); #14844 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Request changes
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: At least one PR is currently conflicting. Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #13013 fix(remote-workspace): stop stale snapshot applies from erasing freshly created terminal tabs | Robert Nisipeanu Community · FIRST_TIME_CONTRIBUTOR | #14607 Title unavailable Unclear · Unknown #14844 Title unavailable Unclear · Unknown | Standalone change | ## Problem A terminal tab created around a direct-SSH remote-workspace snapshot apply can be permanently lost: 1. `createSessionWriteSubscriber` drops its pending write while an apply suppresses persistence (`pendingChan | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Blocked · L Open · checks Unknown · review None | Request changes |
Evidence, tests, review state, risks, and uncertaintyEvidencePR conversation · Diff · Checks Changed paths: Tests and reviewsLatest check rollup: Unknown. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk45 files, +5181/−226. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||
P3stop titlebar spinner timer when extension ctx turns stale1 PR · Standalone · Agent management and search#
Problem: stop titlebar spinner timer when extension ctx turns stale.
Combined impact: A standalone change with no strong in-scope duplicate detected by linked-issue and title-similarity evidence.
Strategic alignment: Agent management and search (stack rank 3).
Relationship: Standalone. Linked issues: #14658 Title unavailable (Unclear, Unknown).
Related older PRs: None found in the completed deep-review evidence; metadata-only clusters remain unverified.
Recommended approach: Consider closing
Landing/consolidation: Review independently; no in-scope dependency detected.
Risks/dependencies: Execution-host, folder-workspace, mixed-version, Git-provider, and cross-platform boundaries require targeted review when relevant.
Confidence: Medium
| PR | Author / source | Linked issues | Role in cluster | What it does | Priority and rationale | Readiness / size | Recommendation |
|---|---|---|---|---|---|---|---|
| #14664 fix(pi): stop titlebar spinner timer when extension ctx turns stale | susemi Community · FIRST_TIME_CONTRIBUTOR | #14658 Title unavailable Unclear · Unknown | Standalone change | ## Summary Fixes the pi process crash caused by the `orca-titlebar-spinner` extension when a session reload happens while the 80ms titlebar animation timer is running. See #14658. ## Root cause The extension's `startAnim | P3 Low-value, stale, or potentially superseded signal; validate before further investment. | Minor changes needed · S Open · checks SUCCESS · review None | Consider closing |
Evidence, tests, review state, risks, and uncertaintyTests and reviewsLatest check rollup: SUCCESS. Review decision: None. Unresolved changes-requested reviews observed: 0. Architecture and risk1 files, +10/−0. Local, folder-workspace, SSH/remote, mixed-version, and cross-platform implications require reviewer confirmation where touched paths cross those boundaries. ConfidenceMedium — description and recent discussion metadata were available, but full unresolved-thread state still requires GitHub review. | |||||||