Permissions

Every Worker in a Hive runs under a permission mode that decides how much it can do on its own. You set the mode per Worker, so a trusted CLI can move fast while a riskier one stays on a short leash. There are three modes: auto, ask, and deny.

The three modes

• auto — The Worker acts without asking. It can read, write, and run commands as the Queen directs, with no per-action prompt. Fastest, but it assumes you trust both the Worker and the spec it is executing.
• ask — The Worker prompts you to approve each action before it runs. You see what it intends to do and approve or reject it. Slower, but you stay in the loop on every change.
• deny — The Worker is blocked from that class of action entirely. Use it to forbid behavior you never want, regardless of what the Queen plans.

Recommended defaults

Start conservative and loosen as you gain trust:

• Use ask for destructive or irreversible actions — deleting files, running migrations, pushing to a remote, or executing shell commands with side effects.
• Use auto for low-risk, high-volume work on code you control, such as edits inside a scratch branch.
• Use deny to hard-block action classes that have no place in a given Hive.

Changing permissions per Hive

Permissions are scoped to the Hive, so the same CLI can be cautious in one Hive and autonomous in another. Open the Worker’s controls inside the Hive and pick its mode. Changes apply going forward; a Worker already mid-action finishes that action under its previous mode, then honors the new setting on the next one.

Next steps

To see how permissions fit into setting up your first workspace, see First Hive. To understand where Workers actually execute, read the Local PTY model.