The CLI re-uses validation from @elevenlabs/elevenlabs-js. When the SDK adds a new value to a model enum (LLMs, TTS, ASR), the CLI doesn't pick it up until someone manually bumps the dep and cuts a CLI release. Users then hit:
Error processing : Error: conversationConfig -> agent -> prompt -> llm: Expected enum. Received "".
even though the server-side catalog already supports the value. This has happened repeatedly (e.g. claude-haiku-4-5, gemini-3-flash-preview, currently qwen36-35b-a3b).
The structural fix is to drop the enums entirely (filed separately against elevenlabs-js). Even with that fix, this CLI repo will keep falling behind on any other SDK update unless the dep bump is automated.
Proposed fix
Automate the SDK → CLI release path:
Related:
#68
elevenlabs/elevenlabs-js#296
The CLI re-uses validation from @elevenlabs/elevenlabs-js. When the SDK adds a new value to a model enum (LLMs, TTS, ASR), the CLI doesn't pick it up until someone manually bumps the dep and cuts a CLI release. Users then hit:
Error processing : Error: conversationConfig -> agent -> prompt -> llm: Expected enum. Received "".
even though the server-side catalog already supports the value. This has happened repeatedly (e.g. claude-haiku-4-5, gemini-3-flash-preview, currently qwen36-35b-a3b).
The structural fix is to drop the enums entirely (filed separately against elevenlabs-js). Even with that fix, this CLI repo will keep falling behind on any other SDK update unless the dep bump is automated.
Proposed fix
Automate the SDK → CLI release path:
Related:
#68
elevenlabs/elevenlabs-js#296