Repository navigation
specs(t27mcp): telegram.t27 reads Telegram through the VIBEE app (refs #10066) - #10326
Merged
Merged
Conversation
…EE app, not the tg CLI The owner's Telegram session already lives in the VIBEE app (gHashTag/999-multibots-telegraf, vibee-render), which serves its tg_* tools over JSON-RPC at POST /mcp. The t27 MCP server now forwards read calls there with the owner's agent key (VIBEE_AGENT_KEY) instead of spawning the tg CLI, whose Keychain session was never created. No second session and no login step. Tools: tg_unanswered, tg_dialogs, tg_history, tg_search, tg_contacts, tg_participants, tg_scheduled, under the app's own names. outcome() now takes the key, the HTTP status and the JSON-RPC error flag: no key, unreachable, denied (401/403), failed (non-200 or an error in a 200), ok. SEND_TEXT says where sending is: the app's bot or mini app, where the owner presses the button on a draft card; a send over /mcp becomes a draft no screen can confirm, so the server keeps no send tool. t27c test-report: 9 of 9 pass, 0 vacuous. 9 mutants, each caught by a failing test. Refs #10066 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
gHashTag
added a commit
to gHashTag/t27-mcp
that referenced
this pull request
Oct 18, 2026
… graded by telegram.t27 (#21) The owner's session already lives in the VIBEE app (vibee-render, gHashTag/999-multibots-telegraf), which serves its tg_* tools at POST /mcp. telegram.mjs now forwards a read call the wasm accepted there with X-Agent-Key from VIBEE_AGENT_KEY, instead of spawning the tg CLI whose Keychain session was never created. Seven tools under the app's names: tg_unanswered, tg_dialogs, tg_history, tg_search, tg_contacts, tg_participants, tg_scheduled. No send tool; tg_unanswered ends with where sending is. wasm/telegram.wasm and wasm/telegram_table.mjs regenerated from specs/t27mcp/telegram.t27 (gHashTag/t27#10326) on the lab: 9 of 9 tests, 0 vacuous, 9 mutants caught. Refs gHashTag/t27#10066 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 18, 2026 09:04
The owner's name for the app that holds the Telegram session is TRI CLAW. Outcome texts, SEND_TEXT and the header now say TRI CLAW. The env variable VIBEE_AGENT_KEY and the vibee-render service address are plumbing names and stay as they are. 9 of 9 tests pass, 0 vacuous; the wasm is byte-identical. Refs #10066 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
to gHashTag/t27-mcp
that referenced
this pull request
Oct 18, 2026
…uild record (#22) Regenerated wasm/telegram_table.mjs from specs/t27mcp/telegram.t27 (gHashTag/t27#10326, which now names the app TRI CLAW). telegram.wasm is byte-identical. VIBEE_AGENT_KEY and the vibee-render address stay: they are plumbing names, not the product's. Refs gHashTag/t27#10066 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
PR DashboardGenerated at: 2026-10-18 09:15:47 UTC
Summary
Seal Status
|
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
1 participant
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.
What
specs/t27mcp/telegram.t27now reads the owner's Telegram account through the owner's TRI CLAW app instead of thetgCLI.TRI CLAW is gHashTag/999-multibots-telegraf,
apps/vibee-editor/render, running as thevibee-renderservice. It already holds the owner's logged-in MTProto session and serves its tg_* tools over JSON-RPC atPOST /mcp. ThetgCLI's Keychain session was never created, and the app's session already exists. So there is no second session and no login step.TG_TOOLStg_unanswered,tg_dialogs,tg_history,tg_search,tg_contacts,tg_participants,tg_scheduled. These are the app's own names, read only.chat_ok,query_ok,limit_foroutcome(has_key, status, rpc_error)SEND_TEXT/mcpbecomes a draft that no screen can confirm, so the server has no send tool.Evidence
t27c test-reportgives 9 of 9 pass and 0 vacuous.tg_unansweredandtg_searchreturn data.Refs #10066
🤖 Generated with Claude Code