> For the complete documentation index, see [llms.txt](https://cleyrop.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cleyrop.gitbook.io/docs/documentation-fr-en/data-and-ai-project/studio-ai/agents.md).

# Agents

Agents are ready-to-use configurations that define the behavior of an artificial intelligence for a specific use case. Each Agent brings together a structured prompt and a selection of Apps from The Factory. This approach makes it possible to create specialized AI capabilities while making them easier to reuse and share within your organization.

Agents are used directly in the Druide and can be shared with other users.

## Create an Agent

**Purpose** : Define a reusable AI capability tailored to a specific business need.

**Creation steps**

1. Access your project's AI Studio
2. Click the tab **Agent**
3. Click **Create an Agent**
4. Fill in the metadata:
   * **Name** : choose a clear name (required)
   * **Description** : describe the Agent's purpose (optional)
   * **Icon** : select an icon to make identification easier
5. Configure the **Instructions** :
   * Write the prompt that will define the AI's behavior
   * Use the pre-filled example as a starting point
6. Select the **Apps** :
   * Choose one or more tools from The Factory
   * Only deployed tools are available
   * Select the Tool **Cleyrop Dataset** to add one or more datasets to your knowledge scope
7. Add a knowledge scope:
   * If the Tool **Cleyrop Dataset** was selected in the previous step, choose one or more **datasets** from those available in the project.
   * Upload one or more files as knowledge sources
   * These files are kept in the Agent and accessible to all project members who have access to the Agent
   * Supported formats: `.txt`, `.pdf`, `.docx`, `.pptx` 
8. Click **Save** or **Publish** according to your needs

{% hint style="warning" %}
If an associated dataset becomes unavailable (deletion, loss of access), a clear status is displayed and it is immediately removed from the active knowledge scope.
{% endhint %}

<figure><img src="/files/6b7574385e780444d1477c9741fae93271587e0d" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/08c60b36d325a7ea0907136c11b375afef41780f" alt=""><figcaption></figcaption></figure>

**Good to know**

* An Agent saved without publication is created with the status **Test** and remains usable by all project members
* The Agent is automatically attached to the current project
* No dedicated assistant is created when an Agent is created

## Use an Agent

<figure><img src="/files/bf1c09fea3ea957e50092cc7dcddb215e2d048e5" alt=""><figcaption></figcaption></figure>

### **From the project**

All project members can use the available Agents, whether they are in Test or Published status.

1. Go to the Druide
2. Select the desired Agent from the list of available agents
3. Start your conversation

{% hint style="info" %}
Only one Agent can be active at a time. Activating it disables the Druide's generic context. Associated Apps are enabled by default. To return to the Druide's generic behavior, leave the active Agent.
{% endhint %}

### **From My Apps**

If an Agent has been shared with you by another project:

1. Go to **My Apps**
2. Identify the Agent in the listing
3. Click **Use** to open the Druide with the agent activated

### **Add attachments**

During a conversation with an active Agent, you can occasionally enrich your exchange by adding files via the button **Attachments**.

* The files are used by the AI for the current conversation only
* They do not modify the Agent's configuration and are not visible to other users
* Supported formats: `.txt`, `.pdf`, `.docx`, `.pptx`
* 5 MB max per file

{% hint style="info" %}
Attachments are different from the knowledge scope: they are temporary and limited to the current conversation. To permanently enrich an Agent, add files via the knowledge scope during creation.
{% endhint %}

### **Conversation history**

Each Agent has its own conversation history, isolated from the Druide's generic context and other Agents.

* Conversations started in an Agent are only visible from that agent
* Changing Agents automatically creates a new conversation; it is not possible to resume an existing conversation when changing agents
* Deleting an Agent makes its conversations inaccessible
* Revoking a share prevents access to the conversations associated with the Agent

{% hint style="info" %}
Switching an Agent from Test to Published does not modify existing conversations.
{% endhint %}

### **View Agent details**

To better understand an Agent's capabilities:

1. From the AI Studio or My Apps, click the button **Information** on the Agent card. From a conversation with an active Agent, click **Open the information panel** next to the Agent's name.
2. Consult the available tabs:
   * **Information** : name, description, owner, instructions
   * **Tools** : list of associated tools and their status
   * **Sharing** : users who have access to the Agent

{% hint style="info" %}
If an Agent uses Tools that require environment variables (API keys, tokens), you must configure them in The Factory before you can use these tools. For users who only have access to the Druide, environment variable configuration is available directly from the interface via the list of Tools.
{% endhint %}

## Manage Agents

### Edit an Agent

Only the Agent owner can edit it.

1. From the AI Studio, access the Agent's details
2. Click **Edit**
3. Modify the desired items (name, description, instructions, Tools)
4. Click **Save** to apply the changes

{% hint style="info" %}
The changes do not affect ongoing conversations but apply to the **new messages** in resumed conversations.
{% endhint %}

## Publish an Agent

Publication indicates that the Agent has been tested and validated, and can be used with confidence.

1. From the AI Studio, access the details of the Agent in Test status
2. Click **Publish**
3. Confirm publication

The status changes to **Published** but the access rules and behavior of the Agent remain unchanged.

## Delete an Agent

Only the owner can delete an Agent. This action is irreversible.

1. From the AI Studio, access the Agent's details
2. Click **Delete**
3. Confirm deletion

{% hint style="warning" %}
Deletion makes the Agent immediately inaccessible to all users and removes access to associated conversations
{% endhint %}

## Share an Agent

#### Share with members outside the project

Project members can share an Agent with other Cleyrop users not part of the project.

1. From the AI Studio, click the action **Share** on the Agent card
2. Select one or more Cleyrop members
3. Confirm the share

The selected users will be able to:

* See the Agent in **My Apps**
* Use it in their Druide
* View its information read-only

They will not be able to edit it, republish it, or share it themselves.

#### Remove a share

1. Go to the Agent details
2. In the **Sharing**, identify the user concerned
3. Click **Remove access**
4. Confirm revocation

The Agent immediately disappears from the user's space **My Apps** and can no longer be used.

## Rights and responsibilities

#### Agent owner

The creator of an Agent automatically becomes its owner. They can:

* Edit the Agent
* Publish or unpublish the Agent
* Share the Agent with other users
* Delete the Agent

#### Project members

Project members (PM, Data Worker) can:

* View all project Agents
* Use all Agents (Test or Published)
* Share Agents with members outside the project

#### Users outside the project

Users with whom an Agent has been shared can:

* View the Agent's information read-only
* Use the Agent in their Druide

#### Ownership transfer

The owner of an Agent or the project owner can change the Agent owner.

1. Go to the Agent details
2. Click **Change owner** (next to the current owner's name)
3. Select a new owner from among the project members
4. Confirm the transfer

The new owner immediately has all management rights. The former owner retains the rights associated with their project role.

**Good to know** : when a user who owns Agents is deleted or deactivated, those Agents are automatically transferred to the project owner.

***

### Best practices

* **Name your Agents explicitly** : use names that clearly reflect the business use case (e.g., "Support ticket analysis", "Financial report generation")
* **Document your instructions** : write precise, structured prompts to ensure consistent behavior
* **Test before publishing** : use Test status to validate the Agent's behavior before marking it as Published
* **Limit the number of Tools** : select only the tools you need to avoid unnecessary complexity
* **Share selectively** : share agents only with users who truly need them
* **Check environment variables** : make sure users have the required API keys before sharing an Agent that uses external tools