Fix Telegram callback API handling by obviyus · Pull Request #91876 · openclaw/openclaw

obviyus · 2026-06-10T07:14:22Z

Summary

Remove Telegram callback duck-typing around concrete grammy API methods.
Preserve callback business connection and topic routing metadata on direct Bot API calls.
Add regressions for callback edit, reply, delete, business metadata, and General-topic routing.

Verification

node scripts/run-vitest.mjs extensions/telegram/src/bot.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts (176 passed)
.agents/skills/autoreview/scripts/autoreview --mode branch --base main (clean)

clawsweeper · 2026-06-10T07:17:05Z

Codex review: needs real behavior proof before merge. Reviewed June 10, 2026, 3:52 AM ET / 07:52 UTC.

Summary
The PR changes Telegram callback handling to use concrete bot.api methods, preserve callback business/topic metadata on edits and replies, and add focused Telegram callback regression tests.

PR surface: Source -7, Tests +129. Total +122 across 4 files.

Reproducibility: no. live high-confidence reproduction was established. Source inspection shows the current callback fallback path drops explicit business/topic params when context helpers are absent, and the PR adds focused unit coverage for that path.

Review metrics: 1 noteworthy metric.

Callback Bot API actions: 5 switched to concrete bot.api calls. The PR changes answer, edit text, edit markup, delete, and reply callback paths, so live transport proof matters before merge.

Merge readiness
Overall: 🧂 unranked krab
Proof: 🧂 unranked krab
Patch quality: 🐚 platinum hermit
Result: blocked until real behavior proof from a real setup is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

[P1] Add redacted real Telegram proof for callback edit, reply, delete, and topic routing after this patch.
Include the exact live environment and observed result in the PR body.

Proof guidance:

[P1] Needs real behavior proof before merge: The PR body only lists unit tests and autoreview; add redacted screenshot, recording, terminal output, or logs from a real Telegram callback flow, then update the PR body for automatic re-review or ask a maintainer to comment @clawsweeper re-review.

Mantis proof suggestion
A native Telegram Desktop proof would materially verify the visible callback edit, reply, delete, and topic-routing behavior that unit tests cannot prove. A maintainer can ask Mantis to capture proof by posting a new PR comment that starts with the OpenClaw Mantis account mention, followed by:

telegram desktop proof: verify callback edit, reply, and delete after button taps, including topic routing where available.

Risk before merge

[P1] No real Telegram callback proof is attached; unit tests do not prove live Bot API behavior for business metadata, topic routing, button edits, replies, and deletes.
[P1] The changed callback transport path can fail or misroute visible Telegram replies/buttons if the explicit business or topic params differ from grammy context behavior.

Maintainer options:

Prove Callback Transport Live (recommended)
Add redacted Telegram Desktop or bot-to-bot proof covering callback edit, reply, delete, and topic routing before merge.
Accept Unit-Only Transport Risk
A maintainer could intentionally land with the focused unit tests while owning the unproven live Telegram Bot API behavior.

Next step before merge

[P1] The protected maintainer label and missing live Telegram proof make this a human validation item rather than an automated repair lane.

Security
Cleared: The diff only changes Telegram runtime callback calls and tests; it does not touch dependencies, CI, secrets, permissions, or package execution paths.

Review details

Best possible solution:

Land the direct bot.api implementation only after maintainer review and redacted real Telegram proof confirm callback edit, reply, delete, and topic-routing behavior in a live transport.

Do we have a high-confidence way to reproduce the issue?

No live high-confidence reproduction was established. Source inspection shows the current callback fallback path drops explicit business/topic params when context helpers are absent, and the PR adds focused unit coverage for that path.

Is this the best way to solve the issue?

Yes, the code shape appears to be the right narrow fix: direct bot.api calls remove callback-context duck typing and explicitly carry the metadata OpenClaw needs. The remaining blocker is live Telegram proof, not a code finding.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against e3fe6715afb6.

