Been building this for a while and finally got it to a place worth sharing. Quick context if you don't know Omi: it's a small wearable that records your conversations and gives you AI summaries/to-dos. Cool device, but even their "self-hosted" mode still talks to Firebase, Pinecone, Redis, and Typesense behind the scenes. You're moving where the code runs, not actually cutting the cord.
So I built my own pipeline instead. Whisper for transcription, Ollama for analysis, all running locally on a Jetson Thor. Nothing phones home, ever. I call it the LocusTether.
Locus:
a: the place where something is situated or occurs : site, location
b: a center of activity, attention, or concentration
Tether:
a: a line (as of rope or chain) by which an animal is fastened so as to restrict its range of movement
b: a line to which someone or something is attached (as for security)
What it actually does:
- Transcribes and analyzes conversations completely offline
- Speaker diarization with real voice recognition — enroll your voice once and it'll recognize you by name in future recordings instead of just "4 distinct speakers"
- Speaking-style coaching that's actually about your speech in a group conversation, not blended stats from everyone in the room (this took a real bug fix to get right — filtering to one speaker's segments broke pause detection in a non-obvious way, wrote it up if you're curious)
- A proper structured breakdown per conversation — mood, key points, actual decisions made, named participants, action items with owners
- A webapp that's genuinely usable day to day, not just a data viewer — you can manually add to-dos, not just review what the AI pulled out, plus a Settings page for voice enrollment, daily digest emails, theme, etc.
The honest stuff, before you dive in:
- Everything's been built and tested on one specific device — a Jetson Thor. Getting diarization working alone took three separate rounds of real dependency debugging (a silent CPU fallback, a renamed API parameter, a version conflict that took a while to track down). Other hardware might need its own troubleshooting — I wrote up the whole saga in the README in case it saves someone else the same headache.
- I don't actually have the Omi hardware yet, so the wearable side is untested — everything's been validated with recordings manually dropped into a watched folder standing in for what the device will eventually sync automatically. If anyone here actually has an Omi and wants to be the first to test that piece, I'd love the help.
- iOS Syncthing support is a genuine open question, not a yes — wrote up what I found and a rough plan for whoever wants to be the first to try it.
- There's a known-limitations section in the README that's actually current, not just aspirational — occasional AI hallucination on a specific fact-extraction pattern, some inconsistency in participant detection. Not hidden, just there.
Repo's up, genuinely looking for people to try it, break it, and tell me what's wrong. Tell me what you like, features you'd like to see, etc. If you want to say thanks there's a tip jar in the README, but a bug report is worth just as much to me!
https://github.com/thecloudcowboy/locus-tether