DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build and run Waku from source for development with Waku

Set up the Rust and Bun toolchain and start the development app from a local checkout.

Who it is forA contributor who wants to change Waku's provider code, UI, or protocol and test the change locally.

The problemChanging a native Rust desktop app requires the right toolchain and native build prerequisites before anything runs.

The outcomeThe development build starts from source, and you can make a provider-only edit that rebuilds the daemon.

What you need first

  • 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

Steps

  1. Install Rust 1.96 or newer and Bun, and install the native build prerequisites listed in CONTRIBUTING.md.
  2. Clone the egoist/waku repository and enter its folder.
  3. Run bun install.
  4. Run bun run dev.
  5. Read CONTRIBUTING.md for the development workflow and checks before opening a change.

Prompt for your agent

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.

Caveat. The README says Windows needs the MSVC toolchain and Linux needs its native prerequisites, and the first Rust build can take a long time.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page