Repository navigation
TUI /sessions only show sessions from last 30 days, while CLI session list shows all my sessions (thank god) #16733
Closed as not planned
Description
Description
What breaks:
The TUI /sessions picker only shows recent sessions and makes it look like older sessions are gone.
What still works:
opencode session list shows the full session history, and the CLI docs say session list should "List all OpenCode sessions."
Why this is concerning
The mismatch between TUI and CLI creates a false data-loss scare and blocks work.
Expected behavior:
- TUI
/sessionsshould show the same session history that the CLI can list. - My entire session to stay unless I decide to prune them
Actual behavior:
TUI only shows recent sessions, while CLI can still see the old sessions
Official docs reference:
OPENCODE_DISABLE_PRUNE is documented as Disable pruning of old data, so users may assume old sessions are protected; the UI should not suggest they vanished when they still exist.
Related issue:
#13877: the existing report says the /sessions picker "only shows a small set of recent sessions."
Help me confirm the accuracy of this:
- Setting
OPENCODE_DISABLE_PRUNE=truefor future protection of my sessions, because that is the only official deletion-related control I could verify - Keep using
opencode session listplus opencode session resume<session_id>until the TUI bug is fixed, because the CLI docs explicitly support listing all sessions and resuming by session ID.
Related issues
- Please review pull requests before approving them, as they damage things that are already working correctly. You're behaving like little children, approving things just because they have a good title. #16718
- TUI /sessions picker only shows recent sessions #13877
Plugins
@ramarivera/opencode-model-announcer
OpenCode version
1.2.22
Steps to reproduce
- Update to 1.2.22
- Open TUI (
opencode) - Write
/sessions - Scroll all the way down only to see that sessions over 30 days are hidden
- Exit TUI
- Run
opencode list sessionsand thank the gods that older sessions are still listed there
Screenshot and/or share link
No response
Operating System
Windows 10
Terminal
Windows Terminal
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Mar 9, 2026
This issue might be a duplicate of existing issues. Please check:
/sessionspicker only shows recent sessions, older sessions still accessible via DBstartfilter in TUI bootstrap combined with child session dilution causes root sessions to be hidden in the pickerBoth issues describe the same behavior you're experiencing. Consider adding your findings as comments there instead.
bobcodev commentedon Mar 29, 2026
Version 1.3+ the problem persists :(
fix(tui): use roots filter instead of time-based filter for session list
fix(tui): use roots filter instead of time-based filter for session list
jchuder commentedon Apr 16, 2026
v1.4.6 same here.
Not sure whether the hardcoded 30 day cutoff was introduced as a defensive measure for memory/startup costs, especially given the memory discussion in #20695. But after looking at the current behavior, I think session discovery and session content loading should be separate to 2 problems.
My suggestion:
id,title,updatedAt, and maybe workspace/status info. That is much cheaper than full message history, diffs, or snapshots...etc, so session discovery should be solved separately from heavy session hydration.This seems aligned with the follow up direction discussed in #17046 and #13877 as well, where count-based limits and pagination / load more were already suggested as better UX than a hard time window.
mr-yifeiwang commentedon Apr 28, 2026
The problem still exists in
v1.4.10.The mismatch between sessions shown in the TUI and CLI is somewhat confusing. If the two interfaces are meant to reflect the same session state, it will make sense for them to stay consistent: when a session is deleted in the TUI, it shall no longer appear in
opencode session list; and likewise a session deleted via CLI shall no longer appear in the TUI.If the current mismatch is intentional, clearer documentation around that behaviour may help. In that case, a bulk cleanup command such as
opencode session clearcan also be useful, so users will not need to delete sessions one by one.Thanks for looking into this.
EdgarSedov commentedon May 30, 2026
Still affected by this. #26432 looks like the most focused active fix for the 30-day picker cutoff / hidden older sessions issue.
Necmttn commentedon Jun 21, 2026
The TUI should distinguish filtered from missing.
A low-risk fix is to show the active window (
last 30 days), total indexed sessions if known, and an explicitload older/ search-all path. If a session is actually pruned or deleted, that should be a different state fromhidden by current filter.That avoids the false data-loss signal while still letting the TUI keep initial load bounded.
Generated with ax.
github-actions commentedon Aug 21, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.