Hopsule is the governance infrastructure for AI-assisted development: you remember, enforce, and orchestrate decisions, architecture, and context across the surfaces below. The product delivers advisory warnings and context, not merge gates controlled by Hopsule.Documentation Index
Fetch the complete documentation index at: https://docs.hopsule.com/llms.txt
Use this file to discover all available pages before exploring further.
Product surfaces
| Surface | Role | Primary user |
|---|---|---|
| Web app | Dashboard: orgs, projects, Brain, Hopper, Capsules, review workflows | Engineers, leads, admins |
| IDE add-on | Sidebar, advisory diagnostics when code conflicts with accepted decisions, MCP in the editor | Daily coding in Cursor, VS Code, Windsurf, compatible hosts |
| MCP server | Model Context Protocol tools so assistants read decisions, memories, and project context natively | Cursor, Claude Code, Copilot, any MCP-capable client |
| CLI tool | TUI, auth, sync (hopsule push, hopsule status), scripting | Terminal-first and automation |
| GitHub App | Repository-level context syncing | Teams linking repos to Hopsule |
How data flows
- You curate decisions, memories, tasks, and Capsules in the web app (and via CLI where supported).
- Brain visualizes relationships in a knowledge graph.
- IDE add-on and MCP consumers read that state to surface warnings and inject structured context into agents.
- CLI syncs and inspects from the shell for developers and pipelines.
- GitHub App keeps repository linkage and related sync workflows connected to your projects.
Hopsule informs; it does not replace your review process or block merges by default. Immutability of accepted decisions is about trust in the record, not silent automation of Git outcomes.
Where to go next
Web app
Dashboard, Brain, Hopper, Capsules.
IDE add-on
Editor integration and advisory diagnostics.
MCP server
Protocol-level tools for AI clients.
CLI tool
Terminal UI and sync.