Gajae Code

Documentation

Telegram onboarding

Create a Telegram bot with BotFather, pair one private chat, and let Gajae Code route asks and replies through the managed Telegram integration.

1. Create a new bot with BotFather

Telegram bots are created and configured entirely through BotFather, Telegram's official bot-management bot. Follow these steps in the Telegram app (mobile or desktop):

  1. Open BotFather. Search for @BotFather in Telegram and confirm the account shows the blue verified checkmark, then press Start to load the command menu.
  2. Run /newbot. Send /newbot. BotFather replies asking for a display name.
  3. Choose a display name. This is the friendly name shown in chats (for example Gajae Code Notifier). It can be changed later with /setname.
  4. Choose a username. Send a unique username that ends in bot (for example gajae_code_notify_bot). Per Telegram's rules, usernames are 5–32 characters, case-insensitive, Latin letters/numbers/underscores only, and the username cannot be changed later.
  5. Copy the token. BotFather replies with an HTTP API token shaped like 123456789:AAH...rest. Copy it now and keep it secret — treat the token like a password. Use /token to regenerate it if it leaks.

See also the Telegram Bot API for the full command surface.

BotFather chat after /newbot: editing @GajaeCodeBot info and setting its command list
Step 1a. Run /newbot in BotFather, name the bot (here gajae-code → @GajaeCodeBot), then optionally set its commands.
 Bot profile page showing the API token with Copy and Revoke buttons and the Settings list including Bot Settings
Step 1b. Open the bot's page to Copy (or Revoke) the API token, then tap Bot Settings to configure it.

2. Enable Threaded Mode in BotFather

Threaded Mode is a BotFather toggle that lets your bot open topics inside the private chat, so it can manage several threaded conversations in parallel instead of one flat timeline. Telegram highlights this as ideal for AI chatbots, and it lets Gajae Code keep each session in its own topic thread with its own context updates, output, and ask buttons.

  1. Open your bot in BotFather. Send /mybots to @BotFather, then select the bot you created in step 1.
  2. Open Bot Settings. Tap Bot Settings to reach the per-bot configuration menu.
  3. Toggle Threaded Mode on. Enable Threaded Mode. This turns on topics in private chats so the bot can create and route messages into per-session threads.
Billing note. Per Telegram's Terms of Service for Bot Developers §6.2.6, enabling topics in private chats is subject to an additional fee for Telegram Star purchases. Threaded Mode is optional — for a single flat private chat, leave it off and continue below.
Bot Settings Threads Settings section with Threaded Mode toggle enabled
Under Threads Settings, turn on Threaded Mode. Telegram notes it lets bots "natively support threaded conversations with users and stream live responses as they're generated, subject to an additional fee for Telegram Star purchases."

3. Pair GJC with a private chat

gjc notify setup

The setup command prompts for the BotFather token, validates it with Telegram getMe, waits for a message from a private chat via getUpdates, then writes notifications.telegram.botToken, notifications.telegram.chatId, and notifications.enabled.

Private chats only. Groups, supergroups, and channels are rejected during pairing so session names and action ids never leak to a shared chat by accident.

4. Token handling

Use the interactive gjc notify setup flow above. This documentation does not provide a protected non-interactive token-input mechanism, so do not pass a BotFather token with --token in shell arguments: command arguments can be visible in shell history and process listings. If a token was supplied that way, remove the history entry where possible and immediately regenerate the token in BotFather with /token, then rerun interactive setup.

--redact suppresses idle summaries and streamed content before remote delivery. Ask questions/options stay visible because they must be answerable on the phone.

5. Check and control it

gjc notify status

Status prints enabled state, a masked token, chat id, and redaction state. Inside a running session, /notify status, /notify off, and /notify on control that session without leaking secrets.

6. Runtime model and SDK discovery

After setup, sessions auto-connect unless GJC_NOTIFICATIONS=0 is set. Each running top-level session publishes its loopback SDK discovery record under .gjc/state/sdk/<sessionId>.json. The Telegram daemon scans those SDK records, connects through the authenticated loopback WebSocket boundary, and owns exactly one getUpdates long poller per bot token/chat pair, avoiding Telegram 409 Conflict failures. Treat each record's credential as a secret and never send it to Telegram.

With Threaded Mode enabled, Telegram threaded conversations can show context updates, live/finalized output, image attachments, inline ask buttons, free-text replies, typing indicators, and double-check acknowledgements — and bots can stream live responses as they are generated instead of waiting for a full reply.

Troubleshooting

  • getMe fails: the BotFather token is invalid or revoked.
  • Setup times out: send any message directly to the bot from a private Telegram chat.
  • 409 conflict: stop any other process polling the same bot token; let the managed daemon own polling.
  • No notifications: check gjc notify status, ensure GJC_NOTIFICATIONS is not 0, and verify the session was not disabled with /notify off.
Prev← What's newNextTroubleshooting →