Back to the Finder

Waku

Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.

Product websitegithub.com Compare with others Missing or wrong data?

Waku product interface, supplied by its publisher
Desktop app
Mac, Windows and Linux
Browser
Yes
Phone
Not listed
Command line
Yes
Agents
Claude Code, Codex, Cursor Agent, OpenCode, Pi and Grok
Your subscription
Works with your own plan
Agents run
On your computer and on your own server
Laptop closed
Keeps going
Isolation
Worktree
Parallel agents
Yes
Scheduled runs
No
Coordinator agent
No
Built-in issues
No
Pull requests
No
Review screen
Yes
Team
Not listed
Self-hosting
Yes
Licence
GPL-3.0
Price from
Free
How it charges
No paid plan
Paid plans from
Not listed

Receipts

Checked
· oldest answer 2026-11-08
Findings
30 published · 20 cross-checked by a second agent · read them all
Sources
19 public pages on 2 sites: github.com, waku.sh
Screenshot
github.com, retrieved · first party repository · shows appearance, not capability
Method
Same rules for all 103 researched ADEs. How we check · Report wrong data

What it does

Where you use it

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

Source and scope for Where you use it

Agents it runs

Waku integrates provider-native session protocols for several coding agents.

Source and scope for Agents it runs

Accounts and subscriptions

Existing authenticated CLIs are required; subscription billing routes were not separately established.

Source and scope for Accounts and subscriptions

Where agents run

Local daemon execution is documented, with an externally managed daemon connection mode.

Source and scope for Where agents run

How work is kept apart

Waku can start a task in a new Git worktree created by the daemon under ~/.waku/worktrees; the desktop composer offers the choice. This separates files and is not a security sandbox.

Source and scope for How work is kept apart

Parallel work

Per-session runtimes continue in the background when changing views.

Source and scope for Parallel work

Scheduled runs

The pinned Waku daemon starts turns on explicit client commands. It contains no product scheduler or external-event task starter.

Source and scope for Scheduled runs

Git and pull requests

Product includes Git and commit dialog; PR creation was not established.

Source and scope for Git and pull requests

Licence and source

Waku source declares GPL-3.0-only.

Source and scope for Licence and source

Price

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

Source and scope for Price

JSON for agentsMarkdown for agents

Report wrong dataSuggest a missing ADE

Typed filters

Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.

Typed filter values
FilterValue
Desktop OS: macOSYes
Desktop OS: WindowsYes
Desktop OS: LinuxYes
Web clientYes
Phone access: Native iOSNo
Phone access: Native AndroidNo
Phone access: Phone browserUnknown
CLIYes
Coding agents: Claude CodeYes cross-checked
Coding agents: CodexYes cross-checked
Coding agents: Cursor AgentYes cross-checked
Coding agents: Gemini CLINo
Coding agents: OpenCodeYes cross-checked
Coding agents: PiYes cross-checked
Coding agents: GrokYes cross-checked
Coding agents: AiderNo
Coding agents: AntigravityNo
Use my subscriptionYes cross-checked
Where agents run: On your computerYes
Where agents run: On your own serverYes
Where agents run: In the vendor's cloudNo
Workspace isolation: Git worktreeYes
Workspace isolation: ContainerNo
Workspace isolation: VM or microVMNo
Parallel runsYes cross-checked
CoordinatorNo
Native issue trackingNo
Unattended triggersNo
Shared promptingUnknown
Team rolesNo
SSONo
Pull request workflowNo
Review interfaceYes cross-checked
Product license: Apache-2.0No. GPL-3.0 cross-checked
Product license: MITNo. GPL-3.0 cross-checked
Product license: GPL-3.0Yes. GPL-3.0 cross-checked
Product license: GPL-3.0-or-laterNo. GPL-3.0 cross-checked
Product license: AGPL-3.0No. GPL-3.0 cross-checked
Product license: AGPL-3.0-or-laterNo. GPL-3.0 cross-checked
Product license: Elastic License 2.0No. GPL-3.0 cross-checked
Product license: Custom termsNo. GPL-3.0 cross-checked
Product license: ProprietaryNo. GPL-3.0 cross-checked
Self-hostingYes cross-checked
Telemetry opt-outUnknown
Free accessYes cross-checked
Starting price: FreeYes. Free
Starting price: Up to $20/monthNo. Free
Starting price: $21–40/monthNo. Free
Starting price: $41–100/monthNo. Free
Starting price: Over $100/monthNo. Free
Starting price: Contact for pricingNo. Free
Pricing model: Free, no paid planYes
Pricing model: Free planNo
Pricing model: SubscriptionNo
Pricing model: Per seatNo
Pricing model: Usage-basedNo
Pricing model: Per machine or computeNo
Pricing model: Bring your own keyUnknown
Pricing model: One-time purchaseNo
Paid plans from: No paid planUnknown
Paid plans from: $10 or less/monthUnknown
Paid plans from: $11–20/monthUnknown
Paid plans from: $21–40/monthUnknown
Paid plans from: $41–100/monthUnknown
Paid plans from: Over $100/monthUnknown
Paid plans from: Contact salesUnknown
Lifecycle status: ActiveUnknown
Lifecycle status: SunsettingUnknown
Keeps going with laptop closedYes
Open-source licenseYes. GPL-3.0 cross-checked
Any desktop appYes
Paid plan up to $20/monthUnknown
Paid plan up to $40/monthUnknown
Any phone clientUnknown

