Permissions

By default, Crush will ask you for permission before running tool calls.

Allowing Tools

If you'd like, you can allow tools to be executed without prompting you for permissions. Use this with care.

permissions allow view ls grep edit mcp_context7_get-library-doc

The bash tool additionally runs a small set of read-only commands (ls, pwd, git status, git log, and similar) without prompting. Crush parses the command to decide, so it applies only when the whole command is provably inert: a redirection, a variable assignment, a command substitution, a pipeline, or an argument that mutates state (git branch -D, git remote set-url) all fall back to the normal permission prompt.

Disabling Built-In Tools

You can also deny tools, hiding them from the agent entirely:

permissions deny bash sourcegraph

To disable tools from MCP servers, see the MCP config.

You only live once

You can also skip all permission prompts completely by running Crush with the --yolo flag. Be very, very careful with this feature.

Command Reference

permissions configures tool permissions. allow skips approval prompts; deny hides tools from the agent entirely.

Usage:  permissions [command]Available Commands:  allow     Allow tools without prompting  deny      Hide tools from the agent

permissions allow

Allow one or more tools to run without prompting.

Usage:  permissions allow <tool> [<tool> ...]

permissions deny

Hide one or more tools from the agent so they cannot be called.

Usage:  permissions deny <tool> [<tool> ...]

permissions allow view ls grep editpermissions deny bash