Skip to content
quoxcli

Check your Telegram bot

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-15.

Is my Telegram bot set up?

Ask whether your webhook is live, then read the bot, webhook and owner binding yourself.

What you get: a straight answer on whether Telegram can reach your Quox, and what to set up next if it cannot.

Ask Quox

Section titled “Ask Quox”

Ask in plain words:

quox · talking to Quox

what is the Telegram webhook set to

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 2ms

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 3641 duration ms · 10.4s

⛓ AEE │ envelope opened · stream_success

The Telegram webhook isn't set. The check returned  active: false  and  has_token: false
, so no bot token is configured and there's no webhook URL registered.

To get one running, a Telegram bot token has to be added first, and then the webhook can
be registered. I can look up the exact commands for that if you want to set it up.

67.4s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.0, 14 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 14 Oct 2026 · test report mv8mnb

Quox read the webhook status from your Quox and explained what the two flags mean. On this install no bot token is set yet, so the answer is the first step to take.

Do it yourself

Section titled “Do it yourself”

1. Read the onboarding status

Section titled “1. Read the onboarding status”
status 
quox tg status Bot: default(no bot token configured)Webhook URL     -Webhook active  noOwner chat      not bound
From a real run on our own install, before a bot was added. The last line is left out.

It shows the bot, its webhook, the chats that have messaged it, and which chat is bound as the owner.

2. Read the webhook

Section titled “2. Read the webhook”
webhook 
quox tg webhook-infoTelegram Webhook Info───────────────────────────────Active               noHas token            noBot username         -Webhook URL          -Pending updates      -Last error date      -Last error message   -
From a real run on our own install, before a bot was added. The last line is left out.

Once a bot is live, Pending updates and Last error message tell you whether Telegram is getting through.

3. Connect it

Section titled “3. Connect it”

With your bot’s token in place, register the HTTPS address Telegram should send updates to, then message the bot and bind that chat as the owner:

Terminal window
quox tg setup <your-https-webhook-url>
quox tg bind-owner <tg_chat_id>

The chat ID shows in quox tg status after the chat has messaged the bot.

What just happened

Section titled “What just happened”

Quox read the Telegram settings on your own Quox. Reading changes nothing, so no approval was needed. Setting the webhook and binding the owner are writes, and you run them yourself.

Next

Section titled “Next”