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
What's the proper way to pass current working directory to the global opencode.json config? #3395
Is this correct way to reference the current location I opened opencode from?
Didn't work for filesystem mcp, and not sure if I should use $(PWD) or some other type of approach. The docs don't mention how to use this.
I think it worked with ".", but it worked through a few errors initially so can't tell if that's opencode fixing the calls since initially it started with /tmp/ as the path it was examining, then /usr/local/go/src/fmt/print.go for some reason, then finally listed document symbols in the actual project.
Partial match with mcp command and relative path, but this is just more focused on how do I use my global config in a local repo properly with a path not hard coded but just where I am working. Not sure if that consistents the same scope as the other.
Activity
github-actions commentedon Oct 23, 2025
This issue might be a duplicate or related to existing issues. Please check:
Feel free to ignore if none of these address your specific case about passing the current working directory to opencode.json.
sheldonhull commentedon Oct 23, 2025
Partial match with mcp command and relative path, but this is just more focused on how do I use my global config in a local repo properly with a path not hard coded but just where I am working. Not sure if that consistents the same scope as the other.
rekram1-node commentedon Oct 23, 2025
Custom lsp servers will spawn in the cwd of wherever you are running opencode