Features
- Sidebar views: dashboard summary, Decisions (by status), Memories, Tasks, and a Context & MCP area for capsule and MCP-related controls.
- Decision enforcement: on save, the extension checks against project rules; violations show as diagnostics (Problems panel + inline). Framing is remembrance: surfacing what the team already decided, not silent rewriting.
- Create and edit: new decisions, memories, and tasks from the palette where product support allows, reducing context switches to the web app.
- MCP: bundled or coordinated Hopsule MCP wiring so the same host (e.g. Cursor) can keep live context while you edit (see MCP server for protocol details).
- Authentication: Device flow via browser; align with Web app account and org membership.
Supported hosts
The ecosystem diagram on hopsule.com highlights Cursor, VS Code, Windsurf, and Claude Code as adjacent clients. Install the extension from your marketplace flow; exact listing name follows Hopsule branding.Project binding
If the repo has no.hopsule config yet, run hopsule init with the CLI tool to link the working copy to a Hopsule project. The add-on uses that linkage to know which decisions to enforce.
Commands (palette)
Typical entries include Hopsule: Login, Hopsule: Logout, Hopsule: Open Dashboard, and views that focus the sidebar on decisions or memories. Use the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and type Hopsule.
Quickstart
Connect Cursor and load a Capsule.
MCP server
Protocol-level tool surface for agents.
Decisions
What enforcement checks against.
CLI tool
Init and repo linking from the terminal.