anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

How do you configure opencode to always be allowed to read all files in a certain directory #7744

New Issue
Closed
opened 2026-02-16 18:08:06 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 18:08:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @todor-a on GitHub (Jan 27, 2026).

Originally assigned to: @jayair on GitHub.

Question

I have the following project structure:

- projects
  - personal
    - foo
    - bar
    - baz

I run opencode from personal/bar and ask it to reference something in personal/foo.

My config at ~/.config/opencode/opencode.json is:

{
  "$schema": "https://opencode.ai/config.json",
  "theme": "opencode",
  "autoupdate": true,
  "permission": {
  "read": {
    "~/projects/personal/**": "allow"
  }
}

And despite having the ~/projects/personal/** in there, I always get asked to confirm that it's okay to read files. What am I doing wrong?

P.S. When you select always allow when prompted, where is that stored?

Originally created by @todor-a on GitHub (Jan 27, 2026). Originally assigned to: @jayair on GitHub. ### Question I have the following project structure: ``` - projects - personal - foo - bar - baz ``` I run opencode from `personal/bar` and ask it to reference something in `personal/foo`. My config at `~/.config/opencode/opencode.json` is: ```json { "$schema": "https://opencode.ai/config.json", "theme": "opencode", "autoupdate": true, "permission": { "read": { "~/projects/personal/**": "allow" } } ``` And despite having the `~/projects/personal/**` in there, I always get asked to confirm that it's okay to read files. What am I doing wrong? P.S. When you select `always allow` when prompted, where is that stored?
yindo added the docs label 2026-02-16 18:08:06 -05:00
yindo closed this issue 2026-02-16 18:08:06 -05:00
yindo commented 2026-02-16 18:08:06 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 27, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8832: opencode not respecting permissions - Users report that permission configurations in opencode.json are not being respected, requiring manual confirmation prompts despite explicit 'allow' rules

Feel free to ignore if this doesn't address your specific case.

@github-actions[bot] commented on GitHub (Jan 27, 2026): This issue might be a duplicate of existing issues. Please check: - #8832: opencode not respecting permissions - Users report that permission configurations in opencode.json are not being respected, requiring manual confirmation prompts despite explicit 'allow' rules Feel free to ignore if this doesn't address your specific case.
yindo commented 2026-02-16 18:08:06 -05:00
Author
Owner
Copy Link
Copy Source

@OpeOginni commented on GitHub (Jan 27, 2026):

I am able to reproduce, currently looking into it

@OpeOginni commented on GitHub (Jan 27, 2026): I am able to reproduce, currently looking into it
yindo commented 2026-02-16 18:08:07 -05:00
Author
Owner
Copy Link
Copy Source

@OpeOginni commented on GitHub (Jan 27, 2026):

@todor-a I did some digging, and it seems the right way to do this is to add this to your permission

{
  "$schema": "https://opencode.ai/config.json",
  "theme": "opencode",
  "autoupdate": true,
  "permission": {
    "external_directory": {
        "~/projects/personal/**": "allow"
    }
}

Once this is added it treats matches to the external_directory as part of the directory you are in, this means that after adding this, you dont need to even add permissions for read tools. And the model can read from directories bar and baz just like it can freely do in the current directory foo.

This also means as it can edit on the current dir foo it can also do things to those external directories bar and baz, so you might want to restrict other tools, but if you know you are just reading, there isnt much of an issue.

If you want to be very strict you can then do is to restrict other tools from interacting with the external_directory, for example you want to be able to read from it but not edit, you can go with this

{
  "$schema": "https://opencode.ai/config.json",
  "theme": "opencode",
  "autoupdate": true,
  "permission": {
    "external_directory": {
        "~/projects/personal/**": "allow"
    },
    "edit": {
        "~/projects/personal/**": "deny"
    },
}

Try this please and let me know how it works

@OpeOginni commented on GitHub (Jan 27, 2026): @todor-a I did some digging, and it seems the right way to do this is to add this to your permission ```json { "$schema": "https://opencode.ai/config.json", "theme": "opencode", "autoupdate": true, "permission": { "external_directory": { "~/projects/personal/**": "allow" } } ``` Once this is added it treats matches to the external_directory as part of the directory you are in, this means that after adding this, you dont need to even add permissions for `read` tools. And the model can read from directories `bar` and `baz` just like it can freely do in the current directory `foo`. This also means as it can edit on the current dir `foo` it can also do things to those external directories `bar` and `baz`, so you might want to restrict other tools, but if you know you are just reading, there isnt much of an issue. If you want to be very strict you can then do is to restrict other tools from interacting with the external_directory, for example you want to be able to read from it but not edit, you can go with this ```json { "$schema": "https://opencode.ai/config.json", "theme": "opencode", "autoupdate": true, "permission": { "external_directory": { "~/projects/personal/**": "allow" }, "edit": { "~/projects/personal/**": "deny" }, } ``` Try this please and let me know how it works
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7744
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?