Commit Often

Give your agent a clean branch and frequent commits. Rollback is your friend when the agent goes wrong.

Agents can make large changes quickly. Without frequent commits, undoing a bad turn means manually reverting dozens of files. With small, frequent commits, you can git reset or git revert to a known-good state in seconds.

1. Create a feature branch for every agent session. Never let an agent touch main directly.
2. Commit after every meaningful change. "Agent added input validation" is a good commit message.
3. Use the agent's own commits if it supports them. Tools like Aider and Claude Code can commit as they work.
4. Push regularly. Local branches can be lost. Remote branches are safer.
5. Review the commit history. It tells the story of what the agent actually did.

• You are running an agent on main.
• There is one giant commit with the message "updates" or "agent work."
• You are afraid to revert because you cannot remember what changed.
• The agent deleted code you now need to recover.