> 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/cube-os-es/blog/preguntas-frecuentes-tu-preguntas-nosotros-respondemos.md).
# Preguntas frecuentes - Tú preguntas, nosotros respondemos
Hemos visto muchas preguntas interesantes de nuestros usuarios en los últimos meses desde que se lanzó la versión beta CUBE OS v0.4: en Facebook, Discord y distintos grupos comunitarios. Algunos preguntan sobre hardware, otros sobre compatibilidad y otros sobre la diferencia entre CUBE OS e iHost. En lugar de responder una por una, pensamos: ¿por qué no facilitarlo para todos?
Por eso estamos iniciando **“Tú preguntas, nosotros respondemos”**Cada dos semanas recopilaremos las preguntas más comunes de la comunidad y compartiremos respuestas claras aquí. Nuestro objetivo es simple: ayudar a más usuarios a entender CUBE OS sin tener que indagar entre documentos interminables o hilos de foro.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cube.ewelink.cc/cube-os-es/blog/preguntas-frecuentes-tu-preguntas-nosotros-respondemos.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.