Telegram notifications when Codex needs your approval for an external action. Approval stays in Codex. Telegram replies do not approve anything.
Run this once:
npx skills add rebel0789/notifier --skill approval-notifier -g -a codexStart a new Codex session after installing.
Create a bot with @BotFather, then tell Codex:
@approval-notifier set up Telegram notifications
Codex opens a local setup page in your browser. It shows how to get a token
from BotFather, gives you Copy and Open Telegram actions, and confirms the
connected bot username. Enter the BotFather token there, not in chat. The page
shows an exact pairing code such as /start abc123. Send that exact code to
your bot in a private Telegram chat. The notifier accepts only that fresh code
from the paired private chat.
This is a one-time setup. Run it again only if you change bots or want to send notifications to a different Telegram chat.
When Codex needs your approval for a deploy, migration, restart, configuration change, or another external action, it sends a Telegram notice first. Reply in Codex with the requested approval phrase.
The notifier also covers a plain-chat approval wait when Codex continues safe work while waiting. It does not send notices for ordinary questions.
Identical notices are limited to one every 30 minutes.
- The bot token and paired chat ID stay in a private local file.
- The repository contains no credentials.
- Telegram is notification-only. It cannot approve, cancel, or trigger work.
- Setup uses a temporary loopback-only page and closes it after pairing.
- Setup has no background service or webhook.
Remove the installed skill with your Skills CLI, then delete the local notifier configuration from your Codex home folder if you no longer want notifications.
npm test