{"repo":"NousResearch/hermes-agent","public_id":"139611","display_label":"Telegram replies with non-numeric reply anchor ids","summary":"Members concern Telegram reply anchors that are not numeric message ids, where one report describes raw int() parsing of wake-identity JSON crashing replies since v0.22.1. Two pull requests propose sending the message unanchored instead of crashing; this describes proposals, not confirmed outcomes.","subsystem":"gateway","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":0,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":139611,"title":"[Bug]: Telegram reply anchors crash on non-numeric ids since v0.22.1 — raw int() on wake-identity JSON kills every reply into affected sessions","url":null,"state":"open"},{"kind":"pr","number":139642,"title":"fix(telegram): send unanchored when a reply anchor is not a message id (#139611)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#140185","number":140185}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":139644,"title":"fix(telegram): send unanchored instead of crashing on non-numeric reply anchors","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#139642","number":139642}],"category":"superseded_by_pr","implication":"superseded"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}