minutes-verify

To verify your Minutes installation, run a health check script that confirms the minutes CLI is on PATH, whisper models are downloaded, and required directories exist. This check ensures all components are configured correctly before you start recording audio.

Your minutes command might fail due to missing whisper models, absent ~/meetings and ~/meetings/memos directories, unavailable audio input devices on macOS, or a stale recording.pid file in ~/.minutes blocking the process.

A Minutes health check looks for the minutes binary on PATH, presence of whisper models in ~/.minutes/models or ~/.cache/whisper, valid filesystem directories, available audio input devices, and stale PID state to prevent transcription errors.

Yes, you can use the Minutes setup verification on local desktop and MCP server setups. It checks binaries, models, storage directories, audio inputs, and PID state to confirm the environment is ready for recording or running agents.

To check if whisper models are downloaded for your minutes transcription setup, run the verification script. It scans ~/.minutes/models or ~/.cache/whisper to ensure at least one model is present before transcription.

If Minutes isn't working after installation, run the verify-setup.sh script. It checks models, audio devices, directories, and PID state, providing clear, actionable remediation steps for any missing or misconfigured components.