harness-integration-wasp-drone — Claude Code and Codex subagent
harness-integration-wasp-drone — a subagent for Claude Code and Codex that wires a single capability—skill, plugin, hook, or MCP server—across all four Wasp Nest platforms at once.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nestWhat harness-integration-wasp-drone does
Shipping a skill or tool to Claude Code, Cursor, ChatGPT Codex, and Claude Cowork means adapting it to each platform's architecture. The challenge: where to place the component, which wiring mechanism to use (hooks, MCP, native extension, or config file), how to detect what each platform actually supports, and what happens when one doesn't.
This subagent owns that layer. It maps each component type to the right location on each platform, picks the wiring mechanism based on what that platform offers, registers MCP servers so they work everywhere—including Cowork's cloud connectivity requirement—and documents graceful degradation when a platform lacks a feature.
It includes a fully worked six-host example (Claude Code, Codex, Cursor, Hermes, pi, OpenClaw) covering the entire path from capability detection through per-platform fallback.
What it helps with
- wire a single skill across all four Wasp Nest platforms at once
- add a new hook or lifecycle event supported on each platform
- register an MCP server so it runs on Claude Code, Codex, Cursor, and Cowork
- check whether a component will work on a specific platform and handle unsupported features
- audit an adapter or tool contract before shipping a skill to the marketplace
Example prompts for the agent
- Check how to wire this hook on each of the four platforms and what to do if Cursor doesn't support it
- Help me register an MCP server in Claude Code and Codex—where should the configs go and what do I need to know about Cowork's cloud requirement
- Test whether this plugin works on all four platforms and place the components correctly
How to install harness-integration-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install wasp-nest-core@wasp-nest2Manually: put the files in place
.claude/agents/harness-integration-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/harness-integration-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/harness-integration-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 harness-integration-wasp-drone
How do I install harness-integration-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install wasp-nest-core@wasp-nest. This opens the config at .claude/agents/harness-integration-wasp-drone.md.
What does harness-integration-wasp-drone do?
It wires a single skill or tool across all Wasp Nest platforms (Claude Code, Cursor, Codex, Cowork) at once. It picks the right component type and location for each platform, selects the wiring mechanism (hooks, MCP, or config), registers servers, and documents how the system handles incompatible platforms.
How does it handle platforms that don't support a feature?
The subagent explicitly documents what happens on each platform: a component may translate to a supported mechanism, degrade in functionality, or be dropped entirely. All paths are recorded in a checklist so the deployment decision is informed.