From 33f6bf9754e71b2f6cd8075ea7c711dfabd37eca Mon Sep 17 00:00:00 2001 From: nesquena-hermes Date: Tue, 16 Jun 2026 17:21:29 +0000 Subject: [PATCH] =?UTF-8?q?docs(changelog):=20v0.51.460=20=E2=80=94=20reco?= =?UTF-8?q?gnize=20command=20STT=20providers=20in=20voice=20probe=20(#4312?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index d5b6faa8..0620d25b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,12 @@ ## [Unreleased] +## [v0.51.460] — 2026-06-16 — Release PU (custom voice providers recognized) + +### Fixed + +- **Command (custom) speech-to-text providers are now recognized by the voice capability probe (#4312).** When `stt.provider` pointed at a Hermes command-type STT provider, the WebUI's `/api/transcribe/capability` probe only knew the built-in providers, so it reported voice input as unavailable and the browser fell back unnecessarily. The probe now delegates command-provider recognition to the agent's own resolver (`_resolve_command_stt_provider_config`) as the single source of truth, consulted after the built-in chain. Thanks @LLMinem. + ## [v0.51.459] — 2026-06-16 — Release PT (your message stays your message) ### Fixed