Notifications and Telegram

Pitwall sends a Telegram message when a run starts waiting for someone. Telegram is the only channel; with no bot set up, notifications are off and the inbox is where you find what waits.

What sends a message

A run starts waiting on	Message
An agent’s question	Questions
A block: limits reached, a failure	Blocked runs
Manual tests, once per round	Manual tests
Its pull request’s merge	Merges
Being closed, with no open pull request	Ready to close

Each message links to its item in the inbox; one about manual tests links to the checklist. Whoever caused the change is not notified of it, and a person is told once, never reminded.

A step paused on a Claude usage limit, with no other account free, is told to the runner’s owner alone, who is the one able to add another token. It cannot be muted.

Set up the bot

Once per instance, by whoever runs it.

1. Create a bot with @BotFather and copy its token. The bot must be this instance’s alone: only one program can read a bot’s messages.
2. Set PITWALL_TELEGRAM_BOT_TOKEN to the token, and PITWALL_PUBLIC_URL to the address people reach Pitwall at: every message links back to it.
3. Restart the server.

Without the token, Your settings says notifications are off. See Configuration.

Connect your account

Your settings → Connect Telegram, open the link on your phone and press Start. The bot confirms in the chat. Send a test message checks it; Disconnect stops every message.

What you are notified for

In each project, on the project’s page, the members list has Notified for toggles on your own row: questions, blocked runs, merges, ready to close, manual tests. Only you change yours. A viewer is notified for nothing.

Muting a kind stops its messages and nothing else: the item stays in your inbox, everyone else is still told, and the run still waits for someone to act.

Answering from Telegram

A question arrives with a button per suggestion. Tap one to answer, or Write my own answer and reply to the message the bot sends. A loose message is never taken as an answer.

Once answered, from Telegram or the web, the message is edited to say who answered, and loses its buttons.