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.
If doctor reports missing authentication, start with browser login:
noxinfluencer login
Use noxinfluencer auth --key-stdin only when browser login is not available and you are manually configuring a key from the Skills dashboard.
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:
logincampaigncollectionemailmessagecrmproductbrand-monitorexportfeedbackagent
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.13 or newer. Prefer schema --all over version checks when diagnosing a stale install. If login is missing, browser onboarding is unavailable from that installed tree. If product is missing, Product Center and email product-card workflows are unavailable. If nested commands such as creator lookalikes, creator search-filter-options, email recipients filter options, email collaborators list, email attachments upload, message project-filters, message creator-filters, message attachments upload, or feedback submit are missing, reinstall the latest CLI before continuing.
Inspect exact command parameters
Use schema before building JSON-first requests:
noxinfluencer schema "creator search"
noxinfluencer schema "creator search-filter"
noxinfluencer schema "creator lookalikes"
noxinfluencer schema "login"
noxinfluencer schema "email create"
noxinfluencer schema "email recipients add"
noxinfluencer schema "email recipients filter update"
noxinfluencer schema "email collaborators add"
noxinfluencer schema "email products replace"
noxinfluencer schema "email attachments upload"
noxinfluencer schema "message list"
noxinfluencer schema "message project-filters"
noxinfluencer schema "message creator-filters"
noxinfluencer schema "message attachments upload"
noxinfluencer schema "product list"
noxinfluencer schema "brand-monitor influencer-list"
noxinfluencer schema "feedback submit"
Many marketing ops commands use --body-file. Prefer a minimal JSON body and validate or preview when the workflow supports it.
Attachment upload commands are different: they use a local --file path and are still mutation commands. Preview first when possible, then use --force only after the target task or thread and attachment file are approved.
For SaaS-aligned hide and deduplication menus, use the options commands before writing request bodies:
noxinfluencer creator search-filter-options
noxinfluencer email recipients filter options
noxinfluencer message creator-filters
noxinfluencer message project-filters
These commands return supported choices, filter IDs, or JSON body patches. Use them instead of inventing raw SaaS field names.
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.
Report issues from the CLI
If the CLI works but a result is confusing or looks wrong, use Support and Feedback:
noxinfluencer feedback submit --message "Email reply count looks wrong" --category bug --file screenshot.png --force
noxinfluencer feedback inbox
Feedback is free and does not consume Skill quota, but it is still a write command. Confirm the message and remove sensitive data before submitting.
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 login, doctor, auth, env, schema, and agent exit-codes have their own response formats. Do not assume every CLI output has the API envelope.
