Troubleshooting｜快工助手

资料正文

💡 Run doctor first. It distinguishes installation and configuration problems from OAuth, skill-state, transport, and business errors.

tts_open_toolkit version
tts_open_toolkit doctor
tts_open_toolkit auth doctor --json

Symptom	Next check
`command not found`	Confirm global npm installation and that the npm global bin directory is on `PATH`. Reopen the terminal after installation.
Wrong or old skills	Run `skill state --json`. Update the same target used for installation. Review `modified` state before overwriting.
Login does not complete	Run `auth doctor --json`, confirm the browser callback can reach localhost, and retry `auth login`.
Missing auth record	Run `auth list --json` and `auth status --json`. Sign in again rather than copying tokens between profiles.
Protected credential store unavailable	OAuth token storage currently requires macOS Keychain or Windows CurrentUser DPAPI. Skill-only workflows can still run where Node is supported.
DevAPI method rejected	Run `devapi list --json` and use the exact installed method name, declared queries, and supported JSON body.
Sandbox operation rejected	Run `sandbox endpoints --json`. Confirm the operation is published, non-delete, and allowed for the active profile.
Business error	Preserve the sanitized message, HTTP status, and request or log ID. Check App, market, scope, and prerequisite context.

tts_open_toolkit update --check
tts_open_toolkit update --yes --registry https://registry.npmjs.org
tts_open_toolkit doctor

Operating system, Node version, CLI version, and AI agent.
The exact safe command, intended outcome, and actual result.
Sanitized JSON error, request ID, log ID, or screenshot.
Whether the problem occurs before login, after login, or during one fixed method.

Do not attach secrets, OAuth callbacks, authorization codes, cookies, or protected-store contents.

Tell us what worked, what was unclear, or what should be added. TTS Open Toolkit Feedback Form