Repository navigation
v1.0.0 - first stable release (pre-release review: 1 High, 10 Medium, 54 Low fixed)
First stable release. Declares the compatibility policy stable: the public
surface listed in the "Compatibility policy" section of
README.md is guaranteed stable across the 1.x series, with
breaking changes to that surface reserved for a future 2.0.
1.0.0 is not a plain re-tag of 1.0.0rc1 (which was never published
to PyPI): a full-codebase review before release
(docs/code-review/full-codebase-review-2026-09-28.md)
found one High and a number of Medium/Low defects, all fixed here. No schema
changes and no new migrations relative to 0.6.0.
Breaking / upgrade notes
hermes-pgvector remaprefuses blank or identical--old/--new
(error:on stderr, exit 1, dry-run included). Before, an identity-equal
remap --executedeleted everymemory_entriesrow of that identity.- An explicit
--configthat cannot be read or parsed is now an error
(exit 1) forstats,backfill,prune,cleanupandremap. It used
to print a warning and silently fall back to the built-in default DSN. - Boolean config keys honour only
1/true/yes/onand0/false/no/off;
blank or unrecognised values now mean the key's default. A blank value for
a default-on key (e.g.hybrid_search) used to read asfalse. prefetch_budget,prefetch_limitandmin_similarityare clamped to
the ranges the config schema already advertised (0.1-7.5 s, 1-50,
0.0-1.0).- Telegram forum, LINE room and webhook sessions are bucketed: session
keys with chat typeforum(Telegram supergroups with topics),room
(LINE multi-person rooms) orwebhooknow normalise to theexternal-grouptheme like other multi-party traffic.
Rows already written under those raw keys are not rewritten; find them
withSELECT DISTINCT agent_identity FROM conversations WHERE agent_identity ~ ':(forum|room|webhook):'and fold them withremapif wanted. - Install backups are hidden:
install.shandhermes-pgvector install --forcenow move a previous install toplugins/.pgvector.bak-<ts>, so
hermes-agent no longer discovers the backup as a second memory provider.
Check~/.hermes/plugins/for an old visiblepgvector.bak*directory
and remove it.
Fixed
- High —
remapdata loss:remap --old X --new X --executedeleted
everymemory_entriesrow forXand exited 0 (each row conflicted with
itself on the insert, then the delete removed the originals). identity_signature()read the config frozen at startup, so edits to
allowed_themes/identity_aliases/bench_mode/write_contexts
never rebuilt cached gateway agents until a restart. It now re-reads
config.yaml(onestatper call, re-parse only on change).- The
on_session_endbackstop wrote multimodal / multi-part user turns a
second time (it flattened content differently from the host), and stored
multi-KB/skillscaffolding for bare or trivial skill invocations. replace()with a blankold_textoverwrote an arbitrary row; editing an
entry into content that already exists left the stale row recallable.- Telegram
forum, LINEroomandwebhooksession keys were not
recognised as multi-party, so the raw key -- including a participant id -- became a
theme of its own, readable from any theme viascope='all'. The bare
per-platform DM keyagent:<ns>:<platform>:dm(a DM with no chat or
sender id) is now DM-bucketed too. - The embed client accepted vectors containing NaN/Infinity/null (or an
integer too large for a float), which the database then rejected, losing
the durable row; they now degrade to a text-only row like any other embed
failure. A blankembed_url:/embed_model:in config.yaml (loaded as
null) no longer crashes the write path, and no unexpected embed-side
exception can drop a durable row any more. backfill: blank rows made of non-ASCII whitespace (NBSP, U+2000-range,
U+3000, ...) or of U+001C-U+001F were retried and counted as failed on
every sweep, or left inremainingforever on some collations; the blank
filter now matches Python'sstr.strip()independent of locale. On
SQL_ASCIIdatabases backfill no longer fails every row (text = bytea),
and rows that are not valid UTF-8 are reported as failed instead of as a
concurrent edit.on_delegation: a host-supplied child identity is normalised like the
agent's own (it is NULL with current upstream, which does not pass one).scripts/conformance.shon a reused clone checked out a stale local branch
instead of the ref it had just fetched.- Docs:
hnsw.ef_searchDSN example (the unquoted form broke the
connection), manual-install migrations path, identity resolution order
(default-profile CLI/cron sessions resolve to the themehermes), the
cleanupPII scan not coveringmetadata.raw_identity, test environment
variables.
Changed
- CI: the live and conformance jobs fail on any skipped test, so a broken
environment can no longer pass green; many new regression tests (about
80) cover the fixes above. - The repro scripts under
docs/code-review/repro-2026-09-26/exit 2 (not
1, "bug present") on environment problems.