Wisp VS Code extension

Run wisp pipelines from the VS Code command palette — no terminal required. All wisp CLI commands are available as palette entries with interactive input prompts, real-time streaming output, and a status bar indicator. A persistent Wisp Explorer sidebar lets you browse manifests and PRDs at a glance and trigger commands with a right-click.

Prerequisites

• Node.js 20+ (for npm ci / tooling)
• A built wisp binary on your PATH, or configure wisp.binaryPath in VS Code settings after install

Commands

Command Palette

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

Explorer Context Menu Commands

Right-clicking nodes in the Wisp Explorer triggers these commands:

Features

• Wisp Explorer sidebar — Activity Bar panel showing all .devenv/manifests/*.json and .devenv/prds/**/*.md files in a browsable tree; auto-refreshes when files change
• Structured output channel — pipeline output streams line-by-line into the "Wisp AI" Output Channel with native VSCode timestamps and a log-level filter dropdown (uses LogOutputChannel). Each line is automatically classified as error, warn, debug, or info based on its content so you can filter to warnings or errors instantly. A run header (▶ wisp <args> + started timestamp) and a completion footer (exit status + elapsed time) bracket every pipeline invocation.
• Status bar indicator — shows $(sync~spin) Wisp: Running during active pipelines and $(check) Wisp: Idle otherwise; click to open the Output Channel
• File pickers — manifest commands filter to **/.devenv/manifests/*.json; PRD commands filter to **/.devenv/prds/**/*.md
• Process cancellation — wisp.stopPipeline sends SIGTERM to the running process and resets the status bar
• Injection-safe — all child process arguments are passed as array entries to child_process.spawn; no shell string interpolation

Wisp Explorer

The Wisp Explorer appears in the Activity Bar (look for the Wisp icon). It organises your workspace into two sections:

📁 Manifests
  📄 wisp-extension              ← manifest name from JSON
    ⚡ Epic 1 - Extension Features
      📋 01-core-commands.md     [github.com/org/repo]
      📋 02-sidebar-treeview.md
    ⚡ Epic 2 - Publishing & Docs
      📋 03-marketplace-publish.md

📁 PRDs
  📁 wisp-extension/
    📄 01-core-commands.md       [Ready]
    📄 02-sidebar-treeview.md    [Ready]

Clicking a PRD node opens the file in the editor. Right-clicking any node shows context menu actions (see Explorer Context Menu Commands above).

The tree auto-refreshes (500 ms debounce) whenever a file matching **/.devenv/manifests/*.json or **/.devenv/prds/**/*.md is created, deleted, or renamed. Use the $(refresh) Refresh button in the toolbar to force an immediate rescan. Malformed manifest JSON shows a ⚠ Invalid JSON error node rather than crashing the tree.

Configuration

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: 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: Binary Path (wisp.binaryPath) in User Settings.

Package a .vsix (local install, no Marketplace)

cd vscode-extension
npm run package

Install the generated wisp-0.1.0.vsix via Extensions → … → Install from VSIX….

Scripts