[FEATURE]: Speech-to-Text Voice Input for Lazy People in OpenCode

### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Hi! First of all, congratulations on the amazing project. I've been working on a Speech-to-Text voice input feature that integrates directly into the TUI. It allows users to start audio recording with a keybind, automatically transcribe speech using different providers, and insert the resulting text directly into the prompt. I've built an initial working version, currently tested only on macOS, and the system includes: - Real-time audio recording via FFmpeg; - Support for Groq Whisper, OpenAI Whisper, and local whisper.cpp; - Automatic microphone/device detection; - Interactive menus for choosing provider, model, and audio device; - Persistent configuration stored in ~/.opencode/state/speech.json; - Customizable keybinds (Ctrl+X v, Ctrl+X P, Ctrl+X D); - Smooth flow: record → transcribe → insert into prompt input; Would this be something you'd be interested in integrating into the project?

GitHubToolDesign & CreativeSource
0Sign in to voteCopy link

FL score

75

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

A speech-to-text voice input feature integrated into a TUI to streamline prompt creation for developers and creatives.

The pain

Typing long prompts or commands in a terminal UI can be tedious and slow, especially for users who prefer voice input or have accessibility needs.

The gap

Existing TUI tools rarely offer integrated, customizable, real-time speech-to-text input that works seamlessly with multiple transcription providers and keybinds.

Build angle

Focus on polishing cross-platform support, improving transcription accuracy, and integrating tightly with popular TUI workflows to reduce friction and boost productivity.

Strengths

  • Innovative integration of speech-to-text directly into TUI prompt input
  • Supports multiple transcription providers and local/offline options
  • Customizable keybinds and device detection enhance usability
  • Addresses a real pain point for users who want faster input methods

Risks

  • Limited initial testing (macOS only) may hinder adoption
  • Speech-to-text accuracy and latency could vary widely by provider and environment
  • Niche user base, primarily TUI users who want voice input
  • Potential complexity in maintaining multiple transcription backends

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “[FEATURE]: Speech-to-Text Voice Input for Lazy People in OpenCode”.

Open FlyBot