What a session really costs
At the end of the top bar a chip says how the computer is doing: memory and CPU, with a green, amber or red dot — the kernel's own verdict. Hover it to see what is heavy and is not k0: if Chrome is the problem, better to know before closing sessions for nothing.
On every note there is what that session weighs. Not the claude process alone: everything it
dragged along — the MCP servers, the browsers they opened, a type check started from a commit hook.
Closing is never losing
Every way k0 frees memory is the same gesture as Close on a note: the session stops, its window goes, the memory comes back. The note keeps its place and its status, and Resume picks the conversation up where it was. A terminal that is working or planning is never closed, by k0 or by the knife, and neither is a note you marked always active.
k0 closes the ones you forget
The window costing you a gigabyte is the one you stopped thinking about yesterday. So after
twelve hours with nothing happening, k0 presses Close itself — on Your turn notes only, since
a question or a plan waiting is not saved until it is answered. A window used an hour ago is never
touched: k0 keeps four clocks for a session and the newest wins.
The knife closes the rest now
Twelve hours is long when you have twenty terminals open and want the memory back before lunch.
Next to each column's + there is a knife, with the number of terminals it would close:
- Click: closes that repository's terminals at Your turn.
- ⌘-click: closes everything that is not working — questions and plans waiting included. Hold ⌘ and every knife shows that bigger number, in red, before you click.
- It asks first, listing the stories. With nothing to close, it goes faint.
Columns that tidy away
Any column can be put away with the button next to the knife. One with a session still running
goes to Old with its name in red — out of your way, not forgotten — and comes back with a click.
A red note whose terminal was closed days ago no longer holds a column on the board by itself.
How to use it
- Nothing to switch on. The chip says it is watching:
RAM 79% · CPU 19% · closes at 12h. - A note k0 closed reads closed automatically; one you closed reads session closed.
- Change the hours with
closeIdleTerminalsAfterHoursin~/.k0/config.json.0switches the automatic closing off; the knife is always there.