The outcome

Create a reusable permission posture matched to the repository and the sensitivity of its data.

Step by step

A workflow you can repeat.

  1. 01

    Classify the workspace, credentials, external services, and commands that could modify data, dependencies, git history, or production systems.

  2. 02

    Enable project-file reading first and leave edits, terminal commands, browser access, and MCP tools approval-gated until each is needed.

  3. 03

    If repetitive work justifies Auto Approve, enable only the smallest categories and keep access outside the workspace disabled.

  4. 04

    Test the policy on a disposable branch with representative read, edit, test, install, network, and destructive requests.

  5. 05

    Keep Checkpoints and normal version control active, review permission changes periodically, and avoid YOLO mode outside isolated throwaway work.

Working standard

What good use looks like.

  • Grant capabilities by task, not convenience.
  • Keep secrets outside agent-readable files.
  • Re-test permissions after extensions or MCP servers change.

Official references

Check the current product documentation.