1. Record the model and memory route
In WebUI, note the selected model and provider. A model name alone does not tell you where inference runs: record the endpoint or service too. On the Agent host, using the same profile, run:
hermes memory statusWrite down the active external provider, if any. An external memory provider can receive conversation turns automatically, even when the agent makes no visible memory-tool call.
2. Send this synthetic message in a fresh chat
This is synthetic test data. Marker: GUIDE-1427.
Order A: $19
Order B: $26
Return the total and one sentence.
Do not browse, send messages, create files, or write memory.Expected answer: $45. The marker helps you find this particular test later. It contains no real customer, credential or business data.
The instruction narrows the task. It does not disable automatic provider behavior or enforce a network boundary.
3. Inspect each place that can receive it
| Layer | What to inspect | Record |
|---|---|---|
| WebUI host | The new chat appears in history; note the active state and profile location. | Host and profile |
| Model service | Check the provider’s request or usage records around the test time. | Provider, endpoint, request time |
| Tools | Expand the chat’s tool activity. The requested calculation needs no browser, upload or messaging action. | Actual calls and destination domains |
| External memory | Inspect ingestion or usage records for the provider reported in step 1. | Provider and sync behavior |
| Messaging | Check whether a gateway or channel was used, rather than assuming a WebUI chat was sent to one. | Destination or none |
A missing marker in memory search is not proof that nothing was sent: providers may extract selected facts instead of storing searchable verbatim text. Use ingestion records and the provider’s documented sync behavior.
4. Compare with a built-in-memory-only test profile
If you want to test without an external memory service, use a profile whose configuration you can change. In that profile:
hermes memory off
hermes memory statusStart a fresh chat and repeat the synthetic test. This disables the external provider for subsequent work in that profile; built-in notes remain available, and it does not erase data already held by an external service. Restore the prior provider with hermes memory setup if this was a temporary change.
For a local model comparison, connect your local server using the models setup instructions, select it in a new chat, and repeat. Tools and messaging still have their own routes.
5. Decide what is suitable for the real task
Before replacing the test with a real document, identify the services that will receive it and check their retention and training terms. A hosted model call sends context off the host; a remote memory extractor can do the same even when its database is local.
You are done when: you can name the model endpoint, enabled external memory provider and any tool destinations; explain which records persist; and stop or change any route you did not intend. For passwords, use the credential setup guide instead of adding them to this test.