> 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/developer-tools/cli/install-the-kick-cli.md).

# Install the Kick CLI

Install or locate the Kick CLI, verify the command works, and prepare your terminal for repeatable automation.

The Kick CLI is the `kick` command. It lets you run Kick workflows from a terminal, script, or agent.

### Before you start

You need:

* A Kick account with access to the client workspace you want to review.
* Permission from your firm to use CLI automation for client work.
* A terminal on your computer.
* Node.js LTS and npm.

### Check Node.js and npm

The Kick CLI is distributed through npm, so your computer needs Node.js and npm first. Check whether they are already installed:

```
node --version
npm --version
```

If either command is missing, install the current Node.js LTS release from [Node.js downloads](https://nodejs.org/en/download/). Node.js includes npm.

npm's docs recommend using a Node version manager when possible because it avoids common permission issues with global installs.

### Get the CLI

Install the Kick CLI from npm, then verify the `kick` command is available:

```
npm install -g @kickfinance/cli
kick --help
```

You can also run the CLI without a global install. This is useful when you want to try the command first or avoid installing a global package:

```
npx @kickfinance/cli --help
```

### Confirm the command path

If an app or agent cannot find `kick`, use the absolute path to the binary in that tool's configuration.

On macOS or Linux, check the path with:

```
which kick
```

On Windows, check the path with:

```
where kick
```

Use the full path when a client launches commands with a minimal environment.

### Next step

After `kick --help` works, continue to [Authenticate and Select Workspace](/ai/developer-tools/cli/authenticate-and-select-workspace.md).


---

# 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/developer-tools/cli/install-the-kick-cli.md?ask=<question>&goal=<user_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.