Repository navigation
Lock session to current directory #841
Description
I started a session in ~/.config/tmux to update some tmux config and was surprised to find that opencode started scanning my home directory for a .tmux.conf file and then created one there when it couldn't find one.
I think the expectation here is that opencode should not read or write above the directory where the session is started.
Metadata
Metadata
Assignees
Labels
No labels
Activity
rekram1-node commentedon Aug 14, 2025
This is default behavior now, opencode is locked to current dir, tools with throw if it tries to go outside. Tho it can always get smart writing scripts to get around if it wants
AndrewBakerATL commentedon Aug 23, 2025
Is this the only operating form now, or is there a way to toggle it back to allow it to interact with other directories?
rekram1-node commentedon Aug 23, 2025
soon support will be added to either disable the lock or add other dirs, not sure when or exact ux but I know the team has talked about it internally
AndrewBakerATL commentedon Aug 23, 2025
In the meantime then, is the only option to restore the functionality downgrading? To which, what release was it that included the change. I went to the tagged releases, but didn't see mention of the change. Checked until ~ v0.5.1
rekram1-node commentedon Aug 23, 2025
tbh I am not sure I think that change was quite a while ago :/
fix(app): keep app and worker opens on new session screen (anomalyco#841