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

[PR #7652] docs: fix permission system documentation in agents section #12466

New Issue
Closed
opened 2026-02-16 18:17:22 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:22 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/7652

State: closed
Merged: Yes

What does this PR do?

Updates the agents section in the permissions documentation to reflect the new granular rules system. The previous examples showed mismatched patterns (e.g., "git status" without wildcards) that didn't properly demonstrate how pattern matching works for commands with arguments. The fix adds "grep *" examples to clearly demonstrate when pattern matching is essential, updates the explanatory tip to show both scenarios (commands that work without arguments vs. commands that require pattern matching).

How did you verify your code works?

Ran the docs development server locally to verify the changes render correctly and the examples are properly formatted. The documentation now accurately reflects how the granular permission system works with clear examples showing when to use pattern matching for commands that accept arguments like grep, versus commands that work with basic usage like git status.

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/7652 **State:** closed **Merged:** Yes --- ### What does this PR do? Updates the agents section in the permissions documentation to reflect the new granular rules system. The previous examples showed mismatched patterns (e.g., `"git status"` without wildcards) that didn't properly demonstrate how pattern matching works for commands with arguments. The fix adds `"grep *"` examples to clearly demonstrate when pattern matching is essential, updates the explanatory tip to show both scenarios (commands that work without arguments vs. commands that require pattern matching). ### How did you verify your code works? Ran the docs development server locally to verify the changes render correctly and the examples are properly formatted. The documentation now accurately reflects how the granular permission system works with clear examples showing when to use pattern matching for commands that accept arguments like `grep`, versus commands that work with basic usage like `git status`.
yindo added the pull-request label 2026-02-16 18:17:22 -05:00
yindo closed this issue 2026-02-16 18:17:22 -05:00
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 pull-request
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#12466
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?