π£ Use it to send deployment notifications, alerts, logs, reports, or media β from scripts, cron jobs, CI/CD pipelines, monitoring tools, or any shell environment.
Whether you're a DevOps engineer automating infrastructure, a developer managing CI/CD pipelines, or just want to notify your Telegram group from a terminal script β Telegram Owl gives you a simple and script-friendly way to do it.
- π¨ Send text messages
- π Attach multiple files
- π Silent messages (no notification sound)
- π‘οΈ Protect messages (disable forwarding/saving)
- πΈ Automatic media type detection (or force as document)
- π§΅ Send to forum thread topics
- π€ Read input from
stdin - π Set environment variables for easy usage
- π§ Cross-platform support (Windows, Mac, Linux)
- π Fast and lightweight (written in Go)
Install with Homebrew
brew tap beeyev/pkg https://github.com/beeyev/pkg
brew install --cask telegram-owlIf macOS blocks the app with "cannot be opened because the developer cannot be verified":
# Option 1: Remove quarantine attribute
xattr -d com.apple.quarantine /opt/homebrew/bin/telegram-owl
# Option 2: Allow in System Settings
# Go to: System Settings > Privacy & Security > Allow "telegram-owl"Install with Scoop
scoop bucket add beeyev https://github.com/beeyev/pkg
scoop install telegram-owlInstall with winget
winget install telegram-owlFor Windows, Mac OS(10.12+) or Linux, you can download a binary release here.
Official multi-architecture images live on Docker Hub, GHCR, and Quay. Pull the tag you need and run the CLI directly:
docker run --rm ghcr.io/beeyev/telegram-owl:latest --helpNeed the binary inside your own image? Copy it from the published image via a multistage Dockerfile:
COPY --from=beeyev/telegram-owl:latest /usr/bin/telegram-owl /usr/local/bin/telegram-owlThis reuses the official build without compiling from source.
To start using Telegram Owl, you need to obtain a Telegram bot token and chat ID. You can learn how to get it here.
telegram-owl \
--token <bot-token> \
--chat <chat-id or @channel> \
[--message "your message"] \
[--attach file1,file2,...] \
[options]| Flag | Description | Environment Variable |
|---|---|---|
--token, -t |
Telegram bot token | TELEGRAM_OWL_TOKEN |
--chat, -c |
Chat ID or @username |
TELEGRAM_OWL_CHAT |
| Flag | Description |
|---|---|
--message, -m |
Text message to send |
--format, -f |
Message format options, possible values: markdown, html |
--stdin |
Read message content from stdin |
--attach, -a |
Attach files (comma-separated or multiple flags) |
--as-document, -d |
Force all files to be sent as documents |
--silent, -s |
Send silently (no notification sound) |
--spoiler |
Hide media with spoiler animation |
--protect |
Prevent forwarding and saving of content |
--no-link-preview |
Disable automatic link previews in messages |
--thread |
Thread ID for forum supergroup topics |
telegram-owl -t $BOT_TOKEN -c @mychannel -m "Server status: OK β
"telegram-owl -t $BOT_TOKEN -c 123456 --format=markdown -m "*Bold text* via Markdown"telegram-owl -t $BOT_TOKEN -c 123456 --format=html -m '<b>Bold text</b> via HTML and <a href="http://www.example.com/">inline URL</a>'Message formatting is supported for both
markdownandhtmlformats. But it does not work when text and files are sent together.
telegram-owl -t $BOT_TOKEN -c 123456 \
-m "Daily report attached" \
-a report.pdf,screenshot.pngtelegram-owl -t $BOT_TOKEN -c 123456 \
-m "Confidential: Project roadmap" \
--silent --protectcat message.txt | telegram-owl -t $BOT_TOKEN -c @devs --stdintelegram-owl -t $BOT_TOKEN -c @forumgroup --thread 67890 -m "New bug report π"Set environment variables to simplify usage:
export TELEGRAM_OWL_TOKEN="123:abc"
export TELEGRAM_OWL_CHAT="112451"
export TELEGRAM_OWL_THREAD="67890"| Limit Type | Value |
|---|---|
| Max attachments | 10 files |
| Max photo size | 10 MB |
| Max file size | 50 MB |
| Max total size per send | 50 MB total |
Feel free to open an issue on GitHub.
The MIT License (MIT). Please see License File for more information.
If you like this project, please consider giving me a β