Skip to content

Auto-Approve

The Auto-Approve menu lets you set granular permissions for what Kodik does automatically, without interrupting you with confirmation prompts.

Image

Auto-approve is off by default: Kodik asks for your confirmation before every tool call, including reading or editing files. Once enabled, you configure fine-grained permissions separately for files inside the workspace and outside it.

The total number of automatically approved requests within a single task is capped by the maxRequests setting (default 20). When that limit is reached, Kodik pauses and asks for confirmation before continuing.

Autopilot (autopilotMode) approves all actions and terminal commands without exception, other than blocked commands (see below). Enable it only in isolated environments or when you are comfortable giving Kodik full control.

In Autopilot mode, sensitive-file protection is also bypassed — Kodik can edit sensitive files without additional confirmation.

Each permission applies separately for files inside the workspace and outside it (...Externally).

PermissionToolDefault
Read project files (readFiles)read_fileon
Read all files (readFilesExternally)read_file outside workspaceoff
List files and directories (listFiles)globon
List all files (listFilesExternally)glob outside workspaceoff
Search in files (rg)rg (ripgrep)on
Search in all files (rgExternally)rg outside workspaceoff
Fetch web content (webFetch)web_fetchoff
Search the web (webSearch)web_searchoff
Edit project files (editFiles)edit_file, edit_filesoff
Edit all files (editFilesExternally)edit_file outside workspaceoff
Edit notebooks (editNotebooks)edit_notebookoff
Edit notebooks everywhere (editNotebooksExternally)edit_notebook outside workspaceoff
Edit sensitive files (editSensitiveFiles)overrides pattern protectionoff

An ...Externally permission is automatically disabled if the corresponding base permission is off. editSensitiveFiles is disabled when editFiles is off.

Command patterns (commandPatterns) let you approve specific terminal commands without enabling Autopilot. Each pattern supports the * wildcard (e.g. npm run *, git *). Individual patterns can be temporarily disabled without being deleted.

Commands are matched case-insensitively from the start of the string.

Some commands are never auto-approved — even in Autopilot mode. The default blocked list includes:

  • File deletion: rm *, sudo rm *, del *, rd *, rmdir *, Remove-Item *, ri *
  • Git clean: git clean*
  • Find with delete: find * -delete*, find * -exec rm*
  • Disk destruction: mkfs*, dd if=*, format *
  • System power: shutdown*, reboot*
  • Other dangerous: > /dev/*, :(){:|:&};:, chmod -R 777 /, chown -R *:* /

You can edit this list in settings — add or remove patterns to match your environment.

Kodik additionally protects files that match sensitive file patterns, even when editing is enabled (unless editSensitiveFiles is explicitly turned on). The default protected patterns include:

  • Secrets and environment variables: **/.env, **/.env.*, **/secrets.*, **/secret.*, **/*secret*, **/*password*, **/*credentials*
  • Package lock files: **/package.json, **/package-lock.json, **/yarn.lock, **/pnpm-lock.yaml, **/composer.lock, **/Gemfile.lock, **/Pipfile.lock, **/poetry.lock, **/cargo.lock
  • Configuration files: **/*.config.js/ts/mjs/cjs/json, **/tsconfig.json, **/jsconfig.json, **/babel.config.*, **/webpack.config.*, **/vite.config.*, **/rollup.config.*, **/.eslintrc.*, **/.prettierrc.*
  • Git files: **/.gitignore, **/.gitattributes, **/.gitmodules, **/.git/**
  • Docker and deployment: **/Dockerfile, **/docker-compose.yml/yaml, **/.dockerignore, **/kubernetes/**/*.yaml
  • CI/CD: **/.github/workflows/**, **/.gitlab-ci.yml, **/.circleci/**, **/.travis.yml, **/azure-pipelines.yml, **/Jenkinsfile
  • IDE files: **/.vscode/**, **/.idea/**, **/.vs/**
  • Database migrations: **/migrations/**, **/migrate/**
  • All dotfiles: **/.*

You can extend or narrow this list in settings.

Kodik can always read its own configuration assets (skills, commands, rules, hooks, sub-agents) without any auto-approve permissions — this is independent of your settings.

For most workflows, start conservatively:

  • Auto-approve reading project files (readFiles, listFiles, rg)
  • Set the request limit to 10–20
  • Leave editing and Autopilot off

As trust in the agent grows, gradually add permissions. Tighten settings for critical production work; Autopilot is acceptable in isolated throwaway environments.