meraGPT

August 22, 2026 · 6 min

A nightly journal your agent keeps for you

Most journaling apps die the same way. You download one, you write for four days, and then you forget it exists because nothing ever asks you to open it. A journal that pings you first survives longer. And a journal on your own box is one where the entries are yours in a way a subscription app can never quite promise.

This is two small pieces working together. A nightly cron that nudges you with a couple of questions over Telegram, and a memory file where your answers get kept. You reply in bed in thirty seconds. On Sunday the agent reads the week back to you.

What holds the entries

Hermes keeps its memory as plain markdown files on your box. That’s the whole storage story here. Your journal is a folder of dated files under memory/journal/, readable only by your box, which is the point of writing anything personal down. If you haven’t set memory up before, the piece on teaching your agent to remember you covers it, and this builds on the same idea.

1. A skill that files what you send

First, teach the agent what to do with a journal entry. Open the SKILLS tab, create a skill, and give it this:

name: journal
description: Save the user's nightly reflections.
When the user replies to a journal prompt, append their
message to memory/journal/YYYY-MM-DD.md using today's
date. Add a one-line mood read at the top if they mention
how they felt. Never summarise away their own words; keep
what they wrote verbatim, then your note underneath.

Now any reply that reads like a reflection lands in the right file, under today’s date, with your own words left alone. The verbatim rule matters. A journal you can’t trust to keep your actual sentences isn’t a journal.

2. The nightly nudge

Open CRON, click CREATE, and name it Nightly journal. The prompt:

Message me on Telegram with two short journal questions.
Vary them night to night. Ask about one thing that went
well and one thing on my mind. Keep it warm and brief,
two sentences, no checklist. Don't answer for me.

Put 0 22 * * * in the schedule for 10pm every night. Check your box’s timezone first, since a fresh box is on UTC and a 10pm nudge in the wrong timezone is a 5pm nudge. Set delivery to Telegram. Hit CREATE.

At 10pm the agent messages you. You reply with a few lines about your day. The journal skill files it. You never opened an app.

3. The Sunday read-back

The reason to keep a journal is to reread it, and nobody does. So schedule that too. A second cron, once a week:

Read this week's files in memory/journal/. Message me
on Telegram with a short reflection: the throughline of
the week, one thing I kept returning to, and one thing
I said I'd do and didn't mention again. Gentle, not a
performance review.

Schedule 0 18 * * 0 for 6pm Sunday. What comes back isn’t a summary of your week so much as a mirror of it. The recurring worry you mentioned three nights running shows up as a pattern you didn’t notice while living it.

Why it stays private

The entries are files on a machine you rent, not rows in a journaling startup’s database. Nobody at meraGPT reads them. The model does see a night’s entry when it files it, since that’s the call that does the writing, but there’s no account somewhere accumulating your inner life into a profile. For a journal, that difference is the entire thing.

You can also just open the files. They’re markdown. If you ever leave, your journal leaves with you as a folder of plain text, which is how it should have been all along.

Related