Support Center

TaskZilla Help Center

Everything you need to get up and running with TaskZilla — the AI-powered project management agent for teams.

Documentation Report a Bug Request Feature Community

Frequently Asked Questions

Quick answers to common questions about TaskZilla setup, configuration, and usage.

Download OpenClaw from taskzilla.ai/download, install with npm i -g openclaw, then run openclaw init to generate your config at ~/.openclaw/openclaw.json. The interactive wizard will walk you through setting up your first agent and Telegram bot token. Full guide in the Install Guide section on this page.
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.
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.
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.
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.
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.
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.
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.
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.
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.

Submit a Ticket

Can't find an answer? Our AI triage agent reviews every ticket within ~1 minute and auto-files issues to GitHub.

Ticket Submitted!
Ticket #TZ-0000
Our AI triage agent will review your ticket in approximately 1 minute. You'll receive an update via email or Telegram if configured.

Support Pipeline

See exactly how your ticket travels from submission to resolution — fully automated AI triage.

1
Ticket Submitted
You fill out the support form at support.taskzilla.ai. Your ticket is stored and queued for AI triage immediately.
support.taskzilla.ai
2
AI Triage
CrewAI orchestrates a Gemini 2.5 Flash analysis pass — classifying severity, extracting key details, and tagging the category.
CrewAI + Gemini 2.5
3
GitHub Search
The agent searches open and closed GitHub issues for duplicates. If a duplicate is found, your ticket is linked directly to the existing thread.
GitHub API
4
Issue Created
If no duplicate exists, a new GitHub issue is auto-filed with the triage summary, severity label, and reproduction steps extracted from your ticket.
GitHub Issues
5
Team Notified
A summary card is posted to the TaskZilla Telegram support group, tagging on-call engineers for high-severity issues.
Telegram Alert

Release Notes

Latest TaskZilla releases — what's new, improved, and fixed.

Loading releases

Install Guides

Get up and running in minutes — two paths depending on what you need.

⚡
OpenClaw CLI
The core runtime — required for everything
Step 1
1
Prerequisites
WSL2 (Ubuntu 22.04+) or native Linux
Node.js v18+  →  recommended: nvm install 22
pnpm          →  npm install -g pnpm
2
Install OpenClaw
pnpm add -g openclaw
# verify
openclaw --version
3
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).
4
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
1
Create a Telegram bot & get your chat ID
# 1. Message @BotFather → /newbot → copy token
# 2. Add bot to your group, send a message
# 3. Get chat ID:
curl https://api.telegram.org/bot<TOKEN>/getUpdates
2
Store your keys
openclaw secrets set TELEGRAM_BOT_TOKEN   <token>
openclaw secrets set CLICKUP_API_KEY      <key>
openclaw secrets set CLICKUP_TEAM_ID      <id>
3
Run the one-line installer
curl -fsSL https://taskzilla.ai/install | bash
Downloads the addon, applies your config, and restarts the gateway automatically.
4
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.

Send Directly to Your Agent

Trigger the TaskZilla agent programmatically via CLI, webhook, or the ACP bridge for full automation.

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

Community

Connect with other TaskZilla users and the team.

🚧
We're still building this. A full community hub — forums, showcase, shared crons, skill marketplace — is on the roadmap. For now, the best place to connect is our Telegram group and GitHub Discussions.
✈️
Telegram Group
Live chat with other users and the core team. Best place for quick questions and sharing setups.
 💬
GitHub Discussions
Feature requests, longer threads, and community proposals. Searchable and indexed.
🏛️
Forum
Structured Q&A, how-tos, and community guides.
Coming soon
🧩
Skill Marketplace
Publish and install community-built skills and cron recipes.
Coming soon