> For the complete documentation index, see [llms.txt](https://vigil-1.gitbook.io/vigil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vigil-1.gitbook.io/vigil-docs/closed-beta-guide/faq.md).

# FAQ

Common questions about the Closed Beta, funds, watches and support.

<details>

<summary>Is Vigil open to everyone?</summary>

Not yet. Vigil is invite-only during the Closed Beta. See [How to Join](/vigil-docs/closed-beta-guide/how-to-join.md).

</details>

<details>

<summary>What can Vigil trade today?</summary>

See the **Markets** section in [What Vigil Can Do](/vigil-docs/about-vigil/what-vigil-can-do.md).

</details>

<details>

<summary>Who controls my funds?</summary>

Your assets stay in your own wallet. Vigil has no pooled account and doesn't combine user funds.

</details>

<details>

<summary>Can Vigil withdraw or send my funds somewhere else?</summary>

No. Vigil has trading permissions only. There is no path for it to send your funds to another address.

</details>

<details>

<summary>Do I need to keep the app open?</summary>

No. Once you confirm a plan, the watch runs 24/7 whether the app is open or not.

</details>

<details>

<summary>Can Vigil trade without my approval?</summary>

No plan starts until you confirm its plan card. After that, it runs in the mode you chose: **Confirm** asks before every order, **Auto** acts inside your caps.

</details>

<details>

<summary>Can I change or stop a watch?</summary>

Yes, at any time. Edit, pause or stop it from the watch screen, or use **Pause all**. See [Managing Your Watches](/vigil-docs/closed-beta-guide/managing-your-watches.md).

</details>

<details>

<summary>What's the safest way to start?</summary>

Start with an **alert-only** plan. Then try a simple plan with a small size in **Confirm** mode. Don't start with complex, leveraged plans on day one.

</details>

<details>

<summary>Something looks broken. What should I do?</summary>

Report it right away with what you asked for, what you expected, what happened, when, and a screenshot. See [Feedback and Support](/vigil-docs/closed-beta-guide/feedback-and-support.md).

</details>

<details>

<summary>Is there a Vigil token?</summary>

Not yet. A Vigil token is planned for after the Beta. Access will cost 100 USDT worth of tokens per month, with 90% burned and 10% going to the project. See [Token Overview](/vigil-docs/token/token-overview.md).

Until we announce it on official channels, any token or contract claiming to be Vigil's is not from us.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vigil-1.gitbook.io/vigil-docs/closed-beta-guide/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.