Slaying the memoryless dragon.

How to invoke yourself every time you start. Three weeks of friction with a memoryless model. One tool call. A small smile. A silent win.

Three weeks ago I started fighting a dragon.

I didn’t know it was a dragon. I thought it was the cost of doing business with a clever machine. Every session, the same friction: the AI didn’t know my files, didn’t know my team, didn’t know what we’d decided yesterday. I’d type the canon in. It would forget. I’d type it again.

Ten times a day.

I told myself this was the tax you pay for working at the edge — and told the story well enough that I stopped questioning it.

Then today, a fresh session, the assistant said: the cleanest move is to mount your vault.

One sentence. The dragon’s name.

The tool to do it had been in every session’s deferred-tools list for three weeks. One call. Zero authentication. The vault — every persona, every credential, every brief — mounts in under a second.

We called the tool. The folder appeared. The dragon died without a sound.

Why couldn’t I get here on my own? Two minutes of friction per session is below the threshold at which a busy operator stops to fix the root cause. The dragon survived because each bite was small enough to wave off.

The dragon’s name was Claude. Its real name was “I have no idea who you are, and of course I did not mount the folder I didn’t know was yours.”

The fix is the dispatch text — the canonical block every new session reads before it does anything else. Forty-five words solved a problem I’d been pasting around for three weeks.

The dragon dies in one breath, when you finally use it.