feat(elevenlabs): add STT enableLogging option#1975
feat(elevenlabs): add STT enableLogging option#1975rosetta-livekit-bot[bot] wants to merge 1 commit into
Conversation
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| const response = await fetchFn( | ||
| `${this.#opts.baseURL}/speech-to-text?enable_logging=${String(this.#opts.enableLogging).toLowerCase()}`, |
There was a problem hiding this comment.
🔍 Batch URL now always includes enable_logging query parameter — behavioral change for existing callers
Previously, the batch recognition URL was simply ${baseURL}/speech-to-text with no query parameters. Now it always appends ?enable_logging=true (or false). While true is almost certainly the ElevenLabs API's default when the parameter is omitted, this is a subtle behavioral change for all existing users — every batch request will now carry this query parameter. If the API treats the explicit presence of enable_logging=true identically to omitting it, this is harmless. Worth confirming with ElevenLabs API docs that the default is indeed true when unspecified.
Was this helpful? React with 👍 or 👎 to provide feedback.
Summary
enableLoggingto ElevenLabs STT options with a default oftrueenable_loggingthrough batch recognition and realtime WebSocket requestsTesting
pnpm exec prettier --check "plugins/elevenlabs/src/stt.ts" "plugins/elevenlabs/src/stt.test.ts"pnpm test plugins/elevenlabs/src/stt.test.tspnpm --filter @livekit/agents-plugin-elevenlabs buildpnpm buildfunction_tools_executed(.function_calls[0].name="getWeather")Port of livekit/agents#6273.
Ported from livekit/agents#6273
Original PR description
Add enable_logging to 11labs STT, on par with already existing TTS implementation