> 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/exercise-editor/sidekick.md).
# Sidekick
Sidekick is a **AI-powered sidebar built into the Editor** and designed to streamline and speed up the designing process in Conducttr.
| Benefit | Feature |
| ----------------------------------------------------------------------- | -------------------------------------------------------------------- |
| No longer necessary to switch tools (Editor vs AI) | A permanent home for various AI assistants straight from the Editor |
| Less need to manually create injects one-by-one | Write directly into the MEL with LISA |
| Designers can move from raw ideas to working exercises faster than ever | Generate exercise ideas/injects/personas out of natural conversation |
### Where to find Sidekick & the Assitants
Sidekick is a **purple sidebar** on the left-hand side of the Editor with the "magic icon" (sparkles) at the bottom:
Assistants are AI helpers that make building and expanding exercises **as simple as having a conversation**.
{% hint style="warning" %}
Only LISA writes directly into the MEL. Other assistants output .csv files for import.
{% endhint %}
### :zap:Assistant sessions
Assistants remember requests only within the current exercises (until the **sessions expires after 60 days**, after which, the session cannot be recovered).
To start a new interaction with an assistant, a new exercise must be created. Assistant sessions are not copied when an exercise is duplicated.
---
# 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/exercise-editor/sidekick.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.
