> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/essential-features/using-your-virtual-keyboard.md).
# Using your virtual keyboard
If you use a VR headset, the virtual keyboard is displayed when you need to enter text in the ENGAGE application.
* When the keyboard is beyond your reach, use the laser pointer from either controller to target a key, and then press the controller’s trigger to select the key.
* When the keyboard is within your reach, use your hand controllers to tap keys to select them . For more information, see [Using hand controllers to interact with your menu](/engage/essential-features/accessing-your-menu/using-hand-controllers-to-interact-with-your-menu.md).
* To submit the value in the currently active field, select 
.
* To close the keyboard, select 
, or select an area outside the bounds of the keyboard.
For more information about specific features of the virtual keyboard, see the following sections.
{% hint style="info" %}
When the keyboard is within your reach, you can also use the controller's trigger to select a key. Move the touch cursor on the controller over the key that you want to select, and then press the controller's trigger button.
{% 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://docs.engagevr.io/engage/essential-features/using-your-virtual-keyboard.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.