Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-17 · high
The change merged as a single commit and only reaches developers building from source until the next tagged release.
Why now: The merge landed August 16, the first commit to the repository since the August 7 preview tag.
Microsoft merged audio input into Foundry Local's Responses API, the only commit to land in the project since August 15, per GitHub. Developers running a local Foundry deployment can send audio to the same endpoint they use for text, no separate service required.
The project already runs Whisper for speech-to-text and ONNX Runtime for GPU acceleration. Wiring audio into the Responses API means a voice input can travel through Whisper, get transcribed, and reach the model without leaving the device. That closes a gap for anyone building a local voice assistant instead of bolting a separate speech-to-text service onto a text-only API.
The change hasn't reached a tagged release yet. The last CLI preview, 0.10.3, shipped August 7, so for now the audio path only works for people building from source. Anyone waiting on a stable CLI install has to wait for the next tag.
Shipping this as a plain merge, not a version bump, reads like Microsoft testing the feature with source users before it becomes a supported surface. Watch whether the next tagged release keeps audio input in the Responses API or changes it. That will show whether this was a finished feature or a trial run.
The merge landed August 16, the first commit to the repository since the August 7 preview tag.
Each link below shares sources, entities, or timing with this story.
Responses API built by OpenAI / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (Responses API built by OpenAI); both cover August, GitHub; reported by the same outlet (github.com).
Responses API built by OpenAI / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Responses API built by OpenAI); both cover August, Responses API; overlapping topics (august, respons).
Responses API built by OpenAI / Shared entities / Same source domain / Shared topic
Linked by a graph relationship (Responses API built by OpenAI); both cover August, GitHub; reported by the same outlet (github.com).
Responses API built by OpenAI / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Responses API built by OpenAI); both cover August, GitHub; overlapping topics (added, august).
Responses API built by OpenAI / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Responses API built by OpenAI); both cover August, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (Responses API built by OpenAI); both cover August, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (Responses API built by OpenAI); both cover August, GitHub; reported by the same outlet (github.com).
Linked by a graph relationship (Responses API built by OpenAI); both cover CLI, GitHub; reported by the same outlet (github.com).