Label changes

Label justifications:

P2: This is a normal Telegram callback bug fix with limited blast radius and focused tests, not an urgent core outage.
merge-risk: 🚨 message-delivery: The changed callback transport path can misroute or fail visible Telegram callback replies/buttons if business or topic metadata is wrong.
rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body only lists unit tests and autoreview; add redacted screenshot, recording, terminal output, or logs from a real Telegram callback flow, then update the PR body for automatic re-review or ask a maintainer to comment @clawsweeper re-review.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram callback button edit, reply, and delete behavior that can be demonstrated in a short Telegram Desktop recording.

Evidence reviewed

PR surface:

Source -7, Tests +129. Total +122 across 4 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	2	38	45	-7
Tests	2	130	1	+129
Docs	0	0	0	0
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	4	168	46	+122

What I checked:

Repository policy applied: Root and extension policy were read, and the Telegram maintainer note says callback/topic transport changes need real Telegram proof over synthetic-only validation. (.agents/maintainer-notes/telegram.md:37, e3fe6715afb6)
Current main behavior: Current main still duck-types grammy context helpers for callback answer/edit/reply/delete paths, with direct API fallbacks that do not explicitly add callback business or topic routing parameters. (extensions/telegram/src/bot-handlers.runtime.ts:1961, e3fe6715afb6)
PR implementation: The PR head calls bot.api.answerCallbackQuery, editMessageText, editMessageReplyMarkup, deleteMessage, and sendMessage directly, adding business metadata and reusable thread params for callback replies. (extensions/telegram/src/bot-handlers.runtime.ts:1963, 22c2c41f344e)
Regression coverage: The PR adds callback tests for business edit metadata, direct Bot API deletion, topic reply params, and General-topic omission. (extensions/telegram/src/bot.test.ts:2831, 22c2c41f344e)
Dependency contract checked: grammY 1.43.0 / @grammyjs/types 3.27.3 expose these Bot API methods with business_connection_id, message_thread_id, and direct_messages_topic_id where relevant, so the direct-call fix needs to preserve those params explicitly.
Proof and label state: The live PR body lists unit-test and autoreview commands only, and the PR currently carries maintainer, status: 📣 needs proof, and mantis: telegram-visible-proof labels.

Likely related people:

steipete: Recent GitHub path history shows repeated Telegram handler and interactive-dispatch maintenance, including refactor: trim telegram helper exports touching extensions/telegram/src/interactive-dispatch.ts. (role: recent area contributor; confidence: medium; commits: d5736710a9d8; files: extensions/telegram/src/interactive-dispatch.ts, extensions/telegram/src/bot-handlers.runtime.ts)
yaanfpv: The portable Codex command picker work changed Telegram callback-button routing and extensions/telegram/src/bot-handlers.runtime.ts, which is adjacent to this callback API fix. (role: feature owner; confidence: medium; commits: 400be62f76ca; files: extensions/telegram/src/bot-handlers.runtime.ts, extensions/telegram/src/native-command-callback-data.ts, extensions/telegram/src/button-types.ts)
alexph-dev: Recent DM topic routing work changed bot-handlers.runtime.ts, bot/helpers.ts, and Telegram topic tests, which overlap the callback topic metadata behavior under review. (role: adjacent owner; confidence: medium; commits: aa117ec4dece; files: extensions/telegram/src/bot-handlers.runtime.ts, extensions/telegram/src/bot/helpers.ts, extensions/telegram/src/bot.test.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

obviyus · 2026-06-10T07:59:08Z

Land proof for PR #91876:

Rebased onto origin/main at 0948bd648af890ba0c342e48b0e50271deddb1df.
Pushed head 22c2c41f344e7df0564a21aebbedf941c5e502bf.
Focused tests passed: node scripts/run-vitest.mjs extensions/telegram/src/bot.test.ts extensions/telegram/src/bot.create-telegram-bot.test.ts.
Fresh branch autoreview clean: .agents/skills/autoreview/scripts/autoreview --mode branch --base origin/main.
CI has unrelated red checks outside this Telegram diff:
- checks-node-agentic-agents-core-runner: src/agents/main-session-restart-recovery.test.ts:910, expected skipped: 2, got skipped: 1.
- build-artifacts: scripts/package-acceptance-workflow.test.ts:1398, QA workflow runner-label assertion.
Branch diff only touches extensions/telegram/src/*.
Changelog not updated; normal PRs use release-generated changelog entries.

Merging via rebase per maintainer instruction despite unrelated red CI.

…26.6.6) (#1040) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/openclaw/openclaw](https://openclaw.ai) ([source](https://github.com/openclaw/openclaw)) | patch | `2026.6.5` → `2026.6.6` | --- ### Release Notes <details> <summary>openclaw/openclaw (ghcr.io/openclaw/openclaw)</summary> ### [`v2026.6.6`](https://github.com/openclaw/openclaw/blob/HEAD/CHANGELOG.md#202666) [Compare Source](openclaw/openclaw@v2026.6.5...v2026.6.6) ##### Highlights - Security boundaries are substantially tighter across transcripts, sandbox binds, host environment inheritance, MCP stdio, Codex HTTP access, native search policy, elevated sender checks, deleted-agent ACP bypasses, loopback tools, Discord moderation, and Teams group actions; exec approvals now fail closed on timeout. ([#91529](openclaw/openclaw#91529), [#91618](openclaw/openclaw#91618), [#91615](openclaw/openclaw#91615), [#91619](openclaw/openclaw#91619), [#91741](openclaw/openclaw#91741), [#91745](openclaw/openclaw#91745), [#91746](openclaw/openclaw#91746), [#91748](openclaw/openclaw#91748), [#91749](openclaw/openclaw#91749), [#91750](openclaw/openclaw#91750), [#91751](openclaw/openclaw#91751), [#91752](openclaw/openclaw#91752), [#91763](openclaw/openclaw#91763), [#89938](openclaw/openclaw#89938)) Thanks [@joshavant](https://github.com/joshavant), [@pgondhi987](https://github.com/pgondhi987), [@mmaps](https://github.com/mmaps), [@eleqtrizit](https://github.com/eleqtrizit), [@shakkernerd](https://github.com/shakkernerd), and [@drobison00](https://github.com/drobison00). - Telegram delivery is safer and more coherent: account-scoped topics route to the right agent, streamed text survives tool calls, `/compact` works on generic ingress, callback handling uses concrete APIs, draft chunking is shared, durable dispatch dedupe moved into the SDK, and unauthorized DM text stays out of cache and prompt context. ([#91189](openclaw/openclaw#91189), [#88682](openclaw/openclaw#88682), [#89588](openclaw/openclaw#89588), [#90212](openclaw/openclaw#90212), [#91876](openclaw/openclaw#91876), [#91874](openclaw/openclaw#91874), [#91904](openclaw/openclaw#91904), [#91478](openclaw/openclaw#91478), [#91915](openclaw/openclaw#91915)) Thanks [@codysai001](https://github.com/codysai001), [@alexzhu0](https://github.com/alexzhu0), [@joelnishanth](https://github.com/joelnishanth), [@snowzlm](https://github.com/snowzlm), [@obviyus](https://github.com/obviyus), and [@sallyom](https://github.com/sallyom). - iMessage recovery and delivery now cover always-on inbound restart, durable echo markers, block streaming, idle approval discovery, hardened outbound transport, and actionable inbound startup diagnostics. ([#91335](openclaw/openclaw#91335), [#91449](openclaw/openclaw#91449), [#88969](openclaw/openclaw#88969), [#88530](openclaw/openclaw#88530), [#91783](openclaw/openclaw#91783), [#91785](openclaw/openclaw#91785)) Thanks [@omarshahine](https://github.com/omarshahine), [@jmissig](https://github.com/jmissig), and [@colmbrogan](https://github.com/colmbrogan). - Browser and MCP connectivity gained existing-session CDP support, discovered WebSocket validation, default-profile `cdpUrl` handling, safer browser-output boundaries, Streamable HTTP loopback transport, corrected OAuth/SSE authorization handling, and broader schema compatibility. ([#91422](openclaw/openclaw#91422), [#89851](openclaw/openclaw#89851), [#91736](openclaw/openclaw#91736), [#91747](openclaw/openclaw#91747), [#91451](openclaw/openclaw#91451), [#80143](openclaw/openclaw#80143)) Thanks [@pgondhi987](https://github.com/pgondhi987), [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia), [@lifuyue](https://github.com/lifuyue), [@eleqtrizit](https://github.com/eleqtrizit), [@LiuwqGit](https://github.com/LiuwqGit), and [@HemantSudarshan](https://github.com/HemantSudarshan). - Control UI startup and first-reply latency are lower through cached model metadata, removal of the startup catalog wait, lazy slash-command loading, and first-event tracing with slow-reply diagnostics. ([#91531](openclaw/openclaw#91531), [#91538](openclaw/openclaw#91538), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583), [#91598](openclaw/openclaw#91598)) - Provider support expands with OpenRouter OAuth onboarding and Claude Fable 5 adaptive thinking, while Codex sessions keep correct compaction ownership, local models skip guardian review, dynamic tool progress normalizes cleanly, and Gemma 4 reasoning replay is preserved. ([#91830](openclaw/openclaw#91830), [#91882](openclaw/openclaw#91882), [#91590](openclaw/openclaw#91590), [#88630](openclaw/openclaw#88630), [#88768](openclaw/openclaw#88768), [#91696](openclaw/openclaw#91696)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@joshavant](https://github.com/joshavant), [@bdjben](https://github.com/bdjben), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). ##### Changes - CLI progress: emit Claude CLI commentary progress events and bridge inter-tool commentary into channel progress without exposing internal protocol scaffolding. ([#89834](openclaw/openclaw#89834), [#90883](openclaw/openclaw#90883)) Thanks [@anagnorisis2peripeteia](https://github.com/anagnorisis2peripeteia). - Observability: allow trusted diagnostics channels to capture tool input/output content, add first-assistant-event traces, and warn on slow initial replies. ([#91256](openclaw/openclaw#91256), [#91568](openclaw/openclaw#91568), [#91583](openclaw/openclaw#91583)) Thanks [@amknight](https://github.com/amknight). - Plugins/ClawHub: dogfood reusable package publishing, let dry runs skip publish approval, allow declared installed trusted hooks, report managed plugin version drift, and warn instead of failing on retired Skill Workshop configuration. ([#91574](openclaw/openclaw#91574), [#91591](openclaw/openclaw#91591), [#90004](openclaw/openclaw#90004), [#90927](openclaw/openclaw#90927), [#90838](openclaw/openclaw#90838)) Thanks [@Patrick-Erichsen](https://github.com/Patrick-Erichsen), [@brokemac79](https://github.com/brokemac79), and [@lonexreb](https://github.com/lonexreb). - Memory/providers: move the local llama.cpp runtime into its provider plugin, batch embeddings across files, persist the agent model catalog cache, and keep QMD JSON search one-shot while filtering stale REM recall previews. ([#91324](openclaw/openclaw#91324), [#89138](openclaw/openclaw#89138), [#90457](openclaw/openclaw#90457), [#91837](openclaw/openclaw#91837), [#91851](openclaw/openclaw#91851)) Thanks [@osolmaz](https://github.com/osolmaz), [@mushuiyu886](https://github.com/mushuiyu886), [@ai-hpc](https://github.com/ai-hpc), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Channels/mobile: add the QQBot group mention toggle, improve iPad and iPhone control surfaces, and expose the active connection host in the TUI footer. ([#91423](openclaw/openclaw#91423), [#91557](openclaw/openclaw#91557), [#89909](openclaw/openclaw#89909)) Thanks [@cxyhhhhh](https://github.com/cxyhhhhh), [@Solvely-Colin](https://github.com/Solvely-Colin), and [@baskduf](https://github.com/baskduf). - Performance: prewarm TUI runtime plugins, deduplicate plugin auto-enable fanout, trim dense text-delta snapshots, and reuse prepared startup model metadata. ([#90782](openclaw/openclaw#90782), [#89978](openclaw/openclaw#89978), [#91580](openclaw/openclaw#91580), [#91531](openclaw/openclaw#91531)) Thanks [@RomneyDa](https://github.com/RomneyDa) and [@ai-hpc](https://github.com/ai-hpc). ##### Fixes - Agent/session recovery: drop stale approval follow-ups after session rebind, remove drained reply-queue items by identity, recover stale main and visible replies, preserve Codex context-engine compaction ownership, lower the default compaction timeout to 180 seconds while respecting explicit configuration, and keep provider-failure terminal lifecycle state correct. ([#85679](openclaw/openclaw#85679), [#91450](openclaw/openclaw#91450), [#91566](openclaw/openclaw#91566), [#91840](openclaw/openclaw#91840), [#91590](openclaw/openclaw#91590), [#91361](openclaw/openclaw#91361), [#91895](openclaw/openclaw#91895)) Thanks [@openperf](https://github.com/openperf), [@yetval](https://github.com/yetval), [@joshavant](https://github.com/joshavant), [@wangmiao0668000666](https://github.com/wangmiao0668000666), and [@TurboTheTurtle](https://github.com/TurboTheTurtle). - User-visible content boundaries: suppress Codex/Harmony protocol artifacts, neutralize browser and LanceDB memory media directives, redact transcript images, and preserve native `/compact` replies through source suppression. ([#89151](openclaw/openclaw#89151), [#91422](openclaw/openclaw#91422), [#91425](openclaw/openclaw#91425), [#91529](openclaw/openclaw#91529), [#90212](openclaw/openclaw#90212)) Thanks [@joelnishanth](https://github.com/joelnishanth), [@pgondhi987](https://github.com/pgondhi987), [@joshavant](https://github.com/joshavant), and [@snowzlm](https://github.com/snowzlm). - Channel delivery: keep WhatsApp captured replies attached to the successor controller after restart, retry Feishu rate limits, preserve Mattermost thread replies, canonicalize LINE webhook paths, restore Discord reply hydration and runtime timeout exports, and show OpenAI Realtime WebRTC assistant transcripts. ([#85823](openclaw/openclaw#85823), [#89659](openclaw/openclaw#89659), [#91684](openclaw/openclaw#91684), [#91649](openclaw/openclaw#91649), [#90263](openclaw/openclaw#90263), [#91686](openclaw/openclaw#91686), [#90426](openclaw/openclaw#90426)) Thanks [@itsuzef](https://github.com/itsuzef), [@ladygege](https://github.com/ladygege), [@jacobtomlinson](https://github.com/jacobtomlinson), [@fuller-stack-dev](https://github.com/fuller-stack-dev), and [@shushushv](https://github.com/shushushv). - Cron: cancel active task runs cleanly, preserve terminal timeout/cancel state, and recover no-deliver tool warnings instead of silently losing the outcome. ([#90666](openclaw/openclaw#90666), [#90678](openclaw/openclaw#90678)) Thanks [@ai-hpc](https://github.com/ai-hpc). - Gateway/config/auth: share the approval runtime socket token, replace arrays explicitly in `config.patch`, skip the deleted-agent guard only for valid ACP harness sessions, surface headless LaunchAgent state, verify SQLite auth migration before cleanup, and arm QMD startup maintenance. ([#87105](openclaw/openclaw#87105), [#91551](openclaw/openclaw#91551), [#91219](openclaw/openclaw#91219), [#91614](openclaw/openclaw#91614), [#91740](openclaw/openclaw#91740), [#91978](openclaw/openclaw#91978)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev) and [@scotthuang](https://github.com/scotthuang). - Providers/Codex: clarify quota errors, restore the Codex synthetic usage line, canonicalize Codex protocol assets, require API-key auth for realtime voice, normalize ACP model refs, preserve Gemma 4 `reasoning_content`, and avoid guardian review for local models. ([#91390](openclaw/openclaw#91390), [#91709](openclaw/openclaw#91709), [#91507](openclaw/openclaw#91507), [#91567](openclaw/openclaw#91567), [#88630](openclaw/openclaw#88630), [#91696](openclaw/openclaw#91696)) Thanks [@hxy91819](https://github.com/hxy91819), [@brokemac79](https://github.com/brokemac79), [@RomneyDa](https://github.com/RomneyDa), [@joshavant](https://github.com/joshavant), and [@Coder-Wangyankun](https://github.com/Coder-Wangyankun). - Updates/builds: recover package Gateway restarts after refresh failure, expose plugin convergence repair, fall back to Corepack in PATH-less pnpm environments, seed the correct Docker store packages, and keep ClawHub dry-run and publish paths reusable. ([#91581](openclaw/openclaw#91581), [#91599](openclaw/openclaw#91599), [#91547](openclaw/openclaw#91547), [#91591](openclaw/openclaw#91591)) Thanks [@fuller-stack-dev](https://github.com/fuller-stack-dev), [@sallyom](https://github.com/sallyom), and [@Patrick-Erichsen](https://github.com/Patrick-Erichsen). - UI: require explicit user intent before opening chat sessions and drain restored chat queues after session switches. ([#91480](openclaw/openclaw#91480)) Thanks [@TurboTheTurtle](https://github.com/TurboTheTurtle). - Android: avoid the `dataSync` foreground-service type for persistent nodes. ([#80082](openclaw/openclaw#80082)) Thanks [@davelutztx](https://github.com/davelutztx). - Native hooks: bound relay lifetimes so abandoned native hook connections cannot linger indefinitely. ([#91550](openclaw/openclaw#91550)) Thanks [@joshavant](https://github.com/joshavant). </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1040

openclaw-barnacle Bot added channel: telegram Channel integration: telegram size: M maintainer Maintainer-authored PR labels Jun 10, 2026

obviyus self-assigned this Jun 10, 2026

clawsweeper Bot had a problem deploying to qa-live-shared June 10, 2026 07:26 Failure

obviyus added 2 commits June 10, 2026 13:13

fix(telegram): use concrete callback API calls

5f19c93

test(telegram): cover callback API metadata

22c2c41

obviyus force-pushed the codex/telegram-api-ducktyping branch from d5d7fdc to 22c2c41 Compare June 10, 2026 07:44

obviyus merged commit 049c3c4 into main Jun 10, 2026
270 of 274 checks passed

obviyus deleted the codex/telegram-api-ducktyping branch June 10, 2026 07:59

obviyus mentioned this pull request Jun 10, 2026

fix(telegram): audit follow-ups — block-mode chunk config, dedupe bucket cleanup, grammy contract trust #91915

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix Telegram callback API handling#91876

Fix Telegram callback API handling#91876
obviyus merged 2 commits into
mainfrom
codex/telegram-api-ducktyping

obviyus commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading

Uh oh!

obviyus commented Jun 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

obviyus commented Jun 10, 2026

Uh oh!

clawsweeper Bot commented Jun 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

obviyus commented Jun 10, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

clawsweeper Bot commented Jun 10, 2026 •

edited

Loading