Cairn

Terminal heartbeat schema defaults and validation fixes

NousResearch/hermes-agent · cluster 119196

Data as of

Nothing open on GitHub. Fix merged in #133793. Check it covers your case.

The short answer

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

These issues and pull requests address a bug where the terminal heartbeat schema caused foreground validation loops and notification flooding. The fixes involve normalizing heartbeat defaults, ensuring disabled heartbeat configurations are schema-valid, and removing a materialized foreground terminal heartbeat.

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.

  • #133793 fix(terminal): a foreground call with heartbeat runs instead of looping on a refusal (#121634, salvage #119201)

    merged to main

    files: tests/tools/test_process_heartbeat.py, tools/terminal_tool.py

4 PRs closed without merging

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

  • #119201 fix: normalize foreground terminal heartbeat defaults · superseded by another PR → 4317ed0, #119202
  • #119202 fix(terminal): make disabled heartbeat schema-valid · merged via another change → 4317ed0, #119196
  • #119203 fix(tools): drop a materialized foreground terminal heartbeat · superseded by another PR → #119201
  • #124108 fix: normalize a materialized foreground terminal heartbeat and give it a disabled schema default · done elsewhere → 4317ed0, #119196, #119202
Closed issues · 1
  • Closed#119196[Bug]: terminal heartbeat schema causes foreground validation loops and notification flooding
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.33: 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
#133793
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
7 Oct 2026

For your agent

The same facts, typed.

cluster/119196.json
cluster/119196.md