> For the complete documentation index, see [llms.txt](https://hokas.gitbook.io/hokas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hokas.gitbook.io/hokas-docs/how-do-i-deploy-my-discord-bot.md).
# How do I deploy my Discord bot?
After deploying our server, we go to the **Manage** page. (If you’re not sure how to deploy your server, you can find out by [clicking here](/hokas-docs/how-can-i-deploy-a-server.md))
Next, in the Command Builder section, select the package you are going to download and enter the name and extension of the file you wish to run. Then click the **Build Command** button.
Next, we click the **Save** button to save the command, then click the **Run Now** button to run it.
You can then check whether the packages have been downloaded and whether the command has run via the Console section on the Overview page.
---
# 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://hokas.gitbook.io/hokas-docs/how-do-i-deploy-my-discord-bot.md?ask=&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.