Filter receipts

Desktop OS: macOS: Yes

Desktop OS: macOS

Typed value: Yes.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Desktop os: macOS signed dmg, a Linux install script into ~/.local, and a Windows per-user installer or portable zip.
  • Task actions: Queue or steer follow-up messages while an agent runs.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Desktop OS: Windows: Yes

Desktop OS: Windows

Typed value: Yes.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Desktop os: macOS signed dmg, a Linux install script into ~/.local, and a Windows per-user installer or portable zip.
  • Task actions: Queue or steer follow-up messages while an agent runs.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Desktop OS: Linux: Yes

Desktop OS: Linux

Typed value: Yes.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Desktop os: macOS signed dmg, a Linux install script into ~/.local, and a Windows per-user installer or portable zip.
  • Task actions: Queue or steer follow-up messages while an agent runs.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Web client: Yes

Web client

Typed value: Yes.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Browser: The pinned release includes a user-hostable browser client with explicit startup, build/deploy and daemon-connection instructions.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. Waku apps/web/src/routes/index.tsx

    Finding: The v0.1.20 source release includes a browser workspace route and instructions to launch it with bun --filter @waku/web dev, connect an existing daemon URL/token and configure its allowed browser origin. Build and deployment commands support a user-hosted browser client.

Phone access: Native iOS: No

Phone access: Native iOS

Typed value: No.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Mobile apps: The pinned release packages native clients only for macOS, Linux and Windows; no native phone application is distributed.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. Waku .github/workflows/release.yml

    Finding: The release workflow packages only macOS, Linux and Windows native applications. The repository has a separate browser app, with no native iOS or Android release target.

Phone access: Native Android: No

Phone access: Native Android

Typed value: No.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Mobile apps: The pinned release packages native clients only for macOS, Linux and Windows; no native phone application is distributed.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. Waku .github/workflows/release.yml

    Finding: The release workflow packages only macOS, Linux and Windows native applications. The repository has a separate browser app, with no native iOS or Android release target.

CLI: Yes

CLI

Typed value: Yes.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Cli: The product-owned waku-daemon command starts/configures the backend with documented bind and origin options; it does not provide a terminal prompt interface.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. Waku crates/waku-daemon/src/main.rs

    Finding: Waku ships the product-owned waku-daemon CLI with bind, parent-pid, allow-origin and explicit non-loopback exposure controls. It starts the Waku backend; it is separate from the coding-agent CLIs and is not a headless agent-prompt command.

Coding agents: Claude Code: Yes cross-checked

Coding agents: Claude Code

Typed value: Yes.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: Codex: Yes cross-checked

Coding agents: Codex

Typed value: Yes.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: Cursor Agent: Yes cross-checked

Coding agents: Cursor Agent

Typed value: Yes.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: Gemini CLI: No

Coding agents: Gemini CLI

Typed value: No.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: OpenCode: Yes cross-checked

Coding agents: OpenCode

Typed value: Yes.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: Pi: Yes cross-checked

Coding agents: Pi

Typed value: Yes.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: Grok: Yes cross-checked

Coding agents: Grok

Typed value: Yes.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: Aider: No

Coding agents: Aider

Typed value: No.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coding agents: Antigravity: No

Coding agents: Antigravity

Typed value: No.

