NousResearch/hermes-agent

Guard /usage against missing context_compressor

Cluster 14715 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These issues and pull requests address a crash or error in the /usage command when the agent's context_compressor attribute is None. The work involves adding a null-check guard in the CLI and possibly the gateway.

Open issues1

  • Issue#14715/usage crashes when agent.context_compressor is None

Open PRs1

  • PR#14887fix(cli): handle missing compressor in /usage

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #14723 fix(cli): /usage with missing context_compressor (#14715) · superseded by another PR → #15546
  • #15546 fix(cli,gateway): guard /usage against missing context_compressor (#14715) · done elsewhere
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
2 PRs closed without merging

For your agent

The same facts, typed.