Cydonia vs Waku
Both are native Rust desktop apps on GPUI that run Claude Code, Codex, Cursor, OpenCode and pi with no account. Waku adds git-backed rewind through a daemon; Cydonia speaks ACP and keeps articles and boards in the project.
Checked against each product's own site on
Waku and Cydonia are close relatives: both are native desktop apps written in Rust on GPUI, both run the coding agents you already use, and neither asks for an account. Waku puts a daemon between the window and the agents and adds checkpoints you can rewind to. Cydonia talks to agents over ACP and gives them documents and boards to work in.
| Cydonia | Waku | |
|---|---|---|
| License | MIT | GPL-3.0 |
| Platforms | macOS, Linux, Windows | macOS, Linux, Windows |
| Built with | Rust and GPUI | Rust and GPUI, with a standalone daemon over its own WebSocket protocol |
| Agents | Any agent in the ACP registry, or a command of your own | Amp, Claude Code, Codex CLI, Cursor CLI, Fx, Grok Build, Kimi Code, OpenCode, Pi, detected when installed |
| How it talks to agents | ACP | Each provider's own structured protocol, such as stream-json or JSON-RPC |
| Account | None | None |
| Rewind | No | A git checkpoint per prompt, restoring the code and the conversation |
| Documents and boards | Articles, boards and tables in .cydonia/ in the project |
No |
When to pick Waku
- You want to rewind a session, code and conversation together, to any earlier prompt.
- You want to reach the agents from a browser, through its daemon.
- You run Amp, Kimi Code or Grok Build, which it drives directly.
When to pick Cydonia
- You want what agents find written down as articles in the project, and work handed to them from a board.
- You want agents to read and write those articles and boards themselves, through Cydonia's MCP tools.
- You want any agent that speaks ACP, not a list of supported CLIs.
- You want an MIT license rather than the GPL.