Skip to main content
The CLI has three kinds of commands: ten data domains that query Hive directly, five management groups, and a set of top-level utilities. Run hive --help for the list on your installed version, or hive <group> --help for one group.

​
Data domains

These are the fastest way to get an answer. Each domain maps onto a set of tools, so you do not have to look up a tool name first.
Run hive <domain> --help to see the flags each subcommand takes. Two things worth knowing:
  • Every subcommand also accepts --args '<json>' if you would rather pass the whole payload at once.
  • If you leave out a required flag in an interactive terminal, the CLI prompts you for it instead of failing. In a script it exits with code 2, so pass every flag explicitly.

​
Setup

--all installs all 16 skill packs into your clients’ skills directories. Pass --skip-skills to configure the clients without them. Both init and uninstall accept --dry-run if you want to see what would change first.

​
Tools

Discovery and execution live under hive tools:
hive tools search matches literal text, not intent. Search for a keyword like funding or nft, not a phrase like “what is this token worth”. A phrase that does not appear verbatim in a tool’s name or description returns no results.
hive tools list returns 50 tools at a time. Use --limit and --offset to page through the full catalog.

​
Authentication

Only hive auth login takes --profile <name>. The other four commands act on the profile that is already active, and reject --profile with error: unknown option. Use hive auth switch <name> to change which one that is. There is no signup command. hive auth login opens the browser, and an account is created on first sign-in if you do not already have one.

​
Keys

Key management lives in the dashboard, at hiveintelligence.xyz/dashboard/keys. Most clients never need a key at all. Claude, Claude Code, Cursor and VS Code authorize through the browser on first connect, and hive auth login stores a credential for the CLI. A key is for the case with no browser to click: a server, a script, or CI.

​
Client configuration

hive config prints setup instructions for a client rather than writing them, which is useful when you want to apply them yourself or check what setup would do. What it prints depends on how that client accepts remote servers:

​
Other

serve is for clients that only speak stdio, or for local development against your own provider keys. Most users should connect to the hosted endpoint instead.

​
Scripting

--json gives output you can pipe:
The envelope has ok, data, and meta, where meta carries the tool name, provider, and runtime status.
--json is honored by every data-domain subcommand and by hive watch, plus hive tools list, search, info, and call, and hive doctor, hive status, and hive upgrade. Commands that only print human-readable text, including everything under auth, ignore it and write to stderr. Piping those to jq gives you an empty stdout, not an error.
Useful global flags: --jq is a small built-in evaluator, not a bundled copy of jq. It supports .field, .a.b, .[N], .[], and select(.field op value). For anything more, pipe --json into real jq. -q suppresses everything that is not data, including the tools table. hive tools list -q prints nothing at all unless you also pass --json.

​
Exit codes

Exit codes are stable, so hive doctor works as a health check in CI: