The outcome

Create an auditable permission and sandbox baseline that behaves safely in interactive and non-interactive sessions.

Step by step

A workflow you can repeat.

  1. 01

    Inventory approved directories, commands, domains, MCP tools, models, subagents, credentials, environments, and actions that always require a person.

  2. 02

    Put shared least-privilege ask and deny rules in reviewed project settings while keeping machine-specific paths and credentials in uncommitted local or user scope.

  3. 03

    Disable bypass and auto modes where policy requires, enable sandbox filesystem and network allowlists, and disable unsandboxed escape when unnecessary.

  4. 04

    Test trusted and untrusted clones, protected files, dangerous command variants, redirects, chained commands, prompt injection, subagents, and non-interactive fallbacks.

  5. 05

    Audit effective rules in the permission panel, version owner-approved settings, rotate secrets, and rerun the test matrix after every CodeBuddy upgrade.

Working standard

What good use looks like.

  • Never commit credentials.
  • Test effective rules from an untrusted clone.
  • Deny unsandboxed escape unless required.

Official references

Check the current product documentation.