HUZAIFA SHOUKAT@huzaifabuildz
SANDBOXFree guide · 1-page PDF

CHECK YOUR AGENT'S BOUNDARIES

Permissions should match the task you actually want it to do.

No email required. Keep it for your next build.

Review the policy

  1. Identify the project folder the agent can read and edit. Keep unrelated files and credential folders outside the allowed scope.
  2. Check allowed network destinations and access to Git or GitHub CLI credentials. Start with the smallest access that can complete your task.
  3. Read the current client setup guide and confirm sandboxing is active in the session; do not rely on a prompt alone.
  4. In a disposable sample project, test an allowed file edit and an attempted read of a dummy file outside the allowed folder. Check that the latter is blocked.

Your boundary checklist

  1. Allowed files: __________ Allowed network destinations: __________
  2. Credential access: __________ Actions requiring approval: __________
  3. Policy confirmed active: __________ Dummy boundary test result: __________

When a task is blocked

  1. Check which permission the specific action needs. Adjust only that scope, then re-run the boundary check.
  2. Review the diff and test the result even when every command ran inside the sandbox.

FROM THE ORIGINAL CREATOR

This companion guide is by Huzaifa. Check the original project for current setup and availability.

KEEP THE GUIDE HANDY

Save the one-page PDF for later.

Download free PDF

TRY NEXT