Second brain5 min read

Journaling with Claude: a workflow

Using a model you already talk to as a thinking partner for your own writing, without handing it the job of deciding what your life means.

If you already use Claude every day, there is an obvious gap: it knows a great deal about everything except you. Each conversation starts from nothing. You re-explain your situation, get a reasonable answer built on the summary you just typed, and the context evaporates when you close the tab.

Meanwhile you have a journal — possibly years of it — containing exactly the context that was missing.

Here is a workflow for closing that gap, and an honest account of where it helps and where it does not.

The shape of the problem

A chat window is good at reasoning and bad at remembering. A journal is good at remembering and does no reasoning at all. Each one has precisely what the other lacks.

The naive fix is to paste entries into the chat. This works and it is worth doing before building anything more elaborate — paste last month's entries, ask a question, see whether the answers are better. They usually are, noticeably. That experiment costs five minutes and tells you whether the rest of this is worth your attention.

What it does not scale to is a real archive. You cannot paste four hundred entries, and the ones you would paste are the ones you can already find, which are not the ones you need.

Connecting the two properly

The standard way to give a model access to a system is the Model Context Protocol, an open protocol for exposing tools and data to an assistant. A journal that speaks MCP can be searched by the model directly: it asks for entries matching a subject, gets them back, and reasons over what it actually retrieved rather than over your summary.

Ember runs a remote MCP server for this, exposing reading tools — search by text, search by theme, list themes, fetch summaries and insights — and, if you explicitly enable it, writing tools. It is in limited release rather than generally available at the moment, so treat it as something arriving rather than something you can switch on today.

The important design point, whatever tool you use: writing should be off by default. A model with read access to your journal is a research assistant. A model with write access to your journal is editing the record of your life. Those warrant different levels of consent, and any system that conflates them is badly designed.

The workflow

1. Keep the journal normally

This sounds obvious and is the step people skip. The value of the whole arrangement is proportional to how much honest material is in the archive, and writing for a model produces performed, hedged entries that are worth very little.

Write as though nobody will read it. That is what makes it worth reading.

2. Ask retrieval questions, not oracle questions

The difference between a useful session and a disappointing one is almost entirely in the question.

Works well:

  • "Find everything I wrote about leaving my job. Put it in order and tell me what changed between the first and the last."
  • "What was going on in March? I remember it being bad and I cannot remember why."
  • "I have written about this before. Find the other times."
  • "Compare how I wrote about this person in 2023 and now."

Works badly:

  • "What should I do about my career?"
  • "What is my biggest blind spot?"
  • "Analyse my personality from my journal."

The first group asks the model to fetch and organise — the thing it is reliably good at. The second asks it to conclude, which it will do fluently and without the standing to do it. There is a longer version of this distinction worth reading before you lean on any of this.

3. Always open the entries

Whatever it reports, read the underlying entries. A finding you have not checked is a rumour about yourself, and these models produce plausible text as a matter of design.

This is also where the real value tends to show up. The model's summary is usually fine; the entry it surfaced that you had entirely forgotten is the thing you came for.

4. Write the conclusion yourself

End the session by writing an entry about what you noticed. In your words.

This matters more than it appears. It keeps the judgement with you, and it means the next time you do this, the archive contains your own hindsight — which is the most valuable kind of entry and the rarest.

What it is genuinely good for

Decisions you have faced before. "The last three times I considered this, what did I write?" Most people are more repetitive than they believe, and the record is unflattering and useful.

Reconstructing a period. You know something happened in spring and cannot reconstruct it. The model reads the entries and gives you back a specific account drawn from your own sentences.

Finding the thread through changed vocabulary. You described the same thing completely differently across four years. Keyword search fails; meaning-based retrieval does not.

Writing from your own material. Essays, talks, letters. The archive holds the specific details you would otherwise invent badly.

Where it falls down

It inherits the archive's bias. Most journals over-represent hard days. A reading of that is an accurate description of your journal and a skewed description of your life.

It will find patterns in noise. Given four hundred entries and an invitation to find a theme, something will always be produced. Coherence is not evidence.

It does not know what any of it meant. It can tell you a subject recurred thirty-one times. The significance is not in the text and will not be extracted from it.

It is not a substitute for a person. Writing gets you distance from your own perspective. It cannot supply someone else's.

A smaller version that works today

If you do not have a connector, the manual version still delivers most of the value:

  1. Export or copy a bounded set of entries — one month, or everything about one subject.
  2. Paste them in with a retrieval question, not an oracle question.
  3. Read the entries it points at.
  4. Write an entry about what you found.

That is the whole loop. The connector removes the copying and lets it reach the entries you could not have found yourself, which matters more as the archive grows — but the loop is the thing, not the plumbing.

And if your archive is currently sitting in another app, getting it somewhere searchable is the prerequisite for any of this. A decade of entries in a format nothing can read is a decade of context the model will never have.

A journal that reads itself back

Ember reads across everything you write and surfaces what keeps returning. Bring an old archive with you, or start tonight.

Keep reading