Sort & filter chat sessions in the companion app by recency, isIdle, isCompleted

[karkarl]

Summary

Add sorting and filtering to the chat session list in the Windows companion app.

Details

Users should be able to:

• Sort the session list by most-recent activity (recency).
• Filter by session state: isIdle, isCompleted.

Acceptance criteria

• Session list can be sorted by recency.
• Session list can be filtered by idle and completed state.

Related

• Tray UI: completed ACP/subagent sessions clutter session list — need archive/hide support #881 (completed ACP/subagent sessions clutter the list — hide/archive support).

Context

Surfaced during chat-session review (2026-07-08).

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 9, 2026, 2:37 PM ET / 18:37 UTC.

Summary
Keep this issue open: current main already orders sessions by recent activity and has a completed-session visibility toggle, but it does not expose an idle-session filter or a general idle/completed filter model.

Reproducibility: not applicable. as a bug reproduction: this is a feature request. Source inspection confirms the current Sessions page lacks an idle filter while already having recency ordering and completed-session visibility behavior.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.
• Include redacted logs or terminal output.

Next step
Needs maintainer UX/product confirmation because current main already has default completed-session hiding, while idle filtering and final completed-filter semantics remain undefined.

Maintainer decision needed

• Question: Should the companion app add an explicit idle/completed filter control on top of the current Show completed toggle, or should the remaining behavior stay under the broader completed-session clutter work in Tray UI: completed ACP/subagent sessions clutter session list — need archive/hide support #881?
• Rationale: Current main already made one UX choice by hiding clean completed sessions by default; adding idle filtering changes the visible session model and needs a maintainer-approved state vocabulary and control design.
• Likely owner: TurboTheTurtle — This person most recently implemented and tested the completed-session visibility behavior that this issue would extend.
• Options:
  • Add scoped session-state filters (recommended): Define idle/completed filter semantics against SessionInfo.Status, then add focused UI and tests on the Sessions page.
  • Fold into the clutter issue: Treat this as part of Tray UI: completed ACP/subagent sessions clutter session list — need archive/hide support #881 so archive, hide, and filtering behavior are designed together.
  • Keep current behavior: Retain recency sorting plus Show completed only, and close or narrow this request if idle filtering is not desired.

Review details

Best possible solution:

Extend the existing Sessions page visibility model only after deciding how idle and completed states should map onto gateway session status, preserving current recency ordering and the completed-session work from #924.

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

Not applicable as a bug reproduction: this is a feature request. Source inspection confirms the current Sessions page lacks an idle filter while already having recency ordering and completed-session visibility behavior.

Is this the best way to solve the issue?

Unclear until maintainers choose the UX semantics. The narrow maintainable path would extend SessionVisibilityFilter and the Sessions page controls instead of adding a competing filter path.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The issue uses isIdle/isCompleted wording while the Windows model currently exposes status strings and a completed-only visibility toggle, so maintainers need to choose the filter semantics before implementation.

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

Label changes

Label changes:

• add P3: The remaining work is a low-risk Sessions page ergonomics enhancement because current main already sorts by recency and hides completed sessions by default.
• add impact:ux-friction: The request targets avoidable friction when scanning or narrowing a growing chat session list.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: 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:

• P3: The remaining work is a low-risk Sessions page ergonomics enhancement because current main already sorts by recency and hides completed sessions by default.
• impact:ux-friction: The request targets avoidable friction when scanning or narrowing a growing chat session list.

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 current-head Sessions page visible proof if tray UI behavior changes.

What I checked:

• Current recency ordering: SessionsPage builds the visible list with OrderByDescending(s => s.UpdatedAt ?? s.LastSeen), so the recency-sorting portion is already present on current main. (src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs:173, c8cd9869d828)
• Current completed-session filter: SessionsPage applies SessionVisibilityFilter.VisibleSessions(filtered, ShowCompletedSessions) and the helper only treats done/completed statuses as clean completed sessions. (src/OpenClaw.Tray.WinUI/Services/SessionVisibilityFilter.cs:7, c8cd9869d828)
• No idle filter in current UI: The Sessions page toolbar exposes channel tabs, a Show completed toggle, and refresh, but no idle filter control. (src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml:30, c8cd9869d828)
• Completed-filter tests are narrow: The focused tests cover hiding clean completed sessions and showing all sessions when the toggle is on, but they do not cover idle filtering. (tests/OpenClaw.Tray.Tests/SessionVisibilityFilterTests.cs:48, c8cd9869d828)
• Feature-history provenance: Blame shows recency ordering came from 4166e0f and the completed visibility helper/tests came from b37b1be. (src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs:165, b37b1bef0a0c)
• Related merged PR scope: Merged pull request Hide completed sessions by default #924 says it addressed only the tray UI portion of Tray UI: completed ACP/subagent sessions clutter session list — need archive/hide support #881 with a Show completed toggle, leaving related behavior as follow-up work. (b37b1bef0a0c)

Likely related people:

• shanselman: The recency ordering and base SessionsPage filter structure trace to commit 4166e0f, authored by Scott Hanselman. (role: introduced behavior; confidence: medium; commits: 4166e0fd63f8; files: src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs, src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml)
• TurboTheTurtle: Merged pull request Hide completed sessions by default #924 and blame show Andy Ye added the current completed-session visibility helper, persisted toggle, and tests. (role: recent area contributor; confidence: high; commits: b37b1bef0a0c; files: src/OpenClaw.Tray.WinUI/Services/SessionVisibilityFilter.cs, src/OpenClaw.Tray.WinUI/Pages/SessionsPage.xaml.cs, tests/OpenClaw.Tray.Tests/SessionVisibilityFilterTests.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.

[karkarl]

Closing as a duplicate of #881.