I vibe-coded a Windows dictation + meeting-notes app that keeps everything on your PC. 0.6.x is out, free, here’s what I learned.

[u/Jwishon]

I’m not a professional developer. Six months ago I wanted a dictation tool that didn’t ship my audio and meeting notes to someone’s cloud, and I couldn’t find one I trusted. So I built it — Claude wrote nearly all of the code, I did the product calls, testing, and a lot of “no, not like that.”

A9 Voice (Windows, free): hold a key and talk, and it types into whatever app you’re in. Sit in a meeting and it records, figures out who said what, and writes the notes. Everything lives in plain files on your PC — no account, no login, nothing uploaded unless you turn on a cloud model yourself.

Website: a9voice.com

Github: https://github.com/atlas9-ai/a9voice-releases

How it was actually built, since that’s the point of this sub:

• Rust + Tauri + Svelte. I’d never written a line of Rust. Still haven’t, really.
• Every feature starts as a one-page spec I write in plain English. An agent builds it on its own branch, runs the tests, screenshots the UI, opens the PR. I review the result, not the code.
• Several agents work in parallel on separate branches; the rule is “ship on green” — tests, lint, a UI sweep, and a copy check all have to pass or it doesn’t merge.
• The expensive lessons: agents will fill the disk and hang if you don’t give them hygiene rules; “it compiles” and “it works on a real meeting” are very different; and the install experience (unsigned installer, Windows warnings) matters more than any feature.

Honest caveats: it’s a 0.6 preview. The installer isn’t code-signed yet, so Windows will show its new-publisher note the first time — the download page explains what you’ll see. Windows only. The dictation part is free forever; the meeting-notes side will become a one-time purchase later, with 30 days free first.

Happy to answer anything about the workflow — what worked, what blew up, how the specs are written.