> For the complete documentation index, see [llms.txt](https://cube.ewelink.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cube.ewelink.cc/blog/faq-you-ask-we-answer.md).

# FAQ - You Ask, We Answer

We see many interesting questions coming from our users in the past months since CUBE OS v0.4 beta released - on Facebook, Discord, and different community groups. Some of you ask about hardware, some about compatibility, and others about the difference between CUBE OS and iHost. Instead of answering them one by one, we thought: why not make it easier for everyone?

That’s why we are starting **“You Ask, We Answer”**. Every two weeks, we will collect the most common questions from the community and share clear answers here. Our goal is simple: help more users understand CUBE OS without digging through endless documents or forum threads.

<figure><img src="https://67406449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnF8kmk9yw3yiy2mRerq%2Fuploads%2FfcO6unCRETAwwL3aD6JB%2F%E5%8F%8C%E5%91%A8%E7%AD%94%E7%94%A8%E6%88%B7%E9%97%AE%402x.png?alt=media&amp;token=94c63a44-7f9f-4009-8770-6f28c0375ff5" alt=""><figcaption></figcaption></figure>


---

# 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://cube.ewelink.cc/blog/faq-you-ask-we-answer.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.