[FEATURE]: Use sandboxing on macOS #6960

Closed
opened 2026-02-16 18:05:43 -05:00 by yindo · 2 comments
Owner

Originally created by @reneleonhardt on GitHub (Jan 20, 2026).

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

There's an easy way to improve security on macOS by sandboxing agents with shell scripts.
Can SandVault be integrated into OpenCode?
https://github.com/webcoyote/sandvault

Security Model

The sandvault user:

  • Cannot access your home directory
  • Runs with standard user privileges
  • Cannot modify system files
  • Has its own isolated home directory
Originally created by @reneleonhardt on GitHub (Jan 20, 2026). 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 There's an easy way to improve security on macOS by sandboxing agents with shell scripts. Can `SandVault` be integrated into OpenCode? https://github.com/webcoyote/sandvault > #### Security Model > > The sandvault user: > > * Cannot access your home directory > * Runs with standard user privileges > * Cannot modify system files > * Has its own isolated home directory
yindo added the discussion label 2026-02-16 18:05:43 -05:00
yindo closed this issue 2026-02-16 18:05:43 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 20, 2026):

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

  • #2242: Is there a way to sandbox the agent? - Discusses restricting file access and mentions seatbelt on macOS
  • #5529: Add per-agent filesystem boundaries (allow/deny paths) + optional run-as user for bash - Comprehensive feature request for per-agent sandboxing with filesystem restrictions and OS user isolation
  • #6606: Spawn a separate process for tool calls - Proposes process isolation for tools with security policy support
  • #4667: Limiting access for tools in a safer way - Discusses using bubblewrap on Linux and per-agent security contexts

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

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be a duplicate of existing issues. Please check: - #2242: Is there a way to sandbox the agent? - Discusses restricting file access and mentions seatbelt on macOS - #5529: Add per-agent filesystem boundaries (allow/deny paths) + optional run-as user for bash - Comprehensive feature request for per-agent sandboxing with filesystem restrictions and OS user isolation - #6606: Spawn a separate process for tool calls - Proposes process isolation for tools with security policy support - #4667: Limiting access for tools in a safer way - Discusses using bubblewrap on Linux and per-agent security contexts Feel free to ignore if none of these address your specific case.
Author
Owner

@reneleonhardt commented on GitHub (Jan 20, 2026):

Closed in favor of #2242

@reneleonhardt commented on GitHub (Jan 20, 2026): Closed in favor of #2242
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6960