> 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/experience-editor/user-interface/the-editor-panel/interacting-with-the-editor-panel.md).

# Interacting with the editor panel

## Interacting with the editor panel on a desktop device

* On a desktop device, left click to select items in the editor panel.

## Interacting with the editor panel on a VR headset

When you use hand controllers, you can choose between tap to select or a laser pointer. Tap to select is the same interaction that you use with your tablet in ENGAGE. The laser pointer is the same interaction that you use to interact with menus in ENGAGE.

![Tap to select interaction (left) and laser pointer interaction (right)](https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-a6da81fbd4e385d487391ef853f9ead800ac5bab%2Fvr_editor_interactions.jpg?alt=media)

To switch between interaction methods, select the icon to the left of the curves icon, as highlighted in the previous image. A hand icon indicates tap to select mode and a mouse cursor icon indicates the last pointer mode.


---

# 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/experience-editor/user-interface/the-editor-panel/interacting-with-the-editor-panel.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.