> How much your AI may change on its own, connector by connector. Four modes, single actions set apart, and how a question reaches you. # Modes How much your AI may change on its own, connector by connector. Four modes, single actions set apart, and how a question reaches you. A mode says what happens when your AI wants to change something in a connector. Reading is never asked. You pick one mode for each [connector](https://www.mcpdelta.com/docs/connectors), and you can set single actions apart. ## The four modes | In the app | What happens | In a terminal | | --- | --- | --- | | **Change on its own** | Every change is made at once, deleting and sending included. | `auto` | | **Ask before deleting or sending** | Other changes are made on their own and can be undone. A change that deletes or sends waits for you. | `ask-final` | | **Ask before every change** | Every change waits for you. | `ask` | | **Read only** | Your AI can read, never change. Every change is refused. | `readonly` | Whatever the mode, each task shows in [Activity](https://www.mcpdelta.com/docs/activity-and-undo), with every change before and after. The app tags **Ask before deleting or sending** as Suggested. A connector you move through Delta MCP gets it, unless it already has a mode. ## What counts as deleting or sending Delta MCP decides from the name of the action. - **Deleting**: delete, remove, cancel, revoke, reset and similar words. An action that runs a statement or a command your AI gives it counts too, unless the statement only reads. - **Sending**: send, reply, post, publish, deploy, merge, invite, share. Names that speak of money, such as refund or transfer, count as sending. The name is all Delta MCP has to go on. An action with an odd name counts as an ordinary change, and the mode decides as for any other. When you need to be sure, pick **Ask before every change**, or switch the action off. ## When a change needs your yes A card opens on your screen. It shows each change before and after, and what can be undone. On a Mac, you approve with Touch ID, your watch or your password, which no AI can do for you. Elsewhere, for now, the card is a page in your browser. It is weaker, and it says so. An approval counts once, for what the card showed. A card closed with no answer is a refusal, and nothing is made. While it waits, the task shows in Activity as **Waiting for you**, and in the menu bar with **Review**. The card can also approve everything in this conversation, for 4 hours at most. That choice is on the card only. **Stop** in the menu bar takes it back. ## Set a mode 1. Open **Connectors** and pick a connector under **Through Delta**. 2. Under **When your AI wants to change something**, pick a mode. The change reaches conversations that are already open, at your AI’s next call. Nothing to restart. From a terminal, see [Modes and payments](https://www.mcpdelta.com/docs/cli-modes). ## Set one action apart 1. In the connector, open **Advanced**. It shows how many actions there are, and how many you set. 2. Next to an action, pick **Like the connector**, one of the four modes, or **Off**. A reading action only offers **Like the connector** and **Off**. When an action is **Off**, your AI no longer sees it, and a call to it is refused. ## Money Money that leaves is meant to follow its own rule, apart from modes. That rule is not in this version yet. Until it ships, **Change on its own** lets payments through. The Payments page will describe the rule when it is written.