A good fit for
- → Multi-file changes in an existing repository
- → Explaining unfamiliar code before editing
- → Repeatable review and test workflows
Know the limits
- → A convincing patch can still weaken tests or change unrelated behavior.
- → Cloud inference and local tool execution have different privacy boundaries.
- → Hook filters are best-effort; configure permissions and isolation separately.
Your first useful workflow
Map first
Ask for the relevant files, existing tests and failure modes without allowing edits.
Approve a bounded plan
State the accepted behavior, forbidden files and stop condition. Review the plan before execution.
Verify the diff
Run trusted checks, inspect changed tests and review the final patch outside the model's explanation.
The practical take
Use the permission system for hard boundaries; a best-effort hook is not a sandbox.
Sources & evidence
Capabilities above are summarized from these official documents. Workflow suggestions are editorial guidance, not a claim of measured product superiority.