*Este artículo fue creado utilizando entrada de voz con IA (Aqua Voice). Tenga en cuenta que puede haber algunas inconsistencias.
Hola. Soy Hiro del Laboratorio de Full Body Tracking.
Today, I’ll talk about how I built my own personal AI secretary using Claude Code.
The “Where did that note go?” problem — everyone deals with it, right?
- The Scattered Notes Problem Is a Universal Experience
- Why Claude Code Becomes a Secretary
- My Setup: Claude Code x Obsidian x VOICEVOX
- The “Stop Hook” Is Quietly the Most Powerful Feature
- Auto-Checking Quality with PostToolUse Hooks
- Why Claude Code Instead of Dispatch?
- What About from a Phone?
- The Essence of Information Management Is Not “Saving” but “Making It Usable”
- Resumen
The Scattered Notes Problem Is a Universal Experience
You have information in Notion, iPhone Notes, LINE Keep, Google Keep — everywhere. You can’t remember where you wrote what.
I was stuck in this exact situation for the longest time.
Switching note apps doesn’t solve it. The problem isn’t the app — it’s the lack of a system for turning what you wrote into something you can actually use later.
Everyone has the habit of taking notes. But almost nobody has the habit of organizing those notes into a usable state.
Why Claude Code Becomes a Secretary
What makes Claude Code special is that it can directly read and write files.
With regular ChatGPT or the Claude chat interface, conversations end as conversations. If you say “organize this,” it’ll organize it, but the result doesn’t automatically get saved to a file somewhere.
Claude Code is different. In my case, here’s how it works:
(1) I throw in notes and thoughts via voice input
(2) Claude Code structures them and writes them out as Markdown files
(3) Those files get saved in Obsidian
(4) Next time I launch Claude Code, it can read past files
In other words, Claude Code handles everything from “organizing” to “saving” automatically.
It’s not just asking in a chat and being done with it — things persist as files. That’s the decisive difference.
My Setup: Claude Code x Obsidian x VOICEVOX
Some people might wonder “Can I use this from my phone?” — but my setup is PC-centric.
Input
I speak my thoughts via voice input (AQUA VOICE, etc.). No keyboard.
Organization and Storage
Claude Code structures my notes and auto-saves them as Obsidian Markdown files. At session end, a Stop hook automatically appends the conversation log to a daily file.
Objectification
I have the organized content read aloud by VOICEVOX and check it with my ears. It’s easier to catch inconsistencies by listening than by reading with your eyes.
Rediscovery
Weeks later, I load past Obsidian notes into Claude Code. Forgotten ideas come back to life.
The “Stop Hook” Is Quietly the Most Powerful Feature
The single most effective part of my setup is actually the Stop hook.
Claude Code has a feature that automatically runs a script when a session ends. I use this to auto-save every session’s conversation content to Obsidian.
Without doing anything extra, everything I discussed with Claude Code gets recorded.
Because of this, “What was that thing we talked about?” never happens. Search in Obsidian and everything — when and what was discussed — comes up.
And since it’s organized by day, looking back and asking “What was I doing on April 7th?” is easy too.
Auto-Checking Quality with PostToolUse Hooks
Another thing I’m doing is using PostToolUse hooks.
These are scripts that run automatically every time Claude Code writes out a file. In my case, I use them for article quality checks.
For example:
- Is the first-person pronoun correct? (“boku” in Japanese — not alternatives like “watashi”)
- Does it follow the note article format?
- Does it start with the proper greeting?
When a rule is violated, a warning is automatically triggered. Claude Code’s writing gets auto-checked by Claude Code. It’s filtered before it ever reaches human eyes.
Why Claude Code Instead of Dispatch?
There are other AI tools like Dispatch, but the reason I chose Claude Code is simple.
It can directly work with local files.
Obsidian files are all local Markdown. Everything is contained on my own PC without going through cloud services.
The peace of mind of having your data in your own hands. That’s something you can’t get with cloud-based tools.
What About from a Phone?
Claude Code is a PC-based tool, so using it from a phone requires some workarounds.
Here’s what I do:
(1) When I’m out, I just dump things into iPhone Notes via voice input
(2) When I get home, I throw those notes to Claude Code for organization
(3) The organized files get saved in Obsidian
If you want to operate Claude Code in real time from your phone, there’s the option of SSH-ing into your PC. I keep a Linux machine running 24/7, so technically I could hit Claude Code via SSH from outside.
But honestly, I don’t feel much need to run my AI secretary from a phone. Taking notes is for the phone; organizing is for the PC. This division of labor works well for me.
The Essence of Information Management Is Not “Saving” but “Making It Usable”
Lots of people take notes. But few people turn those notes into something usable.
The essence of information management with Claude Code is automating the conversion from “saving” to “making it usable.”
If you have to do it manually, you won’t keep it up. Automation makes it sustainable.
Hooks auto-save things. Throw something in and it gets auto-organized. Search and things auto-appear. This “auto” part is what matters. Building a system that doesn’t rely on human willpower. I think that’s the true essence of an AI secretary.
Resumen
Claude Code isn’t a chat AI — it’s an “AI that can handle files.” That’s why it can become a secretary.
My setup:
- Input: Voice input
- Organization and storage: Claude Code + Obsidian
- Auto-recording: Stop hook (daily logs)
- Quality control: PostToolUse hook
- Objectification: VOICEVOX read-aloud
- Rediscovery: Loading past notes
The “Where did that note go?” problem can be solved with systems. Not willpower — automation.
¡Gracias por leer! ¡Síguenos en X y suscríbete a nuestro canal de YouTube!
