Waku rolls back code and AI context together

Waku wraps the coding agent CLIs you already run and rewinds code and conversation together, per its site. That fixes a real trust problem for developers: roll back a bad diff, and the agent still talks about code that's already gone.

Checkpoints live as hidden git refs, so rewinding the working tree and the provider conversation happens in the same step. Roll back a commit, and Waku resets the AI's memory of that commit too.

It's built natively for macOS on Rust and GPUI, the GPU-accelerated framework behind Zed. The app normalizes sessions, transcripts, tool activity, and checkpoints from different CLIs into one provider-neutral model, so switching agents doesn't mean losing history. Everything stays local: no telemetry, no cloud sync.

It picked up 32 points on Hacker News. Performance claims come from a single source and haven't been verified independently, so treat any speed comparisons with caution.

The bet

The interesting claim here isn't the UI. It's that context desync, not model capability, breaks trust in agent coding sessions. If you've rolled back a bad diff and watched the agent reference code that no longer exists, that's the bug Waku targets. Whether a wrapper layer can fix a problem that's really about how CLIs manage state is the open question. Worth watching: whether major CLI vendors build checkpoint-and-rewind natively and make a wrapper like Waku unnecessary.