Waku integrates provider-native session protocols for several coding agents.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi/Oh My Pi, Amp, Fx, Grok, Kimi and DeepSeek.
  • Model providers: Model choices are surfaced through the selected coding agent, not a separate Waku model account.
  • Session integration: Codex app-server, ACP, Pi RPC, Claude/Amp streaming protocols, OpenCode HTTP/SSE.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Use my subscription: Yes cross-checked

Use my subscription

Typed value: Yes.

Existing authenticated CLIs are required; subscription billing routes were not separately established.

  • Agent subscriptions: Waku drives the agent CLIs the user has installed and authenticated, so their native sign-ins and plans apply. Not tested; plan terms not checked.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

  2. Waku README, supported agents

    Finding: Users install and authenticate at least one supported agent CLI before starting Waku, which detects the CLIs and drives them through each provider's native protocol; Waku installs from a signed download or install script.

Where agents run: On your computer: Yes

Where agents run: On your computer

Typed value: Yes.

Local daemon execution is documented, with an externally managed daemon connection mode.

  • Local: Provider processes execute on the daemon host.
  • Byo remote: Desktop can connect to a daemon managed outside its own process; remote paths always refer to daemon host.
  • Provisioning: Default bundled daemon is loopback-only.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Where agents run: On your own server: Yes

Where agents run: On your own server

Typed value: Yes.

Local daemon execution is documented, with an externally managed daemon connection mode.

  • Local: Provider processes execute on the daemon host.
  • Byo remote: Desktop can connect to a daemon managed outside its own process; remote paths always refer to daemon host.
  • Provisioning: Default bundled daemon is loopback-only.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Where agents run: In the vendor's cloud: No

Where agents run: In the vendor's cloud

Typed value: No.

Local daemon execution is documented, with an externally managed daemon connection mode.

  • Local: Provider processes execute on the daemon host.
  • Byo remote: Desktop can connect to a daemon managed outside its own process; remote paths always refer to daemon host.
  • Provisioning: Default bundled daemon is loopback-only.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Workspace isolation: Git worktree: Yes

Workspace isolation: Git worktree

Typed value: Yes.

Waku can start a task in a new Git worktree created by the daemon under ~/.waku/worktrees; the desktop composer offers the choice. This separates files and is not a security sandbox.

  • Worktree: The desktop composer offers a New worktree workspace and the daemon creates it beneath ~/.waku/worktrees. Source inspection at v0.1.20.
  • Source inspection only; no installed-product test. Container, VM and process isolation were not established.
  1. Waku daemon worktree module

    Finding: The daemon creates an isolated Git worktree for a task beneath ~/.waku/worktrees on first submission when the user chose a new worktree.

  2. Waku desktop composer workspace menu

    Finding: The native desktop composer offers a 'New worktree' workspace choice, with a base branch, alongside existing worktrees.

Workspace isolation: Container: No

Workspace isolation: Container

Typed value: No.

Waku can start a task in a new Git worktree created by the daemon under ~/.waku/worktrees; the desktop composer offers the choice. This separates files and is not a security sandbox.

  • Container: The pinned workspace/driver implementation has no Waku-owned container or VM isolation backend; provider sandbox settings are separate.
  • Vm: The pinned workspace/driver implementation has no Waku-owned container or VM isolation backend; provider sandbox settings are separate.
  • Source inspection only; no installed-product test. Container, VM and process isolation were not established.
  1. Waku crates/waku-protocol/src/model.rs

    Finding: The complete Waku workspace enum has ordinary Local, NewWorktree and Worktree cases. The daemon starts provider drivers as processes on its own host; no Waku-owned container or VM isolation backend is implemented. Provider-native sandboxing is a separate scope.

Workspace isolation: VM or microVM: No

Workspace isolation: VM or microVM

Typed value: No.

Waku can start a task in a new Git worktree created by the daemon under ~/.waku/worktrees; the desktop composer offers the choice. This separates files and is not a security sandbox.

  • Container: The pinned workspace/driver implementation has no Waku-owned container or VM isolation backend; provider sandbox settings are separate.
  • Vm: The pinned workspace/driver implementation has no Waku-owned container or VM isolation backend; provider sandbox settings are separate.
  • Source inspection only; no installed-product test. Container, VM and process isolation were not established.
  1. Waku crates/waku-protocol/src/model.rs

    Finding: The complete Waku workspace enum has ordinary Local, NewWorktree and Worktree cases. The daemon starts provider drivers as processes on its own host; no Waku-owned container or VM isolation backend is implemented. Provider-native sandboxing is a separate scope.

Parallel runs: Yes cross-checked

