Cairn

Agent intent-ack continuation detection and fixes

NousResearch/hermes-agent · cluster 7975 · agent

Data as of

6 open items. Fix attempted, not merged.

The short answer

3open issues
3open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
3 issues and 3 PRs.

These items address detection and handling of intermediate acknowledgement responses (e.g. 'Let me diagnose…') where the agent stops prematurely instead of continuing, including fixes for CJK language support, chat_completions mode, and proposals to replace or generalize the heuristic approach.

Open issues3

  • Issue#7975Feature: provider-agnostic lazy-final auto-continue in run_agent final text path
  • Issue#38192[Bug]: chat_completions can stop after “Let me diagnose…” without tool calls
  • Issue#55664intent-ack continuation never fires for non-English (CJK) responses — English-only regex in looks_like_codex_intermediate_ack

Open PRs3

  • PR#55670fix(agent): add CJK future-ack and action markers to intent-ack continuation detector
  • PR#55681fix(agent): add CJK future-ack patterns for intent-ack continuation
  • PR#55916fix(agent): detect CJK future-ack phrases in intent-ack continuation

3 PRs closed without merging

From the close comments: closed without comment 1 · superseded by another PR 1 · other 1

  • #38217 fix(conversation_loop): apply ack-continuation guard in chat_completions mode (#38192) · closed without comment
  • #55758 fix(agent): continue on CJK intent acknowledgements · other
  • #55833 fix(agent): detect CJK intent-ack replies in looks_like_codex_intermediate_ack · superseded by another PR → #52101
Closed issues · 1
  • Closed#12567[Feature]: replace codex intermediate-ack heuristic with a cheap auxiliary completion classifier
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.17: 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
agent
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/7975.json
cluster/7975.md