H1VE — VS Code Extension

See your current branch's feature state — right inside VS Code — from H1VE, the governance & memory layer for teams building with AI.

As your team ships with AI (Claude Code, Cursor, Copilot), context and decisions drift. H1VE keeps every feature aligned; this extension surfaces the branch's feature at a glance in the sidebar: stage, blockers, sign-offs, and the spec — no context switch to the dashboard.

Read-only companion to the CLI nf and the MCP server.

→ h1ve.org · app.h1ve.org

Setup

Already using the CLI? If you've run nf login in a terminal, the extension uses that credential automatically — zero paste, nothing to configure. Just open the H1VE panel (the hive icon in the activity bar) on a feature branch.

Otherwise, the panel shows a "Connect to H1VE" welcome with a button. Or, manually:

• API key: run the command "H1VE: Set API Key" — stored in the VS Code SecretStorage, never in settings. Use a PAT (nf_pat_… from app.h1ve.org/api-tokens).
• h1ve.apiUrl (User/Machine settings — scope machine, default https://app.h1ve.org): on purpose it is not overridable by a repo's .vscode/settings.json, so a repository can't redirect where your API key is sent (OP-12).

The "Branch feature" tree refreshes every h1ve.refreshIntervalSeconds (30s default), on config change, and via "H1VE: Refresh".

Commands

The extension resolves the feature from your current git branch (the branch_slug recorded by nf start). It's read-only — to act on features (start, move, spec, done), use the CLI/MCP.

MIT · built with H1VE, by H1VE 🐝