> For the complete documentation index, see [llms.txt](https://docs.replicacyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.replicacyber.com/user-guide/tasks-overview.md).

# Tasks Overview

### Using Tasks

Tasks can be **Agents**, which use AI to carry out a workflow, or **Workers**, which run predefined, non-agentic steps.

#### From Environments or Storage

In either card or table view, hover over the **Tasks** button and select an available workflow. The interaction is the same; the available tasks reflect the resource and its use case.

* **Environment Tasks** perform work that requires a Virtual Environment and its tools. Availability depends on task assignment and compatibility with the environment’s image.
* **Storage Tasks** perform work against data in the selected storage item, such as analyzing or processing files.

Click the **info icon** beside a task to open its Task Library details. When you close the detail view, the selected card or row and Tasks menu remain locked in place so you can continue from the same context.

#### From Quick Create

**Quick Create** creates environments with predefined tools and settings and limited user input. Most options use non-agentic workflows, but some also apply an agentic workflow during creation to prepare the environment.

These setups reduce manual configuration so you can get to an environment with the tools you need in a few clicks.

#### Following Agent Activity

The **Agent panel** shows agents started from **Environments** or **Storage**. It appears in the bottom-right corner with one-way updates about what the agent is doing.

When the task finishes, the panel reports completion and shows where to find its output, including downloadable files when provided.

Click **Mute** to keep receiving messages without the panel automatically opening for each update. You can also follow agent activity from the **Tasks Dashboard**, where the run and its history remain available after completion.

#### Tasks Dashboard

Open **Tasks** from the left-hand navigation to follow current activity and return to previous results. Runs are grouped by **Pending**, **Running**, **Completed**, and **Failed**.

Select a run to review its status, associated resource, latest update, and recorded activity.

* **Timeline** shows how the run progressed through its statuses.
* **History** provides recorded messages, progress updates, and output links when available.
* **Output** appears when the run provides files and lets you download them.
* **Details** provides additional information about the run.

The Tasks Dashboard is where runs persist. You can return days or weeks later to review agent activity or download files created by an Agent or Worker. Failed runs also remain available for reviewing their recorded activity and output.

If a run gets stuck in **Pending** or **Running**, locate it in the Tasks Dashboard and use its delete action to remove it.

#### Task Library

Open **Task Library** from the left-hand navigation to browse Agents and Workers in grid or list view. Select a task to understand what it does and what to expect before starting it.

Task details can include:

* **What It Does** and **How It Works**: The workflow’s purpose, behavior, and any preparation needed.
* **Task Type and Execution Model**: Whether it is an Agent or Worker and how it runs.
* **Assignment and Supported Images**: Who the task is available to and which environment images it supports.
* **Input and Output**: Required inputs and the results or files the task is expected to produce.

Task Library provides workflow information. Start tasks from **Environments**, **Storage**, or **Quick Create**, and use **Tasks Dashboard** to review their progress and results.

#### Help Shape What Comes Next

The current Agents and Workers showcase what is possible. Your ideas will help shape what comes next—from automating repetitive work to preparing an environment with everything your team needs.

We’re excited to hear what would make the biggest difference in your work. Contact **Replica Support** or your **Sales Engineer** with your ideas, feedback, or requests to improve an existing workflow.

Tell us what you want to accomplish, the tools or data involved, and the result you need. You do not need a finished technical plan—the Replica team can help you explore the possibilities.

Creating and editing Agents directly in the app is planned for a future version. Until then, bring us your ideas so we can build toward the workflows that matter most to you.


---

# 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://docs.replicacyber.com/user-guide/tasks-overview.md?ask=<question>&goal=<user_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.
