[fern-api]

Automated SDK generation by Fern

---

✅ Customizations automatically preserved, but 14 files need your attention.

Action required: 14 files with unresolved customization conflicts

The new generation changed code you previously customized. Non-conflicting customizations have been applied automatically. The following files need manual resolution:

File	Your customization	Why it conflicted
Cargo.lock	fix(deps): patch two advisories; keep the verification script	The new generation changed the same lines you edited
Cargo.lock	Alpha build	The new generation changed the same lines you edited
Cargo.toml	Alpha build	The new generation changed the same lines you edited
dist-workspace.toml	Customer customizations (composite)	This customization was from a previous generation
Cargo.lock	feat: tag CLI requests with the command that made them (#132)	This customization was from a previous generation
Cargo.toml	feat: tag CLI requests with the command that made them (#132)	The new generation changed the same lines you edited
Cargo.lock	feat: Make intent mandatory for agents (#148)	This customization was from a previous generation
Cargo.toml	feat: Make intent mandatory for agents (#148)	This customization was from a previous generation
Cargo.lock	Make intent optional (#150)	This customization was from a previous generation
Cargo.lock	feat: add onboard init, connect, check and test for agent-led setup (#154)	This customization was from a previous generation
Cargo.toml	fix: onboard flags that survive npx, and check that the app loads the key (1.5.1) (#159)	The new generation changed the same lines you edited
Cargo.lock	fix: bump rustls-webpki to 0.103.16 for RUSTSEC-2026-0382 (#174)	This customization was from a previous generation
Cargo.lock	fix: the browser's approval reaches onboard on Windows (1.7.1) (#167)	This customization was from a previous generation
Cargo.toml	fix: the browser's approval reaches onboard on Windows (1.7.1) (#167)	This customization was from a previous generation

How to resolve

1. Check out this branch:

   git fetch origin && git checkout -b fern-bot/2026-10-27_22-30-20_524 origin/fern-bot/2026-10-27_22-30-20_524

   Or if you don't have the repo cloned:

   git clone https://github.com/elevenlabs/cli.git && cd cli && git checkout -b fern-bot/2026-10-27_22-30-20_524 origin/fern-bot/2026-10-27_22-30-20_524

2. Run: fern replay resolve
3. Open the conflicting files in your editor — you'll see standard merge conflict markers
4. Resolve using your editor's merge tools (VS Code, IntelliJ, etc.)
5. Run: fern replay resolve again to finalize
6. Push your changes

Your resolved customizations will be remembered on future SDK generations.
If you merge this PR without resolving, your unresolved customizations will conflict again on the next generation.