Command line and local tools

Most people use Vibe’s desktop window—and that’s enough. This page is for anyone who wants repeatable workflows: scripts, batch jobs, or a small local service on your own machine.

Start with your installed version

Flags and subcommands can change between releases. The reliable first step is to run vibe --help (or your platform’s equivalent path to the binary) and read what your build supports.

Official README notes (check your version)

The upstream project documents CLI support and an HTTP API mode. The README mentions starting the server with --server and opening built-in API documentation in your browser (the example shows port 3022 and a /docs path). Your port or path may differ by version—use the on-screen URL or help output as the source of truth.

# Example pattern from the official README (verify on your machine):
vibe --server
# Then open the local docs URL shown by your build, often similar to:
# http://localhost:3022/docs

Everyday CLI-style examples (may vary)

These patterns are typical for transcription CLIs, but treat them as starting points—confirm flags with vibe --help:

# Transcribe one file
vibe transcribe audio.mp3

# Ask the tool what it supports
vibe transcribe --help

Docker (advanced)

Some teams run services in containers. If you go this route, mount folders for models and audio carefully, keep images updated, and treat the service as local network only unless you know how to harden it.

Download Vibe Transcribe — free

Open source · Works offline · No account needed · v3.0.19

Free download

Windows macOS Linux

Frequently asked questions

Does Vibe Transcribe have a command line interface?

Yes. Vibe ships with a full CLI that supports single file transcription, batch processing, language selection, model selection, and output format choice. Run 'vibe --help' to see all available options.

How do I use Vibe CLI to transcribe a file?

Basic usage: 'vibe transcribe audio.mp3'. For more options: 'vibe transcribe --language en --model small --output-format srt --output-dir ./output audio.mp3'. The CLI uses the same Whisper models as the GUI app.

Can I batch transcribe files with Vibe CLI?

Yes. Use wildcard patterns: 'vibe transcribe ./recordings/*.mp3' to transcribe all MP3 files in a folder. Add '--output-dir ./transcripts' to save all outputs to a specific directory.

Does Vibe have an HTTP API server mode?

Yes. The project documents an HTTP API mode you can start from the command line (see the official README). A common pattern is to use the --server flag and open the local documentation page in your browser (ports can vary by version—use the URL shown on your machine).

Can I run Vibe in Docker for automated transcription?

Yes. Vibe provides a Docker image at ghcr.io/thewh1teagle/vibe. Mount your audio files and models volumes, then use the HTTP API to submit transcription jobs programmatically.