> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/colibri/publishing-and-delivery/publishing-options/mobile-and-desktop.md).
# Mobile and Desktop
Colibri exercises can be played on both **desktop and mobile**. In many cases, mobile may be the preferred option for self-paced exercises because participants can dip in and out as and when they please, even when they're on the go.
For players to access an exercise via mobile and desktop, you'll need to send your participants the link to your exercise. This link is your space URL. You can find this in the window that pops up after clicking `Run exercise` :
This URL can then be accessed via a browser on desktop and mobile.
---
# 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://helpdocs.conducttr.com/colibri/publishing-and-delivery/publishing-options/mobile-and-desktop.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.
