The outcome

Create a verified change that can be inspected or restored without exposing unnecessary system authority.

Step by step

A workflow you can repeat.

  1. 01

    Create a clean branch, review repository instructions and extensions, confirm folder trust, and capture status and baseline tests.

  2. 02

    Enable checkpointing and an appropriate sandbox, verify permitted filesystem and network access, and keep YOLO mode disabled.

  3. 03

    Provide the outcome, acceptance criteria, relevant files, architecture constraints, non-goals, validation commands, and protected resources.

  4. 04

    Review each shell command, file edit, extension or MCP call, network request, dependency change, and sandbox expansion before allowing it.

  5. 05

    Run trusted checks independently, inspect the complete diff and saved checkpoint, and commit or release only through the repository's normal review process.

Working standard

What good use looks like.

  • Enable recovery before edits.
  • Keep YOLO mode off.
  • Review sandbox expansion requests.

Official references

Check the current product documentation.