Permissions

How Miton gates file reads, writes, and command execution for your safety.

Product stage
Development build
Last reviewed
2026-08-27
Successful result
The change is visible in the active project.

What this accomplishes

Understand and manage the trust level Miton holds for a project folder, and the mode that controls how much the agent can do without asking first.

Current availability

This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates.

Before you start

  • A Miton development build and an active project.
  • A connected cloud or local model, plus any credentials or local runtime required by this task.

Folder trust

The first time you open a folder, Miton asks Do you trust this folder? and offers three levels:

Level What the agent can do
Trusted Read, write, run shell commands, and load plugins in this folder.
Restricted Read files and run the language server. No writes, no shell, no plugins.
Untrusted Read files and run the language server. Nothing else. Use this for folders you didn’t create yourself.

The choice persists until you change it. A badge in the title bar shows the active level for the open folder — click it to reopen the dialog and change the level at any time.

Steps

  1. Open a project folder. If it has no trust grant yet, the trust dialog appears.
  2. Choose the level that matches how much you trust the folder’s contents.
  3. To change the level later, click the trust badge in the title bar.
  4. To control how much the agent does without asking, use the Mode chip above the chat input: Plan, Chat, Confirm, Autoedit, or Full access.

What success looks like

The title bar badge shows the folder’s trust level, and the agent’s actions match it — an untrusted folder stays read-only regardless of what a prompt asks for.

Common failures and recovery

  • Repeated approval prompts: Set the folder to Trusted, or switch the Mode chip to Autoedit or Full access if you want fewer interruptions for routine edits.
  • Accidental approval: Use per-turn rewind to restore files to the state before the action ran.