> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/sharing-exporting-embedding/project-cloning.md).
# Project cloning
The **Cloning** feature adds a button to a shared project, allowing other Vectary users to duplicate the project into their own workspace.
This option is especially useful for templates, educational resources, or collaborative workflows where individual editable copies are needed.
The feature can be activated in the **Share settings** by enabling **Cloning**.
When enabled, a **Clone** button appears in the bottom-left corner of the viewer. Selecting it creates a complete copy of the project.
{% hint style="danger" %}
When a project is shared with **'Anyone with the link can clone this project'** enabled, it is automatically licensed under the Creative Commons [**“No Rights Reserved” (CC0)**](https://creativecommons.org/public-domain/cc0/) terms. This license permits commercial use of the cloneable public project, provided such use complies with the license terms.
To review this clause in detail, refer to the [Terms of Service](https://www.vectary.com/terms-of-service/).
{% endhint %}
---
# 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://help.vectary.com/documentation/sharing-exporting-embedding/project-cloning.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.
