I open-sourced the setup I use to ship while I sleep

For a long time I was the slowest part of my own work.

Everything ran through one chat. One conversation, one me. Good ideas queued up behind whatever I happened to be typing. The model in front of me was fast. I was the line it had to wait in.

So I changed the job. Instead of doing the work, I direct it. I stay in one seat and advise, and the building happens in the background, in workers I hand tasks to and check on later. It runs whether I am at the desk or asleep.

That last part is the honest claim, so let me be careful with it. This is not ten times faster, and nothing builds itself. I still decide what gets made, and I review every result. What changed is that I stopped being the single point everything has to pass through.

The proof: I built part of the setup using the setup. I wrote a short spec for a tool I wanted, handed it to a background worker, and went to bed. In the morning the tool existed, its tests passed, and one question was waiting for me about a naming choice. I answered it. That was my whole night shift.

I packaged it and open-sourced it. It is called ARI-OS.

Repo: github.com/PUSHINGSQUARES/ARI-OS

Install page: aris-space.com/applications/ari-os

It is one loop, six steps, and you can learn it in an afternoon:

1. Brainstorm.

Talk the idea out until it is a clear outcome, not a vague wish.

2. Plan.

Turn that outcome into ordered steps.

3. Dispatch.

Hand a step to a background worker and let it run on its own.

4. Watch.

Glance at a small dashboard. See what is running and what is stuck.

5. Review.

Read what came back. Keep it, or send it back with notes.

6. Ship.

Merge the work that passed.

You live on steps one, five and six, the judgement steps. The worker takes three and four. Step two is shared. The parts that need your taste keep you. The parts that do not stop waiting for you.

If you are just getting started with Claude Code: it is pure Python, it installs with one command, it sits on top of your existing setup, and it is reversible. It distils four habits I lean on every day. A handoff layer, so a fresh session picks up cold without losing the thread. Background-first dispatch, so focused work runs while you stay free to steer. Spec-first thinking, so the work has a target before any code exists. And a memory, so the setup recalls what past sessions decided instead of guessing every time.

That last habit is the newest, and the one I lean on most. The memory lives on your own machine and remembers across sessions, so a new chat starts from what you decided last time, not a blank page. It stays narrow on whatever you are working on now, and only looks wider when you tell it to. Every so often it surfaces something from outside your current focus, the way a useful idea turns up when you step away from the desk. It does not think for you. It remembers, so you start from what you already know.

It carries the brain plainly, remembers across sessions (memory), stays narrow / looks wider when you tell it to (the tunnel + your consent), surfaces something from outside your focus (the wander) — and keeps the honesty anchor (it does not think for you).

The principle under all of it: the model is not the intelligence. The system around it is.

Read the deep-dive: https://aris-space.com/documents/tools-and-plugins/ship-while-i-sleep

//A<3

28 comments