See what's new in the
Kick Changelog
Ctrlk
Go to Kick
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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:

If you use profiles, check the selected profile and its default workspace.

Auth or scope errors

Verify the token and workspace:

Then retry with an explicit workspace:

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:

Diagnostics and errors are written to stderr so stdout can be piped safely:

A command returns too much data

Use list controls:

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.

PreviousMCP Troubleshooting

Last updated

Was this helpful?