Telegram
Role: Telegram bot bridge

Bring CoStaff into the Telegram app your team already uses. Text, photos, and file attachments all round-trip — agent-produced PDFs, CSVs and images get auto-delivered back as Telegram attachments. New users go through an approval queue you control.

  • Text + photo + document support, both directions
  • Auto file delivery when an agent produces output
  • Identity approval workflow with rate limiting
  • /start · /reset · /help commands
Discord
Role: Discord bot bridge

A Discord bot that brings CoStaff into your server. Slash commands and plain messages both work, in both directions — and it runs on the same chatbot runtime as the Telegram channel, so behavior stays consistent across apps.

  • Discord bot — commands + messages, both directions
  • Same chatbot runtime as the Telegram channel
  • Same Manager, same agents, same identity handling
LINE
Role: LINE official-account bridge

Meet your users in the app already on their phone. Built on the LINE Messaging API webhook — hand tasks to your AI staff from the app that's already on everyone's phone.

  • LINE Messaging API webhook integration
  • A mainstream chat app across Asian markets
  • Same Manager, same agents, same identity handling
Slack
Role: Slack workspace bridge

CoStaff inside your Slack workspace. Runs over Socket Mode, so there's no public IP or inbound webhook to expose — a natural fit for self-hosted deployments behind a firewall.

  • Socket Mode — no public IP required
  • Firewall-friendly for self-hosted setups
  • Same Manager, same agents, same identity handling
Chatbot SDK
Role: shared channel runtime

The runtime SDK every channel above is built on. Identity, sessions, file delivery, and async callbacks come for free — wiring up a new chat platform takes roughly 150 lines of adapter code.

  • Shared runtime SDK behind all channels
  • Identity, sessions, file delivery, async callbacks built in
  • New platform adapter in ~150 lines
One Manager, every channel

A user is a user.
It doesn't matter which app they message from.

A message from Telegram and a message from Discord both land at the same Manager Agent and the same specialist team.
Identity is normalized across channels — one approval queue, one conversation history, one set of agents.
Run as many channels in parallel as you want — costaff channel add <name>.