Skip to main content

Quick Start

Get ZeroClaw installed and running your first AI agent in minutes.

Prerequisites

You’ll need an API key from one of the supported providers. We recommend OpenRouter for quick starts (supports 200+ models with a single key).Get one at openrouter.ai/keys — free tier available.

Installation

Choose your preferred installation method:
Fastest method for macOS and Linuxbrew users. Pre-built binaries, no compilation needed.

First-Time Setup

Run the onboarding wizard to configure your agent:
You’ll be prompted for:
1

Provider Selection

Choose your AI provider (default: openrouter)Popular options:
  • openrouter — Multi-provider gateway (200+ models)
  • anthropic — Claude models
  • openai — GPT-4, GPT-5
  • ollama — Local models
2

API Key

Enter your API key (securely encrypted at rest using ChaCha20-Poly1305)
3

Model Selection

Pick a default model (optional — smart defaults provided)Examples:
  • anthropic/claude-sonnet-4.6 (default for OpenRouter)
  • gpt-5.2 (OpenAI)
  • llama3.2 (Ollama)
4

Memory Backend

Choose how to store conversation history:
  • sqlite (default) — Embedded, zero-config
  • markdown — Human-readable, git-friendly
  • postgres — Distributed, multi-instance
  • lucid — High-performance vector search
  • none — Stateless mode
5

OTP Pairing (Recommended)

Enable gateway authentication with time-based OTP?Recommended for security. Prevents unauthorized API access.Skip with --no-totp if testing locally behind a firewall.
Skip the wizard? Use non-interactive mode:

Start Your Agent

Option 1: Interactive Chat

Direct command-line chat session:
For multi-turn conversations, start the agent loop:
Type your messages and press Enter. The agent can:
  • Execute shell commands (with approval)
  • Read and write files in your workspace
  • Search the web
  • Call custom tools
By default, all tool executions require user approval. Configure autonomy levels in config.toml to adjust this behavior.

Option 2: Gateway + Dashboard

Start the HTTP gateway server with web UI:
By default, the gateway listens on http://127.0.0.1:3000/
1

Access Dashboard

Open the URL shown in startup logs (usually http://127.0.0.1:3000/)
2

Pair Device (if OTP enabled)

Enter the 6-digit TOTP code from your authenticator app
3

Send Messages

Use the web UI or POST to /api/chat:
The gateway supports Server-Sent Events (SSE) for streaming responses. Connect via /api/stream for real-time output.

Option 3: Channel Integration

Connect to communication platforms:
Run multiple channels simultaneously with the daemon mode:
This starts all configured channels in the background.

Example Workflows

1. File Operations

2. Web Research

3. Code Analysis

4. System Administration

Shell commands execute with your user permissions. Review approval prompts carefully before accepting destructive operations.

Configuration Files

After onboarding, you’ll find:

Quick Config Edits

See Configuration Guide for full reference.

Next Steps

Installation Details

Platform-specific instructions, Docker setup, hardware builds

Configuration Guide

Deep dive into config.toml, environment variables, advanced settings

Tool Reference

Built-in tools, custom tool creation, WASM plugins

Channel Setup

Configure Telegram, Discord, Slack, Matrix, and more

Troubleshooting

Ensure ~/.cargo/bin is in your PATH:
Source builds need ~2GB RAM. Solutions:
  1. Use pre-built binaries: ./bootstrap.sh --prefer-prebuilt
  2. Enable swap space:
  3. Reduce parallelism: CARGO_BUILD_JOBS=1 ./bootstrap.sh
Check your API key:
Verify the key is valid at your provider’s dashboard.
Another service is using port 3000:
For more troubleshooting, see the Troubleshooting Guide in the repository.