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

# Ask Autopilot questions and give it tasks

> Ask about an account or request a precise change. Read the proposed before-and-after values, choose when it should run and confirm only the intended action.

You can ask Autopilot to explain what is happening without asking it to change anything. A request to act follows a separate proposal and confirmation flow.

> [card] [A task did not run?](https://docs.ansio.trade/autopilot/errors.md)
>
> Read expired proposals, permissions, scheduling errors and pending verification.

## Ask a question

Useful questions identify the account and the uncertainty:

* “Why is the STG spread wider on Bybit?”
* “What needs attention on this project?”
* “Which settings changed on this account?”
* “Can you explain the difference between account value and PnL?”

Autopilot uses the account information available to it. Missing or stale data should remain visible as a limitation, rather than being treated as zero.

## Request a change

Include the client, exchange and strategy when more than one account could match. Then state the change and timing.

For example: “Reduce the STG Futures order size by 25% on Bybit.”

![Autopilot proposing a minimum order size change from 40 USDT to 30 USDT, with Confirm task and Dismiss buttons.](https://mintcdn.com/ansio/Tv7Q0RwZX2L68I0t/images/docs/autopilot-task.jpg?fit=max\&auto=format\&n=Tv7Q0RwZX2L68I0t\&q=85\&s=396756af97174c54bf65c45d85b71a3c)

A demo request becomes a proposal. The card identifies the account and shows the exact change before confirmation.

The example changes 40 USDT to 30 USDT. A 25% reduction is different from setting the size to 25 USDT.

## Read the proposal

**1. Account and action**

Confirm the client, venue, market and strategy on the card. If the request is ambiguous, clarify it before continuing.

**2. Before and after**

Read the actual fields and values. A proposed change is not yet an applied change.

**3. Timing**

Read whether it runs once, later or over a period, including the displayed timezone and end time.

**4. Confirm**

Use the card's action, such as **Save & restart** for a settings change or **Confirm task** for other supported tasks.

**5. Follow the result**

Watch the task state and the Changes record. An accepted request still needs an execution result.

Owners and managers can use the web task controls within their account scope. Telegram access has its own permissions.

See [Queue and records](https://docs.ansio.trade/autopilot/records.md) for pausing, resuming and clearing tasks.


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