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
Feature request: ability to disable "File X is not in the current working directory" error #3218
I work in a monorepo and docs and dependencies code are often located outside the current working directory. This error effectively prevents me from accessing them, undermining opencode capabilities. I want a config option to disable this behaviour
@rekram1-node I was trying to tackle this issue, but things started to get complicated with handling different paths separately. Do you mind if I add configuration option for those living on the edge and maybe in the future on could refine it to handle separate paths for more control?
@Mishkun I don't think we want to add it like that, because every single tool would require manual editing of the config.json and that would be painful for user.
It does this (in pr) #3752 ! (and includes always-allow option). the config here is to override this behaviour to yolo mode globaly or per project for those living on the edge (like me), or grumpy defensive "deny"
Activity
rekram1-node commentedon Oct 16, 2025
Yeah we are going to fix this soon we have ran into it ourselves quite a bit as well
JoshuaRileyDev commentedon Oct 20, 2025
Literally just had this for the last couple of days and it's been driving me insane, so good that it's getting fixed.
feat: add pattern-based external file access permission
Mishkun commentedon Nov 1, 2025
@rekram1-node I was trying to tackle this issue, but things started to get complicated with handling different paths separately. Do you mind if I add configuration option for those living on the edge and maybe in the future on could refine it to handle separate paths for more control?
permissions : {
read : {
enabled: ask | deny | allow
external_files: ask | deny | allow
}
}
rekram1-node commentedon Nov 2, 2025
@Mishkun I don't think we want to add it like that, because every single tool would require manual editing of the config.json and that would be painful for user.
I think we will either:
Mishkun commentedon Nov 2, 2025
@rekram1-node
It does this (in pr) #3752 ! (and includes always-allow option). the config here is to override this behaviour to yolo mode globaly or per project for those living on the edge (like me), or grumpy defensive "deny"
feat: add simplified permission system for external file access (anom…
Mishkun commentedon Nov 6, 2025
I guess it was fixed in v1.0.29
@thdxr is that so?
rekram1-node commentedon Nov 6, 2025
Oh yeah that is the case
rekram1-node commentedon Nov 6, 2025
We are gonna have a better UX for it later but rn this was the simple option.
Dax has some plans to overhaul permissions altogether so once that is done we will prolly introduce better ux here