> ## Documentation index
> Fetch the complete documentation index at: [llms.txt](../llms.txt)
> Use this file to discover all available pages before exploring further.

# Plans and approvals

Sleuth shows you what it will build before it builds it. Here is what you approve and how to skip approvals.

[Open Analyze](https://app.sleuth.studio)

## What you approve

A bigger question in Analyze pauses twice before it uses credits:

1. **The plan.** The steps Sleuth will run, in order, and the datasets it will build. Approve it, or reject it and say what to change, like "skip deals, focus on Phase 2 and later."
2. **The dataset design.** The columns each dataset will have and what goes in each one. This is where you add a criterion, drop a column you don't need, or rename one to match how your team talks.

If you don't approve, nothing runs and nothing is charged: the plan waits in the project until you approve it or ask for a change.

After you approve both, Sleuth builds the datasets and the analysis. Later, when you ask Sleuth to change a dataset, it shows you the change and waits for your OK.

## Turn on auto-approve

If you'd rather Sleuth go straight through, turn on auto-approve in Settings. You can choose it separately for plans, dataset designs, and dataset changes. Runs you start from Claude, ChatGPT, or Copilot follow the same settings, so with auto-approve off they wait for your approval there too.

> **Good to know:** Approving the plan is the best moment to check scope. A plan that covers "every ADC in solid tumors" when you meant HER2-low breast cancer builds a much bigger dataset and uses more credits.

## Workflows have one plan screen

Workflows show the whole plan on one screen before they run: the data steps, the outputs, and your credit balance. Add or remove outputs, then choose how it runs:

- **Pause at each step** (recommended): Sleuth stops after each step so you can check the results, pick an option, or skip ahead.
- **Run end to end**: Sleuth takes the defaults, lists them in the chat, and runs straight through.

Nothing runs until you press **Start**. [How workflows run](workflows-overview.md)

## Related

- [Ask a question in Analyze](ask-question.md): How Sleuth turns a question in your own words into a plan, datasets, and an answer you can check.
- [How credits work](how-credits-work.md): What a credit buys, what is free, and how to tell what a job will use before it runs.
- [How a research run works](mcp-run-lifecycle.md): Create a project, send the question, wait for the status to change, handle approvals and clarifications, then read the datasets and the answer.

*Updated November 9, 2026.*
