Wingman plugins for Claude Code, Codex & Gemini

Hosted MCP works with Claude Code, Codex, and Gemini today. Versioned plugin bundles add the Wingman skills only when a full-profile release explicitly lists those assets.

Connecting the MCP endpoint gives your CLI the hosted tools. A full-profile plugin release can add the skill packs on top — /axelera-wingman:wingman-launch, /axelera-wingman:wingman-deploy, /axelera-wingman:wingman-debug, and the rest — plus the Axelera context files. Current Linux-only releases do not publish plugin bundles. Use the hosted MCP setup from the launch page unless the Downloads page explicitly lists a matching plugin asset.

How plugin auth works

Install the plugin

1. Check that this release includes a bundle

   Only full-profile releases publish axelera-ai-wingman-<version>-public-repo.tar.gz in the public releases repo. Linux-only releases do not. If a future Downloads page lists the bundle, set that exact full-profile version below and verify the asset is present before extracting it. Otherwise use hosted MCP without a plugin download.

   Download

   VERSION="${FULL_PROFILE_VERSION:?set a release that lists the plugin bundle}"
   tmpdir="$(mktemp -d)"
   gh release download --repo axelera-ai-hub/wingman \
     --pattern "axelera-ai-wingman-${VERSION}-public-repo.tar.gz" \
     --dir "$tmpdir"
   mkdir -p "$tmpdir/axelera-ai-wingman"
   tar -xzf "$tmpdir/axelera-ai-wingman-${VERSION}-public-repo.tar.gz" \
     -C "$tmpdir/axelera-ai-wingman"

2. Install into your CLI

   When a full-profile bundle exists, each CLI has a one-time install from the extracted archive. Claude Code adds the bundle as a marketplace and installs the plugin. Codex adds it as a plugin marketplace. Gemini validates and installs it as an extension; Gemini gets MCP tools and the GEMINI.md context, and treats bundled skill files as reference until Gemini supports skill auto-loading.

   Claude Code

   cd "$tmpdir/axelera-ai-wingman"
   claude plugin marketplace add .
   claude plugin install axelera-wingman@axelera-ai-wingman

   Codex CLI

   codex plugin marketplace add "$tmpdir/axelera-ai-wingman"

   Gemini CLI

   gemini extensions validate "$tmpdir/axelera-ai-wingman"
   gemini extensions install "$tmpdir/axelera-ai-wingman"

3. Authorize and verify

   Start the CLI and run any Wingman tool. The browser opens for the one-click MCP OAuth approval, same as a plain MCP connection. Then check the skills: in Claude Code, type /axelera-wingman: and the 19 skills should autocomplete. In Codex, skills auto-discover from the bundle. A quick end-to-end test: /axelera-wingman:wingman-list-models find detection models.

4. Keep versions matched

   If you installed a bundle from a full-profile release, update it only when another matching plugin asset is published. Wingman uses one repo version across the apps, plugins, and docs, so a plugin that is behind the app can carry stale skill instructions. A Linux-only app release does not imply that a new plugin archive exists.

What each CLI gets

Distributing to customers

Distribute skills only from a generated, version-matched plugin asset that is actually attached to a full-profile release, never from a source checkout. For Linux-only releases, direct customers to hosted MCP instead.