Harness Dashboard

Visual whiteboard for AI agent architectures — map, trace and manage subagents, skills and relationships across any agentic framework.

Screenshots

Whiteboard	SDD Panel
Architecture Analysis & Advisory	Full-window Dashboard

What it does

Harness Dashboard reads your workspace and renders an interactive graph of your AI agent setup:

• Nodes — Agents, Subagents, Skills (architectural hierarchy) and Features (compact grid, below the agent graph)
• Edges — manages, uses, suggested, discovered relationships with semantic coloring
• Semantic suggestions — TF-IDF cosine similarity recommends missing skill connections
• Detail panel — click any node to read its description and Markdown file inline
• Timeline — SDD progress milestones in a git-style view

Works out of the box with Harness SDD, and ships with universal adapters for Claude Code, Gemini CLI, Cursor, GitHub Copilot, OpenCode and Kiro (see the Supported project structures table below).

Features

What's new in 0.7.0

Unified entity creation wizard, full connection overhaul, and visual polish. No breaking changes.

Agent Builder Wizard — unified entity creation

• All node types in one place — the old "Add Entity" button (steering, hook, skill, subagent) is gone; the Agent Builder Wizard now handles all 6 types: agent, subagent, skill, steering, hook, and feature-spec.
• Guided + Advanced modes — a mode toggle lets you step through fields one by one (guided) or fill everything on a single scrollable page (advanced). State is preserved when switching between modes.
• Header pre-selection — "✨ Generate Spec" and "+ New Node" header buttons open the wizard pre-selecting the relevant type, from any active tab.
• Root-level modal — the wizard is no longer hidden when the Spec Manager or Advisory tab is active.

Whiteboard connection overhaul

• Full relationship coverage — you can now draw any valid architectural link: agent ↔ subagent (manages), agent/subagent ↔ skill (uses), agent/subagent ↔ steering (governs), agent/subagent ↔ hook (triggers).
• Visible connection handles — hovering any connectable node reveals OUT/IN pills without needing to open its detail panel first. Steering and hook nodes also show connection handles.
• Drag-to-connect feedback — a dashed blue line tracks the cursor while dragging a connection; invalid drop targets are blocked by isValidConnection.
• Persistent non-"uses" edges — manages/governs/triggers edges survive extension restarts via workspaceState.

UX polish

• Unified button style — vivid vscode-button color + compact rounded shape with shadow, consistent across header and whiteboard toolbar.
• Floating expand button — the "Expand" button is now fixed bottom-right, always visible regardless of active tab, and hidden when already in full-window mode.
• Full-window detection — __harness_is_full_window injected via nonce-tagged inline script; no extra VS Code API calls needed.

For full details see the CHANGELOG.

Supported project structures

Note on Windsurf: the WindsurfAdapter source file still ships in the extension (the adapter was implemented in FEAT-015 before Windsurf was discontinued), but the table above does not advertise it because new users cannot realistically adopt a discontinued product. The adapter is retained for users with existing Windsurf workspaces. See progress/decisions.md#adr-003-windsurf-discontinuation for the rationale.

Getting started

1. Install — download the latest VSIX from the Releases page and install it via Extensions: Install from VSIX..., or install directly from the VS Code Marketplace (coming soon).
2. Open a workspace that uses Harness SDD or any supported agentic framework
3. Click the Harness Dashboard icon in the Activity Bar
4. The whiteboard renders your agent graph automatically

No config needed. The extension detects your project structure on activation.

Requirements

• VS Code 1.85 or newer
• A workspace with at least one supported agent config file (see table above)

Extension settings

State (dismissed suggestions, disabled connections) is persisted automatically per workspace via VS Code's workspaceState.

Adapter path overrides

Per-adapter detection path overrides under harness-dashboard.adapters.<id>.path. The defaults match each framework's canonical detection directory; override them when your project places its agent files in a non-standard location. Configurable: claude-code, cursor, gemini-cli, copilot, windsurf, kiro. Not configurable: harness-sdd (canonical, .agents/agentic.json) and opencode (canonical, opencode.json/opencode.jsonc) — changing the path would break the framework's own tooling.

{
  "harness-dashboard.adapters.kiro.path": ".kiro"
}

If a configured path is invalid (does not exist or is not a directory), the extension logs a one-line warning to the Harness Dashboard output channel and falls back to the framework's default. See docs/configuration.md for the long-form ConfigurationRegistry reference.

AI provider settings

Configure the OpenAI-compatible fallback provider to help define new specs with the specs panel:

Contributing

Issues and PRs welcome at github.com/marcmassa/harness-manager.

License

MIT © Marc Massa

Note on the repository name

The GitHub repository is intentionally named harness-manager, while the product, the VS Code extension, the npm package, the VSIX file, and the VS Code Marketplace listing are all named harness-dashboard (or harness-dashboard-vscode for the package). The discrepancy is historical: the v0.1.0 release of 2026-06-08 renamed the product from "Harness Manager" to "Harness Dashboard" but the GitHub repository name was not updated at that time.

This mismatch is intentional and documented. The decision to keep the repository name as harness-manager (rather than rename it to harness-dashboard) is recorded in ADR-002. A future maintainer may choose to perform the rename at a project milestone (e.g., v0.4.0 or v1.0.0); until then, the two names refer to the same project.