Maintainer of this skill?
Automated security scan — not a certification.
by egoist
⚡ A native app for all your coding agents.
# Add to your Claude Code skills
git clone https://github.com/egoist/wakuGuides for using ai agents skills like waku.
Last scanned: 8/12/2026
{
"issues": [
{
"type": "npm-audit",
"message": "@esbuild-kit/core-utils: Vulnerability found",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "@esbuild-kit/esm-loader: Vulnerability found",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "drizzle-kit: Vulnerability found",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "esbuild: esbuild enables any website to send any requests to the development server and read the response",
"severity": "medium"
}
],
"status": "PASSED",
"scannedAt": "2026-08-12T05:37:19.496Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how waku compares with popular alternatives.
waku is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by egoist. ⚡ A native app for all your coding agents. It has 1,609 GitHub stars.
Yes. waku passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/egoist/waku" and add it to your Claude Code skills directory (see the Installation section above).
waku is primarily written in Rust. It is open-source under egoist on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh waku against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Waku is a fast, native desktop app for working with local coding agents. It is built in Rust with GPUI and keeps projects, sessions, transcripts on your machine.
On macOS, download the signed .dmg. It updates itself.
On Linux:
curl -fsSL https://waku.sh/install.sh | sh
The script installs into ~/.local without root. See
docs/linux.md for requirements, manual installation, and
uninstalling.
On Windows, run Waku-<version>-<arch>-Setup.exe from the
latest release. It installs
per-user and updates itself. A portable .zip is published alongside it. See
docs/windows.md for requirements and what is not available
there yet.
Waku works with:
Install and authenticate at least one supported agent CLI before starting Waku. Waku detects available CLIs automatically and uses each provider's native structured protocol and session continuity.
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. Waku Desktop depends on
waku-client, not on the daemon implementation. The
daemon owns task SQLite data, uploaded attachments, provider-native session
forks, and all workspace filesystem and Git operations; paths returned by it
always refer to the daemon host. The desktop retains only presentation state
and a disposable preview cache.
The browser client lives at apps/web and uses the generated
browser transport in packages/waku-client. Its
checked-in types are generated directly from the Rust protocol, while its
WebSocket client implements the same handshake, request IDs, subscriptions,
sequence deduplication, and replay cursors as the Rust client. Run
bun run protocol:generate after changing a wire type and
bun run protocol:check to verify that generated files are current.
Projectless task workspaces live on the daemon host under
~/.waku/projects/<date>/<slug>. The daemon moves workspaces created by the
older ~/.waku/<date>/<slug> layout on first load.
Configuration ownership is separate too: the Release desktop writes
~/.waku/app.json, while Debug stays isolated at temp/app.json. Daemon
provider and Computer Use settings live in ~/.waku/settings.json. The
desktop's Settings → Daemon page can explicitly
expose the child daemon on a fixed port, configure exact browser origins, and
copy its stable authentication token. It remains loopback-only by default.
When connected to a daemon managed outside the desktop process, Waku never interprets daemon paths on the client machine. The local folder picker and PTY are therefore unavailable until the protocol gains daemon-host picker and terminal-stream endpoints; files, diffs, Git, skills, usage, task state, and attachments already use daemon RPC.
Release apps bundle and sign waku-daemon. Development keeps the daemon at
target/debug/waku-debug-daemon, allowing provider-only edits to rebuild and
replace the daemon without relaunching Waku Debug.
Development is supported on macOS, Linux, and Windows and requires Rust 1.96 or newer and Bun. Linux supports both Wayland and X11, and Windows needs the MSVC toolchain; install the native build prerequisites listed in CONTRIBUTING.md first.
bun install
bun run dev
The embedded browser and experimental computer-use integration currently remain macOS-only. Agent sessions, projects, transcripts, skills, usage, diffs, file editing, and the terminal run natively on Linux and Windows.
See CONTRIBUTING.md for the development workflow and checks. Release maintainers should also read RELEASING.md.
You can support the project development via GitHub Sponsors.
Waku is licensed under the GNU General Public License v3.0 only.