Tools and permissions

What tools do#

Mirr Code uses tools to read and edit files, search, and run terminal commands. A request such as “Run the tests” can lead to running the project's actual test command.

What can run depends on the work mode and permission settings. Mirr Code does not gain file access that your operating system denies.

When approval is requested#

Read the file paths and command before choosing whether to allow the action. If it is not what you intended, decline and explain the constraint.

Do not run commands that change the database.
Explain the changes needed first.

Permission rules can allow an action, request approval, or block it. Approving one action does not mean you have approved unrelated work.

Automatic execution and Yolo mode#

See Work modes for the standard approval flow, Auto, planning, and Yolo. Yolo skips individual tool approvals, so do not expect an approval prompt before every consequential action while it is enabled.

Files and external services#

Publishing, deleting, and deploying through external tools are real changes too. Limit connected service accounts to the access needed. Production data and billing operations also need backups and the service's own safeguards.

Session recovery is not a universal undo. Sent messages, deployments, and database changes must be handled in the relevant service separately.

Protect secrets#

Do not put passwords or tokens in conversations, code, or public logs. Remove secrets from error messages before requesting help. Review the files changed and commands run to understand the work performed.