Guides
How TeleDevs works
Short version: you host on TeleBotHost, you choose what goes public, TeleDevs shows it in a repo-style layout with optional AI catalog metadata.
- 1
Build in the console
Write TBL commands (JavaScript with TeleBotHost built-ins), env placeholders, and your README. That is still the place you edit and run bots.
- 2
Publish on purpose
Mark a bot as a template or list it in the community store. Unpublished bots never appear on TeleDevs.
- 3
AI catalog fills the gaps
A background pass reads command code and writes a short description, category, and tags. Your owner or store description still shows first when you provide one. An AI mark appears when the AI summary is what visitors see.
- 4
Share a stable link
Every published bot gets a canonical URL with its bot ID. Username slugs still work when they are unique for that owner.
- 5
People browse the source view
Visitors see the file tree, README, .env keys (not secret values), command files, and catalog tags. They can search by name or AI tags, open Telegram, or jump back to your profile.
Browse vs search
Homepages and template browse lists prefer bots that pass catalog quality checks so the main feed stays useful. Search is broader: it can still find published bots by name, username, owner description, or AI description and tags.
What stays private
Env values never appear on TeleDevs. Secrets and account credentials stay in the console. Public pages only show what you publish on purpose.
Open the console
Publish from the same place you already build bots.