> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/project-activities/exercise-file-activities.md).
# Exercise file activities
When you open a project you'll see a list of exercises inside the project. These projects are all using the same project assets.
Click the three dots to the right of the exercise menu:
### Copy exercise vs Duplicate exercise
If you **copy** an exercise:
* A new project will be created with one exercise - the exercise you asked to copy. This exercise is now independent of the original project. So you can change assets without impacting other exercises.
* The new project will be labelled the same as the exercise and will be in the *Projects with no folder* folder
If you **duplicate** an exercise:
* The exercise you selected will be duplicated inside the same project
* You can make changes to the exercise, such as modifying the Master Events Lists (MELs), Pattern of Life (PoL), and/or Style, and those changes will be independent of the other exercises. But it's using the same project assets so changes to personas and media will impact the other exercises in this project.
---
# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/project-activities/exercise-file-activities.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.
