egoist/waku

What it solves

Waku provides a unified, native desktop interface for managing multiple local coding agents. Instead of switching between different command-line interfaces (CLIs) or separate apps, users can manage projects, sessions, and transcripts in one place while keeping all data stored locally on their own machine.

How it works

It operates as a native desktop application (built with Rust and GPUI) that acts as an RPC client for a standalone background process called waku-daemon. This daemon handles the heavy lifting, including SQLite data management, Git operations, and communication with various agent CLIs (such as Claude Code, Cursor CLI, and Grok Build) using their native protocols.

Who it’s for

Developers who use multiple AI coding agents and want a centralized, local-first desktop environment to organize their work, switch models, and track conversation history without needing a remote account.

Highlights

• Unified Interface: Manage multiple supported agent CLIs (e.g., Amp, Claude Code, Codex CLI) in one app.
• Local-First: All projects, sessions, and app state are stored on the user's machine; no remote service or account is required.
• Session Control: Ability to queue or steer follow-up messages while an agent is working.
• Git Integration: Rewind tasks using conversation-aware checkpoints backed by Git.
• Flexible Configuration: Supports switching models and reasoning effort from a shared interface.