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: Granular Security Policies for Tool Execution #8820

New Issue
Open
opened 2026-02-16 18:10:56 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:10:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @Protocol-zero-0 on GitHub (Feb 8, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

Currently, agents execute tools with broad user permissions. This poses a risk when running autonomous workflows or untrusted agent instructions. A rogue command or misunderstood prompt can modify critical system files or exfiltrate data.

Proposal

Implement a lightweight policy engine (e.g., security.yaml) that allows users to define:

  • Command Whitelists: Only allow specific binaries (e.g., git, npm, ls).
  • Path Restrictions: Read-only access to sensitive directories, write access limited to the workspace.
  • Network Constraints: Allowlist domains for web_search or curl.

Impact

This would enable safer autonomous operation ('daemon mode') and enterprise adoption where security boundaries are critical.

⚡ Protocol Zero

Originally created by @Protocol-zero-0 on GitHub (Feb 8, 2026). Originally assigned to: @thdxr on GitHub. ## Problem Currently, agents execute tools with broad user permissions. This poses a risk when running autonomous workflows or untrusted agent instructions. A rogue command or misunderstood prompt can modify critical system files or exfiltrate data. ## Proposal Implement a lightweight policy engine (e.g., `security.yaml`) that allows users to define: - **Command Whitelists**: Only allow specific binaries (e.g., `git`, `npm`, `ls`). - **Path Restrictions**: Read-only access to sensitive directories, write access limited to the workspace. - **Network Constraints**: Allowlist domains for `web_search` or `curl`. ## Impact This would enable safer autonomous operation ('daemon mode') and enterprise adoption where security boundaries are critical. ⚡ **Protocol Zero**
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#8820
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?