---
sidebar_position: 1
title: 1. Install
pagination_prev: intro
pagination_next: get-started/your-first-workflow
---

# Install the CLI

You build **Agents** with Zibby — deployed automations. The CLI command is `zibby agent`.

```bash
npm install -g @zibby/cli
```

Verify:

```bash
zibby --version
```

You should see something like `zibby v0.4.x`.

## No global install? Use npx

Every example below works with `npx @zibby/cli` instead of `zibby`:

```bash
npx @zibby/cli agent new my-agent
```

The first call downloads the package; subsequent calls use the cached copy.

## Log in

Cloud features (deploy, trigger, logs) need authentication:

```bash
zibby login
```

This opens your browser and writes a session token to `~/.zibby/config.json`. Logged in for 30 days.

For CI/CD, set `ZIBBY_API_KEY` in the environment instead — the CLI prefers that over the saved session.

## Pick an agent runtime

Agents hand off to external coding-agent CLIs at runtime. You'll need at least one of these installed (locally — the cloud runtime has them pre-installed):

| Agent | How to install | Auth |
|---|---|---|
| **Cursor** | Install [Cursor](https://cursor.com), or `npm i -g cursor-agent` | `cursor-agent login` (or `CURSOR_API_KEY`) |
| **Claude Code** | `npm i -g @anthropic-ai/claude-agent-sdk` | `ANTHROPIC_API_KEY` |
| **Codex** | `npm i -g @openai/codex` | `OPENAI_API_KEY` |
| **Gemini** | `npm i -g @google/gemini-cli` | `GOOGLE_API_KEY` |
| **Assistant** | None — uses OpenAI Assistants API | `OPENAI_API_KEY` |

You only need one. The cloud runtime supports all five out of the box.

→ Next: [Your first agent](./your-first-workflow)
