> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/remix-a-mission-shared-with-you.md).
# Remix a Mission shared with you
Make your own editable copy of a Mission someone shared with you, then publish, run and schedule it.
A Mission that someone shares with you is view-only: you can look at it, but you can't change it. **Remix** saves your own draft copy of the Mission. You can change the copy, publish it and schedule it. The owner's Mission stays as it is.
You can select **Remix** from:
* the three-dot menu on the Mission's card in the Mission Library. See [Mission cards](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/mission-library-and-mission-page#mission-cards).
* **More options** on the Mission's page. See [More options](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/mission-library-and-mission-page#more-options).
* the Mission pane header, after you select **Configure** on the Mission's page.
**Remix** appears only on Missions shared with you, and only if your role lets you create Missions. Owners don't see it. They use **Create Draft Copy** or **Duplicate** instead.
Watch a one-minute walkthrough, or follow the steps below.
{% embed url="" %}
To remix a Mission:
1. Select **Remix**. Tellius saves a copy of the Mission as a draft that you own. Your copy starts in a new, empty conversation. Kaiya keeps the earlier requests that shaped the Mission as background, so you can ask for changes right away, but they don't appear in the copy's chat. Other messages, files, Missions and Apps from the original conversation don't come along. You can keep changing the copy with Kaiya without affecting the original.
2. A **Mission remixed** message confirms that your copy is saved as a draft and must be published before it can run or be scheduled. Tellius doesn't move you to the copy, so you stay where you are. The copy is named after the original with "(Remix)" at the end, and starts as version V1 in Draft.
3. Select **Open copy** in the message to open your copy. A copy that has a conversation opens in that conversation, where you can review and change it with Kaiya.
4. Check the steps and the preview, then publish the copy. See [Step 4: Publish the Mission](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission#step-4-publish-the-mission).
5. Run the copy, or set up a schedule for it. See [Step 5: Run/Schedule the Mission](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission#step-5-run-schedule-the-mission).
If Tellius can't make the copy, a message says why, for example when your role doesn't allow it.
{% hint style="info" %}
**When to remix:** remix when you want your own version of a shared Mission, for example for a different region or audience, that you run and schedule yourself. Your copy is separate from the owner's Mission. If you only need to read the owner's results, you don't need a copy.
{% 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.tellius.com/tellius-6.4/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/remix-a-mission-shared-with-you.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.
