Wisp AI for VS Code

Run Wisp AI pipelines directly from VS Code — no terminal switching required. Wisp AI exposes every wisp CLI command from the Command Palette with interactive prompts, real-time streaming output, and a status bar indicator.

Prerequisites

• VS Code 1.85 or later
• A built wisp binary on your PATH, or configure wisp.binaryPath in VS Code settings. See the Installation Guide for how to install the CLI.

Quick Start

1. Install this extension from the Marketplace (or install from VSIX / source).
2. Open a folder that contains a manifests/ or prds/ directory so the extension activates automatically.
3. Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run Wisp AI: Show Version.

You should see the wisp version string. If the binary is not found, set wisp.binaryPath (see Configuration) or follow the Installation Guide.

Commands

Command Palette

All commands are available via the Command Palette (Cmd+Shift+P / Ctrl+Shift+P):

Explorer toolbar and context menus also expose Refresh, Open File, Run Orchestrate, Run Orchestrate (this epic only), and Run Pipeline when you use the Wisp AI Explorer view in the Activity Bar.

Features

• Wisp AI Explorer — Activity Bar tree for workspace manifests/*.json and prds/**/*.md, with refresh and context actions to run orchestrate or pipeline from a node
• Real-time streaming output — pipeline output appears line-by-line in a dedicated Wisp AI Output channel; no buffering
• Status bar indicator — shows $(sync~spin) Wisp AI: Running during active pipelines and $(check) Wisp AI: Idle otherwise; click to open the Output channel
• File pickers — manifest commands filter to **/manifests/*.json; PRD commands filter to **/prds/**/*.md
• Process cancellation — wisp.stopPipeline sends SIGTERM to the running process and resets the status bar
• Injection-safe — child process arguments are passed as arrays to child_process.spawn; no shell string interpolation

Configuration

// settings.json (User or Machine settings)
{
  "wisp.binaryPath": "/usr/local/bin/wisp"
}

Security: wisp.binaryPath is machine-scoped so a repository’s .vscode/settings.json cannot point the extension at an untrusted binary.

Documentation

• Installation Guide — Marketplace, VSIX, or from source
• Feature Guide — commands, configuration, troubleshooting
• Publishing Guide — maintainers: releases and PAT setup

Troubleshooting

Binary not found — Add wisp to your PATH, or set wisp.binaryPath in User Settings. See the Installation Guide.

Commands don't appear in the Command Palette — The extension activates when the workspace contains manifests/*.json or prds/**/*.md files. Open your wisp project folder, or search for Wisp AI in the Command Palette to trigger activation.

For contributors and maintainers

Node.js 20+ is required only for npm ci, tests, and packaging — not for end users installing from the Marketplace.

Build and test (before GitHub / PR)

From the repository root (Rust CLI):

cargo build --release
cargo test
cargo clippy

From vscode-extension/:

npm ci
npm run compile
npm test
npm run lint

CI runs the same checks (see .github/workflows/ci.yml).

Try it in the editor

1. Open the vscode-extension folder in VS Code or Cursor (File → Open Folder).
2. Run Run → Start Debugging (F5) to launch an Extension Development Host with this extension loaded.
3. In that window, run Wisp AI: Show Version from the Command Palette (Cmd+Shift+P / Ctrl+Shift+P).

Ensure the wisp binary is on PATH in the host, or set wisp.binaryPath under Wisp AI in User Settings.

Package a .vsix (local install, no Marketplace)

cd vscode-extension
npm run package

Install the generated wisp-ai-<version>.vsix via Extensions → … → Install from VSIX….

Publish

Publishing is automated via .github/workflows/publish-vscode.yml. Push a vscode-v* tag to trigger it. See the Publishing Guide for one-time setup and release steps.

Scripts