Skip to content

Clarify member overrides in squad versioning docs #1300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bets-margulies-vapi merged 1 commit into from
Oct 8, 2026
Merged

Clarify member overrides in squad versioning docs #1300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions fern/assistants/versioning/versioning-with-squads-and-assistants.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,12 @@ A squad version saves the squad's configuration:

- The squad name
- The members, in order
- Each member's assistant version: a pinned version, such as **v3**, or **Latest**.
- Everything you configure for a member in the squad builder, such as its model, voice, tools, and handoffs
- Each member's assistant version: a pinned version, such as **v3**, or **Latest**.
- Member overrides that you configure in the squad builder, such as a member's model, voice, tools, and handoffs
- Squad-level overrides that apply to all members
- Transient assistants defined inside the squad
- Overrides that apply to all members

Member overrides apply only when the assistant runs in this squad. They don't change the assistant itself.

The assistant's own configuration, including its tools, belongs to the [assistant version](/assistants/versioning/versioning-assistants). You change it in the assistant editor, and the squad uses it through the member's pinned or **Latest** setting.

Expand All @@ -26,11 +28,11 @@ The assistant's own configuration, including its tools, belongs to the [assistan
| --- | --- |
| You create a squad | Yes, `v1` |
| You add or remove a member and save | Yes |
| You change a member's tools, handoffs, or other settings in the squad builder and save | Yes |
| You pin a member to an assistant version, change the pin, or set it back to **Latest**, and save | Yes |
| You create member overrides by changing a member's tools, model, handoffs, or other settings in the squad builder and save | Yes |
| You edit an assistant's draft, such as its tools, prompt, or model, in the assistant editor | No |
| An assistant in the squad publishes or restores a version, including changes to its tools | No |
| A tool used by an assistant in the squad publishes a version | No |
| You edit an assistant's draft | No |

A squad that existed before squad versioning was enabled for your organization gets its first versions the next time you save it: the existing configuration becomes `v1` and your changes become `v2`.

Expand Down Expand Up @@ -117,7 +119,7 @@ To make a squad version run the same configuration every time, pin each member,
- **Inbound calls** use the squad's current version.
- **Outbound calls** use the current version by default. To use a specific version, pass `squadVersion` with `squadId` in the [create call request](/api-reference/calls/create).

A call that uses an earlier squad version runs that version's members and pins. Members set to **Latest** use each assistant's current version.
When a call uses an earlier squad version, it runs the squad as it was saved in that version: the same members, member overrides, and pinned assistant versions. Members set to **Latest** are the exception. They use each assistant's current published version, not the version that was current when you saved the squad version.

## Next steps

Expand Down
Loading