I Built a Discord Bot Because I Hated Losing Ideas on My Phone
Second Brain Series — EP4: Discord
An idea hit me out of nowhere while I was on the move. I pulled out my phone, but had no idea where to write it down. Notes apps I never go back to. Claude app, but then it just sits there. I ended up going with “I’ll remember it later.” I didn’t.
This kept happening. Thoughts that came up on my phone died on my phone. What a waste.
Chats That Scatter Everywhere
The Claude app, Claude Code CLI, web chat, plus Slack and KakaoTalk. I could talk to AI anywhere, but everything was saved in its own separate silo. None of it ever made it to my wiki.
At some point a conversation of mine put it perfectly:
“Decisions and info are scattered all over Slack, Discord, and KakaoTalk, and nobody ever moves it to the wiki.”
That was about me. Moving things manually just doesn’t happen. It has to be automatic, or things get missed.
Why Discord?
I needed an entry point where I could fire off a thought from my phone on the spot. I was already using the app, and I could create a channel and use it solo. A Discord bot was the gateway.
The goal was this flow: throw a thought into Discord on my phone → Hermes running in Docker on the dev server picks it up → it reads the second wiki and replies → the conversation gets automatically collected into raw/notes/_auto/.
The specifics of how this loop was built are covered in the loop that automatically feeds Discord messages into the wiki.
Automatic vs. Manual — the Difference Matters
There are two ways things get collected. Hermes (Discord) conversations are automatically pushed to raw every evening by a server cron job. Drop a single line on your phone and it just comes in.
Claude web chat is different. There’s no API, so I have to export manually. I pull it once a quarter and load it in by hand. That difference is huge. Manual paths get skipped. If something requires effort, it eventually stops happening.
Claude Code CLI sessions pile up automatically as local files, so that’s automatic too. How this automation flow ended up making the wiki manage itself is documented separately.
Once I understood that each channel has its own automatic vs. manual status, it changed where I chose to put my thoughts. I started gravitating toward the channels with automatic capture.
The First Thing to Check When Picking an Entry Point
Before deciding where to send a thought, check whether it gets captured automatically. If it’s manual, you’ll stop collecting. One entry point where a single line from your phone stacks up on its own turns scattered thoughts into real assets.
Second Brain Series — EP1·EP2 Background · EP3 Integration · EP4 Discord (this post) · EP5 Usage · EP6 App
Method: Discord ↔ Wiki Loop Build · Deep dive: Hermes and Claude Code Role Split