Files
crewAI/docs/edge/en/enterprise/features/merged-step-card.mdx
Jesse Miller 5827abbc17
Some checks failed
CodeQL Advanced / Analyze (actions) (push) Has been cancelled
CodeQL Advanced / Analyze (python) (push) Has been cancelled
Check Documentation Broken Links / Check broken links (push) Has been cancelled
Vulnerability Scan / pip-audit (push) Has been cancelled
docs: nest One Card per Step under Crew Studio and drop rollout banner (AGE-107) (#6317)
The page itself already landed on main via #6247. This rebases onto main
and applies the two remaining changes:

- Nest crew-studio + merged-step-card into a collapsible "Crew Studio"
  nav group (pencil icon), across edge and v1.14.7 in en, pt-BR, ko, ar.
- Remove the temporary "Rolling out" Note banner (feature ships today).

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-24 13:36:49 -04:00

83 lines
3.8 KiB
Plaintext

---
title: One Card per Step
description: "Each step on the Studio canvas is a single card that combines the task and the agent that performs it."
icon: "layer-group"
mode: "wide"
---
## Overview
On the Studio canvas, each step of work is represented by a **single card**. The card combines two things that used to live in separate nodes:
- **The task** — what to do (name, description, expected output, and response format).
- **The agent** — who does it (the assigned agent, its model, and its tools).
An agent isn't an independent participant in your workflow — it's an attribute of the task: *which agent performs this work.* Putting the task and its agent on one card makes that relationship explicit and turns your automation into a single, left-to-right chain of work units that's easier to read at a glance.
<Frame caption="One card per step: the task with its assigned agent summarized in the footer.">
![Merged step cards on the canvas](/images/enterprise/merged-step-card-canvas.png)
</Frame>
## On the canvas
Each collapsed card shows:
- The **task name and description** at the top.
- A **footer summarizing the assigned agent** — avatar, name, model, and tools.
There's no separate agent node and no vertical agent → task edge. Your steps connect directly to one another in the order they run.
## In the editor
Open a card to edit it. The expanded view is the same card in a detailed state — not a different screen — organized into two clearly labeled sections.
<Frame caption="The expanded editor: the task section open, the agent summarized below it.">
![Expanded step editor](/images/enterprise/merged-step-card-editor.png)
</Frame>
### The task — what to do
Open by default, since this is what you usually edit:
- **Name**
- **Description**
- **Expected Output**
- **Response Format** — surfaced here because it controls exactly what downstream steps (such as routing) read from this step.
### The agent — who does it
The assigned agent is shown as a summary — **name, model, and tools inline**. Its deeper configuration is preserved behind two disclosures:
- **Role, goal & backstory**
- **Agent settings** — reasoning, max reasoning attempts, allow delegation, max iterations, and LLM settings.
<Tip>
An agent's full configuration — Role, Goal, Backstory, Model, Tools, LLM Settings, and the complete Agent Settings block — lives behind the **Role, goal & backstory** and **Agent settings** disclosures, organized by how often you edit it.
</Tip>
## Swapping vs. editing the agent
There are two distinct ways to work with the agent on a card, and they do different things:
- **Swap** reassigns *which* agent performs this task. Use the **Swap** control to pick a different agent from this project, choose one from your Agent Repository, or create a new agent. This is scoped to the task.
- **Editing** the agent — opening **Role, goal & backstory** or **Agent settings** — changes the agent *itself*.
<Frame caption="Swap changes which agent performs the task.">
![Swap agent panel](/images/enterprise/merged-step-card-swap-agent.png)
</Frame>
<Warning>
**Agents are reusable and shared.** The same agent can perform more than one task across your project. Editing an agent's role, backstory, or settings updates that agent **everywhere it's used** — not just on the card you opened. If you want a change to apply to only one step, **Swap** in a different agent instead of editing the shared one.
</Warning>
## Related
<CardGroup cols={2}>
<Card title="Crew Studio" href="/en/enterprise/features/crew-studio" icon="pencil">
Build automations with AI assistance and a visual editor.
</Card>
<Card title="Agent Repositories" href="/en/enterprise/features/agent-repositories" icon="users">
Manage and reuse agents across your automations.
</Card>
</CardGroup>