Cairn
NousResearch/hermes-agent

User feedback during long-running agent tasks

Cluster 6176 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These issues and PRs concern the lack of visible progress indicators, heartbeats, or status updates when agents run long or blocking operations across platforms including CLI, Telegram, and Feishu. Members include bug reports, feature requests, and fixes related to streaming output, ping/ack mechanisms, and status spinners.

Open issues1

  • Issue#6176[Feature]: Streaming Terminal Output

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: other 1

  • #6557 feat(cli): add transient status spinners for tool execution (fixes #6176) · other
Closed issues · 7
  • Closed#7632[Feature]: Optimize the display of Feishu message status.
  • Closed#9116Feature Request: Long-running task watchdog with automatic status heartbeat
  • Closed#11075[Bug]: Telegram can show no visible "Still working..." update during long tool-only runs before max-iteration stop
  • Closed#11631[Bug] Gateway agent runs long-blocking terminal commands on messaging platforms with no user feedback
  • Closed#14425[Feature]: Automatic heartbeat/progress notifications for long-running tools
  • Closed#41080Feature Request: Feishu platform — real-time task status indicator while agent is processing
  • Closed#42633Feature Request: Streaming terminal output for long-running commands
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.11: 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
7
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/6176.json
cluster/6176.md