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.

The CLI is the terminal-native client for Hopsule. It uses the same backend as the dashboard and MCP server, with an interactive TUI (Bubble Tea) for browsing orgs and projects without memorizing flags. Use it next to the IDE add-on, MCP, and GitHub App when you want shell-based workflows.

​
Capabilities

  • Interactive dashboard: hopsule launches the main TUI: org/project selection, keyboard-driven navigation, card vs list views.
  • Authentication: Device code / browser-based login; no passwords stored in the shell config.
  • Entity operations: create, list, filter, and transition decisions; manage memories; tasks (including Kanban-style views where supported); browse Capsules.
  • Hopper in the CLI: project-aware assistant session inside the TUI for teams that live in the terminal.
  • Sync-oriented workflows: commands such as hopsule push publish local or session state so Cursor, Claude, and other tools see updated context (hopsule status for a quick read on decisions and memories).

​
Installation

Published as hopsule on npm. Common paths: 
npm install -g hopsule
On macOS you can also use Homebrew (brew install hopsule/tap/hopsule). Windows users may use Scoop or Chocolatey per the cli-tool repository. Verify: 
hopsule --version

​
Configuration

Supports config file, environment variables, and flags (see the CLI README for full matrix). Repos often add a .hopsule marker so the IDE add-on resolves the default project; the CLI and extension complement each other.

​
When to use the CLI

  • You want fast iteration without opening the browser.
  • You need scriptable or CI steps that authenticate and push context.
  • You prefer keyboard-first operations next to git and your test runner.

Platform overview

CLI vs web, IDE, and MCP.

Solo developer guide

Terminal-first workflows.