The agent wants to run a migration or add a dependency
Some actions should never happen without a person. The agent policy decides which.
For: Team developer, Project lead
What happened
In the middle of a task, the agent was about to change the database schema, add a package or touch CI.
Why it happens
To an agent, a migration is just another command. It does not know which actions your team treats as sensitive unless you tell it.
What Corpole does
- Keeps an agent policy per project: each kind of action is allowed, ask first, or forbidden.
- Turns the policy into Claude Code permission rules through the repository kit, so the agent stops before the action.
- Records a one-off "yes" to an ask-first action in the activity log. A forbidden action stays forbidden, even in an emergency.
What you do
- When the agent asks, look at what it wants to run and answer yes or no.
- If it should never happen, set that action to forbidden on the Project settings page (Agent policy).
Keep it from happening again
- Set the policy once per project; tenant and account can set a baseline for every project.