Shell Mode in the Cursor CLI checks each command before it runs. Which statement matches how allowlisting and admin policies behave there?

The principle — Shell Mode checks every command against your permissions and team settings before it runs, so approval is not purely a local decision.

Why the key is correct — The documentation states plainly that admin policies may block certain commands and that commands with redirection cannot be allowlisted inline. A command that writes its output to a file therefore keeps asking, however often you approve it.

Why the others are wrong — A repeated prompt is evidence about what may be allowlisted, rather than proof that a file failed to save. Admin policies come from the organisation, so a personal project offers no escape from them. And redirection is part of the command, rather than something stripped away before matching.

Remember this — When a prompt keeps returning, look at the shape of the command and at the policy above you.

Sources — Cursor's Shell Mode documentation.