Hermes Telegram Gateway Can Fail to Connect After Request-Layer Patch Error (#64730)
Bug Tracker — July 15, 2026. A documented Telegram adapter incident reports that gateway startup can fail while patching the request layer, leaving no connected platforms even though cron execution continues.
Issue Summary
Issue #64730 reports that Telegram gateway startup fails when the adapter attempts to patch an HTTPXRequest object whose do_request attribute is read-only. The gateway reportedly continues with no connected platforms and retries Telegram, leaving direct-message and group delivery unavailable while cron execution can continue. The upstream issue is marked closed as not planned, so this is recorded as a documented incident rather than represented as an active open tracker item.
Observed Failure Path
| Step | Reported Behavior | User-Level Consequence |
|---|---|---|
| Gateway starts | Telegram adapter initializes and attempts to patch the request layer. | Normal startup should connect the configured Telegram platform. |
| Request-layer patch | HTTPXRequest.do_request is reported as read-only. | Adapter initialization errors before a usable Telegram client is established. |
| Platform state | Gateway proceeds with no connected platforms and retries Telegram. | Telegram direct messages and group delivery are unavailable. |
| Scheduled work | Cron execution can continue despite the channel failure. | Background tasks may run without their expected messaging delivery path. |
Operational Impact
Classification: P1. Status: Closed as not planned. This page summarizes a publicly reported incident; its scope, remediation status, and reproducibility can change. Validate behavior on the relevant Hermes version, adapter, and deployment path before treating a workaround or closure as complete.
Mitigation and Verification
- Check gateway startup logs and connected-platform state after updates; treat a running process as insufficient evidence that Telegram delivery is healthy.
- Run a real DM and group-message smoke test after adapter or dependency changes, alongside a cron-to-delivery test.
- Because issue #64730 is closed as not planned, review the current supported Telegram integration path and release notes before applying version-specific mitigations.
- Use an independent delivery-health signal so operators can detect the condition where scheduled work continues but outbound Telegram delivery does not.
Source Evidence
Primary issue: NousResearch/hermes-agent issue #64730
For a managed-agent comparison, the relevant question is whether configuration settings and channel failures remain consistent, observable, and recoverable across interfaces—not only whether the happy path succeeds.