tauri-wasp-drone — Claude Code subagent: what it does, how to install
tauri-wasp-drone — a subagent for Tauri 2 desktop and mobile apps: reviews project config, traces a v1 migration, and designs the Rust-to-webview IPC.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install backend-and-desktop-tools@wasp-nestWhat tauri-wasp-drone does
The subagent sits at the Tauri boundary: windows and webviews calling into Rust, capabilities that gate access, plugins and sidecars crossing process lines, signed bundles that later turn into updates. It reads src-tauri/, tauri.conf.json, the Cargo and JavaScript package versions side by side, plus build targets and the mobile setup.
Before any planning it loads the core skill tauri-stinger and goes through the files inside it. No skill, no work. Its toolset covers reading, searching, editing and running commands; the model is inherited from the parent session and tasks run in an isolated worktree. When the skill falls short, it searches the web and documentation.
Plain Rust work outside the Tauri shell belongs to rust-wasp-drone, frontend framework internals to the matching UI drone, AI provider policy to ai-tools-platform-wasp-drone, formal security sign-off to security-wasp-drone. A local build never becomes a signed release, a store submission or a live update without explicit authority from the user.
What it helps with
- Review
src-tauri/config before a Tauri 2.x update - Move a v1 project to v2: allowlists into capabilities, commands, events
- Design typed IPC commands and channels between Rust and the webview
- Trim capabilities so each window gets only the permissions it needs
- Wire bundle settings, updater artifacts and signing
Example prompts for the agent
- Review the Tauri 2.x update in
src-tauri/and draft a dated impact plan covering core, CLI and plugins. - Migrate this app from Tauri v1 to v2 and list every config and capability change.
- Design the IPC layer for the settings window: typed commands, an event channel for progress, and error handling.
How to install tauri-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install backend-and-desktop-tools@wasp-nest2Manually: put the files in place
.claude/agents/tauri-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/tauri-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/tauri-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about tauri-wasp-drone
How do I install tauri-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install backend-and-desktop-tools@wasp-nest. The agent file lands at .claude/agents/tauri-wasp-drone.md.
What does tauri-wasp-drone do?
It handles Tauri 2 engineering: project configuration, the v1-to-v2 migration, Rust-to-webview IPC, capabilities and scopes, plugins and sidecars, local persistence, bundles and updater signing.
How is it different from rust-wasp-drone?
General Rust and Cargo work that is not specific to the Tauri shell goes to rust-wasp-drone; this subagent covers the Tauri boundary only.