feat: Add Azure OpenAI Realtime API support for transcription (STT)#4476
feat: Add Azure OpenAI Realtime API support for transcription (STT)#4476jack-jackhui wants to merge 7 commits intofastrepl:mainfrom
Conversation
👷 Deploy request for hyprnote pending review.Visit the deploys page to approve it
|
✅ Deploy Preview for hyprnote-storybook canceled.
|
jack-jackhui
force-pushed
the
pr/azure-openai-support
branch
from
496f20a to
878f321
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
|
|
||
| pub async fn write_text(output: Option<&Path>, text: String) -> CliResult<()> { | ||
| write_bytes_to(output, (text + "\n").into_bytes()).await | ||
| } |
There was a problem hiding this comment.
Double newline when writing text to stdout
Low Severity
write_text appends "\n" to the text before passing it to write_bytes_to, which then appends another b"\n" when writing to stdout. This produces a double trailing newline for text output to stdout. The old code used println! which added only a single newline. The write_json path is unaffected because serde_json::to_vec doesn't include a trailing newline.
Additional Locations (1)
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| .write_all(b"\n") | ||
| .map_err(|e| CliError::operation_failed("write output", e.to_string()))?; | ||
| } | ||
| Ok(()) |
There was a problem hiding this comment.
File output missing trailing newline in write helper
Low Severity
write_bytes_to ignores the add_newline parameter when writing to a file (the Some(path) branch on line 18-23 returns early without checking add_newline). The old code explicitly appended "\n" when writing text to a file via tokio::fs::write(path, transcript + "\n"). Now, write_text and write_json both pass add_newline: true, but that flag only takes effect for the stdout path. Output files produced via --output will be missing their trailing newline, breaking POSIX text file conventions.
|
You have used all of your free Bugbot PR reviews. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
- Detect Azure OpenAI endpoints by host (.openai.azure.com) - Use transcription_session.update message format for Azure - Do not include deployment in WebSocket URL (Azure rejects it) - Add api-key header support for Azure authentication - Store Azure state in adapter for proper message formatting
Bugbot correctly identified that write_text was adding a newline to the text, and then write_bytes_to was adding another newline when writing to stdout. Fixed by: - Removing the newline concatenation in write_text - Adding an add_newline parameter to write_bytes_to for explicit control - Both write_text and write_json now add exactly one trailing newline
The file output path was ignoring the add_newline parameter. Now both stdout and file output respect the add_newline flag, ensuring POSIX text file conventions are followed.
jack-jackhui
force-pushed
the
pr/azure-openai-support
branch
from
3c00a48 to
f648331
Compare
|
You have used all of your free Bugbot PR reviews. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
2 participants
This PR adds support for Azure OpenAI Realtime transcription API (speech-to-text).
This complements PR #4222 which added Azure support for LLM (chat/summarization).
Changes
.openai.azure.com)transcription_session.updatemessage format for Azure (instead ofsession.update)api-keyheader support for Azure authenticationTechnical Details
Azure OpenAI Realtime API differs from standard OpenAI in several ways:
transcription_session.updateinstead ofsession.updateapi-keyheader instead of Bearer tokenTested with Azure AI Foundry deployment.
Note
Medium Risk
Medium risk because it changes release automation (tags, artifacts, prereleases, npm publish) and modifies API request tracing/error reporting, which could impact production deploys and debugging if misconfigured.
Overview
Release automation is reworked for
clianddesktoppipelines.cli_cd.yamlnow supportsnightlyvsstablechannels (channel-scoped concurrency), computes prerelease versions, renames artifacts tochar, marks GitHub releases as prereleases for nightly, and adds an npm publish job that ships a wrapper package underapps/cli/npm.Desktop release/publish workflows drop Linux artifacts and improve nightly release notes.
desktop_cd.yaml/desktop_publish.yamlremove Linux build/download expectations and generate release bodies that link to either the website changelog (stable) or a GitHub compare view (nightly), while controllingmakeLatestbased on channel.API and tooling updates.
apps/apiadds richer tracing fields derived from forwarded headers and marks spans as errors on 5xx/failures; OpenAPI generation is updated with new request bodies/schemas (calendar list requiresconnection_id,CreateSessionRequestgainsmode/optionalconnection_id, and addsGET /nango/whoami). Changelog and blog automation are pointed fromapps/web/content/changelogtopackages/changelog/content, a Porter workflow is removed, and STT E2E now runs provider-matrix tests for both direct providers andtranscribe-proxysuites.Written by Cursor Bugbot for commit b14ca37. This will update automatically on new commits. Configure here.