Blaze Livekit plugin integration

[HoangPN711]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9e42604

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 22 packages

Name	Type
@livekit/agents-plugin-blaze	Patch
@livekit/agents	Patch
@livekit/agents-plugin-anam	Patch
@livekit/agents-plugin-baseten	Patch
@livekit/agents-plugin-bey	Patch
@livekit/agents-plugin-cartesia	Patch
@livekit/agents-plugin-deepgram	Patch
@livekit/agents-plugin-elevenlabs	Patch
@livekit/agents-plugin-google	Patch
@livekit/agents-plugin-hedra	Patch
@livekit/agents-plugin-inworld	Patch
@livekit/agents-plugin-lemonslice	Patch
@livekit/agents-plugin-livekit	Patch
@livekit/agents-plugin-neuphonic	Patch
@livekit/agents-plugin-openai	Patch
@livekit/agents-plugin-phonic	Patch
@livekit/agents-plugin-resemble	Patch
@livekit/agents-plugin-rime	Patch
@livekit/agents-plugin-sarvam	Patch
@livekit/agents-plugin-silero	Patch
@livekit/agents-plugin-xai	Patch
@livekit/agents-plugins-test	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[CLAassistant]

All committers have signed the CLA.

[toubatbrian]

Have you ran the tests on those plugins?

[HoangPN711]

Have you ran the tests on those plugins?

Yes — I re-ran the plugin tests and checks after the latest fixes.

What I validated:

• Unit tests for the Blaze plugin (LLM/STT/TTS)
• Type checking
• Lint/format checks

I also added a regression test for the stream options race-condition and fixed the STT/TTS typed-array buffer window handling from review feedback.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 20 additional findings in Devin Review.

[devin-ai-integration]

🟡 STT throws non-framework BlazeHttpError instead of APIStatusError on HTTP failures

The STT _recognize method throws BlazeHttpError (a plain Error subclass defined in plugins/blaze/src/config.ts:86) for HTTP error responses, while the LLM (plugins/blaze/src/llm.ts:208-211) and TTS (plugins/blaze/src/tts.ts:392-395) implementations correctly throw APIStatusError from the framework. BlazeHttpError does not extend APIError, so any caller that checks error instanceof APIError to distinguish API failures from other errors will misclassify STT HTTP errors. The framework's error handling infrastructure (e.g., the retryable property on APIError, error classification in the voice pipeline) expects APIError subtypes. After all internal retries exhaust, this non-framework error type escapes to the caller.

Prompt for agents

In plugins/blaze/src/stt.ts, the _recognize method throws BlazeHttpError (from config.ts, which extends Error directly) on HTTP error responses (line 195). This is inconsistent with the LLM and TTS implementations in the same plugin, which throw APIStatusError (a framework-provided APIError subclass). The fix is to replace the BlazeHttpError throw with an APIStatusError throw, matching the pattern used in llm.ts:208-211 and tts.ts:392-395. The isRetryableError check in the retry loop (line 202) should then check for APIStatusError.retryable or APIStatusError.statusCode instead of BlazeHttpError.status. This may also allow removing BlazeHttpError and isRetryableError from config.ts entirely if they are no longer needed.

---

Was this helpful? React with 👍 or 👎 to provide feedback.