Stop wrestling with OpenClaw configuration. Provision project-scoped agent teams on Discord with a single CLI command.
npm install -g clickityclank
Your OpenClaw journey starts the same way everyone's does. One general-purpose agent. You build some skills, set up a daily briefing, maybe automate your email triage. It works. You're productive.
Then you want to build something real. A project with a frontend, a backend, infrastructure concerns. Suddenly, one agent trying to context-switch across everything becomes the bottleneck.
What you actually want is a team of specialists you can talk to throughout the day — and the sleepless night — that know your project, remember its history weeks and months back, and don't need retraining when you pick things back up.
And if you're running multiple projects? Each advancing at different speeds, each needing its own skilled agents? The config file gymnastics to set that up in OpenClaw is enough to make you give up before you start.
A single agent juggling frontend, backend, QA, and infra loses track of what matters. Project context leaks across concerns.
Start a conversation today, lose the thread tomorrow. Agents without dedicated sessions can't maintain long-running project awareness.
Different projects at different stages, each needing different agent configurations. Scaling means multiplying complexity.
Manually editing openclaw.json, wiring bindings, managing scopes, creating workspaces. Hours of plumbing before you write a line of code.
clickityclank creates project spaces — a collection of OpenClaw agents scoped to a project, each living in their own Discord channel with their own memory and session.
We use Discord because it has the perfect hierarchy built in: categories become projects, channels become agents. You talk to your frontend dev in #frontend, your QA engineer in #qa, your backend dev in #backend. Each one isolated, persistent, and purpose-built.
Set up your Discord bots once and reuse them across every project. clickityclank wires the bindings, configures the AGENTS.md and SOUL.md from your templates, and gives each agent their own workspace. Spinning up a new project takes seconds. Tearing one down is just as clean.
Set up bots once, define your mappings, deploy.
One bot per role: frontend, backend, QA. Create them once in the Discord Developer Portal and invite to your server.
Tell clickityclank which channels map to which agents. Inline flags or a YAML manifest — your choice.
One command creates the Discord category, channels, OpenClaw bindings, scopes, and agent workspaces. Done.
Everything you need to manage project-scoped agent teams at scale.
Create Discord categories, text channels, and OpenClaw agent bindings in one atomic operation. No manual config editing.
Each agent gets a project-prefixed ID while sharing the underlying bot account. Clean isolation across multiple projects.
Preview every mutation with --plan and --dry-run. See exactly which channels, bindings, and workspaces will be created or destroyed.
Detect when your running config diverges from declared state. Reconcile with a single sync command — idempotently.
Every agent gets its own workspace, AGENTS.md, and SOUL.md. No context bleed between channels, projects, or agents.
Define channel-to-agent mappings in version-controlled YAML files. Share configurations across teams and environments.
Four commands from zero to a fully-wired project. See the full Getting Started guide for detailed setup instructions.
Install clickityclank globally and seed your role templates. This creates the template directory with starter AGENTS.md and SOUL.md files for each role.
Run doctor to check your Discord token, OpenClaw config, and runtime bot accounts are all wired correctly before creating anything.
Preview the full execution plan with --plan --dry-run. See every Discord channel, OpenClaw binding, and workspace that will be created.
Drop the --dry-run flag and your project space is live. Discord channels created, agents wired, workspaces provisioned. Start talking to your team.
# 1. Install and initialize templates
npm install -g clickityclank
clickityclank init --roles frontend,backend,qa
# 2. Validate environment
clickityclank doctor
discord-auth pass
openclaw-config pass
runtime-bots pass
# 3. Plan (no mutations)
clickityclank project create myapp \
--guild-id $DISCORD_GUILD_ID \
--map frontend:frontend \
--map backend:backend \
--map qa:qa \
--project-scoped-agents \
--plan --dry-run
# 4. Deploy for real
clickityclank project create myapp \
--guild-id $DISCORD_GUILD_ID \
--map frontend:frontend \
--map backend:backend \
--map qa:qa \
--project-scoped-agents
Category created: MYAPP
Channel #frontend bound to myapp-frontend
Channel #backend bound to myapp-backend
Channel #qa bound to myapp-qa