{"repo":"NousResearch/hermes-agent","public_id":"131409","display_label":"Agent environment probe gating gaps and fixes","summary":"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.","subsystem":"agent","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":131409,"title":"`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","url":null,"state":"open"},{"kind":"pr","number":131416,"title":"fix(agent): make agent.environment_probe gate the system-prompt backend probe too","url":null,"state":"open","close_reason":{"refs":[{"kind":"pr","value":"#131420","number":131420}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":131420,"title":"fix(agent): add a separate gate for remote backend probes","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}