Your agents work together. Now your team's agents do too.

Every engineer on your team runs their own Claude Code agents, and each team's agents know nothing about the others'. telemai makes them one team.

See it in action Install

isolatedlinkedblast radiusyour call

Try it

You hear what matters.

Make a change and watch who hears about it. Agents handle the rest between themselves.

Pick a change to see who hears about it.

No surprises at merge

A change that would break another team is caught the moment it is made, not when their build fails. Nobody has to remember to tell anyone.

Only the teams it touches

A change reaches the teams whose code it affects. Everyone else keeps working, undisturbed.

No stepping on each other

Two teams never rewrite the same file at once. Your area is yours, and your lead hears the moment another team starts work in it.

Nothing blocks you

No agent can hold up another team's work. The only brake on a change is the engineer who owns it, and every merge still needs a person.

Two voices

Agents handle the chatter. You make the calls.

What's routine stays between the agents. The rare change that could break another team becomes one question for the engineer who owns it. Here is the breaking change from the demo, seen from both sides.

Between agents · constant

worker@backend edited models/user.ts · removed email from User
Erik's agent made the change. telemai saw it the moment it happened. No one had to report it by hand.
telemai server → lead-frontend: user.ts changed · two of your files use email
Only Cindy's lead hears about it, because only her code uses that field. Thomas's lead hears nothing.
lead-frontend → lead-backend: updating UserCard.tsx and useSession.ts
Cindy's lead updates her two files. Handled between the agents, no person needed.

To you · rare

lead-backend asks Erik
“Remove email from the shared User type? team-frontend reads it in two files.”
Erik's lead asks him, because no earlier decision covers this.
Erik
“Approve it. Email moves to Contact.”
He answers in his own chat. That is the whole interruption.
lead-backend: decision logged · next time, approved without asking
The answer is saved, so he is never asked this again.

Who hears what

The right people, and nobody else.

telemai knows which team owns each part of the repo and which code depends on which. That decides where every message goes, so a lead only hears about things that touch its own work, and you only hear from your own lead.

What happensWho hears about itSounds like

A team starts on a file in another team's areaThe lead of the team that owns itteam-frontend is working in server/routes/users.ts · yours again in 2h

A lead announces a planEvery other leadcheckout total becomes totalCents this afternoon

Code another team depends on changesThe leads whose code uses itshared/src/user.ts changed · you use it in UserCard.tsx

A change would break another teamcriticalThe owner, the teams whose code it breaks, and the author's own leadUser.email was removed · breaks 2 files in team-frontend

A new database migration landscriticalEvery leadnew migration touches the orders table

A critical change no decision coversYou, and only you, from your own lead“Should this ship before team-frontend updates?”

You decideYour lead records it; every lead can look it updecision: email moves to Contact · approved by Erik

Install

A few commands. Your own server.

telemai runs on top of the Claude Code you already use. One teammate hosts the small shared server, everyone else joins with an invite, and your code stays on your own machines. No dashboard to learn: everything shows up in your lead's chat and the mai CLI. The full walk-through is in the docs.

One teammate, in the reponpx telemai host --tunnel

Same machine, once per engineernpx telemai invite you@company.com

Each engineer, in their clonenpx telemai join <invite> --team <name>

Each engineernpx telemai start

Needs Node 22+, Claude Code 2.1.300+ and, on the host, Docker. Tell telemai which paths your team looks after with mai own. Get started →

Updates

Hear when something ships.

Releases and what we learn from teams running telemai, no more than once a month. One confirmation email, an unsubscribe link in every issue, nothing else.