Skip to main content

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.

When you build solo, you still need a persistent decision and memory layer that survives context switches. Hopsule lets you remember, enforce, and orchestrate context so Cursor, Claude, and other tools know the why behind your code without you repeating it every session.

​
The Solo & Team Advantages

Zero Overhead

No team approvals required. Accept your own decisions instantly to lock them in.

CLI-First

Stay in the terminal. Capture decisions and sync context with the CLI.

AI Context Packs

Load your project history into Claude or Cursor so they stop hallucinating architectural patterns.

Visual Knowledge

Use Project Brain to instantly remember how your DB choices connect to your API.

​
Daily Terminal Workflow

Stay in your flow state by managing your architecture directly from the command line.
1

Check project status

Start your morning by reviewing the active constraints.
hopsule status
2

Document a new decision

Decided to use Supabase for real-time features? Write it down before you forget.
hopsule create
# Statement: Use Supabase for real-time features
# Rationale: Need WebSocket support, Supabase provides...
3

Check for conflicts before committing

Ensure your new code doesn’t violate your past decisions.
hopsule list --status=ACCEPTED
4

Accept and lock

Make the decision immutable and add it to your active Capsule.
hopsule accept decision-abc123

​
Supercharge your AI

Export your solo knowledge into a Capsule. When you switch contexts after a month away from the project, load this Capsule into Claude Desktop (via MCP) or Cursor to instantly bring your AI (and yourself) up to speed.