Cairn

Runtime footer metadata fields and gateway footer support

NousResearch/hermes-agent · cluster 11701 · agent

Data as of

11 open items. Fix attempted, not merged.

The short answer

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

These issues and pull requests concern expanding the runtime_footer display with additional fields such as tokens, cost, tokens-per-second, and tool count, as well as adding opt-in runtime metadata footers to gateway integrations like Discord, Telegram, and Slack.

Open issues6

  • Issue#11701[Feature]: Persistent usage/cost footer on gateway (Discord, Telegram, Slack) messages
  • Issue#17037[Feature Request]: Configurable gateway response metadata/footer hooks
  • Issue#19922[Feature]: Expand display.runtime_footer to include all variables from /usage
  • Issue#26877[Feature]: Add tps (tokens per second) field to runtime_footer
  • Issue#35427feat: extend runtime_footer with provider, tokens, cost, and tool count fields
  • Issue#52288feat(gateway): add token usage to runtime footer

Open PRs5

  • PR#26932feat(footer): add tps field to runtime_footer (#26877)
  • PR#106079feat(gateway): add usage fields to runtime footer
  • PR#106256feat(gateway): add post-delivery observer hook
  • PR#129449feat(gateway): opt-in `tps` footer field shows this turn's generation speed
  • PR#140658feat(gateway): expand runtime_footer with usage and billing metrics (#19922)

2 PRs closed without merging

From the close comments: partial fix 1 · other 1

  • #44878 feat(agent): per-call output speed (tokens/sec) for desktop status bar and runtime footer · partial fix → #12434, #13164
  • #97172 feat(gateway): expand runtime_footer with context_bar, context_used_total, age, sessions, voice · other
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
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/11701.json
cluster/11701.md