Cairn
NousResearch/hermes-agent

Fix per-prompt timer to use monotonic clock

Cluster 46177 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 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
1 issue and 1 PR.

These issues and PRs address a bug where the CLI status-bar elapsed timer used the wall clock, causing it to jump or behave incorrectly on NTP adjustments, system clock changes, or resume from sleep. The fix switches the timer to a monotonic clock source.

Open issues1

  • Issue#46177Per-prompt status-bar timer uses wall clock and jumps on NTP/clock change or resume

Open PRs1

  • PR#46239fix(cli): use monotonic clock for per-prompt elapsed timer (#46177)

2 PRs closed without merging

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

  • #46179 fix(cli): drive per-prompt timer with monotonic clock · superseded by another PR → #55548
  • #46340 fix(cli): use time.monotonic() for per-prompt status bar timer · duplicate → #46179
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
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/46177.json
cluster/46177.md