Cairn
NousResearch/hermes-agent

Expressing zero tools via CLI -t toolsets option

Cluster 126122 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 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 0 PRs.

These members concern the CLI -t option being unable to request zero tools: an empty -t "" reportedly falls back to configured toolsets, and a none sentinel is proposed. Two of the three titles are identical pull-request-style titles about making zero tools expressible and failing closed on an empty -t.

Open issues1

  • Issue#126122CLI/-z: no way to request zero tools — `-t ""` silently uses configured toolsets; add a `none` sentinel

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: stale or abandoned 1 · other 1

  • #127881 fix(toolsets): make zero tools expressible, fail closed on an empty -t · stale or abandoned
  • #138999 fix(toolsets): make zero tools expressible, fail closed on an empty -t · other
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.67: 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.

cluster/126122.json
cluster/126122.md