The CLI is a front door, not a second building with suspiciously similar furniture.
1. Motivation
hb exposes common setup, workspace, configuration, LLM, Toolkit, Prompt, and dashboard workflows without inventing separate runtime authorities.
--help on any command for the exact options installed in your environment.
2. Setup and Paths
hb setup initializes the default Context Registry and ensures the default workspace definition.
It does not create a project-local .heavenbase/ directory.
hb pj resolves HeavenBase path aliases such as %/ for package state and &/ for resources.
3. Workspaces
hb ws activate <id> action.
hb ws presets list and hb ws presets show debug inspect packaged presets.
Use debug for local no-service examples, local-lts for a local service stack, and web-lts for managed deployments.
4. Configuration
hb config and its hb cfg alias edit values through ConfigManager.
--scope to target a layer, --version for retained history reads, and --json for JSON output or value parsing.
5. Dashboard
--app explicitly requests Chromium --app; --install-app creates ~/Applications/HeavenBase.app for Finder and Dock launch.
The dashboard refuses non-loopback binds unless --allow-network is explicit.
That option exposes an unauthenticated configuration API, so use it only on a network you trust.
6. LLM
--preset, --model, --provider, --gateway, cache, and verbose controls.
Chat and sessions accept repeated --mcp values for URLs or Toolkit refs such as quickstart.math-tools:-1.
The canonical Toolkit ref is namespace.toolkit:version.
Negative versions count from newest to oldest, so -1 selects the latest.
7. MCP Toolkits
hb mcp --help to inspect stdio, HTTP, removal, and Capsule-listing commands.
8. Prompts and Translations
hb prompt --help for translation bind, unbind, set, and remove operations.
9. Alternate CLI Compilers
Typer is the packaged CLI frontend. Host applications may compile the same command Registry to Click or argparse:Summary
hbis a shallow adapter over public HeavenBase domains.- Workspace creation, import, and activation remain separate.
- LLM, Toolkit, and Prompt commands reuse their Python authorities.
- Command help is the exact reference for the installed build.

