> 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/how-to-join.md).

# How to Join

The Closed Beta is invite-only. Here's how invites work.

**The Vigil Closed Beta is invite-only.**

We're keeping the first group small. Right now, the quality of feedback matters more than the number of sign-ups.

## If you've been invited

You'll receive an invite link directly from the team, with any extra setup steps.

Go straight to [Quick Start](/vigil-docs/closed-beta-guide/quick-start.md).

## If you haven't been invited yet

{% stepper %}
{% step %}

### Follow Vigil and join the community

Invite waves are announced on X and in Telegram first. See [Community & Links](/vigil-docs/community-and-links/community-and-links.md). The team is active in the chat and notices who shows up.
{% endstep %}

{% step %}

### Ask a current Beta user

Once a Beta user is set up and active, they can invite a small number of people.
{% endstep %}
{% endstepper %}

## How invites grow

When a new user joins, connects their wallet and runs their first plan, they unlock a few invites of their own.

This is on purpose. We'd rather grow through traders bringing in traders they trust than through a long list of accounts that never run a plan.

**Who we're looking for:** people who already have a plan and want it carried out, day and night.

{% hint style="danger" %}
The team will **never** DM you first, ask for your seed phrase or private keys, or ask you to send funds to "unlock" access.
{% endhint %}


---

# 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/how-to-join.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.