Repository navigation
Conversation
Author
ideshun
marked this pull request as ready for review
October 15, 2026 16:16
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Behavior
Expose Telegram group activation, allowlists, topic isolation, reply/edited-message policy, streaming, reactions, delivery options and media settings in the channel drawer. Defaults preserve existing group activation; users can explicitly choose stricter modes.
Topic-isolated sessions include channel instance, chat and topic identity, with routing metadata retained for scheduled delivery. Single-choice
ask_user_questionprompts and paginated model menus use native callbacks bound to sender/chat/topic and recheck agent ownership, thread identity and model eligibility. Stopping a Telegram response also signals the active Harness stream.Dependency and scope
Requires the Gateway companion PR below. No dependency version is invented before its release; channel save/probe rejects unsupported options on older Gateway builds instead of silently ignoring them. Gateway should merge/release first, then Octop can pin the released version before this is ready to merge.
Agent switching is explicitly unsupported. Multi-select/free-text questions retain text handling. This does not introduce Telegram security-approval buttons or grant group administrators Octop administrative authority.
Validation
Commit hooks: Ruff, mypy (564 files), 128 targeted backend tests, TypeScript/Vite/PWA production build passed. Targeted frontend tests: 21 passed. Tested against companion Gateway source.
Full Octop suite is not claimed green: the 4,500-test local run was stopped for runtime cost; a broader run also exposed a reproducible history subprocess timeout outside these changes. Live Telegram behavior has not been tested. Draft until dependency release, full CI and live verification.
Companion Gateway PR: TencentCloud/octop-gateway#34