Cairn

Telegram base_url ignored in standalone send path

NousResearch/hermes-agent · cluster 51223 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 3 PRs.

A bug where the send_message tool bypasses the configured Telegram base_url (used for self-hosted Bot API servers) in proactive/cron send scenarios, along with associated fix attempts.

Open issues1

  • Issue#51223[Bug]: send_message tool ignores telegram base_url — proactive/cron sends bypass self-hosted Bot API server

Open PRs3

  • PR#51224fix(telegram): honor base_url in standalone send_message tool (#51223)
  • PR#73156fix(send_message): honor telegram base_url in standalone send path (#51223)
  • PR#125409fix(telegram): standalone sends honour custom Bot API base_url and read timeout
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/51223.json
cluster/51223.md