Cairn

Auto-delete temporary progress/status messages in gateways

NousResearch/hermes-agent · cluster 4882 · gateway

Data as of

5 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs concern adding opt-in auto-deletion of transient tool-progress and status messages across Discord and Telegram gateways. Work spans feature requests, implementation of delete_message actions, and delayed cleanup mechanisms.

Open issues4

  • Issue#4882[Feature] Auto-delete tool progress messages after completion
  • Issue#21889feat(discord): add delete_message for cleanup_progress support
  • Issue#47858Gateway: delayed cleanup for Telegram/meta progress messages
  • Issue#62157Feature request: let the Discord gateway agent self-delete its own messages (and expose a code-exec tool)

Open PRs1

  • PR#47859feat: add delayed gateway meta cleanup

3 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1 · other 1

  • #21890 feat(discord): add delete_message for cleanup_progress support · superseded by another PR → #80576
  • #62255 feat: expose Discord self-delete as a core action (#62157) · other → #62152, #62157
  • #62580 fix(discord): implement delete_message so cleanup_progress actually works · duplicate → #21890, #42661, #60450
Closed issues · 1
  • Closed#21252Feature: Add auto-delete option for tool status messages on Telegram
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.15: 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
gateway
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/4882.json
cluster/4882.md