Speaking My Mind: How I Use wisprflow, Claude Code, and Obsidian to Think and Create

Speaking My Thoughts Into a System That Writes for Me

I’ve always thought faster than I can type. Typing slows me down. Writing feels like translating my thoughts through a delay. So instead of fighting that, I built a workflow that lets me speak my work into existence — no friction, no cursor blinking at me.

Here’s how it works.

Step 1: wisprflow — Typing, Replaced

At the heart of my setup is wisprflow, a simple but transformative tool. With a keyboard shortcut, a small mic window appears, I start talking, and my words turn into clean, structured text — instantly.

But here’s the real difference: wisprflow doesn’t just transcribe what I say; it understands what I mean.

When I speak naturally — with pauses, “ums,” and half-finished sentences — it uses AI to clean that up. It fixes grammar, adds punctuation, and writes what I intended to say, not the messy version that came out of my mouth.

That’s not an error — it’s the point. It saves me from editing later.

So instead of forcing myself to type a blog, I just start talking:

“New idea: write about how I use voice, AI, and Obsidian to capture thoughts.”

Seconds later, that’s written neatly in Markdown, ready to go wherever my cursor is — a doc, an email, or my note vault.

Typing is no longer part of the equation.

Step 2: Claude Code — The AI That Lives in a Directory

Once my thoughts exist as text, Claude Code steps in.

Claude Code isn’t your typical AI chat. It actually runs inside a directory. That means it has full context of the files, the folder structure, and the relationships between everything in that workspace.

When you initialize Claude Code in a repo (or, in my case, my Obsidian vault), you’re giving it permission to understand the entire environment it’s in.

That allows it to do things like:

• Read Markdown notes and connect them intelligently.
• Generate or update documentation that matches the style of the vault.
• Summarize, expand, or clean up content based on your own writing patterns.

And when you create agents within Claude Code, they inherit that same context.
For example, I’ve built agents that can:

• Maintain my Obsidian documentation.
• Convert rough notes into publish-ready articles.
• Summarize or reorganize large folders of ideas.

Because Claude Code lives inside my workspace, it doesn’t just generate random text — it works in harmony with what’s already there.

It’s like having an AI collaborator who knows where everything lives.

Step 3: Obsidian — My Brain, Externalized

Finally, everything lives in Obsidian — my second brain.

Obsidian is a Markdown-based knowledge system that stores everything as plain text. No cloud lock-in, no database — just a folder of .md files that I fully control.

It lets me link ideas together with internal backlinks and visualize how my thoughts connect over time.

In practice:

• wisprflow captures new thoughts directly into Obsidian notes.
• Claude Code refines or expands them inside that same directory.
• And I use Obsidian’s graph and tagging system to keep everything connected.

It’s the layer that turns individual notes into a living, evolving knowledge network.

Step 4: The Workflow in Motion

Here’s what an actual workflow looks like:

Capture the idea
I hit my wisprflow shortcut and say:

“Note: write about how Claude Code understands Obsidian directories and can maintain documentation automatically.”

The note appears instantly
It shows up in my Obsidian vault under /notes/claude-code-workflow.md.

Claude Code expands it
Inside the same directory, I ask Claude:

“Add examples of how agents can maintain this documentation and create summaries.”
It writes directly into that Markdown file — no copy/paste, no manual steps.

Link and organize
In Obsidian, I link that note to others on AI tools, workflows, and documentation methods. My vault automatically grows more interconnected.

Publish or build
When it’s ready, I have another agent that formats and moves it into my “Published” folder — ready for my site, blog, or documentation repo.

It’s a creative chain reaction:
Voice → wisprflow → Claude Code → Obsidian → Publish.

Why I Work This Way

I’m not chasing automation for its own sake — I’m chasing flow.

When I’m in flow, I don’t want to stop thinking to type, format, or organize. wisprflow captures my mind as it moves. Claude Code processes it intelligently in place. Obsidian connects everything I’ve ever thought about.

The result is a seamless loop where I can speak ideas, document them, and publish — without ever losing the thread of thought.

In Short

• wisprflow captures voice, cleans it up with AI, and replaces typing.
• Claude Code lives inside my directory, processes notes, and powers intelligent agents.
• Obsidian organizes everything into a structured, searchable vault.

Together, they form the perfect balance between creativity, structure, and speed.
I don’t write anymore — I speak, and my system listens, understands, and builds with me.