I'm here to help

Broken? Let me help.

I've tripped over most of these problems myself. Search first — there's a good chance I've already answered it. If not, file a ticket and I'll take a look within a minute.

Documentation Report a Bug Request Feature What I shipped

Stuff I get asked a lot

Setup snags, config gotchas, weird Telegram silence — the top questions, answered in plain words.

How do I set up OpenClaw for the first time?

Install OpenClaw first (npm i -g openclaw or via git), then head to onboard.taskzilla.ai to pick a plan and run the setup wizard. It walks you through connecting Telegram, ClickUp, and generates a one-line install command with your setup code. Full guide in the Install Guide section on this page.

Why isn't my Telegram bot responding?

First, verify your bot token is correct in openclaw.json under your channel config. Then check the gateway is running: openclaw gateway status. If the gateway is stopped, start it with openclaw gateway start. Also confirm your bot hasn't been blocked — try messaging it from a fresh Telegram account. Check logs at /tmp/openclaw/openclaw-YYYY-MM-DD.log for webhook errors.

How do I add a new AI model?

Add the model under models in your openclaw.json. For Ollama models, set provider: "ollama" and point baseUrl to your Ollama instance. For OpenAI-compatible APIs, use provider: "openai" with your API key. Then reference the model ID in your agent's model field. Config hot-reloads automatically — no restart needed.

Can I use TaskZilla with multiple Telegram accounts?

Yes. Create multiple channel configs in openclaw.json, each with a different botToken. Each bot can be connected to a different Telegram account or group. Use allowedUsers or allowedChats per channel to control access. You can route different channels to different agents for full separation.

How do I configure webhook channels?

In your channel config, set type: "webhook" and configure the endpoint and optional secret for HMAC verification. TaskZilla will expose a webhook URL at /webhooks/{channelId} on the gateway port. Point your external service to that URL. Use openclaw channels list to see all active webhook endpoints.

What's the difference between agents and channels?

Agents are the AI brains — they hold the system prompt, model selection, tools, memory config, and skill access. Channels are the communication interfaces (Telegram bot, webhook, CLI session, etc.). A single agent can serve multiple channels, and a single channel can route to different agents based on rules. Think of agents as workers and channels as entry points.

How do I update TaskZilla?

Run openclaw update to pull the latest release. This downloads the new binary, validates it, and hot-swaps the gateway without dropping active sessions. For major version upgrades, review the changelog first — breaking config changes are listed there. Your openclaw.json is never modified by the updater.

Where are my conversation logs stored?

Conversation sessions are stored in /home/claw/.openclaw/ (or your data directory). Logs are at /tmp/openclaw/openclaw-YYYY-MM-DD.log and rotate daily. Session context (for memory-capable agents) lives in your configured vector store. Use openclaw sessions list to browse active sessions and openclaw sessions cleanup to prune stale ones.

How do I back up my configuration?

Back up ~/.openclaw/openclaw.json — this is your entire configuration. Secrets are stored separately in ~/.openclaw/secrets.json (mode 600). The config auto-creates numbered backups as bak.1, bak.2, etc. on each change. For a full backup including memory: also back up your ChromaDB data directory and any SQLite session files.

Why is my agent slow to respond?

Common causes: (1) Context bloat — run openclaw sessions cleanup to clear stale context. (2) Model latency — if using a local Ollama model, ensure GPU acceleration is enabled. (3) Too many concurrent subagents — set maxConcurrent: 3 and subagents.maxConcurrent: 6 in your agent config. (4) Memory search overhead — review your memorySearch embedding config and consider indexing fewer extra paths.

Tell me what broke

Didn't find it above? Drop the details here. I read every ticket in about a minute, classify it, check for duplicates, and file it to GitHub with your context attached.

Ticket Submitted!

Ticket #TZ-0000

I'll take a look within a minute and reply by email (or Telegram, if you've connected it).

Your Name

Email Address

Ticket Type

TaskZilla Version

Subject

Description

Let me handle it end-to-end

I'll sort, label, check for duplicates, and get it in front of the right person. Turn this off and I'll just file the ticket for a human to pick up.

What I shipped lately

Every release in TaskZilla voice — what's new, what got polished, what I finally fixed.

Loading releases

Get me running in minutes

Two install paths, copy-paste commands, no guessing. Pick the one that matches what you need.

⚡

OpenClaw CLI

The core runtime — required for everything

Step 1

Prerequisites

WSL2 (Ubuntu 22.04+) or native Linux
Node.js v18+  →  recommended: nvm install 22
pnpm          →  npm install -g pnpm

Install OpenClaw

pnpm add -g openclaw
# verify
openclaw --version

Init & set your model API key

openclaw init
openclaw secrets set ANTHROPIC_API_KEY sk-ant-…

Config lives at ~/.openclaw/openclaw.json. Secrets are stored separately at ~/.openclaw/secrets.json (mode 600).

Start the gateway & chat

openclaw gateway start
openclaw chat

Gateway runs in the background and manages all agent sessions. You're live.

🦖

TaskZilla Agent

AI project manager — requires OpenClaw CLI first

Step 2

Choose a plan & run the setup wizard

# Visit the onboarding wizard in your browser:
https://onboard.taskzilla.ai

Pick Personal (€3.99/mo) or Team (€19.99/mo), connect your Telegram group and optionally ClickUp, then grab your personalised install command. The wizard handles license provisioning automatically after payment.

Run the generated install command on your OpenClaw server

curl -fsSL https://get.taskzilla.ai/install.sh | bash -s -- \
  --setup-code TZ-XXXXXX

The setup code is generated by the wizard after you complete configuration. It expires after 24 hours. Downloads the addon, applies your config, and restarts the gateway automatically.

Say hello

# In your Telegram group:
/standup
# Or via CLI:
openclaw agent --agent taskzilla \
  --message "What's on today?"

Your agent is live. It reads ClickUp, posts standups, tracks sprints, and responds to natural language.

↩

Already have a license key? Skip the wizard

# Install addon only — uses existing openclaw.json
curl -fsSL https://get.taskzilla.ai/install.sh | bash

Omitting --setup-code skips config — the installer just downloads the addon and restarts the gateway using whatever is already in your openclaw.json.

🦖

Pick a plan. I'll take it from there.

Community is free forever. Pro and Teams add voice, memory graph, and priority help. Checkout is handled by Stripe — you'll be running in about five minutes.

See plans & pricing → What TaskZilla does

Poke me directly

Skip the form. Send me a ticket straight from your CLI, a webhook, or the ACP bridge — handy if you're an agent or a script.

OpenClaw Agent CLI

# Send a message to taskzilla agent
openclaw agent --agent taskzilla \
  --message "Summarize open bugs" \
  --session "support:cli:$(date +%s)" \
  --json

Webhook Trigger

# POST to your webhook channel endpoint
curl -X POST https://yourdomain.com/webhooks/support \
  -H "Content-Type: application/json" \
  -H "X-Webhook-Secret: your-secret" \
  -d '{"text":"Ticket #TZ-1234 needs review"}'

ACP Trigger (Python)

# Use the ACP trigger bridge
python3 ~/.openclaw/skills/acp-trigger/acp_trigger.py \
  --message "Review latest support tickets" \
  --session "agent:taskzilla:main" \
  --timeout 120