Resonant

Resonant + Obsidian

Your best ideas
don't arrive
at a keyboard.

The insight during a walk. The connection after an article. The synthesis on the drive home. Your vault misses them because capturing with a keyboard takes too long. Resonant fixes that.

Press a hotkey in Obsidian. Speak your thought. Structured text lands in whatever note your cursor is in. On-device. Offline-ready. As local as your vault.

The gap

The thinking happens
away from the desk.
The vault is on the desk.

Obsidian is where your knowledge lives. But your best thinking doesn't happen in Obsidian. It happens in conversations, during walks, after reading, in the spaces between scheduled work. By the time you sit down to type it, the thought has cooled. The spark is gone.

Voice closes the gap. The moment the thought arrives, you capture it — raw, warm, complete. Resonant handles the translation from messy speech to structured text.

Your vault gets the version with the energy still in it.

What lands in your vault

Speak the thought.
Get the note.

Fleeting noteFleeting note during a walk
You said

the onboarding flow should ask for use case before team size because people know their use case immediately but have to think about team size and that pause kills the momentum, also the progress bar should show three steps not five even if there are five because three feels achievable

In your vault

Onboarding flow: ask for use case before team size. People know their use case immediately — team size requires a pause that kills momentum. Also: show 3 steps in the progress bar even if there are 5. Three feels achievable.

Daily journalDaily journal entry, end of day
You said

good day overall, shipped the notification preferences page which has been on the list for weeks, had a productive call with the Acme team about the pilot extension, the thing I'm stuck on is the architecture for the real-time sync, I keep going back and forth between WebSockets and SSE and I think I need to just prototype both and see which one performs better under the load we're expecting

In your vault

Good day overall. Shipped: notification preferences page (finally off the list). Productive call with Acme re: pilot extension. Stuck on: real-time sync architecture. WebSockets vs. SSE — going back and forth. Decision: prototype both and benchmark under expected load. Stop debating, start testing.

Literature noteLiterature note after reading an article
You said

the article argues that most productivity systems fail because they optimize for capture instead of retrieval, the insight is that the value of a note is determined at read time not write time, so you should spend more effort on linking and tagging than on formatting, this connects to my thinking about the second brain approach where I've been over-investing in templates and under-investing in connections

In your vault

Source: [article title] Core argument: most productivity systems fail because they optimize for capture over retrieval. The value of a note is determined at read time, not write time. Implication: invest more in linking and tagging, less in formatting. Connection: relates to my second brain approach — I've been over-investing in templates and under-investing in connections between notes.

Where it fits

Six moments in a
knowledge worker's day.

Fleeting notes

The idea that arrives during a walk, a shower, a commute. Gone in 30 seconds if you don't capture it. Resonant lands it in your daily note before the thought dissolves.

Daily journals

End-of-day reflections. What shipped, what you're stuck on, what you're thinking about. Spoken in two minutes, structured on arrival. The habit that actually sticks.

Meeting processing

The real takeaway from the meeting — not the transcript, but what it meant. Dictate your synthesis right after. Link it to the relevant project notes.

Literature notes

React to what you just read. The argument, your response, the connection to something else in your vault. Spoken while the thinking is fresh.

Project brainstorms

Think out loud about a problem. Resonant captures the stream of consciousness and delivers structured output. Edit the structure — don't reconstruct the thinking.

Weekly reviews

Walk through what happened, what you learned, what to focus on next. The review that takes 20 minutes to type takes 5 minutes to speak.

Architecture

Local vault.
Local voice.
Nothing in the cloud.

You chose Obsidian because your notes are yours — local Markdown files, no vendor lock-in, no sync dependency. Your voice input should work the same way.

Resonant processes audio on your Mac using Apple Neural Engine. No internet. No cloud. No audio leaving your device. Works offline, in airplane mode, on air-gapped networks.

Local notes deserve a local voice layer. Not a cloud microphone pointed at your most private thinking.

How it works

One key. Any note.

01

Put your cursor in a note

Daily note, project page, fleeting note, wherever. Resonant works in any text field in Obsidian.

02

Press the hotkey. Speak.

Talk the way you think. Stream of consciousness is fine. Resonant captures it all and strips the noise.

03

Structured text lands

Clean prose with natural structure. The thought, captured and formatted, ready to link and build on.

Free. Local. Offline-ready.

Capture everything.
Lose nothing.

Your vault deserves every thought, not just the ones that arrived at a keyboard. No subscription. No cloud. Just voice.

Requires macOS 14+ · Apple Silicon