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
tui: /sessions no longer prioritizes sessions from the current cwd #38326
The /sessions command no longer prioritizes sessions associated with the current working directory. Instead, sessions from all folders are shown without cwd-based prioritization, making it harder to find the sessions relevant to the active project.
Environment
opencode version: opencode2 v0.0.0-next-15853
OS: Linux omarchy 7.1.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat 18 Jul 2026 17:30:57 +0000 x86_64
Terminal: TERM=xterm-256color, COLORTERM=truecolor; terminal program unavailable
Shell: /usr/bin/bash
Install/channel: next
Active plugins: .opencode/plugins/graphify.js, /home/kkosu/.opencode/plugins/graphify.js
Reproduction
Open OpenCode from a working directory that has existing sessions.
Invoke /sessions.
Observe the ordering of the listed sessions.
Expected Behavior
Sessions associated with the current working directory should be prioritized, as they were previously. Sessions from other folders may still be listed after the current cwd sessions.
Actual Behavior
Sessions from all folders are shown without prioritizing sessions from the current working directory.
Additional Context
This appears to be consistently reproducible. No workaround or related recent change has been identified.
If your report describes a distinct regression (cwd-based prioritization was working and broke recently, rather than never working), it may be a new occurrence worth keeping open. Please confirm whether this started with a specific version.
Activity
github-actions commentedon Jul 22, 2026
This issue might be a duplicate of existing issues. Please check:
If your report describes a distinct regression (cwd-based prioritization was working and broke recently, rather than never working), it may be a new occurrence worth keeping open. Please confirm whether this started with a specific version.
Kristijan-K commentedon Jul 22, 2026
github-actions commentedon Sep 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.