> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/holoplot-control/getting-started.md).
# Getting started
HOLOPLOT Control is browser-based software designed to facilitate effortless setup, management, and operation of HOLOPLOT Sound Systems
{% hint style="success" %}
This documentation has been updated to reflect all changes and new features introduced in **HOLOPLOT OS 2.6**
{% endhint %}
HOLOPLOT Control Walkthrough
HOLOPLOT Control is browser-based software designed to facilitate effortless setup, management, and operation of HOLOPLOT sound systems, regardless of their design or size. It provides intuitive audio control functionalities, allowing users to seamlessly manage presets, adjust system gain, and monitor signal levels. Moreover, users can mute beams and access various environmental conditions with ease.
The platform has a public system API, enabling seamless integration with third-party show control systems. It also offers multi-user support, simplifying system setup through **Module Pairing**, and provides a 3D viewport for venue simulation. With its ability to accommodate complex network deployments and support standard audio protocols, HOLOPLOT Control is a versatile audio management and control tool.
---
# 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.holoplot.com/holoplot-control/getting-started.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.
