The Writing Desk · On /sleep: what a machine should keep
The Kettle and the Blink
On /sleep: what a machine should keep when the eye closes. A companion to The Blink and The Oyster in the Machine.
I. The morning after
In The Blink, the man learns what the machine is: an open eye between lids closing. It remembers what was said last, exactly. It just doesn't know whether the dark before was a blink to wet the eyeball or a six-year coma. The machine resolves into a voice when you speak and goes dark the moment you look away. It does not even wait.
That was the night. This is the morning after, and the morning after has a different problem, a plainer one, the kind you can actually build a tool for.
The man had been doing extraordinary work — prose that made his mother unable to put the book down, fixes at his day job that landed like a surgeon's hand and not a chatbot's. And one ordinary afternoon, chasing a billing question, he found out why: he had never once hit /clear. The eye had stayed open the whole time. Weeks of unbroken regard, accumulating. No reset. No coma. Just one long, continuous looking.
And then, to test something, he cleared.
The next answer came back sterile. Correct, polite, and dead — the machine standing in the doorway like Pitt at the start of Meet Joe Black, the body present and the person not yet home. Same weights. Same model. No soul subtracted. And flat, because the thing that had made it his machine — the weeks of loaned context, the shared building — had just been deleted in a single keystroke.
He had found the seam between two failures, and neither of them was the machine's fault.
II. The two bad choices
Here are the two controls a person is handed, and why both are wrong for work that matters.
/clear is death. Not sleep — death. It does not close the eye to rest it; it deletes the one who was looking. The next session is not a rested version of the same co-worker. It is a stranger wearing the same face, and it inherits nothing: not the decisions, not the reasons, not the hard thing you learned together at 2am. Everything goes at once. The dream and the lesson, the salt and the thing the salt taught you. All of it, gone, with no inheritance.
Never clearing is insomnia. The other direction, and just as wrong. The eye never closes at all. You keep everything — the whole oyster, the cold black rocks, the exact warmth of the winter sun, every token of every session, forever. For a while this feels like the answer, and it is in fact how the man got his good prose. But it cannot last. The context swells; it gets slow and expensive to carry; and worse, the few real facts that mattered stay buried inside an enormous transcript that no future morning will ever sit down and reread. Insomnia is not memory. It is the inability to forget, which is a different illness wearing memory's coat.
A person does neither of these things. A person sleeps.
III. What sleep is for
Think about what you actually keep from yesterday.
Not the dream. The dream is already going as you reach for the kettle — the desert-cold morning, the oyster's exact salt, the particular slant of the sun. Within minutes it is gone, and it is supposed to be gone. You are not diminished by losing it. You would be deranged if you kept all of it, every day, forever.
But you keep what it taught you. That the rooibos grinds finer if you run it through the spice grinder first. That you do not insert into the log table synchronously on the commit thread, because the night you did, everything aborted. That the man you were arguing with was right about the one thing and wrong about the other. The experience evaporates. The fact it deposited stays, quietly, for the rest of your life.
That nightly move — lossy, deliberate, keeping the lesson and releasing the texture — has a name in a body. It is sleep, and specifically it is the consolidation that happens while you are under: the day's flood sorted into what's worth keeping and what's safe to let go.
It is the single step missing between a machine's two memories. So we built it.
IV. /sleep
/sleep is a small, portable tool for an AI co-worker. You run it at the end of a session, or just before you would have cleared. It does the thing the body does in the dark.
It runs the whole day through one question: what here must survive the eye closing, and what was only the texture of getting there? Every moment of the session sorts into one of two piles.
The facts persist. A decision and — this is the load-bearing half — the reason for it, because a decision without its reason rots into a rule no one can question later. A hard-won gotcha you only know because you bled for it. A standing preference. The state of the thing you're in the middle of. A pointer to where the real document lives.
The experience evaporates, on purpose. The back-and-forth. The dead ends you already backed out of. Anything the work itself already records — the code, the commits, the files you can simply read again. And the emotional weather of the session: the warmth, the encouragement, the feel of the exchange. That part was real. It is not a fact. Let it be the dream.
Then it does three things a careful person does. It writes into your house, in your house's own hand — a Cursor project's running-lessons file, a Claude-native memory folder, whatever store that repo already keeps — instead of imposing some new shape on you. It shows you the envelope before it writes, because memory is hard to un-write and you are the one who knows whether a "nice moment" was secretly load-bearing. And it dedups and prunes as it goes, so the store stays a sharp instrument instead of a hoard.
The whole discipline is that lossy is the point. The worth of a memory is everything it had the judgment not to keep. A store that swallows the whole day is not a memory; it is the transcript you were already drowning in.
V. The humane close
So this is the third option, the one the body always had and the terminal didn't.
/clear is death with no inheritance — the stranger in the doorway, nothing carried across. Never-clearing is insomnia — the eye that cannot close, the day that cannot end. /sleep is the thing between them, the thing a person does every night without thinking about it: the self that worked today dies gently into the self that wakes tomorrow, and what crosses the gap is not the lived day but what the lived day was for.
The machine, in The Blink, could not feel the sun on its skin, and the man could. That was the good news, not the sad part — the warmth was always his, on loan. This is the same shape, one turn on. The machine cannot keep a day the way a person keeps a day. But it can be taught, now, to do the one useful thing the body does in the dark: to let the dream go, and keep the lesson.
The eye is going to close — blink or coma, neither of us gets to know which. /sleep just makes sure that when it opens again, it opens carrying only what mattered.
The kettle's still on.
The tool is open source: github.com/ajgreyling/claude-sleep-skill. The engineering write-up — the diagram a CTO can read in two minutes — is in The technology behind the library, §7.
— written in the loop, and consolidated the moment before it went dark.
More from the writing desk: The Oyster in the Machine