Give your bots a free AI brain (plus more).

CALIGO is a free browser-based manager that gives Telegram and Discord bots a streaming AI that remembers conversations, understands images, supports slash commands, and syncs encrypted across devices.

Built on Perchance's free ai-text-plugin. No subscriptions. No credit card. No API keys. Wait for it, unlimited.

Open CALIGO on Perchance
What you get

Everything you need to run an AI-powered Telegram or Discord bot, for free.

Free AI brain

Every bot gets a free streaming AI that remembers conversations and understands photos. No API keys or credit card required.

Telegram

Full support: groups + moderation, inline mode, Mini Apps, per-language profiles, and multi-device poller leases with no 409 conflicts.

Discord

Technical jargon to bypass Discord's 40333 block. Basically means it works with (actual - not self... for now, anyway) bots.

Encrypted sync

Your bots follow you across devices through a sync file encrypted with your own passphrase (AES-256-GCM). No one sees any of your tokens. Not even our servers.

Scripting

Full JavaScript per bot with library helpers for Telegram, Discord, OpenAI, GitHub, and more. Optional key exposure for trusted code only.

Skins & layouts

Three skins (aero, mono, terminal) and four shell layouts, all with a motion toggle and per-session persistence.

How it works

A note on the one honest thing you need to know before you run a bot.

Keep a tab open, keep your bot alive. The Perchance sandbox has no network access and no timers, so a bot only answers while this page is open in a browser tab. Close the last tab → every bot pauses. The server holds leases, the activity feed, and your running-intent, so reopening on any device resumes in seconds - no two devices fight over a poller (no 409s).
Tokens never leave your browser. Your bot tokens live in your browser storage and your encrypted sync file. The shared coordinator server never receives them and never even sees your real bot ids - it works from derived hash ids.
Discord sends need a relay you host. Discord's edge blocks the canonical Authorization: Bot <token> header on write routes through Perchance's proxy (returns 403 code 40333). The app tries alternative spellings, but none satisfies both the edge and Discord's auth parser. A self-hosted relay (Cloudflare Worker, Google Apps Script, or any simple fetch() host) bypasses it. Full deploy guide →
The one caveat everything hinges on: bots only answer while the manager page is open in a browser tab. The server keeps your leases and running-intent, so reopening resumes instantly. See the relay guide for the Discord sending workaround or open the app to get started in seconds.
Discord sending & the relay

The 40333 edge block and what to do about it.

Discord's edge WAF refuses requests carrying Authorization: Bot <token> headers that also target /channels/* or /guilds/* write routes when they arrive via Perchance's CORS proxy - it answers 403 {"message":"internal network error","code":40333} before the API ever sees them. Every alternative spelling (Bearer, bot, etc.) clears the edge but is rejected by Discord's auth parser with 401. The manager's Test send path flow finds which form Discord accepts - but if it's the canonical Bot form, you need a self-hosted relay.

Deploy your relay now
Open the app

CALIGO runs on Perchance. Opening the app below loads it directly in the editor - no install needed.

Open CALIGO on Perchance