Preserving executed tool calls on empty-response exit

NousResearch/hermes-agent · cluster 120826

Data as of

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

The short answer

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

These issues and PRs concern a bug where tool calls that have already been executed are lost from the model's context when an agent exits due to an empty response or Stop, causing them to be re-run. The members explore fixes to retain that tool call history when the empty-response scaffolding is dropped.

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.

  • #121279 Empty-response give-up or Stop no longer erases an executed tool call (#120826, salvage #120827)

    merged to main

    files: agent/session_persistence.py, agent/turn_api_call.py, agent/turn_recovery.py, tests/agent/test_empty_response_recovery_persistence.py, tests/agent/test_message_sequence_repair.py

3 PRs closed without merging

From the close comments: merged via another change 2 · other 1

  • #120827 fix(agent): keep executed tool calls when empty-response scaffolding is dropped · merged via another change → dae147f, 299dfd3, #120826, #121279, #120883
  • #120867 fix(agent): keep empty-response tool history at exit owners · other → #120827
  • #120883 fix(agent): preserve executed tools after empty-response exits · merged via another change → c92c72c, 6ef6e83, 299dfd3, #121279, #120826, #120827
Closed issues · 1
  • Closed#120826[Bug]: after an empty-response give-up or Stop, an already-executed tool call vanishes from the model's context and gets re-run
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.40: 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
#121279
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.