Fuseraft for VS Code

Run and manage Fuseraft multi-agent orchestration without leaving your editor.

Features

Activity Bar Panel

A dedicated Fuseraft panel in the activity bar gives you three persistent views:

Run Task — a webview form for composing and launching tasks:

• Multi-line textarea for your task description (paste prose, markdown specs, or bullet lists)
• Config dropdown auto-populated from configs found in your workspace
• Checkboxes for common flags with inline descriptions:
  • Human-in-the-loop (--hitl) — pause after every agent turn to review or redirect
  • Show tool calls (--tools) — print tool invocations inline in the output
  • Verbose (--verbose) — enable debug logging and token counts
  • DevUI (--devui) — open real-time session visualization in the browser
• Run Task button (Ctrl+Enter) — builds and runs the command in the integrated terminal
• Run Task File… button — opens a file picker to select a .md or .txt task file

Sessions — lists all past sessions from ~/.fuseraft/sessions/, showing session ID, task preview, age, and status (complete / incomplete). The list auto-refreshes as sessions change on disk.

• Click an incomplete session to resume it
• Click the preview icon or right-click → View Session Transcript to open a formatted transcript panel

Configs — discovers every YAML or JSON file in your workspace that contains an Orchestration: key. Click any config to open it. The list updates automatically when files are added or removed.

Session Transcript Viewer

Click the preview icon next to any session to open a rich transcript panel showing:

• Session metadata: ID, task, config path, start time, completion status
• Every agent turn as a card with a color-coded header per agent
• Tool calls with ✓ / ✗ status indicators and argument summaries (click the label to collapse)
• Per-turn token usage (input / output) and cost
• Session-level totals: turn count, total tokens, total cost

CodeLens on Config Files

When you open a fuseraft config, three inline actions appear above the first line:

▶ Run Task   ✓ Validate   ⎇ Diagram

Right-Click Menus

Config files (orchestration.yaml, *.fuseraft.yaml, etc.) — right-click in the file explorer or inside the editor:

• Run Task with This Config
• Validate Config
• Validate Config and Show Diagram

Task files (.md, .txt) — right-click in the file explorer, inside the editor, or on the editor tab:

• Run Task File with Fuseraft — runs fuseraft run -f <file>, prompting for a config if multiple are found

Command Palette

All commands are available via Ctrl+Shift+P / Cmd+Shift+P under the Fuseraft: prefix:

Initialize Config Wizard

Fuseraft: Initialize Config walks through four steps:

1. Template — choose from all available templates:

   Template	Description
   dev-team	Planner → Developer → Tester → Reviewer with keyword routing and a periodic Verifier
   graph	Same four-agent pipeline as a declarative directed graph with back-edges for revision cycles
   brownfield	Archaeologist recons the codebase first, then Planner → Developer → Reviewer
   brownfield-graph	Brownfield pipeline as a directed graph with separate back-edges to Developer and Planner
   magentic	Manager LLM dynamically coordinates Researcher + Developer (no fixed routing)
   research	Researcher gathers information, Writer produces the final report
   devops	Three-agent pipeline for infrastructure and deployment tasks
   content	Writer drafts, Editor refines and approves
   minimal	Single general-purpose agent — simplest possible setup
   designer	Describe your use case in plain language and get a validated config back

2. Model — pick from common models across all providers, use auto-detection, or type any model ID

3. Provider endpoint — pick a known provider URL, use your saved default, or enter a custom URL

4. Output path — defaults to config/orchestration.yaml, fully editable

The generated config file opens automatically in the editor as soon as fuseraft writes it to disk.

Status Bar

A ⊙ Fuseraft button is always visible in the status bar. Click it to run a task.

YAML / JSON IntelliSense

The extension ships a full JSON Schema for fuseraft config files. You get autocomplete, inline documentation, and validation for all fields — Agents, Models, Plugins, Capabilities, Contracts, Routes, Security, Compaction, and more.

Schema validation is enabled automatically for files matching **/orchestration.json and **/*.fuseraft.json. For YAML files, add this to your VS Code settings (requires the YAML extension):

"yaml.schemas": {
  "<extension-path>/schemas/fuseraft-config.schema.json": [
    "**/orchestration.yaml",
    "**/*.fuseraft.yaml"
  ]
}

Or reference the schema inline at the top of any config file:

# yaml-language-server: $schema=<extension-path>/schemas/fuseraft-config.schema.json
Orchestration:
  Name: MyTeam
  ...

Requirements

• fuseraft CLI must be installed and on your PATH (or configure the path in settings).
• VS Code 1.85 or later.

Extension Settings

Development

# Install dependencies
npm install

# Compile
npm run compile

# Watch mode
npm run watch

Press F5 in VS Code to launch an Extension Development Host with the extension loaded.

To package:

npx vsce package

License

MIT