The quick read
- Ask it to inspect existing instructions, scripts and nearby patterns.
- Review the diff and validation results.
Define the job
Provide the repository context, expected behaviour and relevant constraints. A request such as ‘make the app better’ encourages a broad interpretation. A request to repair a specific import failure gives the coding agent a clear target and a way to verify completion.
Use the repository’s evidence
Ask it to inspect existing instructions, scripts and nearby patterns. Let it run appropriate checks, but distinguish commands it proposes from commands it actually executes. Keep secrets and production access governed by the surrounding environment rather than relying on a prompt alone.
Inspect before accepting
Review the diff and validation results. Check whether the original issue is resolved and whether unrelated files changed. For a small bug, a targeted regression check may be more useful than an expensive broad test run. Confirm the current permission settings and supported environment in the official product documentation. A coding agent is most helpful when its work can be followed from problem to evidence to patch, with a clear account of any unverified behaviour.
Sources & notes
Source-based guide, not a hands-on product test. Features and availability can change.
anthropic.com — official reference
Sources reviewed for the September 2026 launch edition.
