> 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/player-guide/virtual-desktop.md).
# Virtual Desktop
The Virtual Desktop is the player-facing interface wherein the exercise takes place. It is designed to look and feel like a familiar digital workspace, immersing players in a crisis scenario as if it were taking place in real time.
All injects, channels, and persona interactions are delivered here, creating a **safe but realistic training environment**.
Players (i.e. the training audience) can interact with your exercise via any device with a web browser. After log in they'll see the Virtual Desktop.
{% hint style="info" %}
Note that **all the channels are configurable by the designer**. They design which channels to use, how they should be named and what icon should represent them and more.
{% endhint %}
### Multi-channel exercise
In the Virtual Desktop, you'll be working in a multi-channel exercise meaning that **communications will come at you via various applications** as it does in real life.
Every time you see a **red flashing dot** that means you have a notification, indicating new information to check in a channel.
{% hint style="info" %}
Note that the icons you see might be different from those shown above because the designer of the exercise is able to **customise and configure the interface**. Even if the icons and images are different, it will work the same way as described in these articles.
{% 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://helpdocs.conducttr.com/player-guide/virtual-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.
