DocsHiGantic CLIAutomation & CI

Automation & CI

Noninteractive environments should use one complete credential override, structured output, explicit profiles, and capability-specific safety rules. Do not automate the browser device flow.

Set the complete environment override

export HIGANTIC_API_BASE_URL="https://agent.higantic.com"
export HIGANTIC_AGENT_ID="your-agent-id"
export HIGANTIC_API_KEY="your-scoped-key"

Keep keys out of source and logs

Store the scoped key in the CI provider's secret manager. Never put it in a repository, prompt, CLI argument, shell history, committed environment file, or command transcript.

Use machine-readable output deliberately

higantic auth status --json
higantic auth profiles --json
higantic doctor --json
higantic skills install --json

Capability commands return structured results according to their own guide. Human authentication and skill commands use English unless --json is present.

Keep capability rules with the workflow

Each capability defines its own scopes, resource identifiers, confirmation flags, idempotency behavior, and conflict recovery. Build the CI step from that capability's documentation instead of assuming every command has the same write contract.

Exit code	Automation behavior
0	The command completed successfully, including warning-only diagnostics
2	Authentication, configuration, validation, connectivity, or another command error needs attention
3	A concurrency-aware capability detected a conflict; read current state before retrying

Noninteractive skill installation

higantic skills install --yes --json

Pass --yes only when installing every selected missing offered skill is intentional. Optional installation failures never turn a successful login into an authentication failure.