> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://support.atomicwork.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://support.atomicwork.com/_mcp/server.

# Improving AI Coworker performance

> Review suggestions in the Performance tab of an AI Coworker, apply a change to its latest draft, and dismiss suggestions you don't need.

After an AI Coworker such as Atom, AccessOps, CloudOps, or DeviceOps has been running in production, open its **Performance** tab to review suggestions based on those runs. You can apply a suggestion to the coworker's latest draft, or dismiss it.

To open a coworker, go to **AI Workforce > AI Coworkers** and select it. The coworker page includes **Overview**, **Configuration**, **Instructions**, **Skills**, **Tools**, **Budget**, **Runs**, **Performance**, and **Evals**.

## Suggestions

Suggestions appear in the **Performance** tab. The left of the tab lists three queues:

* **All** — every suggestion for this coworker.
* **Recommended** — suggestions that still need a decision.
* **Reviewed** — suggestions you have applied or dismissed.

The table columns are **Recommendation**, **Status**, **Based on**, and **Created at**. **Based on** lists the run IDs the suggestion was learned from. Status values captured in the product are **Needs review** and **Applied**.

![The Performance tab of a CloudOps Manager coworker, open on the Recommended queue, with four suggestions that need review.](/_fern-files/_img/634de0b05ca67fba96567da5d13e99efbd38051f2341f5776897f56baedb6abd.webp)

If nothing has been surfaced yet, **Recommended** shows **Nothing to review yet**. The supporting copy is: "As this coworker runs, we'll surface ways to improve it here for your review."

![The Recommended queue empty state, with the message Nothing to review yet.](/_fern-files/_img/7d756f76eb40642e0da68f8af6e78e57404683e319f19afac294d87dfda5911e.webp)

**Reviewed** uses **Nothing reviewed yet**, with the copy: "Recommendations you accept or dismiss will show up here."

### Review a suggestion

A suggestion opens in a panel on the right. The heading names the kind of change. The kinds captured in the product are:

* **Edit voice** — a change to the coworker's **Voice** instructions.
* **Edit goal** — a change to the coworker's **Goal**.
* **Needs a person** — a change a person needs to make outside the coworker, such as connecting a server in the **MCP store**.

The panel includes:

* **What needs to change** — a short description of the problem and the proposed fix.
* **The change we drafted** — for **Edit voice** and **Edit goal**, the drafted edit, with **Unified** and **Split** views of the diff. A footer line such as **Adds 1 line to your draft · Voice** summarises the edit.
* **Why this suggestion?** — the reasoning, including the runs it was learned from.

![A suggestion panel headed Edit voice, showing what needs to change, a drafted Voice diff, why the suggestion was made, and Apply to draft.](/_fern-files/_img/22e82f55049af073240665cd60742a7e30da5a9c48e321ab2370ba944d161b20.webp)

1. Open the AI Coworker and select the **Performance** tab.
2. Open **Recommended** (or **All**) and select a suggestion.
3. Read **What needs to change**, **The change we drafted**, and **Why this suggestion?**
4. For an **Edit voice** or **Edit goal** suggestion, select **Apply to draft** to write the change into the coworker's latest draft, or **Dismiss** to decline it. Use the arrows at the top of the panel to move between suggestions.
5. For a **Needs a person** suggestion, the primary action is **Go to MCP**, not **Apply to draft**. Use it when the change is to connect something in the **MCP store**. You can still **Dismiss** the suggestion.

![A Needs a person suggestion that asks a workspace admin to connect PagerDuty in the MCP store, with Dismiss and Go to MCP actions.](/_fern-files/_img/011edd363fd3ab86af5e00d3e022b7d91d11fe6d1fe6e2b0a3934aa681bac5aa.webp)

> **Note**
>
> When you apply a suggestion, its changes are applied to the AI Coworker's latest draft. The current version of the coworker stays in place until you take that draft forward.

After you apply a suggestion, its **Status** becomes **Applied**, and it moves to the **Reviewed** queue.

![The All queue after a Voice suggestion was applied. The applied row shows a green Applied status; the other suggestions still need review.](/_fern-files/_img/8bd67009d154eab150dd4af4c48d0888340dad82360da4aef999b9b331022cf1.webp)

Switching to the **Reviewed** queue shows all suggestions you have acted on — applied or dismissed.

![The Reviewed queue with suggestions that have been applied or dismissed.](/_fern-files/_img/cc95bd838ddcec62e6f35cca566737d92f250de12119c6bd36b7663c9753574c.webp)

You can confirm the draft in **Version histories**. In the capture, applying a Voice suggestion created **V2** with a **Draft** badge, while **V1** remained the **Current version**.

![Version histories after a suggestion was applied, showing V2 as a Draft and V1 as the Current version.](/_fern-files/_img/d744b4e7b9ca02ff2cbd24c70fc441ef2970f20c63fdd466e599980c2ff259e0.webp)

## Behaviors and performance suggestions

> **Note**
>
> **Behaviors** are checks you define on each eval scenario — plain-language statements of how the coworker should act in a given situation. When a behavior drifts (the coworker stops passing a check it used to pass), that drift can surface as a suggestion in the Performance tab. To define and test behaviors, see [Behaviors](https://support.atomicwork.com/documentation/ai-workforce/evals#behaviors) in the Evals article.

## FAQs

1. **What happens when I apply a suggestion?**
   Applying a suggestion applies its changes to the coworker's latest draft. The current version stays in place. In **Version histories**, the new draft is listed with a **Draft** badge, and the live version keeps the **Current version** badge.

2. **What kinds of suggestions appear in Performance?**
   The suggestions captured in the product edit the coworker's **Voice** or **Goal**, or ask a person to make a change outside the coworker (for example, connecting a server in the **MCP store**). A **Needs a person** suggestion uses **Go to MCP** rather than **Apply to draft**. Suggestions can also originate from behavior drifts caught during evals.

3. **What is the difference between Recommended and Reviewed?**
   **Recommended** holds suggestions that still need a decision (**Needs review**). After you apply or dismiss a suggestion, it appears in **Reviewed**. **All** shows the full list.

## Related articles

* [Evaluating AI Coworkers](https://support.atomicwork.com/documentation/ai-workforce/evals)
* [Understanding how AI Coworkers run](https://support.atomicwork.com/documentation/ai-workforce/understanding-how-ai-coworkers-run)
* [Setting up an AI Coworker](https://support.atomicwork.com/documentation/ai-workforce/setting-up-an-ai-coworker)
* [Workforce roles and permissions](https://support.atomicwork.com/documentation/ai-workforce/workforce-roles-and-permissions)