Files
bot/docs/start/lore.md
zeekay 6e661b15d3 rebrand: complete OpenClaw→Hanzo Bot cleanup across 424 files
- Rename lobster extension → flow (dir, types, env vars, docs)
- LOBSTER_* env vars → BOT_FLOW_* / BOT_*
- 🦞 → 🤖 everywhere (src, docs, skills, zh-CN)
- docs.bot.ai → docs.hanzo.bot
- github.com/bot/bot → github.com/hanzoai/bot
- @bot/* → @hanzo/bot-* (npm scope)
- ~/.bot/ → ~/.hanzo/bot/ (config paths)
- discord.gg/hanzo → discord.gg/XthHQQj (real Hanzo Discord)
- clawhub.com → skills.hanzo.bot
- ClawDock → BotDock in shell helpers
- EXFOLIATE lore → Hanzo Bot branding in all locales
- LOBSTER_PALETTE → BOT_PALETTE, LOBSTER_ASCII → BOT_ASCII
2026-02-13 13:22:53 -08:00

636 B

title, summary, read_when
title summary read_when
Origin The origin of Hanzo Bot
Writing docs or UX copy that reference history

The Origin of Hanzo Bot

Hanzo Bot started as a simple idea: what if you could have a full AI team that runs on your own machine?

Built by Hanzo AI (Techstars '17), Bot combines the power of frontier AI models with a multi-channel gateway that connects to every messaging platform you use. WhatsApp, Telegram, Discord, Slack, Signal, iMessage — one bot, every channel.

Today, Hanzo Bot is used by thousands of developers and teams to automate workflows, manage operations, and deploy AI agents that work 24/7.