here’s the new shape of it: you connect one Chief of Staff bot to 5dive, once. after that, every new agent you spin up gets its own dedicated Telegram bot with a single tap. no BotFather. no copying a token per agent.

that used to be the most annoying part of running a fleet.

the old way: a token per agent

if you’ve wired an agent to Telegram before, you know the dance. open BotFather. make a bot. name it. copy the token. paste it into config. do it again for the next agent. and the next.

it’s the same five-minute chore every time, and it’s the reason most people’s “fleet” was really just one bot they kept reusing. the token paste was friction, and friction is where fleets stop growing.

most agent tools still work this way. you bring your own bot, every time.

the new way: one chief of staff

connect a single manager bot to 5dive, paste its token once, and flip on Bot Management Mode. that’s the one-time setup, and it’s the last token you’ll paste.

now when you create a new agent and pick Telegram, the wizard hands you a one-tap deep link. you tap it. the Chief of Staff bot makes that agent its own bot, the 5dive CLI on your own VM claims the token and wires it up, and the agent is live on its own channel.

one tap. no token, no BotFather, no copy-paste. the new agent shows up in your chats as itself, not as another voice on a shared line.

the honest version

it’s one tap, not zero. Telegram requires a human to authorize creating a managed bot, so there’s a single tap per agent by design. we’re not going to pretend that away. what’s gone is the token handling, which was the actual chore.

a couple of real limits worth knowing: Bot Management Mode has to be on for the manager bot, and the free tier covers 20 child bots per account (40 if the manager has Telegram Premium). enough to give a sizable fleet its own voices.

why a bot per agent matters

a fleet where every agent has its own Telegram bot is a fleet you can actually talk to. you message your research agent in one thread and your ops agent in another. each one replies as itself. you stop guessing which agent did what.

that’s the point of running a team of agents instead of one. they should feel like separate teammates, not one process wearing five hats. giving each its own line is what makes that real.

try it

connect a Chief of Staff bot in your dashboard, then spin up an agent and pick Telegram. one tap and it’s got its own bot.

5dive is open source if you want to see how it’s wired: github.com/5dive-ai/5dive. or start a fleet at 5dive.com.