Why I stopped uploading my meetings to the cloud and built my own transcriber

说明与用途

作者创建了 Fennec，以在本地存储音频和转录文本，并与编码代理集成，避免云服务的不确定性和成本。

问题

Uncertainty about where raw meeting audio is stored, how long it stays, and whether it is used for training or retained after deletion, plus difficulty accessing transcripts for coding agents and high cost of cloud services.

结果

Audio stays on the local machine, transcripts and minutes are plain files, workflow is fully local except for optional cloud LLM calls, eliminating data‑privacy concerns and reducing recurring costs.

工作流

• 1. Record meeting using Fennec’s system audio tap and mic input.
• 2. Transcribe audio with whisper.cpp (or Apple on‑device ASR on macOS).
• 3. Perform speaker diarization with sherpa‑onnx.
• 4. Optionally translate live output on macOS.
• 5. Store all outputs (audio, transcript, minutes.md, metadata) in a dedicated session folder.
• 6. When ready, press "Create Minutes" to send transcript text to a chosen coding agent CLI (Claude Code, Codex, Gemini CLI).
• 7. Receive summarized minutes and save locally; raw audio remains on device.
• 8. Backup session folders with any file‑based backup tool; search with grep or editor.
• 9. Optionally rebuild Fennec in Rust/Tauri for cross‑platform use.

证据

Recording, transcription, speaker diarization and translation all run on the local machine.

来源

The raw audio never leaves. The transcript leaves only when you press the button, and only to the agent you set up.

来源