OperateDeveloper tools
Use the signed CLI and coding agents
Give a local coding agent a narrow deployment surface without giving it Docker or Keychain authority.
Install and enable the CLI
Open Settings → Developer Tools
Choose Install CLI. LiveHQ creates a symlink at ~/.local/bin/livehq and does not edit shell startup files.
Choose Enable CLI
The authorization is bound to the signed-in user, workspace, Mac, current application bundle, and active hosting profile.
Reinstall after an app upgrade when prompted
This moves the symlink to the CLI embedded in the current LiveHQ bundle. Do not disable and re-enable authorization merely to update the executable.
Verify the control surface
Status proves the current account, workspace, device enrollment, Docker runtime, and CLI lock state. Capabilities lists the exact commands and current product limitations.
Doctor is diagnostic; do not run it as a prerequisite when an ordinary deploy already succeeds.
livehq status --output json
livehq capabilities --output json
livehq doctor --output jsonDeploy through one ordinary command
Private is the safe default. A manifest declaring public access additionally requires --confirm-public. Database, release work, explicit secrets, custom health, and non-private access belong in livehq.yaml version 2.
The CLI emits structured JSON or NDJSON for agents. It does not open the Docker socket, read arbitrary Keychain items, or reach another hosting profile.
livehq deploy /absolute/path/to/project --output jsonKeep agent authority narrow
- Sign-out locks the CLI immediately.
- Disable CLI revokes the authorization for this profile.
- Secret values come from explicit env or stdin sources; LiveHQ never reads .env automatically.
- Destructive commands require explicit identifiers and confirmation flags.
- The runtime agent remains the sole Docker, runtime-Keychain, database, and OriginLink broker.