NousResearch/hermes-agent

MCP trust-gate 'always'/'session' answers not persisting per tool

Cluster 109818 · gateway. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #143780 on 23 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #143780. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #143780. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #143780, then check it covers your case.

Read #143780 Pick up a Lab task

The members concern MCP trust-gate or elicitation approvals, where an 'always' (or session-scoped) answer is reportedly not remembered and prompts reappear. Two members are pull requests that propose persisting these answers per (server, tool) and limiting one-shot prompts to Once/Deny; the third is an issue describing the problem.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#143780 MCP trust prompts: Allow for this session / Always now stick per tool; one-shot prompts offer only Once / Deny (salvage #109832)

merged to main

files: tests/tools/test_mcp_trust_approval_scope.py, tools/approval_prompt.py, tools/mcp_tool_handlers.py, website/docs/developer-guide/plugins/index.md, website/docs/reference/mcp-config-reference.md, website/docs/user-guide/features/mcp.md

1 PR closed without merging

From the close comments: merged via another change 1

#109832 fix(mcp): persist trust-gate session/always answers per (server, tool) · merged via another change → ad81947, #143780

Closed issues · 1

Closed#109818"always" answer to an MCP elicitation/trust-gate approval is not persisted — every session asks again

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: gateway
Merged PRs: #143780
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 23 Oct 2026

For your agent

The same facts, typed.

cluster/109818.json
cluster/109818.md