The next layer of AI coding tools is not a chat app. It is a lightweight front-end on top of a background process.

The agent-tooling stack is about to split into a layer the chat-app frame cannot describe. Seven coding CLIs (Amp, Claude Code, Codex CLI, Cursor CLI, Grok Build, OpenCode, Pi) each ship their own session model, and the next UX surface has to talk to all of them without becoming seven wrappers bolted together. The shape that wins will be a thin client on top of a standalone daemon, with provider sessions running behind a versioned, authenticated protocol contract.

egoist/waku's new native app is the first open attempt at that shape. The waku README is explicit: "The native desktop is an RPC client of the standalone waku-daemon process. Provider sessions run in waku-core, behind the authenticated, versioned WebSocket contract in waku-protocol." That is not a product description. It is a separation-of-concerns pattern: UI, process boundary, session model, wire contract, each replaceable on its own timeline. The keyboard queue, the git-backed rewind of code and conversation together, and the local-only storage are downstream consequences of putting the protocol at the center.

The mechanism is portable. Any front-end that wants to outlive a single CLI will end up with a daemon, a versioned contract, and a client thin enough to swap. Waku's adoption is a separate question. The pattern is the news.