Choose a mode for the task
Ask requests approval for many changes and commands; Auto allows file writes but still asks about storage changes, DNS changes, and commands. Plan is read-only. Full allows most actions without asking, but sending a message, publishing a deployment, and spending non-model credits still require approval every time.
Mode names do not replace your review of the configured tools and connected resources. An agent can only use capabilities available in its run, and some actions still have their own approval checks. Read the current mode description in the product before starting a task with consequential access.
Respond to individual approval requests
When a permission request appears, inspect the action and its arguments before choosing to allow it, allow it always where offered, or deny it. An approval should apply to the specific operation you understand; do not approve a request merely because the agent's overall goal sounds reasonable.
If the same request appears repeatedly, check whether the task needs that capability and whether the selected mode is suitable. Narrow the tools or resources available to the agent when possible, then start a new run and review its behavior. A permission mode is one part of safe setup, alongside scoped access and a clear task description.