Skip to content

Persist transcription engine choice in presets#50

Merged
nmbrthirteen merged 1 commit into
mainfrom
feat/persist-transcription-engine
Jul 6, 2026
Merged

Persist transcription engine choice in presets#50
nmbrthirteen merged 1 commit into
mainfrom
feat/persist-transcription-engine

Conversation

@nmbrthirteen

Copy link
Copy Markdown
Owner

Follow-up to #48.

The AssemblyAI vs Whisper engine selector already exists in the studio (added in 5f27df4, shipped in v2.3.0/v2.3.1) and the CLI already has --engine/--assemblyai-api-key. The reporter's screenshot shows the older "Auto (Whisper)" tab, so they were on a pre-v2.3.0 build.

This adds the one thing still missing for "consistently choose their preferred engine": the engine choice was component-local React state that reset on reload. Now it's saved with the preset config and restored on load, exactly like whisper_model. The AssemblyAI API key is deliberately not persisted here (it lives in the global .env via ASSEMBLYAI_API_KEY, the secure store).

Build passes.

The Whisper/AssemblyAI engine selector was component-local state that
reset on reload. Save it with the preset config and restore it on load,
matching whisper_model, so a saved show keeps its preferred engine.
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nmbrthirteen, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7f881f17-d97e-405f-8e6f-bf0551d4001f

📥 Commits

Reviewing files that changed from the base of the PR and between da158e6 and 6c275d6.

📒 Files selected for processing (1)
  • src/ui/client/EpisodeWorkspace.jsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/persist-transcription-engine

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@nmbrthirteen nmbrthirteen merged commit 2fa331d into main Jul 6, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant