You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature: UI to close/dismiss Done agents + bulk cleanup (sidebar has no close affordance) #10718
When agents finish, the sidebar shows them as Done (green check) but provides no visible close / dismiss / delete control. On remote Mac mini hosts this leaves many live PTYs + agent processes (e.g. dozens of idle grok processes), which burns RAM/swap and makes the machine feel slow.
CLI can clean this (orca terminal close, orca terminal stop), but that is not discoverable from the UI and is awkward as daily hygiene.
Environment
Orca desktop 1.4.155 (com.stablyai.orca)
Host: Mac mini (16 GB), agents often driven remotely from another machine
Agents: Grok / Claude / etc. as Orca-managed terminals
Observed behavior
Sidebar under a project/worktree shows N agents, many labeled Done - Grok (green ✓).
Hover / focus on a Done agent row does not expose Close, Dismiss, or Remove.
Status lights communicate “done” but not how to reclaim resources.
Finished agents remain connected terminals; OS still has agent CLI processes (often --resume idle).
Remote workflow amplifies this: sessions pile up across days without a “clean finished agents” path in UI.
Measured example before cleanup (same host):
Metric
Value
orca terminal list
44 connected
grok processes
~75
RAM
16 GB with compressor pressure + swapouts
After CLI cleanup of zombie agent tabs (keep active shells): terminals 6, grok processes ~9.
Expected
Per-agent close in the sidebar (X / context menu: Close tab, Kill agent).
Bulk actions on a worktree or project:
Close all Done agents
Close all idle agent tabs older than N hours
Keep active / non-Done
Optional warning badge when finished-but-still-connected agent count exceeds a threshold (e.g. >5) with one-click “Clean Done agents”.
Keyboard shortcut for “Close current agent tab” and “Close all Done in this worktree”.
Why it matters
ADE is built for fleets of agents; without lifecycle UI, fleets become memory leaks.
Remote mini / VPS users hit this first (16–32 GB boxes, many short sessions).
Status “Done” currently looks like a completed task, not a resource still held.
Workarounds today
# list
orca terminal list --json
# close one tab
orca terminal close --terminal term_xxx # often works better than --tab alone
orca terminal close --terminal term_xxx --tab
# stop all terminals on a worktree (destructive to active ones too)
orca terminal stop --worktree path:/path/to/wt
These are fine for agents/power users, not for the default UI loop.
Related product note
orca terminal close --tab sometimes returns terminal_tab_not_found while the handle still appears in terminal list; plain orca terminal close --terminal <handle> succeeds. Worth aligning list/close lifecycle too.
Request
Treat agent process lifecycle as a first-class UI surface: Done should either free resources or clearly offer “Close & free”. Happy to test builds on macOS arm64 remote host setups.
Live PTYs — visible in orca terminal list --json. Closing with orca terminal close --terminal <handle> frees processes/RAM.
Sidebar inline-agents history — worktree card shows N agents / Done - Grok with relative times even when no matching live terminal remains. After closing live tabs, the Done rows still show (green checks, no close affordance). CLI has no API to clear this history.
So “cleanup” via CLI can free resources while the UI still looks crowded. That makes the missing UI close control worse: users think agents are still running when they’re already ghosts.
Related close CLI quirk
orca terminal close --terminal X --tab often returns terminal_tab_not_found while the handle still appears in terminal list. Plain orca terminal close --terminal X succeeds more reliably.
Request add-ons
Clear / dismiss Done agent history on a worktree card (not only live tabs)
Distinguish live vs history in the sidebar (or auto-prune history when PTY is gone)
Emit terminal_closed (or equivalent) from PTY layer
Worktree / inline-agents subscriber filters history on that event
Related CLI quirk (same area)
orca terminal close --terminal X --tab often returns terminal_tab_not_found while the handle still appears in terminal list. Plain close without --tab is more reliable.
Out of scope / not Orca’s bug
Aggressive third-party hygiene scripts that close mid-conversation agent tabs are operator error; session files remain resumable. That does not excuse missing lifecycle sync or dismiss UI.
Confidence
~85. Would revise downward if Done rows are intentionally append-only audit history with documented TTL, or if a hidden dismiss gesture already exists.
Source: live remote mini repro (Orca 1.4.155) + independent Kimi review on the same write-up.
Confirmed on Orca 1.4.177 with a Codex automation targeting an existing worktree (reuseSession: true).
Each successful automation run:
completes normally,
leaves no live terminal,
adds one more non-dismissible Done - Codex row to the worktree card.
After two runs, the card shows 2 agents, although orca terminal list reports no live terminals. Tapping the completed rows does not open anything. The count continues growing by one after every run.
Expected: completed runs may remain in Automation Run History, but ghost inline-agent rows should be automatically pruned or offer per-row/bulk dismissal or a retention TTL.
Activity
howardpen9 commentedon Jul 26, 2026
The screenshot from my laptop; I can't closed them on UI level. Which is annoying.
howardpen9 commentedon Jul 26, 2026
Follow-up from real host (same remote mini)
Two layers of “Done agents”
orca terminal list --json. Closing withorca terminal close --terminal <handle>frees processes/RAM.N agents/Done - Grokwith relative times even when no matching live terminal remains. After closing live tabs, the Done rows still show (green checks, no close affordance). CLI has no API to clear this history.So “cleanup” via CLI can free resources while the UI still looks crowded. That makes the missing UI close control worse: users think agents are still running when they’re already ghosts.
Related close CLI quirk
orca terminal close --terminal X --taboften returnsterminal_tab_not_foundwhile the handle still appears interminal list. Plainorca terminal close --terminal Xsucceeds more reliably.Request add-ons
howardpen9 commentedon Jul 26, 2026
Independent review (Kimi K3) — classification
Cross-check by Kimi (Moonshot CLI, model k3) on the same host evidence. Summary for triage:
Verdict: both (bug + missing feature)
inline-agents/ history not synced to terminal lifecycleSeverity: P2
Not P0/P1: no crash, no data loss; sessions often still resumable (
grok --resume).Still P2 because:
Two-layer model (confirmed useful for fix design)
orca terminal closeorca terminal listRoot issue for ghosts: Layer A close does not update Layer B.
Suggested ship (minimum)
UX
CLI (illustrative)
Internal
terminal_closed(or equivalent) from PTY layerRelated CLI quirk (same area)
orca terminal close --terminal X --taboften returnsterminal_tab_not_foundwhile the handle still appears interminal list. Plainclosewithout--tabis more reliable.Out of scope / not Orca’s bug
Aggressive third-party hygiene scripts that close mid-conversation agent tabs are operator error; session files remain resumable. That does not excuse missing lifecycle sync or dismiss UI.
Confidence
~85. Would revise downward if Done rows are intentionally append-only audit history with documented TTL, or if a hidden dismiss gesture already exists.
Source: live remote mini repro (Orca 1.4.155) + independent Kimi review on the same write-up.
nwparker commentedon Aug 3, 2026
Saw you closed this -- did you want this open @howardpen9 ?
creatorKoo commentedon Aug 9, 2026
Automation-specific repro
Confirmed on Orca 1.4.177 with a Codex automation targeting an existing worktree (
reuseSession: true).Each successful automation run:
Done - Codexrow to the worktree card.After two runs, the card shows
2 agents, althoughorca terminal listreports no live terminals. Tapping the completed rows does not open anything. The count continues growing by one after every run.Expected: completed runs may remain in Automation Run History, but ghost inline-agent rows should be automatically pruned or offer per-row/bulk dismissal or a retention TTL.