Fix unbound pt_key_to_sequence variable on config import failure

NousResearch/hermes-agent · cluster 101757 · 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 fixes address an UnboundLocalError where pt_key_to_sequence is not guaranteed to be bound when a voice config import fails in the CLI/TUI. The fixes ensure the variable is always initialized before use as a fallback.

Open issues1

  • Issue#101757[Bug]: Docker exec hermes tui throw local variable 'pt_key_to_sequence' error

Open PRs2

  • PR#101774fix(cli): guarantee pt_key_to_sequence is bound in voice keybinding fallback
  • PR#105656fix(tui): avoid UnboundLocalError on pt_key_to_sequence when config import fails (#101757)

1 PR closed without merging

From the close comments: duplicate 1

  • #102479 fix(cli): guard pt_key_to_sequence binding when voice config import fails (#101757) · duplicate → #101774, #101757
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.