LocalAI has widened the front door to its realtime WebRTC API. A merged change now accepts the raw SDP offer format used by OpenAI's generally available client flow, while preserving the JSON-wrapped offer that LocalAI already understood. That sounds like plumbing, but it removes a very practical compatibility snag before a live session can even begin.
LocalAI Watch analysis
What happened
An official repository commit merged on 29 August extends the /v1/realtime/calls signalling route so clients can send multipart form data containing SDP directly. The existing JSON envelope remains available, so this is an additive compatibility change rather than a forced migration. The commit also adds route tests for the accepted formats, which is the useful bit when protocol support starts breeding tiny exceptions in the shed.
The scope is specific: this concerns the opening WebRTC handshake. It does not by itself prove broader media quality, full feature parity with OpenAI, or availability in a tagged LocalAI release. The evidence supports a merged repository change, so users should treat release packaging as a separate checkpoint.
Why it matters
For developers building against OpenAI-shaped realtime clients, an SDP mismatch can stop the session before audio or other media has a chance to flow. Accepting the GA-style payload reduces the need for a LocalAI-only adapter and makes one client path easier to carry between hosted and local deployments. Existing integrations keep their old route, which lowers the immediate regression risk.
The larger signal is that compatibility work is moving beyond matching endpoint names. Wire formats, content types and handshake behaviour are where supposedly compatible APIs either become useful or turn into a weekend spent arguing with curl. This change tackles one of those unglamorous edges directly.
Our read
LocalAI has not announced that every realtime client can now stroll in, order a pint and behave perfectly. It has, however, removed one bouncer from the door. That is a modest claim, and a materially useful one.
What to watch
- Confirm which tagged release first includes the merged signalling change.
- Watch for reports from GA OpenAI WebRTC clients across browser and server environments.
- Check whether follow-up work closes any remaining differences in session options, events or media handling.
Discussion spark: Would raw SDP support make you more likely to reuse an existing OpenAI-style WebRTC client with LocalAI, or are other realtime gaps still the deciding factor?
Sources and evidence
- Add support for SDP from OpenAI's GA API (29 August 2026, 22:04 UTC)
- LocalAI main-branch commit feed (29 August 2026, 22:04 UTC)
This is an independent WittyWires tracker and is not affiliated with, endorsed by, or speaking for LocalAI, mudler, or any person or organisation mentioned.