Skip to content
vavio

What does Hermes Agent remember after I start a new chat?

Starting a new chat in Hermes Agent gives you a fresh conversation with its saved memory. It does not put every previous conversation back into the model’s context. Older history can remain available to search, while saved skills and files remain on the computer. On Vavio, hosting keeps that computer separate from your laptop; it doesn’t make Hermes recall everything automatically.

Four things that can outlast a conversation

These distinctions follow Hermes v0.23.1, commit 3b42157. They describe the built-in memory system; a configured external memory provider can behave differently.

What you want to keep Where it belongs How a new chat uses it
A short, lasting fact or preference Built-in memory: memories/MEMORY.md and memories/USER.md in the active Hermes home Enabled stores enter the starting prompt as a snapshot
The details of an earlier conversation Session history, stored in state.db Hermes can retrieve relevant messages with session_search; the whole archive isn’t automatically loaded
A repeatable procedure A saved skill Hermes loads its instructions when relevant; see skills, tools and plugins
A report, source document or other working artifact A file at a known path Hermes must read the file when it needs its contents

A saved report can still exist even when Hermes doesn’t know where you put it. A useful handoff names the file, its purpose and the next task. Keeping the path in a suitable skill or memory entry helps Hermes find the document again; it doesn’t embed the whole document in every future prompt.

What /new changes

In the documented gateway behavior, /new or /reset creates a fresh conversation for the window or chat route where you run it. It leaves the earlier session’s history intact. Other views attached to the old session stay there, and work already running there can continue. Use the explicit Stop control if you intend to stop that work.

Restarting the gateway is different from starting a chat: Hermes is designed to recover the durable conversation after a restart. Neither restarting nor /new is a command to erase all saved notes or files. Use the controls for the particular data you intend to change.

Compression is another distinction. It reduces a long conversation’s working context; it isn’t a promise that every detail stays in the next model call. A stored transcript and the context sent to the model are separate things.

Check a saved fact before relying on it

Treat “I’ll remember that” as a claim to verify. For a harmless preference, you could ask:

Use the memory tool to save that I prefer a short summary before the details. Show me the saved entry.

Then check the tool result and the actual entry in the active profile’s memory. On a self-managed computer with terminal access, the default-home files can be read with:

cat ~/.hermes/memories/MEMORY.md
cat ~/.hermes/memories/USER.md

These are self-hosting paths, not a Vavio SSH setup instruction. If you use a named profile or HERMES_HOME, inspect that home’s memories directory instead. Don’t paste private memory contents into a public support request.

Start a fresh chat after confirming the write and ask for that preference. Check its answer against the stored entry. This is a suggested owner check; we did not run a live memory trial for this article.

If it fails, distinguish these cases:

  • No applied write: the model may have replied without calling the tool. When write approval is configured, a pending change also needs approval before it becomes saved memory.
  • Different profile: each profile has its own built-in memory and session store. A note saved in one isn’t automatically available in another.
  • Disabled store: check both memory_enabled and user_profile_enabled. Either store can be disabled independently; turning off one does not necessarily remove the tool for the other.
  • An already-open session: its starting memory snapshot does not refresh whenever another session saves a fact. New tool results can show current data, but the original prompt snapshot stays fixed.

The built-in stores are deliberately small. Defaults are 2,200 characters for MEMORY.md and 1,375 for USER.md, with configurable limits. A write that exceeds its limit fails; don’t assume the confirmation means it fitted. Keep lengthy instructions in a skill and detailed material in files.

Find an old discussion when a summary isn’t enough

Ask Hermes to search past sessions for the particular decision or phrase, then inspect the returned messages. The built-in session_search reads stored conversation records. It gives Hermes a way to retrieve history, not perfect recall of every task.

History must still be present in that profile’s database. Deleting or pruning sessions can remove what search needs. And a past message saying a job finished is evidence of what the conversation said; check the actual file, service or delivered result before treating the job as complete.

What managed hosting changes

Vavio supplies a managed Hermes computer for $14.99 per month, with model usage billed separately. Its MCP server and CLI let a supported assistant help manage the setup. The computer can be available while your laptop is off, but it still uses Hermes’s memory and session rules. Hosting doesn’t turn a new conversation into full recall or establish a tested export-and-restore path.

If occasional work on your own machine is enough, the same memory distinctions apply there. If you want Hermes away from your laptop and prefer someone else to handle its server, compare the current hosting offer. Choose the location for the job, then verify the particular fact or result you need Hermes to carry forward.

Sources

Written by Vavio with AI assistance and checked against official Hermes documentation and pinned v0.23.1 source. This is a source review, not a live memory or recovery test.

More from the Vavio blog: Hermes Agent guides