telegram

Telegram

One owner-only Telegram integration provides both the established bot bridge and the optional Mini App. The first positive private Telegram chat binds as the sole owner. Text, photos and files (documents, video, audio and voice notes within this integration's 10 MiB download cap) can be sent to Ouroboros, with or without a caption; replies, photos, videos, documents, typing state, subagent cards, quiz cards, and opt-in notifications are mirrored back to that owner. Telegram's typing indicator stays on while a reply you asked for, mirrored to this chat, is actively being prepared by Ouroboros or a working helper; it stops for Pause, Stop now and after the answer, and a question waiting for you, a model-access wait or background work never keep it on (DESIGN §9). A quiz card is answered by tapping an option or by replying to the card with a free-form answer; both reach the same host decision ingress as the web UI. The bridge speaks the install's interface language (Settings → Appearance → Language, or /language here): its own lines are English source translated by the install's translation memory, so the bot ships no dictionary and follows any language the owner chooses. Slash commands keep their ordinary command-mode rules even in replies; quote a literal command as code or include it inside an explanation to send it as a quiz answer.

Version 1.3 remembers every mirrored part, including media and completion notices, in a bounded durable message map. Replying passes its host row or work reference through normal chat; Ouroboros decides what it means. Unknown or evicted ids add nothing. Answers to an earlier owner message from this Telegram chat use a native reply; answers to its latest owner message stay unquoted. Silent mode edits only within one task episode and reply origin; Continue episodes remain separate messages. Relay success stays silent; a host-reported failure arrives as one line. A relayed row quotes the owner's words verbatim as plain text, under where he wrote them and with the file names, above the note. Quiz buttons and replies keep their decision path; earlier parts of a long question carry ordinary references.

Version 1.3.2 warns when the derived reference map cannot be saved, without blocking an owner message or later outbound parts. Completion notifications reference their work, not an authored answer shown only in Main. Version 1.3.3 gives a finished root task's notice the task card's cost words for its whole tree: $3.42 when final, up to $3.42 while costs may still arrive, Tracked: when some step has no price; an unknown cost adds nothing.

Version 1.2.1 marks questions that wait for an owner answer and clears the waiting line after an answer submitted through Telegram. Version 1.2.3 serves the stored settings on GET settings/save so the Settings form shows saved values before Save, and shortens the four long option labels. Version 1.2.4 introduced a non-clean completion notice even with the task toggle off; version 1.2.14 replaces that policy with a true opt-out (below). Version 1.2.5 shows the whole quiz card: its project, the host's facts about the asking task, and every option's detail, with localized field names; a card too long for one Telegram message arrives as ordered parts followed by the keyboard message, and nothing authored is cut. Version 1.2.6 edits a sent question card on its lifecycle (chat.quiz_state): a web answer settles it, a closed wait drops the waiting line yet keeps buttons, a finished task says a late answer still counts, and (1.2.13) a question closed unanswered states that and its reason without buttons. Answers and closures are final. An open question (no options) is the same whole card without buttons; it asks for a reply in your own words.

Version 1.2.9 routes every Telegram API call through the optional skill-local TELEGRAM_PROXY setting, including polling, sends, downloads, notifications, and the companion's menu button lifecycle. The Settings form masks the proxy and never reads its stored credentials back into the browser.