> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/ai/troubleshooting/cli-troubleshooting.md). # CLI Troubleshooting Fix common Kick CLI issues with installation, credentials, workspace selection, output parsing, paging, and command failures. Use the symptom that matches what you see. ### The `kick` command is not found Check whether the CLI is installed: ``` kick --help ``` If the command is not found, install the CLI using your firm's instructions. If the CLI is installed but an app or agent cannot find it, use the absolute path to the binary. ### No Kick credentials found For interactive use: ``` kick login ``` Or provide a token: ``` export KICK_PAT=kick_pat_... kick whoami ``` You can also pass a token directly for a single command: ``` kick --token kick_pat_... whoami ``` ### The wrong workspace is active List available workspaces: ``` kick workspaces list ``` Then pass the workspace explicitly: ``` kick --workspace transactions find --limit 10 ``` If you use profiles, check the selected profile and its default workspace. ### Auth or scope errors Verify the token and workspace: ``` kick whoami kick workspaces list ``` Then retry with an explicit workspace: ``` kick --workspace transactions find --limit 10 ``` If a write action fails, confirm that the token has write scope and the user has permission to perform that action in Kick. ### CLI output is hard to parse Use a machine-readable output mode: ``` kick transactions find --output json kick transactions find --output json-compact kick transactions find --output yaml ``` Diagnostics and errors are written to stderr so stdout can be piped safely: ``` kick transactions find --output json | jq '.[0].id' ``` ### A command returns too much data Use list controls: ``` kick transactions find --limit 10 kick transactions find --fields id,date,amount,counterparty ``` When a command returns a next cursor, pass it to fetch the next page. ### A write command returns a preview This is expected for preview-first actions. Review the preview. If it matches your intent, repeat the call with the returned confirmation token or use the documented confirmation option for that command. Do not automate confirmation unless the workflow has been reviewed and approved by your firm. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kick.co/ai/troubleshooting/cli-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.