Parallel runs

Typed value: Yes.

Per-session runtimes continue in the background when changing views.

  • Concurrent sessions: Each session has its own runtime, not tied to the selected view.
  • Status visibility: Runtime events include turn started/finished, permission, error and process exit.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

Coordinator: No

Coordinator

Typed value: No.

Waku exposes independent provider sessions and their native subagent activity. The pinned daemon/protocol supplies no product coordinator role or agent-to-agent delegation interface.

  • Orchestration owner: No Waku-owned coordinator role or delegation operations in the pinned command set and daemon implementation.
  • Bounded inspection of the full Command enum, daemon dispatcher and core/protocol sources; provider-native subagents are not Waku orchestration.
  1. Waku crates/waku-protocol/src/protocol.rs

    Finding: The closed command set provides client-driven session starts, prompts, steering, cancellation and session persistence. Source inspection found no Waku coordinator/delegation role, schedule service, external-event run starter or separate issue operations. Provider-native subagents are separate.

Native issue tracking: No

Native issue tracking

Typed value: No.

Waku tasks are persisted agent sessions. The pinned model and persistence API provide no independent product issue or backlog entity.

  • Task session separation: Tasks are AgentSession objects, without a distinct issue entity or state machine.
  • The source uses task as the session name; a conversation/session list does not meet the native issue filter.
  1. Waku crates/waku-protocol/src/model.rs

    Finding: Persisted tasks are AgentSession records with provider, conversation, workspace and run status. Projects group sessions. No separate issue/backlog entity or issue state machine exists in the pinned model or daemon persistence API.

Unattended triggers: No

Unattended triggers

Typed value: No.

The pinned Waku daemon starts turns on explicit client commands. It contains no product scheduler or external-event task starter.

  • Schedules: No product-owned scheduler or event-to-run service in the pinned daemon and protocol.
  • Events: No product-owned scheduler or event-to-run service in the pinned daemon and protocol.
  • Recurring tasks: No product-owned scheduler or event-to-run service in the pinned daemon and protocol.
  • Bounded search of core/protocol/src and full dispatcher for cron, scheduler, schedule, webhook and trigger; user scripts are outside this scope.
  1. Waku crates/waku-protocol/src/protocol.rs

    Finding: The closed command set provides client-driven session starts, prompts, steering, cancellation and session persistence. Source inspection found no Waku coordinator/delegation role, schedule service, external-event run starter or separate issue operations. Provider-native subagents are separate.

Team roles: No

Team roles

Typed value: No.

Waku uses a shared full-control daemon capability token and browser-origin checks. The pinned authentication path has no organization roles, project roles or enterprise SSO.

  • Organization roles: The pinned daemon only checks the shared capability token and allowed origins, without users, roles or SSO.
  • Project roles: The pinned daemon only checks the shared capability token and allowed origins, without users, roles or SSO.
  • Sso: The pinned daemon only checks the shared capability token and allowed origins, without users, roles or SSO.
  • Trusted clients share full daemon control; this is not a named human identity or role system.
  1. Waku crates/waku-daemon/src/main.rs

    Finding: The daemon authenticates trusted clients with one full-control WAKU_DAEMON_TOKEN and exact allowed browser origins. It has no per-user/workspace roles or enterprise identity/SSO flow.

SSO: No

SSO

Typed value: No.

Waku uses a shared full-control daemon capability token and browser-origin checks. The pinned authentication path has no organization roles, project roles or enterprise SSO.

  • Organization roles: The pinned daemon only checks the shared capability token and allowed origins, without users, roles or SSO.
  • Project roles: The pinned daemon only checks the shared capability token and allowed origins, without users, roles or SSO.
  • Sso: The pinned daemon only checks the shared capability token and allowed origins, without users, roles or SSO.
  • Trusted clients share full daemon control; this is not a named human identity or role system.
  1. Waku crates/waku-daemon/src/main.rs

    Finding: The daemon authenticates trusted clients with one full-control WAKU_DAEMON_TOKEN and exact allowed browser origins. It has no per-user/workspace roles or enterprise identity/SSO flow.

Pull request workflow: No

Pull request workflow

Typed value: No.

Product includes Git and commit dialog; PR creation was not established.

  • Pull requests: The pinned product workspace/Git API has commit and push but no PR creation or management operation.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. Waku crates/waku-protocol/src/workspace.rs

    Finding: The product Git API supports branch inspection, checkout, commit and push, but no pull-request creation/management operation. Bounded source inspection found no native PR workflow. Agents can still invoke external tools on their own.

