I want to tell you about the morning I almost gave up on the book.

It was a Saturday, the good kind — coffee made, house quiet, three hours that belonged to no one but the story. I’d been carrying this novel for the better part of a year. I knew my characters the way you know people you’ve lived with. I sat down to write chapter twelve, and I asked the AI I’d been drafting with to help me pick up where I’d left off.

It asked me who the protagonist was.

Not in a cruel way — it didn’t know any better. But I’d told it who she was a hundred times. I’d explained her mother’s death, the sister she didn’t speak to, the reason she flinched at the word home. And every session, the slate wiped clean. Every Saturday, I introduced her again like we’d never met. By chapter twelve I wasn’t writing a novel anymore. I was a translator, endlessly re-explaining my own book to a machine that kept forgetting it.

That morning I closed the laptop and thought: maybe I’m not a writer. Maybe this is just what it feels like, and everyone else pushes through.

The thing nobody names

It took me a while to understand that the problem wasn’t me, and it wasn’t exactly the AI either. It was something structural — a limitation so baked into how these tools work that most writers never get a name for it. They just feel it, blame themselves, and quietly stop.

The machines have a fixed amount of memory for any one conversation. When you exceed it — and a novel exceeds it fast — the oldest material falls off the edge and is simply gone. Not summarized. Not filed away. Gone. So the AI isn’t ignoring the fact that your protagonist’s mother is dead. By chapter twelve, it genuinely cannot see chapter one anymore.

I started calling it context amnesia, because that’s what it felt like — a companion with no short-term memory, meeting you fresh every single day. And once I had a name for it, I couldn’t stop seeing it. In every forum thread where a writer asked why the AI kept changing their character’s eye colour. In every “previously on” recap people pasted at the top of each session, doing by hand the remembering the tool should have done for them.

What I actually wanted

I didn’t want a machine that wrote my book. I’ve never wanted that. The whole point — the joy of it — is the writing. What I wanted was simpler and somehow harder: a companion that remembered. That held the architecture of my novel the way I held it in my head, so I could sit down on a Saturday and just continue, the way you continue a conversation with an old friend who already knows the story.

So I started building it. Not a writing app — there are plenty of those. A writing companion. Something that knows your characters by name, keeps your timeline straight, remembers the twist you’ve been protecting, and brings all of it into the room every time you write. Something that never asks you who your protagonist is, because it already knows.

I called her Aura. I wrote a fair bit of what became WriterScribe inside WriterScribe — including, eventually, the words you’re reading now.

Why I’m writing this

I’m starting this journal because I think a lot of writers are sitting where I sat that Saturday — laptop closed, wondering if the problem is them. It isn’t. The blank page is hard enough without a tool that forgets your work between visits. You deserve better company than that.

Once a week, I’ll write here about the craft of finishing — honestly, from this desk, one writer to another. No funnels, no ten-step hustle. Just the things I’m learning about how books actually get done, and how the right kind of help changes what’s possible.

If you’ve been carrying a story, and you’re tired of explaining it to a machine that keeps forgetting — come write with us. There’s a calmer way to work, and your book deserves to be finished.

— Ed