CLI command reference｜快工助手

资料正文

§1 CLI command reference

The executable is tts_open_toolkit. Use --json where supported when another program or AI agent consumes the result.

§2 Command groups

Group	Purpose
`version`, `doctor`	Print version, executable, platform, Node version, config layers, cache, and default skill directory.
`skill`	Install, update, list, and inspect bundled or custom coding-agent skills.
`auth`	Sign in with Partner Center OAuth, manage profiles, inspect health, and run explicit diagnostics.
`devapi`	List and call the fixed OAuth Toolkit method catalog.
`app`	List developer Apps through the supported Developer Center route.
`sandbox`	List sandbox accounts, inspect the endpoint catalog, and call supported non-delete operations.
`openapi proxy`	Start a local, context-bound proxy for supported OpenAPI requests using the active OAuth profile.
`mcp`	Register and list MCP servers at user or project scope.
`setup`	Install managed Codex or Claude Code hooks, with dry-run and backup behavior.
`history`	Record and query local prompt and skill-usage history.
`update`	Check for or install a CLI package update.

§3 Common commands

tts_open_toolkit --help
tts_open_toolkit version
tts_open_toolkit doctor

tts_open_toolkit skill add --agent codex
tts_open_toolkit skill list --agent codex --json
tts_open_toolkit skill state --agent codex --json

tts_open_toolkit auth login
tts_open_toolkit auth status --json
tts_open_toolkit auth list --json

tts_open_toolkit devapi list --json
tts_open_toolkit app list --json
tts_open_toolkit sandbox endpoints --json

tts_open_toolkit update --check

§4 Advanced OpenAPI proxy

tts_open_toolkit openapi proxy --app-key <app_key> --shop-cipher <shop_cipher> --json

The proxy binds to localhost, injects the selected App and Shop context, uses the active protected OAuth profile, and validates a short-lived local request signature. Use it only with an explicit App/Shop selection and a supported API workflow.

§5 Exit and output behavior

A non-zero exit indicates validation, authentication, transport, or business failure.
Preserve sanitized error text and request or log IDs for troubleshooting.
Never log OAuth callbacks, authorization codes, access tokens, refresh tokens, App Secrets, or protected-store contents.

§6 Was this page helpful?

Was this page helpful?

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