hermes-agent/website/docs/user-guide/features
xxxigm 88fcf0c8c0 docs(memory): clarify that memory does not auto-compact when full
The "Persistent Memory" callout said "when memory is full, the agent
consolidates or replaces entries to make room," which reads as if the
store self-compacts automatically. It does not: the `memory` tool
returns an overflow error and the agent does the consolidation in-turn
(the design from #41755). Also note that `replace` is bound by the same
limit — swapping in a longer entry can still overflow — which is the
exact case that confused a user (replace rejected near the cap even
though the math was correct).
2026-06-10 14:39:50 -07:00
..
_category_.json
acp.md
api-server.md
batch-processing.md
browser.md
built-in-plugins.md
code-execution.md
codex-app-server-runtime.md
computer-use.md
context-files.md
context-references.md
credential-pools.md
cron.md
curator.md
delegation.md
deliverable-mode.md
extending-the-dashboard.md
fallback-providers.md
goals.md
honcho.md
hooks.md
image-generation.md
kanban-tutorial.md
kanban-worker-lanes.md
kanban.md
lsp.md
mcp.md
memory-providers.md
memory.md docs(memory): clarify that memory does not auto-compact when full 2026-06-10 14:39:50 -07:00
overview.md
personality.md
plugins.md
provider-routing.md
skills.md
skins.md
spotify.md
subscription-proxy.md
tool-gateway.md
tool-search.md
tools.md
tts.md feat(tts): add Gemini audio tag rewrite 2026-06-10 02:57:39 -07:00
vision.md
voice-mode.md
web-dashboard.md docs: document commits field on /api/hermes/update/check 2026-06-08 08:58:26 -07:00
web-search.md
x-search.md