Agent environment probe gating gaps and fixes

NousResearch/hermes-agent · cluster 131409 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 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 items address a bug where agent.environment_probe config did not gate the system-prompt backend probe, and a related fix adding a separate gate specifically for remote backend probes. A reported issue documents that the prompt-backend-probe container runs on every chat turn with a remote terminal backend and cannot be disabled.

Open issues1

  • Issue#131409`prompt-backend-probe`: one container per process with a remote terminal backend, no off switch (see #72423), and a non-`~/.hermes` HERMES_HOME shares the live profile's container identity

Open PRs2

  • PR#131416fix(agent): make agent.environment_probe gate the system-prompt backend probe too
  • PR#131420fix(agent): add a separate gate for remote backend probes
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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.