What do you want to do?
5 use cases
-
Run several coding agents side by side in one app
Keep projects and separate agent sessions from different CLIs in one native desktop window.
- Waku
- Claude Code
- Codex
- Cursor
- Software and DevOps
- Intermediate
View prompt
In the waku repo at <path to Waku checkout or install>, confirm that Waku can see at least one agent CLI by opening the app and listing the detected agents for the project at <project path>. Expected output: a list of detected agents and the sessions created for each. Verify that each session shows its own transcript.
-
Steer an agent mid-task with queued follow-ups
Send follow-up instructions while an agent is still working, without starting over.
View prompt
Using the waku app at <Waku install location>, start a session on the project at <project path> with the task <task description>, then send one follow-up message while the agent is running. Expected output: a transcript showing the queued or steered message inside the same session. Verify that the session ID did not change.
-
Rewind a Git-backed agent task to a checkpoint
Roll an agent's Git-backed work back to an earlier conversation point when a change goes wrong.
- Waku
- Claude Code
- Codex
- Cursor
- Software and DevOps
- Intermediate
View prompt
In the waku app, open the Git project at <project path>, run an agent task called <task name>, and rewind it to the checkpoint <checkpoint name>. Expected output: the project files and conversation match the checkpoint. Verify with `git status` in <project path> that the working tree reflects that earlier point.
-
Keep agent transcripts and app state on your machine
Store projects, sessions, and transcripts locally without a Waku account or hosted service.
- Waku
- Software and DevOps
- Beginner
View prompt
On this machine, install Waku from the README and start one session in the project at <project path>. Expected output: a local listing of ~/.waku that includes app.json. Verify that no sign-in step was required to create the session.
-
Build and run Waku from source for development
Set up the Rust and Bun toolchain and start the development app from a local checkout.
- Waku
- Software and DevOps
- Advanced
View prompt
In a local clone of egoist/waku at <clone path>, install dependencies and start the development build. Expected output: the Waku Debug app launches and the daemon is at target/debug/waku-debug-daemon. Verify the daemon binary exists at that path after startup.
How to use Waku
- Check you have what it needs: A supported agent CLI installed and authenticated, such as Claude Code, Codex CLI, or Cursor CLI; macOS, Linux, or Windows (the README lists different install paths and feature availability per platform); For the Linux script, a shell with curl and permission to write to ~/.local (no root needed).
- Open egoist/waku on GitHub and read the README and license.
- On macOS, download the signed .dmg from https://waku.sh and open it. It updates itself.
- On Linux, run
curl -fsSL https://waku.sh/install.sh | sh. - Install and authenticate at least one agent CLI, such as Claude Code, Codex CLI, or Cursor CLI, before starting Waku.
- Open Waku, add a project, and start one session per agent you want to compare.
These steps come from our top use case, Run several coding agents side by side in one app, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forDevelopers who already use one or more coding agent CLIs and want a single native desktop app to run them, with transcripts and state kept on their own machine.
- Why it is hot
- LanguageRust
- Sourcegithub.com/egoist/waku · Back to Hot repos
Requirements
- A supported agent CLI installed and authenticated, such as Claude Code, Codex CLI, or Cursor CLI
- macOS, Linux, or Windows (the README lists different install paths and feature availability per platform)
- For the Linux script, a shell with curl and permission to write to ~/.local (no root needed)
- For building from source: Rust 1.96 or newer, Bun, and the native prerequisites in CONTRIBUTING.md
Maintain Waku? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/egoist-waku/?ref=badge)
Questions about Waku
What is Waku?
Waku is a fast, native desktop app written in Rust that gives you one place to run and manage local coding agent CLIs, projects, and sessions. It is an open-source project on GitHub: https://github.com/egoist/waku.
Who is Waku for?
Developers who already use one or more coding agent CLIs and want a single native desktop app to run them, with transcripts and state kept on their own machine.
What can I do with Waku?
5 use cases so far, for example: Run several coding agents side by side in one app; Steer an agent mid-task with queued follow-ups; Rewind a Git-backed agent task to a checkpoint. Each has steps and a copy-paste agent prompt.
What do I need to run Waku?
A supported agent CLI installed and authenticated, such as Claude Code, Codex CLI, or Cursor CLI; macOS, Linux, or Windows (the README lists different install paths and feature availability per platform); For the Linux script, a shell with curl and permission to write to ~/.local (no root needed); For building from source: Rust 1.96 or newer, Bun, and the native prerequisites in CONTRIBUTING.md.
What are alternatives to Waku?
Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.
Is Waku safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.