Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/verification.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,11 +59,11 @@ These ran in a fresh profile on macOS, with Hermes 0.23.1 and this package insta

## When the trust setting applies

Hermes 0.23.1 records a server's trust setting when its gateway connects the server. These checks ran on macOS with the API-key entry above. Each read was one `arcmira_execute_read` call, and each prompt was answered Deny.
Hermes 0.23.1 records a server's trust setting when its gateway connects the server. These checks ran on macOS with the API-key entry above. Each read was one `arcmira_execute_read` call.

- A chat started the gateway, with no service installed and no `trust` line. After the line was added, `hermes gateway restart` stopped that gateway and ran the new one in the same terminal until Ctrl+C. `hermes gateway restart --detach` started the new one in the background and returned. In both cases the next chat asked before the read.
- A chat started the gateway, with no service installed and no `trust` line. After the line was added, `hermes gateway restart` stopped that gateway and ran the new one in the same terminal until Ctrl+C. The next chat showed the prompt before the read. The prompt went unanswered, Hermes returned "The user did not approve running write-capable MCP tool 'arcmira_execute_read' on untrusted server 'arcmira'. The command was NOT run.", and nothing ran. In a second run, `hermes gateway restart --detach` started the new gateway in the background and returned. The next chat showed the prompt, and Deny was chosen.
- In an open chat, after the line was added, `/reload-mcp` printed "MCP servers reconciled (no server changes)", and the next read in that chat ran without asking.
- With the gateway installed as a launchd service, `hermes gateway restart` and `hermes gateway restart --detach` each returned, and launchd ran the new gateway with its cron scheduler. The next chat asked before the read. After `hermes gateway stop`, the gateway and the cron scheduler stayed down until the next chat started the service again.
- With the gateway installed as a launchd service, `hermes gateway restart` returned, and launchd ran the new gateway with its cron scheduler. The next chat showed the prompt before the read, and Deny was chosen. After `hermes gateway stop`, the gateway and the cron scheduler stayed down until the next chat started the service again. In a separate run, `hermes gateway restart --detach` with the service installed also returned, and launchd ran the new gateway with its cron scheduler. No chat followed that run.
- With this package installed at `34231f97eaacb5461a3f9e23c22d851330df98f6`, before its trust setting, and a gateway connected, the package was moved to this revision with `hermes plugins install --force --ref`. Hermes printed "Gateway reloaded plugins — deferred: MCP servers (next session)", and the next chat ran the read without asking.
- With a gateway running, `hermes mcp add arcmira --url "https://mcp.arcmira.com/mcp?via=hermes" --auth header` added the server, and a new chat ran the read with no restart.

Expand Down
Loading