Cairn
NousResearch/hermes-agent

Handle KeyboardInterrupt cleanly in single-query chat

Cluster 61508 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 2 PRs.

These issues and PRs address unhandled KeyboardInterrupt exceptions that cause traceback output when a user interrupts single-query chat mode via signal. The work involves catching the interrupt gracefully in the CLI.

Open issues1

  • Issue#61508Single-query chat prints KeyboardInterrupt traceback on signal

Open PRs2

  • PR#61509Handle KeyboardInterrupt in single-query chat
  • PR#61669fix(cli): handle chat -q interrupts cleanly

1 PR closed without merging

From the close comments: merged via another change 1

  • #62693 fix(cli): catch KeyboardInterrupt in single-query mode · merged via another change → #71783
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/61508.json
cluster/61508.md