cubox-cli

Manage Cubox bookmarks via the cubox-cli command-line tool.

Authentication and Secrets

If any command fails with "API Key does not exist", never ask the user to paste their API token into chat and never construct commands that embed a literal token in argv. Use one of these safe paths:

Interactive login: ask the user to run cubox-cli auth login in their own terminal.
Agent / CI without persistence: ask the user to set CUBOX_SERVER and CUBOX_TOKEN in their shell before invoking the CLI.
Non-interactive persisted login: ask the user to pipe the token via stdin: printf '%s' "$TOKEN" | cubox-cli auth login --server cubox.pro --token-stdin.

Forbidden: asking for tokens in chat, suggesting cubox-cli auth login --token <literal-token>, committing credentials, or copying tokens into screenshots or shared notes. If a token may have leaked, tell the user to rotate it from the Cubox extensions page.

Commands

Most query commands and batch mutation commands output compact JSON by default. Add -o pretty for indented JSON, -o text for human-readable output.

Known success-output exceptions: save, update, and auth subcommands currently print plain text even when -o json is selected. Do not assume every successful command stdout is parseable JSON.