Review interface: Yes cross-checked

Review interface

Typed value: Yes.

Local transcripts, attachments and diffs are retained on the daemon host.

  • Diffs: Native diff view and daemon Git RPC.
  • Documents: Attachments stored by daemon.
  • Persistence: Task SQLite data and provider session forks live on host.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Product license: Apache-2.0: No. GPL-3.0 cross-checked

Product license: Apache-2.0

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: MIT: No. GPL-3.0 cross-checked

Product license: MIT

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: GPL-3.0: Yes. GPL-3.0 cross-checked

Product license: GPL-3.0

Typed value: Yes. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: GPL-3.0-or-later: No. GPL-3.0 cross-checked

Product license: GPL-3.0-or-later

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: AGPL-3.0: No. GPL-3.0 cross-checked

Product license: AGPL-3.0

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: AGPL-3.0-or-later: No. GPL-3.0 cross-checked

Product license: AGPL-3.0-or-later

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: Elastic License 2.0: No. GPL-3.0 cross-checked

Product license: Elastic License 2.0

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: Custom terms: No. GPL-3.0 cross-checked

Product license: Custom terms

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Product license: Proprietary: No. GPL-3.0 cross-checked

Product license: Proprietary

Typed value: No. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Self-hosting: Yes cross-checked

Self-hosting

Typed value: Yes.

Core app and daemon run on user-controlled machines without a Waku account.

  • Self hosting: Local desktop and standalone daemon can be built and run.
  • Vendor dependencies: No Waku account or remote Waku service required.
  • Account independence: Local app state remains on the machine.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Free access: Yes cross-checked

Free access

Typed value: Yes.

Source and direct downloads permit local evaluation without a Waku account.

  • Ongoing free: Open-source local build/download without a Waku account.
  • Self host cost: Users supply their machine and agent credentials.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Starting price: Free: Yes. Free

Starting price: Free

Typed value: Yes. Free.

Source and direct downloads permit local evaluation without a Waku account.

  • Ongoing free: Open-source local build/download without a Waku account.
  • Self host cost: Users supply their machine and agent credentials.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Starting price: Up to $20/month: No. Free

Starting price: Up to $20/month

Typed value: No. Free.

Source and direct downloads permit local evaluation without a Waku account.

  • Ongoing free: Open-source local build/download without a Waku account.
  • Self host cost: Users supply their machine and agent credentials.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Starting price: $21–40/month: No. Free

Starting price: $21–40/month

Typed value: No. Free.

Source and direct downloads permit local evaluation without a Waku account.

  • Ongoing free: Open-source local build/download without a Waku account.
  • Self host cost: Users supply their machine and agent credentials.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Starting price: $41–100/month: No. Free

Starting price: $41–100/month

Typed value: No. Free.

Source and direct downloads permit local evaluation without a Waku account.

  • Ongoing free: Open-source local build/download without a Waku account.
  • Self host cost: Users supply their machine and agent credentials.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Starting price: Over $100/month: No. Free

Starting price: Over $100/month

Typed value: No. Free.

Source and direct downloads permit local evaluation without a Waku account.

  • Ongoing free: Open-source local build/download without a Waku account.
  • Self host cost: Users supply their machine and agent credentials.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Starting price: Contact for pricing: No. Free

Starting price: Contact for pricing

Typed value: No. Free.

Source and direct downloads permit local evaluation without a Waku account.

  • Ongoing free: Open-source local build/download without a Waku account.
  • Self host cost: Users supply their machine and agent credentials.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

Pricing model: Free, no paid plan: Yes

Pricing model: Free, no paid plan

Typed value: Yes.

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • Workspace fees: Waku says there is no Waku account.
  • Model cost: Waku uses your existing agent CLI logins, plans and rate limits, so those providers bill for model usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

Pricing model: Free plan: No

Pricing model: Free plan

Typed value: No.

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • Workspace fees: Waku says there is no Waku account.
  • Model cost: Waku uses your existing agent CLI logins, plans and rate limits, so those providers bill for model usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

Pricing model: Subscription: No

Pricing model: Subscription

Typed value: No.

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • Workspace fees: Waku says there is no Waku account.
  • Model cost: Waku uses your existing agent CLI logins, plans and rate limits, so those providers bill for model usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

Pricing model: Per seat: No

Pricing model: Per seat

