Use the Dosu CLI

Operate Dosu through dosu. Prefer structured output and let the CLI and App validate product rules.

Start correctly

Run dosu --version. Do not probe installation with unrelated package-manager commands.
If it is unavailable and Node is present, try npx -y @dosu/cli --version and use npx -y @dosu/cli as the command prefix for this session. Otherwise ask before installing anything.
Run dosu --help or the relevant nested --help before using a command not covered by the command reference.
Pass --json whenever that leaf command exposes it. Parse the result; do not scrape the human table.

dosu login supplies the JWT used by tRPC-backed commands.
dosu setup selects an organization, Library context, and MCP deployment, creates an API key, and can configure an agent tool.
dosu ask needs an API key. docs generate, docs auto-tag, and docs publish need both JWT login and the API key. Other platform commands generally need JWT login; commands scoped to an organization or current Library also need the corresponding setup selection.
For coding-agent setup, follow the nonblocking dosu setup --agent --tool <id> workflow in workflows.md. Relay its URL and execute its returned resume_command; never invent ticket commands.