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: directory indicator stays stale after /move in a new session #43938
After using /move in a newly created session to select an existing worktree, the directory indicator continues to show the base directory. It does not update until activity starts in the moved session.
Expected: the directory indicator updates immediately after /move changes the session's worktree.
Actual: there is no visible indication that the directory changed, and the base directory remains displayed.
Plugins
Local notifier.js plugin.
OpenCode version
1.18.18, installed via mise release channel.
Steps to reproduce
Create a new session with /new.
Use /move and select an existing worktree.
Observe that the directory indicator still shows the base directory.
Screenshot and/or share link
Not provided.
Operating System
Arch Linux, kernel 7.1.8-arch1-3, x86_64.
Terminal
Terminal application unavailable from the environment. TERM=xterm-256color, COLORTERM=truecolor.
Submitted PR #49560 to resolve this for active sessions on the current dev branch architecture by updating useDirectory() in packages/tui/src/context/directory.ts to inspect the active session's directory (session?.directory) as soon as SessionEvent.Moved is projected.
Activity
timrichardson commentedon Aug 25, 2026
this is present in v2 as well
timrichardson commentedon Aug 25, 2026
Fix proposed in #44829.
mavasbel commentedon Sep 19, 2026
Hi @kommander, @timrichardson — thank you @timrichardson for the earlier investigation and proposal in #44829!
Submitted PR #49560 to resolve this for active sessions on the current
devbranch architecture by updatinguseDirectory()inpackages/tui/src/context/directory.tsto inspect the active session's directory (session?.directory) as soon asSessionEvent.Movedis projected.thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