Typed value: No.

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • Workspace fees: Waku says there is no Waku account.
  • Model cost: Waku uses your existing agent CLI logins, plans and rate limits, so those providers bill for model usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

Pricing model: Usage-based: No

Pricing model: Usage-based

Typed value: No.

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • Workspace fees: Waku says there is no Waku account.
  • Model cost: Waku uses your existing agent CLI logins, plans and rate limits, so those providers bill for model usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

Pricing model: Per machine or compute: No

Pricing model: Per machine or compute

Typed value: No.

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • Workspace fees: Waku says there is no Waku account.
  • Model cost: Waku uses your existing agent CLI logins, plans and rate limits, so those providers bill for model usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

Pricing model: One-time purchase: No

Pricing model: One-time purchase

Typed value: No.

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • Workspace fees: Waku says there is no Waku account.
  • Model cost: Waku uses your existing agent CLI logins, plans and rate limits, so those providers bill for model usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

Keeps going with laptop closed: Yes

Keeps going with laptop closed

Typed value: Yes.

Local daemon execution is documented, with an externally managed daemon connection mode.

  • Client disconnect: A service-managed remote daemon continues after a client disconnects; desktop-managed local children still depend on their host.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. Waku crates/waku-core/src/server.rs

    Finding: Service-managed daemons keep running when authenticated clients disconnect. The daemon retains provider sessions independently of the attached client; a remote daemon is distinct from a same-host desktop child.

Open-source license: Yes. GPL-3.0 cross-checked

Open-source license

Typed value: Yes. GPL-3.0.

Waku source declares GPL-3.0-only.

  • Client license: GNU GPL version 3 only.
  • Source visibility: Public repository.
  • Source revision: 10bcd728c9b2f07d664cfece3c8c870d3418ddd2
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

Any desktop app: Yes

Any desktop app

Typed value: Yes.

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Desktop os: macOS signed dmg, a Linux install script into ~/.local, and a Windows per-user installer or portable zip.
  • Task actions: Queue or steer follow-up messages while an agent runs.
  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

All public findings

Findings may summarize a source. They are not presented as verbatim statements.

waku:ACC-01: Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

waku:ACC-01

Native desktop runs on macOS, Linux and Windows; daemon has a browser client.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. Waku apps/web/src/routes/index.tsx

    Finding: The v0.1.20 source release includes a browser workspace route and instructions to launch it with bun --filter @waku/web dev, connect an existing daemon URL/token and configure its allowed browser origin. Build and deployment commands support a user-hosted browser client.

  3. Waku crates/waku-daemon/src/main.rs

    Finding: Waku ships the product-owned waku-daemon CLI with bind, parent-pid, allow-origin and explicit non-loopback exposure controls. It starts the Waku backend; it is separate from the coding-agent CLIs and is not a headless agent-prompt command.

  4. Waku .github/workflows/release.yml

    Finding: The release workflow packages only macOS, Linux and Windows native applications. The repository has a separate browser app, with no native iOS or Android release target.

waku:ACC-02: Waku integrates provider-native session protocols for several coding agents. cross-checked

waku:ACC-02

Waku integrates provider-native session protocols for several coding agents.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:ACC-03: Existing authenticated CLIs are required; subscription billing routes were not separately established. cross-checked

waku:ACC-03

Existing authenticated CLIs are required; subscription billing routes were not separately established.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

  3. Waku README, supported agents

    Finding: Users install and authenticate at least one supported agent CLI before starting Waku, which detects the CLIs and drives them through each provider's native protocol; Waku installs from a signed download or install script.

waku:ACC-04: Agent CLIs must be installed and authenticated; projectless local tasks are supported. cross-checked

waku:ACC-04

Agent CLIs must be installed and authenticated; projectless local tasks are supported.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

waku:ACC-05: The daemon exposes a versioned authenticated WebSocket contract, not an established public CLI. cross-checked

waku:ACC-05

The daemon exposes a versioned authenticated WebSocket contract, not an established public CLI.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

waku:ACC-06: Skills and tools pass through provider integration; a product MCP server contract was not established. cross-checked

waku:ACC-06

Skills and tools pass through provider integration; a product MCP server contract was not established.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:ACC-07: Desktop uses Rust and GPUI; browser client is separate. cross-checked

waku:ACC-07

Desktop uses Rust and GPUI; browser client is separate.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

waku:PLAN-01: Local projects and projectless task folders are supported. cross-checked

waku:PLAN-01

Local projects and projectless task folders are supported.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

