> ## Documentation Index
> Fetch the complete documentation index at: https://docs.druks.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Approvals

> How a run waits for your yes, and where you give it.

An app decides where a person must make the call. At that point the run stops
and asks you. Nothing changes until you answer.

## What you see

* **The question,** in one sentence. For example: "I'd like to upgrade 3
  packages in acme/api."
* **Why,** with the facts: what it fixes and whether the tests pass.
* **The plan,** when you want the details: the diff or the list of changes.
* **The cost so far.**
* **Your choices.** Usually Approve, Change or Stop. Some apps ask a short
  question instead.

## While the run waits

* **No agent runs.** Druks releases the sandboxes of the run while it waits.
* **It survives restarts and deploys.** After your answer, the run continues
  from the same point.
* **It waits up to 14 days.** After 14 days without an answer, the run fails
  with a gate-timeout failure. See [troubleshooting](https://docs.druks.ai/troubleshooting.md).

## Where you answer

You answer in the same places on Druks Cloud and on a self-hosted Druks.

| Where | How |
| - | - |
| Dashboard | Open the run. The waiting step shows the question and the buttons. |
| Slack | Druks posts the question with buttons to the Slack channel you select. See [notifications](https://docs.druks.ai/configuration.md#notifications). |
| Chat | Ask what waits for you, and answer in the [chat](https://docs.druks.ai/chat.md). |
| Claude Code or Codex | Connect the Druks MCP server. Your agent lists what waits, reads the question and answers it. See [connect your agent](https://docs.druks.ai/connect-your-agent.md). |

Druks accepts one answer for each question, from whichever place answers
first.

## After you answer

* **Approve:** the run continues and makes the change, for example it opens a
  pull request.
* **Change:** you write what to change. The agent tries again and asks you
  again.
* **Stop:** the run ends. Nothing changes.

Each question, answer and cost stays in the run history, with who answered and
when.

## For app builders

In code, an approval is a gate. See
[wait for input](https://docs.druks.ai/writing-an-app.md#wait-for-input) in the app guide, and
[waiting for people and systems](https://docs.druks.ai/concepts.md#waiting-for-people-and-systems).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.