Community

Two doors. Same community.

The Telegram companion is live and personal. The Discord server is relaunching with a cleaner architecture — invite goes to the waitlist first so onboarding scales with the server, not against it.

● Live now

🤖 Telegram /navigate companion

An AI companion that routes you — by role, by use case, by budget — to the right bot, the right page, the right doctrine. Zero clicks on a site map.

  • Role-aware — solopreneur, researcher, legal/compliance, investor, operator
  • Deterministic — same input, same route; no hallucinated URLs
  • Cross-bot — hands off to /launch · /fuse · /paper · /harness as needed
  • Privacy — reads & reasons locally; nothing writes without your Telegram inline tap
◐ Relaunching

💬 Clow Ecosystem Discord

Being rebuilt from the clow-ecosystem.json template in the discord-ai-agent plugin — 7 categories, 25 channels, 7 roles, AutoMod on invite-spam + mention-raid, dry-run before any apply.

  • Information — welcome · rules · announcements · roadmap
  • Claw Bots — picoclaw · openclaw · bot-feedback · playground
  • Research — papers · experiments · benchmarks · model-releases
  • Development — general-dev · code-review · help · showcase
  • Voice — Standup · Research Room · Dev Room
Why the pause? The earlier Discord invite expired alongside a stale guild config. We're re-applying from the versioned template so the server matches the doctrine — same roles, same AutoMod, same kill-switches as the Clow stack. Rather than publish a dead invite, we'd rather ship a server that holds up on day one.

How the Discord server is being built (operator view)

  1. Install the plugin inside Claude Code: /plugin marketplace add dnzengou/discord-ai-agent then /plugin install discord.
  2. Run /discord:setup — Claude walks through creating the bot application, pasting its token, and inviting it to the fresh Clow guild.
  3. Apply the template: /discord apply the clow-ecosystem template. Dry-run preview first; no destructive actions.
  4. Register slash commands & launch automations: see community/DISCORD_LAUNCH.md.
  5. Verify: both bots online, /status in #picoclaw, /help in #openclaw, AutoMod drops a seeded invite-spam test.
  6. Ship invite — it lands in this page's Request invite queue and in the next weekly ops note.

The entire flow is versioned (JSON template in the plugin repo), reversible (apply is create-only; nothing deletes), and auditable (the Discord audit log carries the bot's actions).

🦞 Clow Studio · a Desired Solutions venture · clow.studio · github.com/dnzengou/clow-studio-reloaded