> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.neetoinvoice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Install the neetoinvoice CLI on macOS, Linux, or Windows.

## Install

<CodeGroup>
  ```bash macOS theme={"system"}
  brew install neetozone/tap/neetoinvoice
  ```

  ```bash Linux theme={"system"}
  curl -fsSL https://neetoinvoice.com/cli/install.sh | sh
  ```

  ```powershell Windows theme={"system"}
  irm https://neetoinvoice.com/cli/install.ps1 | iex
  ```
</CodeGroup>

On macOS the install script works too, if you would rather not use Homebrew:

```bash theme={"system"}
curl -fsSL https://neetoinvoice.com/cli/install.sh | sh
```

On Windows, Command Prompt is supported as well:

```cmd theme={"system"}
curl -fsSL https://neetoinvoice.com/cli/install.cmd -o install.cmd && install.cmd
```

## Verify the install

```bash theme={"system"}
neetoinvoice --help
```

To print the version, commit, and build date:

```bash theme={"system"}
neetoinvoice version
```

```json theme={"system"}
{
  "binary": "neetoinvoice",
  "commit": "3f9a1c2",
  "date": "2026-07-21T09:14:22Z",
  "version": "1.0.7"
}
```

## Update

```bash theme={"system"}
neetoinvoice update
```

The command detects how the binary was installed and runs the matching upgrade. You can also
upgrade directly:

<CodeGroup>
  ```bash macOS theme={"system"}
  brew upgrade neetoinvoice
  ```

  ```bash Linux theme={"system"}
  curl -fsSL https://neetoinvoice.com/cli/install.sh | sh
  ```

  ```powershell Windows theme={"system"}
  irm https://neetoinvoice.com/cli/install.ps1 | iex
  ```
</CodeGroup>

<Note>
  Re-run `neetoinvoice completion <shell>` after an upgrade so shell completion picks up any
  newly added commands. See [Shell completion](/cli-reference/utility#shell-completion).
</Note>

## Shell completion

```bash theme={"system"}
neetoinvoice completion zsh
```

This writes the completion script under `~/.config/neetoinvoice/completions` and wires your
shell to load it on next start. `bash`, `fish`, and `powershell` are supported the same way.

## Next steps

<Card title="Authentication" icon="lock" href="/cli/authentication">
  Sign in to your workspace and confirm the CLI can reach it.
</Card>