Tray UI: completed ACP/subagent sessions clutter session list — need archive/hide support

[shanselman]

Summary

The Windows tray app (and likely other UI surfaces) shows a growing list of completed ACP/copilot sessions and native subagents with no way to hide or dismiss them. This makes the session list cluttered and hard to navigate.

Current behavior

• Every sessions_spawn call (ACP codex/copilot sessions, native subagents) adds an entry to the session list in the tray UI
• Completed sessions remain visible indefinitely in the UI
• With frequent cron jobs or coding agent usage, the list quickly grows to dozens of entries with names like "copilot", "subagent", etc.

Expected behavior

• Completed/done sessions should be hidden from the tray UI session list (or collapsible/filterable)
• Ideally, a "hide completed sessions" toggle in the tray UI
• ACP sessions should respect agents.defaults.subagents.archiveAfterMinutes the same way native subagents do (or have an equivalent acp.archiveAfterMinutes setting)

Config context

agents.defaults.subagents.archiveAfterMinutes is set to 60 — this helps with native subagents but ACP sessions don't appear to be affected by it.

Suggested fixes

1. Tray UI: Add a toggle or filter to hide status: done sessions from the session list
2. ACP sessions: Apply archiveAfterMinutes (or equivalent) to ACP session lifecycle so they drop off the list after completion
3. Config knob: A sessions.uiShowCompleted: false or similar setting that controls visibility across all UI surfaces

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 28, 2026, 3:49 AM ET / 07:49 UTC.

Summary
Keep open. Current main still renders any non-cron session returned by sessions.list and has no completed/done hide toggle or archive setting; no canonical issue or PR supersedes this work, and the ACP lifecycle/config pieces need maintainer direction.

Reproducibility: yes. for the UI half from source: a SessionInfo with Status set to done that survives sessions.list enters _allSessions and ApplyFilter renders it. No live gateway/ACP runtime reproduction was run in this read-only review.

Next step
The remaining work is real but needs a maintainer choice between tray-only visibility, ACP lifecycle semantics, and a new persisted config surface before implementation.

Review details

Best possible solution:

Choose a narrow completed-session visibility policy for the tray first, then separately decide whether ACP lifecycle should honor an archive setting or expose a distinct config knob.

Do we have a high-confidence way to reproduce the issue?

Yes for the UI half from source: a SessionInfo with Status set to done that survives sessions.list enters _allSessions and ApplyFilter renders it. No live gateway/ACP runtime reproduction was run in this read-only review.

Is this the best way to solve the issue?

Unclear: a tray-only hide-completed toggle is the narrowest local repair, while ACP archive semantics and a global config knob need maintainer product/API direction.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Changing ACP archiveAfterMinutes behavior may belong partly to gateway/ACP lifecycle outside this tray repository, while a tray-only filter is local but narrower.
• Hiding completed sessions by default could make completed transcripts harder to find unless maintainers choose a discoverable toggle, archive view, or clear default policy.

Codex review notes: model internal, reasoning high; reviewed against d08a3e749973.

Label changes

Label changes:

• add impact:other: The concrete impact is session-list clutter and navigation friction, which is maintainer-visible but outside the specific owned impact labels.
• add issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.
• add clawsweeper:source-repro: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P2: The issue describes a normal-priority tray usability problem with limited blast radius and no evidence of data loss or core runtime failure.
• impact:other: The concrete impact is session-list clutter and navigation friction, which is maintainer-visible but outside the specific owned impact labels.

Evidence reviewed

Acceptance criteria:

• ./build.ps1
• dotnet test ./tests/OpenClaw.Shared.Tests/OpenClaw.Shared.Tests.csproj --no-restore
• dotnet test ./tests/OpenClaw.Tray.Tests/OpenClaw.Tray.Tests.csproj --no-restore
• Collect visible tray proof showing completed sessions hidden or toggled according to the chosen policy.

What I checked:

