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

feat: Add Permission Control for Path Restrictions in Bash Tool #1801

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

Originally created by @thuanpham582002 on GitHub (Sep 23, 2025).

Originally assigned to: @thdxr on GitHub.

Summary: Allow users to approve bash commands that reference external paths via permission system.

Problem: Bash tool hard-rejects external paths without user control.

mkdir -p ~/.config/opencode  # ❌ Fails immediately

Solution: Add external_paths permission type:

{
  "permission": {
    "external_paths": "ask"   "ask" | "allow" | "deny"
  }
}

Implementation: Modify bash.ts to use Permission.ask() for external paths instead of hard rejection.

Benefits:

  • User control over external path access
  • Consistent with other tool permissions
  • Enables legitimate operations (config migration, etc.)

Files: packages/opencode/src/tool/bash.ts

Originally created by @thuanpham582002 on GitHub (Sep 23, 2025). Originally assigned to: @thdxr on GitHub. **Summary:** Allow users to approve bash commands that reference external paths via permission system. **Problem**: Bash tool hard-rejects external paths without user control. ``` bash mkdir -p ~/.config/opencode # ❌ Fails immediately ``` Solution: Add external_paths permission type: ``` json { "permission": { "external_paths": "ask" "ask" | "allow" | "deny" } } ``` Implementation: Modify bash.ts to use Permission.ask() for external paths instead of hard rejection. Benefits: - User control over external path access - Consistent with other tool permissions - Enables legitimate operations (config migration, etc.) Files: packages/opencode/src/tool/bash.ts
yindo closed this issue 2026-02-16 17:32:41 -05:00
yindo commented 2026-02-16 17:32:41 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 23, 2025):

note: we probably want some functionality to allow access for other tools to work outside cwd too, like read for instance.

@rekram1-node commented on GitHub (Sep 23, 2025): note: we probably want some functionality to allow access for other tools to work outside cwd too, like read for instance.
yindo commented 2026-02-16 17:32:41 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 23, 2025):

This will be done as part of: #1961

@rekram1-node commented on GitHub (Sep 23, 2025): This will be done as part of: #1961
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
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#1801
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?