[FEATURE]: more general external_directory permissions #4991

Activity

1. benceferdinandy-signifyd

   added

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on Dec 2, 2025
2. github-actions commented on Dec 2, 2025

   

   github-actionsBot

   on Dec 2, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • [FEATURE]: allow /tmp or $TMPDIR folder access option #4743: Allow /tmp or $TMPDIR folder access option - discusses making external_directory more extensible with environment variables and wildcards
   • [FEATURE]: edit/write permission with deny,allow,ask using glob #4287: edit/write permission with deny,allow,ask using glob - proposes using glob patterns for more granular permission control
   • permissions for compound commands #4800: permissions for compound commands - relates to permission resolution for complex CLI arguments
   • [FEATURE]: Setting global permissions for custom tool #4881: Setting global permissions for custom tool - discusses broader permission configuration for tools

   These issues all touch on making the permission system more flexible and generalizable beyond specific hardcoded tools. Feel free to ignore if your specific case isn't addressed by these.
3. rekram1-node commented on Dec 2, 2025

   

   rekram1-node

   on Dec 2, 2025

   Contributor

   More actions

   Yeah it could definitely be better

   and if it looks like it matches something on the filesystem invoke the external_directory permissions?

   What does this mean?
4. benceferdinandy-signifyd commented on Dec 2, 2025

   

   benceferdinandy-signifyd

   on Dec 2, 2025

   Author

   More actions

   Yeah it could definitely be better

   and if it looks like it matches something on the filesystem invoke the external_directory permissions?

   What does this mean?

   So imagine a command that has an argument that looks like a path but isn't, or is a path, but not relevant on the machine (for the first, maybe some script that does API calls, but the base URL is embedded so you have something like http GET /api/lookup for the latter something like ssh remotemachine ls /var/lib/). In both cases it would look like path outside of the CWD, but the first one is not a path, the latter is not a path on the machine. So my suggestion would be to parse CLI arguments for path like things, but verify if those things are actually paths that exist on the current machine. Such a check (that probably should be glob aware) would tell opencode that /api/lookup is not a path on this machine, so no need to apply external_directory permissions.

   Does that make sense? I feel this would remove the need to hardcode specific commands (although some common commands could still get their own special rules if needed).
5. rekram1-node commented on Dec 2, 2025

   

   rekram1-node

   on Dec 2, 2025

   Contributor

   More actions

   Yeah I see what you mean
6. rekram1-node

   assigned

   thdxr

   on Dec 2, 2025
7. thdxr

   closed this as completedon Mar 25, 2026