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

[FEATURE]: Limit tool (e.g. write, edit) permissions to specific folders #3945

New Issue
Open
opened 2026-02-16 17:42:02 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 17:42:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @driebe on GitHub (Dec 28, 2025).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Hi opencode team,

I love your product and have a suggestion on how to improve secure interaction with the agents. It would be great if some of the tools (primarily write & edit) could be limited to certain project folders in the project.

For example: I want to limit my tester.md to only be able to create files in my ____tests_____ folders or edit files which have test in the filename - but no other files.

This could potentially look like this:

permission:
  write:
    "*/*test*": allow
    "*": deny
  edit:
    "*/*test*": allow
    "*": deny

Thanks for your consideration!

Originally created by @driebe on GitHub (Dec 28, 2025). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Hi opencode team, I love your product and have a suggestion on how to improve secure interaction with the agents. It would be great if some of the tools (primarily write & edit) could be limited to certain project folders in the project. For example: I want to limit my tester.md to only be able to create files in my `____tests_____` folders or edit files which have `test` in the filename - but no other files. This could potentially look like this: ``` permission: write: "*/*test*": allow "*": deny edit: "*/*test*": allow "*": deny ``` Thanks for your consideration!
yindo added the discussion label 2026-02-16 17:42:02 -05:00
yindo commented 2026-02-16 17:42:02 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 28, 2025):

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

  • #5529: [FEATURE]: Add per-agent filesystem boundaries (allow/deny paths) + optional run-as user for bash - This is the most comprehensive and directly related issue, proposing allow/deny filesystem path patterns per-agent with extensive discussion on implementation
  • #4667: Limiting access for tools in a safer way - Proposes sandbox-style security contexts with read/write path restrictions and allowed executables
  • #3585: Add pattern-based directory access restrictions to prevent verbose per-tool configurations - Requests global pattern-based exclusion rules for sensitive files
  • #2242: Is there a way to sandbox the agent? - General sandboxing request with discussion about restricting access outside the working directory

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Dec 28, 2025): This issue might be a duplicate of existing issues. Please check: - #5529: [FEATURE]: Add per-agent filesystem boundaries (allow/deny paths) + optional run-as user for bash - This is the most comprehensive and directly related issue, proposing allow/deny filesystem path patterns per-agent with extensive discussion on implementation - #4667: Limiting access for tools in a safer way - Proposes sandbox-style security contexts with read/write path restrictions and allowed executables - #3585: Add pattern-based directory access restrictions to prevent verbose per-tool configurations - Requests global pattern-based exclusion rules for sensitive files - #2242: Is there a way to sandbox the agent? - General sandboxing request with discussion about restricting access outside the working directory Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:42:02 -05:00
Author
Owner
Copy Link
Copy Source

@driebe commented on GitHub (Dec 28, 2025):

Your github actions search is way more comprehensive than the GitiHub search :(. I will close this for #5529

@driebe commented on GitHub (Dec 28, 2025): Your github actions search is way more comprehensive than the GitiHub search :(. I will close this for #5529
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 discussion
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#3945
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?