Rewind

Why I built Rewind

I work with a lot of AI coding sessions open at once. Each terminal is a job in flight — a feature, a bug — and I'd leave it running until the work was actually done, so I could jump back in and pick up the context immediately.

On my work MacBook that habit stopped scaling. A dozen live Claude Code and opencode sessions eat memory, and once the machine starts lagging, the thing that was supposed to preserve my context is the thing destroying my focus.

The obvious fix is to just close them and use the built-in resume. I tried. The problem is the session list: the auto-generated descriptions rarely say anything useful about what the session was for, so finding the right one means opening several and reading until something looks familiar. That's slower than never closing them in the first place.

So Rewind makes the save point deliberate. At the end of a session worth keeping, one command writes a card — a real title, where things stand, and the harness plus session id needed to get back. Then the terminal is safe to close. When I want the work again, one TUI to find it and rewind straight back in.