Evidence record / hermes-agent

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-hermes-agent-canary-makes-mcp-session-and-permanent-trust-answers-stick-per-tool

Canary makes MCP session and permanent trust answers stick per tool. For an untrusted MCP server, previous session/always answers were reduced to one-call consent and the next write-capable call asked again. Canary supplies an mcp:<server>/<tool> identity: session approval is remembered for the chat and permanent approval enters the profile’s command allowlist. Consent that cannot safely be remembered, including spend-limit and payment-card prompts, offers only one-call approval or denial. The initial trust repair committed at 2026-10-23T23:16:43Z and the YOLO change at 2026-10-23T23:54:27Z; argument redaction followed at 2026-10-24T00:39:48Z. Follow-ups make YOLO/approval-off bypass the untrusted-server trust prompt while retaining the distinct spend gate, and mask secret-shaped arguments in the displayed approval preview.

Channel: preview-or-beta. Half: both. Date: 2026-10-24.

Operator consequence: The preview can reduce repeated prompts, but an Always answer now grants the wider authority its label describes. Re-audit saved rules when testing it. Do not sell repeated prompting on stable as already fixed, and do not treat prompt redaction as evidence that the called server receives no secrets. Cost approval and tool trust are separate decisions.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-hermes-agent-canary-makes-mcp-session-and-permanent-trust-answers-stick-per-tool

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact