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
/sessions should 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=true for future protection of my sessions, because that is the only official deletion-related control I could verify
- Keep using
opencode session list plus 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
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 sessions and thank the gods that older sessions are still listed there
Screenshot and/or share link
No response
Operating System
Windows 10
Terminal
Windows Terminal
Description
What breaks:
The TUI
/sessionspicker only shows recent sessions and makes it look like older sessions are gone.What still works:
opencode session listshows 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:
/sessionsshould show the same session history that the CLI can list.Actual behavior:
TUI only shows recent sessions, while CLI can still see the old sessions
Official docs reference:
OPENCODE_DISABLE_PRUNEis 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:
OPENCODE_DISABLE_PRUNE=truefor future protection of my sessions, because that is the only official deletion-related control I could verifyopencode 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
Plugins
@ramarivera/opencode-model-announcer
OpenCode version
1.2.22
Steps to reproduce
opencode)/sessionsopencode list sessionsand thank the gods that older sessions are still listed thereScreenshot and/or share link
No response
Operating System
Windows 10
Terminal
Windows Terminal