# Install the CLI (/docs/cli/install)



Pollaris CLI requires Python 3.11 or newer. Install it in an isolated environment so its dependencies do not alter your project.

The CLI is available on [PyPI](https://pypi.org/project/pollaris-cli/).

## Install [#install]

With `uv`:

```bash
uv tool install pollaris-cli
```

Or with `pipx`:

```bash
pipx install pollaris-cli
```

Confirm the installed command:

```bash
pollaris --version
export POLLARIS_API_URL="https://api.pollaris.cc"
pollaris capabilities --json
```

## Upgrade [#upgrade]

```bash
uv tool upgrade pollaris-cli
```

For a local MCP bridge, install the optional dependencies:

```bash
uv tool install 'pollaris-cli[mcp]'
```

## API configuration [#api-configuration]

Use `https://api.pollaris.cc` as the production API URL, without `/v1/`.
The CLI appends `/v1/agent` to its requests. Set `POLLARIS_API_URL` in your
agent's environment so later invocations use the same deployment.

For local or staging deployments, set that variable to the relevant API origin.
Pollaris accepts plain HTTP only for loopback development addresses such as
`localhost`. Use HTTPS for remote API deployments.

## Credential storage [#credential-storage]

The CLI stores access credentials in a supported operating-system keychain. It never prints credentials in normal or JSON output.

Headless environments without a keychain must supply an explicit Fernet key through their secret manager:

```bash
export POLLARIS_CLI_SECRET_KEY="YOUR_FERNET_KEY"
```

Do not commit that value or paste it into a prompt. If neither secure option is available, the CLI stops instead of saving credentials as plain text.

## Start authorization manually [#start-authorization-manually]

You normally do not need this step because a create command begins authorization automatically. To connect first:

```bash
pollaris auth login --json
```

Open the returned `authorization.url`. After approval, resume with the exact `next_action.command` returned by Pollaris.