Skip to main content
The web app (app.hopsule.com) is the control plane for Hopsule. Authentication and organization membership (for example via Clerk) gate access; all durable entities you create here are what downstream clients (IDE, MCP, CLI) consume.

​
Responsibilities

  • Organizations and projects: multi-tenant boundaries and shared governance across repositories and teams, with clear project scope for decisions and memories.
  • Decision lifecycle: draft, pending review, ACCEPTED (immutable), and deprecated states. Conflict analysis runs when decisions move toward acceptance.
  • Memories: persistent rationale and context linked to decisions; they explain the why without weakening decision authority.
  • Capsules: portable context packs: curated subsets of decisions and memories you activate for a project or workflow. Same capsule idea powers “load context” experiences in other surfaces.
  • Brain: interactive knowledge graph of decisions, memories, tasks, and relationships. Use it to explore impact before you accept or deprecate rules.
  • Hopper: in-product, project-aware assistant: retrieval over capsule content, constraint-aware answers, and violation awareness on generated output (see Hopper AI).

​
How it relates to other surfaces

The web app is where humans author and approve governance. The IDE add-on and MCP server read that state to warn or ground agents. The CLI mirrors many operations for terminal-centric workflows and automation.
Connect GitHub from project settings when you want repository-linked onboarding and graph construction; import time scales with repository size.

​
Learn more

Quickstart

Account, GitHub, and first capsule path.

Decisions

Lifecycle and authority model.

Capsules

Context packs and portability.

Project Brain

Graph visualization and exploration.