# Agents for Telegram

> An independent buyer’s guide to AI agents in Telegram: what the chat can decide, where an approval is settled, and what a self-hosted bot actually runs.

Every page has a markdown twin (linked below) and the whole site is in [llms-full.txt](https://agentsfortelegram.com/llms-full.txt).

## Pages

- [Home](https://agentsfortelegram.com/index.md): Kortix connects a Telegram bot to an open source CompanyOS, so questions arrive as buttons and an action that needs permission waits for a named person.
- [Open source agent](https://agentsfortelegram.com/open-source-telegram-ai-agent.md): Compare open source Telegram AI agents by the file behind them: per-agent tool grants, where each one runs, and how a change reaches review.
- [Company tools](https://agentsfortelegram.com/telegram-agent-with-company-tools.md): An open source Telegram agent reaches company tools through server-side connectors, so the bot token never carries a CRM or repository login.
- [Approvals](https://agentsfortelegram.com/approvals-in-telegram.md): An open source Telegram agent asks with buttons. An approval is one exact action, decided by a named person on Kortix's Review page.
- [Telegram vs Slack](https://agentsfortelegram.com/telegram-vs-slack-for-ai-agents.md): Telegram ties a message to an allowed id; Slack ties it to a linked account that is a project member. Compare both for open-source AI agents.
- [Self-hosted agent](https://agentsfortelegram.com/self-hosted-telegram-agent.md): Self-hosting an open source Telegram agent splits three ways: the platform, the session’s computer, and where the records sit.

## Kortix

- [Kortix](https://kortix.com): The open-source CompanyOS.
- [Kortix docs](https://kortix.com/docs): installing, self-hosting and configuring Kortix.
- [Kortix on GitHub](https://github.com/kortix-ai/CompanyOS): the open-source repository.