NousResearch/hermes-agent

Customizable CLI status bar fields via configuration

Cluster 41909 · hermes cli. Data as of 2026-10-24 20:38 UTC

Nothing open on GitHub. Fix merged in #98250 on 30 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #98250. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #98250, then check it covers your case.

Read #98250 Pick up a Lab task

These members share one theme: making the CLI status bar's fields user-selectable, mainly through a display.status_bar.fields config option. One also mentions added metrics such as cache-hit %, latency, and tokens/second with per-field toggles, and another asks about custom and responsive fields.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#98250 feat(cli): status bar gains cache-hit %, latency, t/s, and per-field toggles (salvage #92696, #39760, #97970)

merged to main

files: agent/agent_init.py, agent/conversation_loop.py, cli.py, contributors/emails/[redacted:email], hermes_cli/config_defaults.py, tests/cli/test_cli_status_bar.py, website/docs/user-guide/configuration.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#41995 feat(cli): add display.status_bar.fields config for customizing status bar · superseded by another PR → #92696
#92696 feat(cli): status bar fields are now user-selectable via display.status_bar.fields (#41909, salvage #41995) · merged via another change → #98250

Closed issues · 1

Closed#41909Custom (and responsive) fields in the CLI status bar?

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: hermes cli
Merged PRs: #98250
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 30 Aug 2026

For your agent

The same facts, typed.

cluster/41909.json
cluster/41909.md