If It Stops When I Close the Laptop, I'm Done With It

If a tool stops when I close the laptop, I’m done with it.

For years I picked tools the other way. Does it work while I’m looking at it? Can I click around, see the thing update, feel in control?

That’s the wrong test now.

The useful ones keep going after the lid is down. Notes that other systems can read without me exporting a file. A bot with its own computer, still working after I’ve left the room.

#The old stack needed me in the chair

Most of the software I used to run my life was built around a session. Open the app, do the work, close the app. The knowledge lived in that session. Next morning I had to open it again and remember where I was.

Obsidian was already closer than most of it. Plain markdown files, on disk, not locked in somebody else’s database. I can read them in twenty years. I can search them. I can hand them to something else.

What changed is where those files live.

They still start in Obsidian. That’s the editor. That’s where I write. Then they sync to GitHub, so every client that needs them can read the same files. An agent on a different machine. A script that runs overnight. Me, later, on another device. Nobody is waiting for me to export a zip.

This is not a notes-on-GitHub product. The notes are the files. Obsidian is just the nicest way to write them.

That sounds small. It isn’t. It’s the difference between a second brain that only works at my desk, and a set of files that anything I own can use.

#The lid test

I started putting everything else through the same filter.

Does this thing keep state when I’m not here? Can something else pick up the work, or does it need my cursor in the window? If I walk away for an hour, is progress still happening?

A chat window fails that test. You close the tab, the work stops. A bot with its own computer passes it. The machine is still on. The logins are still there. You only get pulled in when something actually needs you.

That’s why Grok Bot is interesting, and why I’m not going to write a review of it. Persistent computer, not a longer chat. Whether the beta is tidy this week is a different question. The category is the point.

Same test, different tool. Markdown in Obsidian, synced to GitHub, passes. A notes app that only exists as a webpage in my browser fails. A weekly job that runs while I’m out of the room passes.

#What I’m actually changing

I’m not ripping the whole stack out. I’m just not adding anything that needs me in the chair to be useful.

New tool, same three questions. Where do the files live? Can something else read them without me? Does the work continue when the lid is closed?

If the answers are “in the app”, “no”, and “no”, I’m out. I’ve spent enough years as the integration layer between systems that don’t talk to each other. That used to be a job. Now it’s a design smell.

AI is part of this, obviously. The useful bit isn’t a cleverer prompt, though. It’s a system that can see the same files I see, do the boring half, and wait for me on the bit that needs a decision.

I still write the opinions. I still say yes before anything goes live. The machine does the rest, including the rest that happens after I’ve closed the laptop.

That’s the filter. I’m sticking to it.