# Guardrails

> Which of an orchestrator's actions wait for you, set for each orchestrator.

Some things an [orchestrator](/docs/orchestrators) does can lose work or speak for you. Guardrails say which of them wait for you, so a chat you already gave **Full access** is not asked twice.

## Setting them

**Settings → Orchestrator → Guardrails** lists them for one orchestrator; with more than one, pick which at the top:

| Guardrail | What it covers | Default |
|---|---|---|
| **Stop a session** | the orchestrator ends a session and closes its terminal | **Follow chat permission** |
| **Force stop, or a stop that loses work** | the session is working, or its folder has changes not committed | **Always ask** |
| **Send a drafted reply as you** | a reply the orchestrator wrote goes to a session in your name | **Follow chat permission** |

Each is one of:

- **Follow chat permission** — it asks, unless the orchestrator's chat runs in **Full access**.
- **Always ask** — your words or your click, every time.
- **Never ask** — it acts on its own call.

Guardrails are kept by devpit, out of reach of the orchestrator's own chat, and a change to one is written in that orchestrator's sessions log.

## When it asks

As before: your own message in its chat — `stop fix-login`, or ✅ — or one click on what it shows above the composer, on the [Remote](/docs/remote) or on Telegram. See [Orchestrator sessions](/docs/orchestrator-sessions#stopping-a-session).

## When it does not

With a guardrail off, the orchestrator stops the session or sends the draft itself. It then tells you in one line what it did, what that lost and which guardrail let it, and the same line goes to its sessions log.

A stop that would lose work answers to **Force stop, or a stop that loses work**, which asks by default even in **Full access**. With that one off too, the orchestrator still has to ask for a forced stop on purpose before any work is lost.
