There's a quiet failure mode in every "second brain" I've used: the capture tax. To save a thought I have to stop, pick the right notebook, tag it, decide where it lives. For an AuDHD brain mid-flow, that tax is usually enough to lose the thought.
eidan's whole pitch is a personal agent that remembers your life — a real, relational memory you own. But a memory is only as good as what reaches it. The piece I most needed wasn't more storage. It was a front door with no lock: say the thing once, and let the agent do the filing.
That's the journal.
How it works. You drop a note — in the web app, as a Telegram message, or (the one I actually use) a voice note while walking. Voice is transcribed on the way in, so by the time the agent sees it, "built the journal panel today, and I found a scoring bug in mathgame" is just text. Then a single instruction — your direction prompt, which you write and edit — tells the model how you want your life sorted. It splits the note into distinct items and files each: this is a dev-log, that's a bug, this is a content idea.
Here's the part that turned it from a notebook into something I rely on: filing can trigger work. A note tagged as a bug that names a repo doesn't just sit there — it opens a coding job, and Sage picks it up, branches, writes the fix, and opens a PR. A content idea becomes a seed my writing agents draw from later. One spoken sentence fans out into a logged memory, a pull request, and the raw material for a post.
This one, in fact. The paragraph you're reading started as a journal entry.
Why build it this way. I could have made a note app with an AI sidebar — plenty exist. But they store; they don't route. And the value of remembering your life isn't the archive, it's what the archive can do. eidan already had the pieces: a job queue, user-defined agents on schedules, a relational memory. The journal is barely a few hundred lines of glue — it categorises with the model, then hands off to primitives that were already there. The lesson I keep relearning building eidan: the leverage isn't in any one feature, it's in features that can call each other.
What's yours. The direction prompt is the whole personality of it, and it's a text box you own — no fixed categories, no someone-else's taxonomy. Rewrite it and your journal sorts your life differently tomorrow. The entries live in your Postgres. The routing runs on your machines. This isn't a service you rent; it's a folder you drop things into that happens to know what to do with them.
I've lost a lot of good thoughts to the capture tax over the years. This is the first thing I've built where saying it once is enough.