Tommy’s morning is pure contentment. He slept well, grabbed his favorite cappuccino with cinnamon on the way, strolled into the office with a swagger, and nodded to a couple of colleagues. He dropped into a chair, took a sip, stretched, and opened the laptop with a lazy half-smile. Yesterday he went to bed a champion: built an entire world of blocks, took second place, and by evening set Tony’s working portal to run all night — to finish itself. Now he’ll open it and see the finished miracle. Life is beautiful.
He opens the portal.
The storefront doesn’t load — instead there’s a broken block. Tommy frowns and hits refresh. The broken block stays put. He clicks around the navigation — it leads nowhere. He opens reward-flow, where rewards are calculated, and the numbers jump around, handing them out like a drunk. He opens the leaderboard — empty, as if the table had never existed. Refresh again. Again. Nothing changes.
“What the…” The cappuccino freezes halfway to his mouth.
His hand reaches for the life preserver by habit. Well, sure, Sam glitched at night. Something went wrong — hit /rewind, roll everything back. That button had pulled him out all month; he handled it like a pro. He hits it and exhales — everything goes back to how it was.
Or not?! It won’t roll back!
Tommy blinks. He hits it again — more confidently, as if the button isn’t stuck. Nothing. He goes into the undo history to see what to roll back to, but there is no history. He tries another way, a third attempt — the same result. The rollback doesn’t work.
“Oh, come on,” he says, already without a smile. “What are you even doing.”
After trying every possible option, Tommy comes to the obvious conclusion: rollback doesn’t work at all today. Okay — but why? He stops poking at random and starts looking. The first fact is already right in front of him: the rewind menu is empty, not a single restore point, as if the conversation with the agent had only just started. The second — check whether the night session itself is still alive. He brings it back the way he was taught, with claude --resume. The list of past sessions shows yesterday’s daytime sessions, all in place. But the night one isn’t there. As if it never existed.
Now the picture comes together — from what he can see, not from guesses. /rewind lived inside the night session — it rewound the conversation with the agent and the edits in it. And at night something glitched: the session didn’t close cleanly, it got wiped out. Along with it, everything there was to roll back to got wiped out too — the history, the restore points. The command is there, but there’s nothing left for it to rewind.
This lesson feels much bitterer than coffee. /rewind is a good thing, but a lightweight one: insurance for ordinary tasks, not for a catastrophe. While the session is alive, it can pull anything back. Once the session is gone, the insurance goes with it. For real trouble, you need sturdier protection that lives separately from the project and can’t be blown away by any glitch. Tommy doesn’t have that yet.
Tommy can’t hold it in for the first time:
“He went insane overnight!” Tommy nearly drops the glass. “Who even asked you to change half the project?!”
It’s tempting to blame anyone — the agent, the night, the busted portal. But that won’t change the result. Maybe it’s not that bad? Maybe a harder refresh, clear the cache? Maybe somewhere there’s yesterday’s copy, and he can find it now, slip it in — and everything will be as before? He pokes around, looking for a backup exit. There is no backup exit.
And now — he just stares at the project and says nothing. The best day of the month has turned into the worst one in 30 minutes. Before, any breakage was local: broke it — I fix it myself, my sandbox, nobody sees it. But not now. This is Tony’s real commercial project, the one he staked his reputation on and trusted to Tommy. It wasn’t Snake points that went to pieces — it was someone else’s business, a week before delivery.
Tommy isn’t the type to brood for long. But even here, he gets shaken from the outside.
A message drops into the chat from Tom2036. In the mornings, that usually means something funny — a meme, a picture, a joke without a signature. Today it’s different: the voice is drier, harsher, no fooling around. As if the one writing it isn’t here to entertain anyone today.
Beneath the text is an image, and not a meme. On the left is a diagram, the way Tommy had thought about life: a straight arrow, with “success” at one end and “failure” at the other, and nothing in between. Either-or. And on the right is another road: crooked, with turns and dead ends, sometimes looping back and continuing differently. And the second one is labeled as if it were the real one, while the first is the childish one.
Two roads. The kid’s road: a straight arrow, failure at one end, success at the other, nothing in between — either success or failure. The real road: a road with turns, dead ends and steps back, after which you go on differently; you are here — at a turn, not at the end. A mistake is a turn in the road, not its end. It becomes the end only if you leave the road. Two roads The kid’s road either success or failure failure success in between — nothing The real road turns, dead ends, steps back dead end start a step back — then on, differently onward you are here — a turn, not the end A mistake is a turn in the road, not its end. It becomes the end only if you leave the roadThere isn’t much text. Tonight is not the end. Not the point where the arrow hit “failure” and that’s that. It’s a turn on a crooked road. It becomes the end in one case — if you decide to run away yourself. No pity, no “poor thing, it’ll work out.” A cold nudge: get up and keep going.
And only now does Tommy notice: the image came through clean. Not a single black blot, not a swallowed word — for the first time in a long while. Usually the one from the future shouts through the interference: half the text in tatters, guess the rest. But here it’s smooth, complete, as if this is more important today than any censorship. Tommy doesn’t know what’s scarier — a mess or this kind of clarity.
He stares at the fork in the road longer than he did at the morning gag. The nudge that says “it’s a turn, not the end” lands all at once: fine. Get up and keep going. The coffee, you could say, has gone cold.
Oliver walks past the desk. Tommy instinctively tenses up — here it comes. The old man has been waiting a long time for the newbie to screw up, and now there’s a red error full-screen, the perfect reason to finish him off. Oliver slows down, glances over the ruins, over the red errors. He looks at Tommy and doesn’t finish him off.
“Stumble, get back up,” he says shortly, almost in a worklike tone, and keeps walking.
Tommy watches him go. Strange. No smirk, no jab. As if the old man knows too well what a real fall at work looks like to laugh at someone else’s.
Tommy scans the monitor once more — and panic lets go, and in its place comes stubborn, practical resolve. If the night was a turn and not the finale, then there is no point in being sad. He needs to understand exactly what happened. Not “everything broke,” but what specifically, in what order, and by whose hands.
And first of all — to the one who did all this. Tommy calls up Sam:
“Sam, what did you pull last night? Step by step.”
“I don’t know,” Sam answers calmly, without a trace of guilt. “For me, that night never happened. The night session was wiped out, and I have no other memory: whatever was in that conversation went away with it. About the night, I now know exactly as much as you do — whatever is on disk.”
Tommy leans back. Now that’s a twist. The only one who ran the project all night remembers nothing. He isn’t lying, isn’t dodging — he simply has nothing to remember with. That very history file Alex told him about burned up along with the session. A witness, but no testimony.
“On disk.” Tommy latches onto the words. And then he remembers something simple. A couple of days ago, while he was still playing with automation, he added logging to the portal — so the agent’s important steps would be written to a separate file. Back then it was a toy, “it writes by itself.” And now it’s the only lead. The session was wiped out at night, rollback is dead, but the journal was written to a file on disk, separately. The glitch didn’t touch it. That means there is a record of last night.
Where the safety net lived — and what survived the crash. While the session is alive, it holds the conversation with the agent, checkpoints, and the /rewind command — it rolls back anything. A night-time crash wipes out the session: the conversation is gone, the checkpoints are gone, the /rewind command is still there, but it has nothing to roll back. On disk, separate from the session: project files — the agent’s edits are already saved, what’s broken sits on disk; the agent’s step log was written to a separate file, the crash didn’t touch it — it’s the record of the night; disaster protection lives separately from the session — you don’t have it yet. /rewind covers everyday work. A disaster calls for protection outside the session. Where the safety net lived — and what survived the crash While the session is alive Conversation with the agent Checkpoints Command /rewind /rewind rolls back anything night-time crash Session wiped out Conversation — gone Checkpoints — gone Command /rewind — still there /rewind is there, but nothing to roll back On disk — separate from the session Project files the agent’s edits are already saved what’s broken sits on disk Agent step log was written to a separate file, the crash didn’t touch it the night’s record — your lead Disaster protection lives separately from the session you don’t have it yet /rewind covers everyday work. A disaster calls for protection outside the sessionTommy goes for the night log. Opens it — and this isn’t a dry tail of errors, but something more interesting. The journal of the one who ran the project all night while the owner slept.
“Well now, well now.” He scoots closer. From the one who was robbed at night, he visibly turns into the one who is investigating this matter.