> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/greyt/greyt-telescope/general-info/configurations.md).
# Configurations
The GreyT Telescope can be assembled in two different configurations, with each having a different way for running the string.
Like the name implies, the Internal String configuration runs the string through the center of the telescope. This gives the string more protection since it is inside the stages, and also leaves more room open around the telescope for other mechanisms.
{% tabs %}
{% tab title="1 Stage" %}
Internal String Run
{% endtab %}
{% tab title="2 Stage" %}
Internal String Run
{% endtab %}
{% tab title="3 Stage" %}
Internal String Run
{% endtab %}
{% tab title="4 Stage" %}
Internal String Run
{% endtab %}
{% endtabs %}
The External String configuration runs the string outside the telescope. While this does not provide as much protection for the string, it does allow for easier assembly and maintenance of the system. Additionally, since the base stage sits lower in the flipped gearbox, this configuration also allows for longer stages, meaning more stroke for the same height telescope.
{% tabs %}
{% tab title="1 Stage" %}
External String Run
{% endtab %}
{% tab title="2 Stage" %}
External String Run
{% endtab %}
{% tab title="3 Stage" %}
External String Run
{% endtab %}
{% tab title="4 Stage" %}
External String Run
{% endtab %}
{% endtabs %}
---
# 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.wcproducts.com/welcome/greyt/greyt-telescope/general-info/configurations.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.
.svg?alt=media&token=2afdb217-eb72-4f78-89a0-4e9bdc19fe30)
.svg?alt=media&token=d4718d18-ddd9-416d-b55c-6aa33818c4d3)
.svg?alt=media&token=2d8c11c6-809a-4fe3-b069-ba6910072cd1)
.svg?alt=media&token=9f8a21f8-8b01-4222-ab15-7adddb208f63)