- Create a Sandbox – These agents can’t really be contained and have been known to delete entire projects – Use Docker to create a wrapper around the Agents activities. Or you could make a new user account on your PC with non-Admin privileges and let Microsoft file permission create a boundary
- Create code backups at least daily – in case the Agent deletes everything
- 90% of your work will be code review or running the code and getting the Agent to make changes based on error logs or your commands. You will need to prompt the Agent to recheck their own work – ask it to provide a summary of how the software works to force it to look deeper at the code
- If creating code from scratch you will need to pass as much context to the Agent as possible, detailed plans and examples of what you want. Get the Agent to describe the problem back to you before it starts
- Have a blueprint document which sits in the project folder that the agent can refer to, ask it to update its CLAUDE.md file based on this
- Always work with multiple Agents – You get ClaudeCode to write the scripts, then ask Codex to check the work and you pass the corrections back again. Tell Claude the comments are from a 3rd party and that it doesn’t have to agree with all the changes
- Migrations (e.g. Java to Kotlin) are relatively smooth because the Agent has the old project to refer to
- Github Test Automation – This is the holy grail. Especially useful if you don’t have a Mac, but want to deploy on Apple products. You set Github as a connected experience on the Claude website. Then you ask Claude to login to Github via CLI. Once inside you ask Claude to test the software then read the error logs – then make changes then push the code and iterate 10 times if you wish
For Android running on windows the playbook is simple – ask the Agent to run the adjacent build code to check for lint errors – later we ask the Agent to actually test in the Android emulator itself
“Claude can you please run this and save the logs in the project:
./gradlew lint –stacktrace –info -Dorg.gradle.console=plain > lint-log.txt 2>&1″
