NousResearch/hermes-agent

Reduce repetitive Codex provider-wait heartbeat noise

Cluster 92550. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #115807 on 19 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #115807 Pick up a Lab task

These items address a UX issue where a status or warning message about waiting on the Codex provider was being repeated every 30 seconds, creating noisy, warning-like output during otherwise healthy requests. The proposed fix consolidates this into a single neutral status message.

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.

#115807 fix(agent): long provider waits show one neutral status naming the watchdog instead of a 30s warning drumbeat (#92550, salvage #92657)

merged to main

files: agent/chat_completion_helpers.py, agent/chat_completion_nonstream.py, agent/chat_completion_stream_monitor.py, agent/chat_completion_wait_notice.py, apps/desktop/src/store/provider-wait.test.ts, apps/desktop/src/store/provider-wait.ts, tests/agent/test_codex_ttfb_watchdog.py, tests/agent/test_nonstream_wait_notice.py, tests/agent/test_wait_notice_cadence.py, tests/hermes_cli/test_load_progress.py, website/docs/user-guide/configuration.md

1 PR closed without merging

From the close comments: merged via another change 1

#92657 fix(agent): stop repeating the Codex wait notice every 30s · merged via another change → 926055b, #115807, #92550, #92657

Closed issues · 1

Closed#92550[UX]: 30s Codex provider-wait heartbeat is warning-like noise during healthy requests

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.67: 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

Merged PRs: #115807
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/92550.json
cluster/92550.md