waku:PLAN-04: Session and project data persist on the daemon host. cross-checked

waku:PLAN-04

Session and project data persist on the daemon host.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

waku:PLAN-06: Waku tasks are persisted agent sessions. The pinned model and persistence API provide no independent product issue or backlog entity.

waku:PLAN-06

Waku tasks are persisted agent sessions. The pinned model and persistence API provide no independent product issue or backlog entity.

  • The source uses task as the session name; a conversation/session list does not meet the native issue filter.
  1. Waku crates/waku-protocol/src/model.rs

    Finding: Persisted tasks are AgentSession records with provider, conversation, workspace and run status. Projects group sessions. No separate issue/backlog entity or issue state machine exists in the pinned model or daemon persistence API.

waku:COORD-01: Per-session runtimes continue in the background when changing views. cross-checked

waku:COORD-01

Per-session runtimes continue in the background when changing views.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:COORD-03: Waku exposes independent provider sessions and their native subagent activity. The pinned daemon/protocol supplies no product coordinator role or agent-to-agent delegation interface.

waku:COORD-03

Waku exposes independent provider sessions and their native subagent activity. The pinned daemon/protocol supplies no product coordinator role or agent-to-agent delegation interface.

  • Bounded inspection of the full Command enum, daemon dispatcher and core/protocol sources; provider-native subagents are not Waku orchestration.
  1. Waku crates/waku-protocol/src/protocol.rs

    Finding: The closed command set provides client-driven session starts, prompts, steering, cancellation and session persistence. Source inspection found no Waku coordinator/delegation role, schedule service, external-event run starter or separate issue operations. Provider-native subagents are separate.

waku:COORD-04: The pinned Waku daemon starts turns on explicit client commands. It contains no product scheduler or external-event task starter.

waku:COORD-04

The pinned Waku daemon starts turns on explicit client commands. It contains no product scheduler or external-event task starter.

  • Bounded search of core/protocol/src and full dispatcher for cron, scheduler, schedule, webhook and trigger; user scripts are outside this scope.
  1. Waku crates/waku-protocol/src/protocol.rs

    Finding: The closed command set provides client-driven session starts, prompts, steering, cancellation and session persistence. Source inspection found no Waku coordinator/delegation role, schedule service, external-event run starter or separate issue operations. Provider-native subagents are separate.

waku:COORD-05: Steering and queued follow-ups depend on the provider; explicit cancel paths are documented. cross-checked

waku:COORD-05

Steering and queued follow-ups depend on the provider; explicit cancel paths are documented.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:COORD-07: Model and effort controls are shared, but not every provider applies changes identically. cross-checked

waku:COORD-07

Model and effort controls are shared, but not every provider applies changes identically.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:RUN-01: Local daemon execution is documented, with an externally managed daemon connection mode.

waku:RUN-01

Local daemon execution is documented, with an externally managed daemon connection mode.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. Waku crates/waku-core/src/server.rs

    Finding: Service-managed daemons keep running when authenticated clients disconnect. The daemon retains provider sessions independently of the attached client; a remote daemon is distinct from a same-host desktop child.

waku:RUN-02: Waku can start a task in a new Git worktree created by the daemon under ~/.waku/worktrees; the desktop composer offers the choice. This separates files and is not a security sandbox.

waku:RUN-02

Waku can start a task in a new Git worktree created by the daemon under ~/.waku/worktrees; the desktop composer offers the choice. This separates files and is not a security sandbox.

  • Source inspection only; no installed-product test. Container, VM and process isolation were not established.
  1. Waku daemon worktree module

    Finding: The daemon creates an isolated Git worktree for a task beneath ~/.waku/worktrees on first submission when the user chose a new worktree.

  2. Waku desktop composer workspace menu

    Finding: The native desktop composer offers a 'New worktree' workspace choice, with a base branch, alongside existing worktrees.

  3. Waku crates/waku-protocol/src/model.rs

    Finding: The complete Waku workspace enum has ordinary Local, NewWorktree and Worktree cases. The daemon starts provider drivers as processes on its own host; no Waku-owned container or VM isolation backend is implemented. Provider-native sandboxing is a separate scope.

waku:RUN-03: Provider sessions and checkpoints preserve conversation continuity with provider-specific restrictions. cross-checked

waku:RUN-03

Provider sessions and checkpoints preserve conversation continuity with provider-specific restrictions.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:RUN-06: Driver events distinguish permission, error, process exit and turn state. cross-checked

