> For the complete documentation index, see [llms.txt](https://ayakaleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ayakaleaf-pro.ayaka.space/on-premises/installation/using-the-toolkit/1.-download-the-toolkit.md).

# 1. Download the Toolkit

### Downloading the Toolkit <a href="#downloading-the-versions-toolkit-short" id="downloading-the-versions-toolkit-short"></a>

The Toolkit is compatible with both the Server CE and Overleaf Pro and is the recommended installation method. Using the Toolkit will allow you to easily get started with Server CE and seamlessly upgrade to Overleaf Pro if required.

{% hint style="info" %}
[ayaka-notes/toolkit](https://github.com/ayaka-notes/toolkit) is modified to use overleaf-pro image from ghcr directly. Also with texlive provided by ayaka-notes. But you can download official overleaf-toolkit.
{% endhint %}

{% stepper %}
{% step %}

### Clone the Overleaf Toolkit repository

To install the toolkit you'll need to navigate to the intended installation path and then clone the Overleaf Toolkit (@Ayaka-notes) GitHub repository using this command:

{% code title="Clone repository" overflow="wrap" %}

```bash
git clone https://github.com/ayaka-notes/toolkit.git ./overleaf-toolkit
# official toolkit (Not Recommend)
# git clone https://github.com/overleaf/toolkit.git ./overleaf-toolkit
```

{% endcode %}

{% hint style="info" %}
To prevent any potential permissions issues we recommend installing the Toolkit in your user's `$HOME` directory.
{% endhint %}
{% endstep %}

{% step %}

### Change into the toolkit directory

Wait for the cloning process to complete then let's switch into the newly created `overleaf-toolkit` directory:

{% code title="Change directory" %}

```bash
cd ./overleaf-toolkit
```

{% endcode %}
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ayakaleaf-pro.ayaka.space/on-premises/installation/using-the-toolkit/1.-download-the-toolkit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.