• Repository policy read: AGENTS.md was read fully; its tray UX validation and visible-proof guidance applies to any future fix, while this review remained read-only. (AGENTS.md:48, d08a3e749973)
• Current tray filtering: UpdateSessions drops only cron-spawned sessions before saving _allSessions; there is no completed/done status filter here. (src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs:97, d08a3e749973)
• Current tray render path: ApplyFilter starts from _allSessions, optionally filters by channel, orders by update time, and renders every remaining row. (src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs:152, d08a3e749973)
• No UI control for completed visibility: The Sessions page exposes channel tabs and refresh controls, but no hide-completed/archive visibility toggle. (src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml:22, d08a3e749973)
• Session status is parsed but not used for hiding: SessionInfo.Status exists and OpenClawGatewayClient.PopulateSessionFromObject fills it from the gateway response, so a completed-status UI policy is feasible but absent. (src/OpenClaw.Shared/OpenClawGatewayClient.cs:3450, d08a3e749973)
• No config/archive knob found: Repository search found no archiveAfterMinutes, uiShowCompleted, hide-completed, or completed-session setting in current source, tests, or docs. (d08a3e749973)

Likely related people:

• bkudiess: Recent commit 989f9ff added safe session lifecycle actions and checkpoint controls in the Sessions page immediately before this report. (role: recent area contributor; confidence: medium; commits: 989f9ffde2dd; files: src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs, src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml)
• QQSHI13: Recent commit 6283fb1 worked on chat session routing from session rows and toasts, adjacent to session identity/navigation behavior. (role: adjacent session routing contributor; confidence: medium; commits: 6283fb174ead; files: src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs, src/OpenClaw.Tray.WinUI/Pages/ChatPage.xaml.cs)
• Copilot: Git blame shows the current SessionsPage filter, GatewayService session forwarding, and session parser trace to 58e363d; the routing signal is weaker because the commit title covered broader UI fallback work. (role: historical provenance; confidence: low; commits: 58e363d993f2; files: src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs, src/OpenClaw.Tray.WinUI/Services/GatewayService.cs, src/OpenClaw.Shared/OpenClawGatewayClient.cs)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[llongley]

I'm getting ramped up on the project and would like to pick this one up as a first issue, so I'm dropping a comment to signal I'm looking at it. I'd have self-assigned to make that clearer, but it looks like I don't have permissions on the repo yet - happy for a maintainer to assign me if that's the norm here.

Before I start I want to make sure I build the right thing. The issue lists three fixes - a tray toggle to hide completed sessions, ACP sessions honoring archiveAfterMinutes, and a global sessions.uiShowCompleted config knob. I'd like to start with just the first one: a "hide completed sessions" toggle on the tray Sessions page that filters the already-loaded session list. The ACP lifecycle piece and the cross-surface config knob feel like separate changes, so my instinct is to land the tray filter first and treat those two as follow-ups. Does that split make sense, or would you rather see them bundled?

A few things I'd want your read on before I start:

1. Should completed sessions be hidden by default (with the toggle to bring them back), or shown by default (with the toggle to hide them)? I'm leaning hidden-by-default, since that's the clutter the issue is about, but it's your call.
2. Should the toggle persist across restarts? I'm assuming yes - a visibility preference that resets every launch would feel broken - but wanted to confirm.
3. Which statuses count as "completed"? I had a look at the gateway repo, and a session's run status is one of running | done | failed | killed | timeout (session-utils.types.ts), where terminal means everything except running. My instinct is to hide only clean done and keep failed/killed/timeout visible, since a run that failed or got killed is probably the one you want to notice. Happy to hide all four terminal statuses instead if you'd rather "completed" mean "any finished run".
4. That same gateway row carries abortedLastRun separately from status, so my plan is to keep any session with that flag set visible even when its status would otherwise hide it. Shout if you'd rather done always win.

Thanks!

[shanselman]

@llongley no one really has permissions, so just send PRs. Your comment was 5D ago, and now there's a PR from another, can you take a look at that and validate?