Launch AI CLIs with Wingman

Watch the whole flow first, then fly it yourself. By the end, Claude Code is running in a Wingman terminal with the hosted MCP connection already wired — and you know where Codex and Gemini live too.

Claude Code launched from Wingman: one click in the sidebar, one browser approval, and the wingman tools are live in the session.

Launch a CLI from the app

The desktop app launches every supported CLI for you. It checks the CLI is installed, registers the hosted MCP endpoint, opens a terminal, and starts the tool. You never type the setup command yourself — but each step below shows it anyway, so you know exactly what runs and can do the same from any terminal outside the app.

1. Sign in and check your local tools

   Open the desktop app and sign in from Wingman Home. The Local AI tools panel on the home screen lists Claude Code, Codex, and Gemini with their install status. A missing tool shows a ready-to-copy install command — copy it, run it in a terminal, and re-check. The Connect AI tools button on the account card configures every installed CLI in one click.

2. Start Claude Code

   Click Connect Claude Code in the Wingman activity-bar sidebar (or pick it from the AI Tools menu — step 5). Wingman verifies your sign-in, prepares an authenticated MCP connection, and opens a terminal named Claude Code with the session started. Outside the app, the same wiring is one command:

   Claude Code

   claude mcp add --transport http --scope user wingman https://mcp.wingman.axelera.ai/mcp

3. Approve the browser sign-in on first tool use

   The first time the CLI calls a Wingman tool, your browser opens to authorize the connection. One click — it reuses your existing Wingman session. This is the standard MCP OAuth flow; nothing is stored in plain text and no shared token exists. Then try it: ask Claude to use the wingman RAG search tool to find how to deploy a model to my card.

4. Start Codex CLI or Gemini CLI

   Both live in the sidebar under Local AI CLIs and in the AI Tools menu. Wingman registers the MCP server, verifies the registration, and starts the CLI in its own terminal (Codex CLI or Gemini CLI). Codex on some versions supports codex mcp login wingman to authorize up front; otherwise the first tool call prompts you, same as Claude. Verify with codex mcp list or gemini mcp list.

   Codex CLI

   codex mcp add wingman --url https://mcp.wingman.axelera.ai/mcp
   codex mcp login wingman  # if your Codex CLI exposes MCP OAuth login
   codex mcp list           # verify

   Gemini CLI

   gemini mcp add --transport http --scope user wingman https://mcp.wingman.axelera.ai/mcp
   gemini mcp list          # verify

5. Know the AI Tools quick pick

   The AI tools row in the Wingman sidebar opens the Wingman AI Tools menu — every launcher in one list: Connect Claude Code, Claude Vibe (starts Claude with permission bypass — only use it when your workspace policy allows it), Gemini CLI, Codex CLI, Manual MCP setup for other clients, and the native VS Code extensions view. When in doubt, start here.

Newly supported CLIs

Where each CLI launches