HiGantic CLI Quickstart
The higantic command provides one shared workflow for authentication, profiles, diagnostics, skills, and capability commands. This guide stays capability-neutral so the same setup continues to work as the CLI grows.
AI handoff
Let your coding agent set this up
Copy this prompt into Codex, Claude Code, or another terminal-capable coding agent.
Set up the HiGantic CLI on this computer for Excalidraw Canvas, Managed Assets, and HTML Artifacts. Follow the official quickstart at https://higantic.com/docs/cli/quickstart. Run npm install --global @higantic/cli && higantic setup so guided setup starts only after installation succeeds, review all three public capability skills (higantic-html-artifacts, higantic-assets, and higantic-excalidraw), then verify local health with higantic doctor --offline. Each setup prompt is independent; pressing Enter accepts its default Yes choice. Do not ask me to paste an API key. When authentication is required, run higantic auth login and let me complete the browser approval myself. Explain every command before running it, do not publish or delete anything, and stop once the CLI, skills, and local diagnostics are ready.
1. Install the CLI and start setup
Install the official CLI globally with npm, then start guided setup only after installation succeeds. This installs the higantic command independently from every agent skill.
npm install --global @higantic/cli && higantic setup
The CLI and skills are separate
higantic and bundles the dependency-free Python application. Node.js and Python 3.9+ are required; installing the CLI does not silently install any agent skill.2. Choose skills
Command runbook
Rerun the guided setup
Resume setup if it was skipped, then review every missing public HiGantic skill independently.
Run
higantic setup
Expected
╭─ HiGantic setup
│ ✓ CLI 1.8.2 ready
│
│ Command higantic
│ Public skills 3
╰────────────────────────
Choose optional agent skills
Enter installs · n skips
01/03 HTML Artifacts
Create and maintain safe, versioned HTML artifacts in HiGantic.
Install globally? [Y/n]If it fails
Run npm list --global @higantic/cli to confirm the package is installed, ensure the npm global binary directory is on PATH, open a new terminal, and retry.
Press Enter to install an offered skill or type n to skip it. Setup offers HTML Artifacts, Managed Assets, and Excalidraw separately. These direct commands remain available when you want only one capability:
npx --yes skills add Aneaire/higantic-skills --skill higantic-html-artifacts --global
npx --yes skills add Aneaire/higantic-skills --skill higantic-assets --global
npx --yes skills add Aneaire/higantic-skills --skill higantic-excalidraw --global
3. Authorize one agent
Command runbook
Sign in through the browser
The terminal displays a ten-minute verification code. The browser lets you choose one active agent and approve only the permissions requested by your installed capabilities.
Run
higantic auth login
Expected
Open: https://dashboard.higantic.com/auth/device User code: ABCD-EFGH Waiting for browser approval (expires in 600 seconds)... Signed in to My Agent (AGENT_ID) using profile 'default'.
If it fails
If a profile already exists, follow the printed status, logout, and login commands. The CLI never silently replaces a stored API key.
4. Check the setup
higantic auth profiles higantic auth status higantic doctor
A healthy doctor report ends with Result: Ready. Warnings explain optional or incomplete setup; errors return a nonzero exit code and include a recovery hint.
5. Learn the command map
higantic --help higantic setup higantic auth --help higantic skills install
| Command family | Purpose |
|---|---|
| setup | Confirm the CLI and review every missing public skill |
| auth | Sign in, inspect status, switch profiles, and revoke a key |
| doctor | Run read-only configuration, dependency, credential, and connectivity checks |
| skills | Review and install optional HiGantic capabilities |
| Capability commands | Create or manage resources using the rules in that capability's guide |
Choose the capability you need from its own documentation section. Each capability page owns its installation, required permissions, commands, confirmations, and recovery rules.