Skip to content

Commit ab23b8f

Browse files
committed
second pass
1 parent f2a0de3 commit ab23b8f

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

fern/squads.mdx

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ subtitle: Use Squads to handle complex workflows and tasks.
44
slug: squads
55
---
66

7-
Squads let you break complex workflows into multiple specialized assistants that hand off to each other during a conversation. Each assistant in a Squad handles a specific part of your workflow—like one assistant for lead qualification that transfers to another for appointment booking.
7+
Squads let you break complex workflows into multiple specialized assistants that hand off to each other during a conversation. Each assistant in a Squad handles a specific part of your workflow; for example, one assistant for lead qualification that transfers to another for appointment booking.
88

99
**Why use Squads?** Large, all-in-one assistants with lengthy prompts and extensive context lead to:
10-
- **Higher hallucination rates** - Models lose focus with too many and sometimes conflicting instructions
10+
- **Higher hallucination rates** - Models lose focus with too many and potentially conflicting instructions
1111
- **Increased costs** - Longer prompts consume more tokens per request
1212
- **Greater latency** - Processing large contexts takes more time and will increase the latency of your assistant.
1313

@@ -20,14 +20,14 @@ Squads solve this by splitting complex prompts into focused assistants with spec
2020
## Usage
2121

2222
To use Squads, you can create a `squad` when starting a call and specify `members` as a list of assistants and destinations.
23+
24+
<Info>
2325
The first member is the assistant that will start the call, and assistants can be either persistent or transient.
26+
</Info>
2427

2528
We recommend using [Handoff Tools](/tools/handoff) to specify which destinations the current assistant can handoff too, and when to handoff to each assistant. Each assistant within the squad can use its saved handoff tools as well as handoff tools from Assistant Overrides (see below).
2629

2730

28-
<!-- Each assistant should be assigned the relevant assistant transfer destinations.
29-
Transfers are specified by assistant name and are used when the model recognizes a specific trigger. -->
30-
3131
```json
3232
{
3333
"squad": {
@@ -137,6 +137,9 @@ You may also define inline tools via assistant overrides through the `model` obj
137137

138138
### Member Overrides
139139
To override the configuration of _all_ assistants without modifying the underlying assistants, use the `memberOverrides`.
140+
<Info>
141+
Note: This is `squadOverrides` for [`assistant-request`](api-reference/webhooks/server-message#response.body.messageResponse.AssistantRequest.squadOverrides)
142+
</Info>
140143

141144
```json
142145
{

0 commit comments

Comments
 (0)