> ## Documentation Index
> Fetch the complete documentation index at: https://docs-eos.fpt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Digital Worker details

> The parts a Digital Worker is made of, and what each one decides

Clicking a Digital Worker in the list opens its own page. On the **Digital Worker builder** tab, the left column lists the parts that make up the Digital Worker, while the right column gives you a quick read on how it is currently configured.

![Agent details](https://mintcdn.com/fpt-15dbd015/ZZ_AlSQhekpFaExV/images/eos/en_agent_details.jpg?fit=max\&auto=format\&n=ZZ_AlSQhekpFaExV\&q=85\&s=20bd30eeaf35bf9ecd6b9d50e4f186b1)

## The parts of a Digital Worker

| Component | What it decides |
| - | - |
| [**Instructions**](https://docs-eos.fpt.ai/eos/en/instructions.md) | Who the Digital Worker is, what it can do, in what order it works and how it speaks |
| [**Model**](https://docs-eos.fpt.ai/eos/en/model.md) | The brain behind the Digital Worker - reasoning ability, context length and cost |
| [**Skills**](https://docs-eos.fpt.ai/eos/en/skills.md) | Repeatable jobs packaged up for the Digital Worker to reach for at the right moment |
| [**Knowledge bases**](https://docs-eos.fpt.ai/eos/en/knowledge.md) | Which documents the Digital Worker may read when it answers |
| [**Connections**](https://docs-eos.fpt.ai/eos/en/connections.md) | Which systems the Digital Worker may read from and write to, and under whose account |
| [**Guardrails**](https://docs-eos.fpt.ai/eos/en/guardrails.md) | What the Digital Worker must not do, and which actions need a human to approve |
| [**Digital Worker capabilities**](https://docs-eos.fpt.ai/eos/en/agent-capabilities.md) | Which of the Digital Worker's ten built-in capabilities (long-term memory, web search, code execution and so on) it is allowed to use |

Each part has its own page in this section.

## The publish readiness bar

At the bottom of the left column, a bar tracks whether the Digital Worker has everything it needs: Instructions written, a model chosen, tools attached, guardrails configured and a test run completed. Treat it as a suggested route, not a hard requirement.

> [!NOTE]
>
> **Triggers** is still marked *Coming soon* - it will be documented once it goes live.

## Conversation history of a Digital Worker

History now belongs to the Digital Worker itself. A Digital Worker shared on a Workspace keeps every conversation under that Digital Worker, so you can read them all back no matter which Workspace the Digital Worker was opened from.

Open the Digital Worker, go to the **Analytics** tab and click **History**.

![Conversation history of an agent](https://mintcdn.com/fpt-15dbd015/ZZ_AlSQhekpFaExV/images/eos/en_agent_history.jpg?fit=max\&auto=format\&n=ZZ_AlSQhekpFaExV\&q=85\&s=c7c4008a4389d83ed8672f444aafb1d7)

The list has these columns:

| Column | Meaning |
| - | - |
| **End time** | When the conversation ended |
| **Conversation ID** | The identifier used to search and to raise a support ticket |
| **Channel** | Where the conversation came from: Workspace, Test, Web, API, Zalo, Teams or Scheduled |
| **User** | Who was talking to the Digital Worker |
| **Messages** | How many messages the thread holds |

Above the list, **All channels** narrows the view to one channel and **All time** sets the period. The search box takes message content, a sender name, a conversation ID or a message ID.

### Reading one conversation

Click any row and **Conversation details** opens on the right with the whole thread in order. Steps where the Digital Worker called a tool appear as **Tool call** entries, so you can see what it looked up before it answered.

![Conversation details](https://mintcdn.com/fpt-15dbd015/ZZ_AlSQhekpFaExV/images/eos/en_agent_history_detail.jpg?fit=max\&auto=format\&n=ZZ_AlSQhekpFaExV\&q=85\&s=3f1c4c5653b7ac1a8a1d49000efc3623)

> [!NOTE]
>
> History is read only: This screen does not edit or delete conversations. **Performance**, the other item on the Analytics tab, is still in development and will arrive later.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.