sst
[Feature Request] Adding directories / creating workspaces
One of the features I utilize frequently in Claude Code is adding additional directories to a session that are outside the scope of my working directory. Are there currently plans to implement such a feature or to create a workspace similar to VS code?
I work always on workspace with several java modules (independant pom.xml and git repository for each) and i manage to open opencode from the main directory and in its AGENTS.md I gave instructions about my workspace structure and to always do "cd [module_dir]" before any bash commande. It manages to do it but sometimes it forgets or target the wrong module. Since v0.3.108 it does not work anymore because of new constraints in bash tool code (exact_path) so i will stay on v0.3.107 until it's resolve or this feature request is implemented; Loving Opencode by the way ;)
please add this, it's pretty important feature, and one of the few things that have me going back to claude code.
+1 Current check for when a command references paths outside the project directory is great. But very annoying if we can't add extra directories.
For me too this is the main thing that keeps me going back to Claude Code.
The 0.5 -> 0.6 version bump for opencode built in functionality ro allow for this among other things
NOT currently available through tui but should be easy to add now
Sorry for bringing this up again - I don't mean to spam the issue, but I wanted to emphasize how much this missing feature impacts daily workflow.
Currently, I have to rely on symlinks to get access to other / related projects.
You can use bash to bypass it (not everything works tho, well, excess security motivated to use it even less securely xD
Please implement this as it's been a nightmare me trying to work with this issue over the last few days, even going as far as having it read images, it can't do that now
@JoshuaRileyDev reading images should work, what model + provider are you using?
Also we will add this soon, we are currently rewriting tui and shipping it this week, but this is one of the features that we want + need so I hope we can add it shortly after.
I think the main question was what does the UX look like to add another dir, because the way claude code does it is kinda meh, I think codex does it by just requiring permission which is decent but it doesnt add a dir in the sense that you can use "@" to get files from that other dir, etc
I guess if anyone has opinions or ideas on ux feel free to drop them
@rekram1-node What do you think about going the claude code way, but allowing to travel the directory path with the keyboard arrows? If we are talking about TUI
I mean, Claude Code gives you not very optimal path to include in auto-accept rule. By allowing to travel the path (i mean its depth), you can configure if you want broader rule. F.e.:
Agent proposal:
/home/user/apps/app1/logs
Aflter pressing left arrow on keyboard, it changes to:
/home/user/apps/app1 pressing againg changes to /home/user/apps/, etc
Then you can accept this new rule and continue to use the agent
╭───────────────────────────────────────────────────────────────────────────────
│ Bash command
│
│ rm -rf /home/user/.prompts
│ Remove .prompts directory
│
│ Do you want to proceed?
│ 1. Yes
│ ❯ 2. Yes, and don't ask again for rm commands in /home/user <--- **Talking about this path**
│ 3. No, and tell Claude what to do differently (esc)
╰───────────────────────────────────────────────────────────────────────────────
Gemini and Qwen cli both support multiple directories. If opencode works from a single root directory only, that is so sad
hi @thdxr & @rekram1-node Could you share the estimated completion time for this feature?
