CLI Diagnostics

Use this page when installation, setup, or agent automation does not behave as expected.

Start with health checks

noxinfluencer doctor

Use doctor when you need to check whether the CLI can read configuration, reach the server, authenticate the API key, and query quota.

For Chinese onboarding URLs and hints:

noxinfluencer --lang zh doctor

Verify the command tree

noxinfluencer schema --all

The current CLI baseline expects the installed command tree to expose:

  • campaign
  • collection
  • email
  • message
  • crm
  • product
  • brand-monitor
  • export
  • agent

If those command groups are missing, reinstall the latest CLI:

npm install -g @noxinfluencer/cli@latest

Version output alone is not enough when local or global compiled files are stale.

The current documented baseline is @noxinfluencer/cli 0.4.7 or newer. Prefer schema --all over version checks when diagnosing a stale install. If product is missing, Product Center and email product-card workflows are not available from that installed command tree.

Inspect exact command parameters

Use schema before building JSON-first requests:

noxinfluencer schema "creator search"
noxinfluencer schema "email create"
noxinfluencer schema "email products replace"
noxinfluencer schema "product list"
noxinfluencer schema "brand-monitor influencer-list"

Many marketing ops commands use --body-file. Prefer a minimal JSON body and validate or preview when the workflow supports it.

Stable exit codes for agents

noxinfluencer agent exit-codes

Use this when your agent, harness, or automation needs to distinguish retryable failures from auth, quota, invalid request, async-not-ready, duplicate data, or internal failures.

Useful global options

  • --json / --plain: choose output format
  • --trace-json: emit structured request traces to stderr
  • --dry-run: preview a request without executing mutation behavior
  • --force: execute a mutation after approval
  • --idempotency-key: override the automatic Idempotency-Key for write requests
  • --enable-commands: restrict available commands for controlled agent runs
  • --no-input: fail instead of prompting
  • --lang zh: use Chinese URLs and hints

Proxy checks

The CLI reads standard proxy environment variables directly:

export HTTPS_PROXY=http://127.0.0.1:10808
export HTTP_PROXY=http://127.0.0.1:10808
export NO_PROXY=127.0.0.1,localhost

Use HTTPS_PROXY for online Skill API requests. Add HTTP_PROXY only for local or non-TLS server URLs. socks5:// in ALL_PROXY is not supported by the current CLI transport.

Response format reminder

API-backed commands return the standard envelope with success, data, summary, meta, and sometimes a legacy credits compatibility field. Treat quota response data as the canonical Skill quota snapshot.

Local commands such as doctor, auth, env, schema, and agent exit-codes have their own response formats. Do not assume every CLI output has the API envelope.