waku:RUN-06

Driver events distinguish permission, error, process exit and turn state.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:TEAM-01: Multiple trusted clients sharing one daemon token can attach to the same runtime and send prompts or steering. Submitted messages fan out to every client; this does not establish distinct human identities or an invited multi-person workflow.

waku:TEAM-01

Multiple trusted clients sharing one daemon token can attach to the same runtime and send prompts or steering. Submitted messages fan out to every client; this does not establish distinct human identities or an invited multi-person workflow.

  • Shared full-control token only; individual identity, attribution and role isolation are absent. Source inspection, not a simultaneous-user workflow test.
  1. Waku crates/waku-core/src/daemon.rs

    Finding: Multiple trusted clients can attach to the same provider runtime, send prompts or steering, and receive the submitted message through the shared event stream. The token gives all clients full control, without individual user attribution.

waku:TEAM-02: Waku uses a shared full-control daemon capability token and browser-origin checks. The pinned authentication path has no organization roles, project roles or enterprise SSO.

waku:TEAM-02

Waku uses a shared full-control daemon capability token and browser-origin checks. The pinned authentication path has no organization roles, project roles or enterprise SSO.

  • Trusted clients share full daemon control; this is not a named human identity or role system.
  1. Waku crates/waku-daemon/src/main.rs

    Finding: The daemon authenticates trusted clients with one full-control WAKU_DAEMON_TOKEN and exact allowed browser origins. It has no per-user/workspace roles or enterprise identity/SSO flow.

waku:TEAM-03: Access modes map to provider-specific approval/sandbox options with explicit limitations. cross-checked

waku:TEAM-03

Access modes map to provider-specific approval/sandbox options with explicit limitations.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku docs/providers.md

    Finding: Documents provider-native session protocols, background session runtime, steering, cancellation and per-provider permission differences. Model changes may apply live or restart a driver; provider changes restart.

waku:SHIP-01: Local transcripts, attachments and diffs are retained on the daemon host. cross-checked

waku:SHIP-01

Local transcripts, attachments and diffs are retained on the daemon host.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

waku:SHIP-03: Product includes Git and commit dialog; PR creation was not established.

waku:SHIP-03

Product includes Git and commit dialog; PR creation was not established.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku docs/commit-messages.md

    Finding: Commit dialog can generate a message using the selected agent CLI. Generation reads Git diff, not conversation history; Claude/Codex use pinned lower-cost models.

  3. Waku crates/waku-protocol/src/workspace.rs

    Finding: The product Git API supports branch inspection, checkout, commit and push, but no pull-request creation/management operation. Bounded source inspection found no native PR workflow. Agents can still invoke external tools on their own.

waku:SHIP-05: Conversation-aware Git checkpoints support rewinding tasks. cross-checked

waku:SHIP-05

Conversation-aware Git checkpoints support rewinding tasks.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

waku:OWN-01: Waku source declares GPL-3.0-only. cross-checked

waku:OWN-01

Waku source declares GPL-3.0-only.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

  2. waku Cargo.toml

    Finding: Pinned build manifest declares GPL-3.0-only and native Rust GPUI dependencies.

waku:OWN-02: Core app and daemon run on user-controlled machines without a Waku account. cross-checked

waku:OWN-02

Core app and daemon run on user-controlled machines without a Waku account.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.

waku:OWN-04: Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

waku:OWN-04

Waku is GPL-3.0 open source with no price or paid plan published (optional GitHub Sponsors only); it uses your existing agent logins and plans, which their providers bill.

  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Waku homepage FAQ

    Finding: Says Waku drives the agent CLIs already on your machine with your existing logins, plans and rate limits, and has no Waku account. Cloud agents are planned. No price is shown.

waku:OWN-06: Downloadable releases and public issues are available; support commitments remain unknown. cross-checked

waku:OWN-06

Downloadable releases and public issues are available; support commitments remain unknown.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku v0.1.20 release

    Finding: Release published 2 October 2026 with OpenCode session continuity and provider discovery fixes.

waku:OWN-08: Source and direct downloads permit local evaluation without a Waku account. cross-checked

waku:OWN-08

Source and direct downloads permit local evaluation without a Waku account.

  • Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
  1. waku README.md

    Finding: Rust/GPUI desktop for local coding agents on macOS/Linux/Windows; projects, sessions and transcripts are local. Browser client uses daemon RPC; remotely managed daemon disables local picker and PTY.