The other half of Ear for Omi
Audio goes to your own computer.The organized result comes back to your phone.
Ear for Omi does not organize anything by itself. What the pendant records is handled by two services you run yourself. The developer runs no server: every block below is in your hands, or uses your own keys.
Who does what
The pendant listens, the phone carries and shows, the recording backend transcribes: audio becomes a transcript, and what you say after pressing the button becomes a command. Then the second brain turns it into topics, to-dos and memories, and sends them back to your phone.
- PendantRecords; has a button
- Ear for OmiCarries audio, holds no keys, shows everything
- Recording backendStores, splits, transcribes, handles commands
- Second brainTopics, to-dos, memories
On you
Pendant and phone- MicrophoneRecords audio
- ButtonPress, then speak
- On boardStores when offline
- RecordingConnection status
- Live textDraft on the phone
- BufferKept until confirmed
- OfflineSynced from pendant
- TopicsTopics, review, to-dos
- RepliesSpoken and on screen
- KeysHolds none
Your own computer
e.g. an always-on Mac mini- IntakeConfirms only after writing to disk
- Split and identifySentences, voiceprints, music check
- TranscribeA model turns audio into text
- Write to OmiEach conversation, once
- Button commandsFinds the intent, answers or notes it
- Web pagesStatus, conversations, commands
- KeysOmi and model keys live here
- TopicsEach point must match the transcript
- Daily reviewWritten when the day ends
- To-dos, memoriesPeople too, pulled out of the topics
- For the appTopics side, search, edits
- Web adminRead topics, edit notes, settings
Markdown folderYour files; opens in any editor
Outside
Your own keys- TranscribeTakes audio
- OrganizeTakes text
- KeyYour own
- WrittenConversations, once
- ReadSummaries, once
- LaterEdits stay yours
Where the data lives
Sources flow into the second brain, which organizes them into one Markdown folder. All of it is on your computer.
Sources
- Pendant recordingsAsks the backend every minute
- Omi’s summaryRead once per conversation
- FootprintSynced every hour
- Your own diaryOptional; read, never changed
- Your edits in the folderRead back, not overwritten
Markdown folder
- Topics
- Daily reviews
- To-dos
- Memories, notes
- People, goals
- Footprint
Used by
- The phone
- Web admin
- Voice commands
Recordings and transcripts
In the recording backend’s own folder: each conversation’s recording and transcript, and the voiceprints it has learned.
Topics and notes
A folder of Markdown files that opens in Obsidian or any text editor.
- 主題/ topics
- 每日/ daily
- 待辦/ to-dos
- 記憶/ memories
- 人物/ people
- 目標/ goals
- 記事/ notes
- You can edit these files directly; the second brain will not overwrite what you changed.
- Deleting moves a file to a trash folder, so it can be restored.
- Deleting the app does not touch the backend’s data; the phone only holds a cache and your footprint.
What you need
- 1An always-on computerFor example a Mac mini that stays on and does not sleep. The setup guide is written for a Mac mini.
- 2An Omi developer keyCreated on Omi’s web app, with write access. The backend uses it to write conversations to Omi.
- 3A key for a model serviceAn OpenAI-compatible API. You need one model that can take audio (transcription) and one for text; they can be the same. The model service bills you for usage.
- 4A way for the phone to reach that computerPut the phone and the computer on the same private network, or serve the backend over HTTPS. Each phone pairs once by scanning a QR code from the backend, and unpaired devices cannot get in from outside; the admin pages open only to trusted networks. Even so, it is best to let only networks you trust reach the backend.
- 5Comfort with a terminal, or an AI assistant to install itThe setup guide is written for an AI assistant to follow, with a command and a check for every step. It installs directly on macOS (a Mac mini, for example) and starts on boot.
How to get it
The backend does not come with the app and is not on the App Store. Email us and we will send you the backend’s code and the setup guide. You receive source code; model files and packages are downloaded from their official sources during setup. The guide and the backend’s web pages are currently in Traditional Chinese.
Email us for the backend sona.orbit.hi@gmail.com