Product surfaces
| Surface | Role | Primary user |
|---|---|---|
| Web app | Organizations, projects, Brain, Hopper, Capsules, review workflows | Engineers, leads, admins |
| IDE add-on | Inline diagnostics, sidebar entity browser, MCP wiring inside the editor | Daily coding in VS Code, Cursor, Windsurf, compatible hosts |
| MCP server | Model Context Protocol tools for any MCP-capable agent | Cursor, Claude Code, Copilot, custom agents |
| CLI tool | TUI, sync, scripting, hopsule push-style workflows | Terminal-first and CI-friendly automation |
Data and authority flow
- Authoritative state lives in Hopsule’s backend (decisions lifecycle, memories, tasks, Capsules, org/project membership).
- Web app is where you curate that state, visualize the Brain (knowledge graph), and chat with Hopper under project constraints.
- IDE add-on subscribes to the same rules: on save, it can surface advisory warnings when code conflicts with ACCEPTED decisions.
- MCP server exposes tools (navigation, decisions, memories, tasks, context) so LLM clients fetch structured project context instead of guessing.
- CLI syncs and inspects state from the shell (
hopsule push,hopsule status, interactive TUI), ideal for repos and automation.
No client overrides an ACCEPTED decision. Enforcement and AI behavior are constraint-aware, not a second authority.
Where to go next
Web app
Dashboard, orgs, Brain, Hopper, and Capsules.
IDE add-on
Editor integration and real-time advisory diagnostics.
MCP server
Protocol-level access for AI agents and IDEs.
CLI tool
Terminal UI and sync for developers and pipelines.