> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/stagehand/stagehand-apprentice/installing-the-stagehand.md).
# Installing the Stagehand
The Stagehand Apprentice ships from the factory with top handles and rubber feet installed, making it a snap to set on any flat surface. No matter the mounting method, the Stagehand Apprentice should always be oriented horizontally.
## **Required Tools**
Before beginning any work assemble the following tools:
* 3/16β Hex Top handle scews ΒΌ-20 SHCS
* 9/64β Hex Case and Rack Bracket screws 8-32 SHCS
* 5/32β Hex Rubber Feet 10-32 SHCS
## Rack Mount
If you prefer to rack up your Stagehands all you need to do is install the included rack ears and install the Stagehand in a rack. The Stagehand must remain horizontal when in use, to maintain proper heat ventilation.
To rack mount the Stagehand Apprentice:
* Remove the four SHCS holding the two plastic handles on the top of the Stagehand\\
* Remove the four SHCS and rubber feet from the bottom of the Stagehand\\
* Install the rack ears on each side of the Stagehand with the included hardware, 3x SHCS per side.\\
* Secure the Stagehand in an equipment rack, keeping it horizontal
---
# 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.creativeconners.com/docs/stagehand/stagehand-apprentice/installing-the-stagehand.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.