Skip to content

Feature request: ability to disable "File X is not in the current working directory" error #3218

Closed

Description

@Mishkun

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


version: opencode 0.15.4

Activity

  1. rekram1-node commented on Oct 16, 2025

    @rekram1-node
    Contributor

    Yeah we are going to fix this soon we have ran into it ourselves quite a bit as well

  2. JoshuaRileyDev commented on Oct 20, 2025

    @JoshuaRileyDev

    Literally just had this for the last couple of days and it's been driving me insane, so good that it's getting fixed.

  3. added a commit that references this issue on Oct 30, 2025
    bd84709
  4. Mishkun commented on Nov 1, 2025

    @Mishkun
    ContributorAuthor

    @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
    }
    }

  5. rekram1-node commented on Nov 2, 2025

    @rekram1-node
    Contributor

    @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:

    • Prompt user and ask them for permission
    • introduce some /add-dir or equivalent
  6. Mishkun commented on Nov 2, 2025

    @Mishkun
    ContributorAuthor

    @rekram1-node

    • Prompt user and ask them for permission

    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"

    Image
  7. Mishkun commented on Nov 6, 2025

    @Mishkun
    ContributorAuthor

    I guess it was fixed in v1.0.29

    @thdxr is that so?

  8. rekram1-node commented on Nov 6, 2025

    @rekram1-node
    Contributor

    Oh yeah that is the case

  9. rekram1-node commented on Nov 6, 2025

    @rekram1-node
    Contributor

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions