Explain why a blank provider language can still resolve to English. Align the guides and environment reference with first-nonempty resolution while preserving configuration values and documenting command-backend limits.
Constraint: Documentation must describe current runtime behavior, not pending default-language or CLI changes.
Confidence: high
Scope-risk: narrow
Reversibility: clean
Tested: Four configuration cases through the real loader and resolver; parsed YAML unchanged.
Tested: Clean English Docusaurus build and rendered table/cross-link checks; git diff --check.
Not-tested: Other documentation locales; no runtime code changed.
Classic CLI gains a Codex-style backtrack picker. Esc Esc on an idle, empty composer with no
overlay (or /rewind) lists earlier prompts newest first with a preview and turn number.
- Enter: prefill the prompt for editing. Nothing is cut until the edit is submitted; the
submission rides to the process loop as a BacktrackResend, which re-validates the picked
turn (same session, same text) and then runs the same durable rewind /undo uses. Esc Esc,
Ctrl+C, an empty submit, or submitting a slash/! command cancels and cuts nothing.
- f: fork. Runs the existing /branch path, then rewinds only the CHILD to just before the
picked prompt and prefills it; the parent's rows stay active.
- /rewind N and /rewind fork N do the same without the picker.
Esc Esc with a draft still discards it; mid-turn Esc Esc is unchanged.
undo_last's rewind body moves into CLISessionMixin._rewind_to_user_ordinal (shared by /undo
and the picker; same compaction-carrier handling, agent patching and memory rewound hook).
The picker lives in a new hermes_cli/cli_backtrack.py mixin; cli_tui_mixin.py is untouched.
CommandDef rewind is cli_only (desktop: terminal); desktop registry and parity table regenerated.
The reference said "/save | Save the current conversation" and listed /save
as CLI-only. On main /save takes <json|md|html> [filename] [redact] in the
CLI, TUI, Desktop and messaging gateway (hermes_cli/commands.py registers it
without cli_only).
- CLI table: formats and aliases, redact, where the file lands (always on
the user's machine; Desktop uses a save dialog), bare /save behaviour.
- Messaging table: new /save row (file sent to the chat as a document).
- Notes: drop /save from the CLI-only list.
- Same changes in the zh-Hans copy.
Follow-up to the Web Extract removal:
- Review row: `/review` is a full independent subagent, and its own guide
(features/delegation.md "Review model") pins a strong model, so advise a
separate (often stronger) model instead of a cheaper one; drop the
"async delegation rail" internals and link the canonical section.
- Voice Chat row: drop the source-file path, say that reasoning is off on
voice turns even on `auto` and that GPT-Live ignores the slot, link
features/voice-mode.md "Voice chat model".
- Drop the hard-coded slot count: "11" went stale because nothing ties it
to `_AUX_TASK_SLOTS`, and plugin-registered tasks add rows anyway. The
intro gives examples and links the table instead of a partial list.
- Apply the same corrections to the zh-Hans mirror, which still listed
Web Extract and 11 slots.
- Remove the remaining "web extraction" mentions from aux-task lists in
the CLI aux picker prose, fallback-providers, agent-loop, integrations
index and the --usage-file paragraph.
Refs #147807
Removes 7 optional skills:
- notion, airtable: the official vendor MCPs are in the MCP catalog
(OAuth, no Portal needed), hosted connectors exist, and each vendor
keeps its own skills repo.
- shopify: hosted connector plus Shopify's own maintained `shopify`
skill in Shopify/Shopify-AI-Toolkit.
- duckduckgo-search, searxng-search: both are bundled web_search
backends now and web_search works keyless out of the box, so these
fallback-only skills essentially never surfaced.
- honcho: Honcho left core for Plastic Labs' catalog plugin, which owns
the `hermes honcho` commands this skill documented.
- mpp-agent: the verified Pay plugins (hosted and local) cover paying
HTTP 402 / x402 / MPP APIs with a bundled skill.
makenotion/skills, Airtable/skills and Shopify/Shopify-AI-Toolkit become
default trusted taps (all MIT, vendor-owned) so the topic still shows in
`hermes skills browse`, matching the wandb/qdrant/pinecone precedent.
The `box` skill stays for now.
AIRTABLE_API_KEY leaves OPTIONAL_ENV_VARS (its only consumer was the
skill); NOTION_API_KEY stays because the Teams meeting pipeline's Notion
sink reads it, and its description now says so. Related-skill links,
docs examples and the zh-Hans catalogs drop the removed names.
Round-2 review P3 #2: the two version gates compare differently. Document that a
hermes-agent requirement uses PEP 440 with its marker, requires_hermes compares
major.minor.patch and passes what it cannot parse, and that a misfit of either
sits out and is refused at enable/install instead of being disabled.
Independent review (P2): binding the core name to `{ workspace = true }` makes uv
ignore the specifier, so a selected extra `hermes-agent[other]>=2` installed against
Hermes 1. Main's runtime path had the same hole: `applicable_requirements` drops a
runtime `hermes-agent>=2` without checking it.
Every applicable requirement naming hermes-agent (runtime dependencies, manifest
pip_dependencies, and the extras this generation installs, markers evaluated on the
target interpreter) is now checked against the version identity requires_hermes reads
(the committed pyproject version is a 0.0.0 placeholder). A mismatch raises
ResolutionConflict naming the plugin, the requirement and the running version, which
update-time eviction treats as a verdict on the plugin and parks it.
PM renames a virtual plugin member (no build backend) to hermes-plugin-<key>
so two profiles can enable the same plugin. Its own `name[extra]` references in
dependencies and optional-dependencies kept the declared name, so uv resolved
them as a different package: a lock failure (and an update that disables the
plugin) when no index serves the name, or someone else's package installed in
place of the extra when one does.
Rename those references (canonicalize_name match; extras, specifiers and
markers kept as written) and `tool.uv.conflicts` package entries along with the
project, before the extras pass, so its self-reference closure reads the names
uv sees.
Independent review finding 3 on #148199: `_runtime_member_metadata` removed
unselected extras and every dependency group but kept `tool.uv.sources`
alternatives qualified by them, so uv refused the whole workspace ("Source
entry for `x` only applies to extra `dev`, but the `dev` extra does not
exist") for a plugin that syncs on main. Alternatives scoped to a group or
to an extra this sync does not install are now dropped, in both the table
and list forms; a package keeps its key while any alternative remains, and
unqualified runtime sources always stay.
uv locks every extra of every workspace member, but PM's generation sync
installs only the extras `--extra` names. A plugin test extra such as
`dev = ["httpx<0.28"]` therefore failed the lock against core's
httpx==0.28.1 and `hermes update` disabled the plugin. The generated member
snapshot now keeps only the extras this generation selects plus those the
plugin's own requirements name (`plugin[runtime]`), and drops conflicts that
point at removed extras. Explicit `--extra` of a plugin-declared extra still
locks and installs it.
Review finding: a carried extra whose per-extra trials failed on a download or tooling
error was left out of the published selection with no decline and no retry record.
Those facts end the old venv's re-scan, so no later update ever carried it again and
the extra was silently lost.
A transient trial result is not a verdict: the sync now fails before publishing,
naming the extra, so the next update scans the old venv again and retries it. Only
build verdicts are left out and recorded, as before.
A migration from a pre-PM venv carries the extras that venv held (matrix,
fal, ...) into PM's first generation. Those reached sync_venv as if the user
had requested them, so one that no longer builds (python-olm's vendored
libolm without a working cmake/C++ compiler) failed the whole sync. No
facts.json was written, the old venv is never deleted, and every later
`hermes update` re-scanned it, re-carried the same extra and failed the
same way: one optional extra bricked updates for good.
sync_venv now takes `carried`, the entries of `extras` that were carried
rather than asked for. When the sync fails with a build or resolver verdict,
pm.carried_extras proves core plus the requested extras build without them,
re-adds each carried extra on top of what fits, and syncs without the ones
that do not. A build verdict is recorded in declined-extras.json (with the
reason, so a later lazy-install refusal names the cause instead of a
`--without` nobody ran) and the operator is told which extra was left out and
to run `hermes pm install --extra NAME` to add it back. A download failure is
left out of this update but not recorded. Requested extras and core still
fail loudly. Both legacy callers (the source-launch sync and the historical
takeover) pass the carried list.
The streamed uv tail also keeps the build-backend marker now: a native
build's traceback runs past the 2000-character tail, so the failure read as a
fetch error instead of a BuildFailure verdict (this also hid plugin build
verdicts from plugin eviction).
Also fixes committed_venv's docstring: PM never deletes the in-tree venv.
python-build-standalone records CC='clang -pthread', CXX='clang++ -pthread',
clang-led LDSHARED/LDCXXSHARED and AR=/tools/llvm/bin/llvm-ar in sysconfig.
setuptools compiles with those unless the environment overrides them, so on
Debian/Ubuntu/WSL hosts with only gcc/g++ every C/C++ sdist under PM's pinned
interpreter failed with "No such file or directory: 'clang++'" (python-olm
via the matrix extra), and any build_clib static library failed on the
missing llvm-ar even where clang exists.
For the pinned interpreter on Linux, pm/build_compilers.py reads the recorded
toolchain once per interpreter and setdefaults CC/CXX (and the linker each
one leads) to the gcc-family equivalent when the recorded compiler is absent
and gcc/g++ is on PATH, keeping flags such as -pthread, and defaults AR to
the host's ar. User-set CC/CXX/LDSHARED/LDCXXSHARED/AR win; other
interpreters keep their sysconfig. The macOS AR default moves into the same
module unchanged. When no compiler exists at all, a BuildFailure now names
the missing compiler and how to install one instead of "retry".
The fail-loudly-on-missing-compiler idea comes from #130255.
Co-authored-by: jose_ugalde <vivojf@gmail.com>
A plain unaddressed follow-up in a channel thread the bot participates in
gets reply_expected=None, so a bare [SILENT] is rejected and the gateway
posts the unexpected-silence notice. That is noisy when humans in the
thread talk to each other without @mentioning.
thread_followup_silence (config.extra / SLACK_THREAD_FOLLOWUP_SILENCE,
default false) makes such non-DM thread replies reply_expected=False so the
silence marker stands. DMs, @mentions and flat channels are unchanged,
and the default keeps the #110952 behaviour.
Move the Slack config getter factories into adapter_config_readers.py to
keep adapter.py within its code-health line cap.
_TRUSTED_LOCAL_ORIGIN_PORTS (9119, 5173, 5174, 4174) was trusted on every
backend, including packaged Desktop backends on an ephemeral port. A Vite app
on 5173, or on 5174 when 5173 is taken, could still read the session token
from / and open /api/ws. _is_trusted_local_origin() now accepts only the bound
port and the desktop dev renderer this backend was spawned for
(HERMES_DESKTOP_DEV_SERVER). `hermes dashboard` keeps working on 9119 because
that is its bound port.
The dashboard's Vite dev server was the only client that relied on a fixed
port: the browser's Origin on proxied /api upgrades is Vite's. The /api proxy
now presents upgrades from Vite's own page (Origin host equals Host) with the
backend's origin, and passes every other Origin through for the backend to
refuse, so it does not launder foreign pages the way Vite's rewriteWsOrigin
would. Vite's default CORS grants every localhost port and would hand another
local page the token hermesDevToken() injects into index.html, so it is off.
(cherry picked from commit 66de028a3ce39ec49a32205855dc269d30bf3942)
Running the documented commands against a scratch HERMES_HOME showed several
claims in the new reference were wrong:
- `hermes project bind-board` does not link a board's tasks to the project. It
records the board on the project and, when the board exists and the project has a
primary folder, sets the board's default workdir (from the CLI only a bare
`--workspace worktree` task uses it). The board's project_id stays null, so tasks
get no project link or deterministic branch; only the kanban dashboard's Project
selector or `hermes kanban create --project` links tasks. Unbinding clears only
the project's record.
- The CLI resolves `<project>` by an exact id or a slug in any case, not by display
name; name matching is only in the desktop_project tool.
- `set-primary` normalizes paths, so the "spell it the way show prints it" tip was
wrong.
- A desktop_project move leaves the active-project pointer alone only when the
project has a folder, and the desktop sidebar following the viewed chat can still
select the new project.
Also: the worktree + branch default applies to linked non-dir tasks of a project
with a primary folder; an unknown `--project` creates an unlinked task without an
error; complete the exit-code list; note desktop delete (folders and chats kept),
the sidebar's automatic groups, and the Windows HERMES_HOME default; drop internal
table/function names and the raw sqlite queries; replace troubleshooting advice
that made two projects own one folder; point background-systems.md at the
reference; shorten the routing row; and regenerate the bundled-skill docs page.
website/docs/reference/cli-commands.md made the same bind-board claim; its summary
rows and `hermes project` section now describe what the CLI does, and `--project`
is listed among the `kanban create` flags.
A machine stop during an install can leave an unpacked wheel in PM's uv
cache whose files are NUL bytes: uv renames its unpack directory into
archive-v0 without flushing the data. uv reuses that entry on every sync, so
every later plugin enable, repair or install failed with "The wheel is
invalid", and neither a retry nor the suggested `hermes pm doctor` helped.
When uv's install step fails on a cached artifact (invalid wheel, invalid
RECORD, or a cache pointer to a missing archive), PM now removes the named
package(s) plus any other entry that fails the same validation through
`uv cache clean`, deletes leftover corrupt archives, and retries. A retry
only follows a failure naming a package not purged yet (at most three), so a
source that serves a broken wheel fails once more with a message naming the
package and the cache directory. Other failures are untouched.
`hermes pm doctor` now reports corrupt uv cache entries, and
`hermes pm doctor --repair` removes them.
First-run setup keeps passing --migrate-secrets (what core's old OpenClaw step did); the named
command forwarded setup's choice too, so API keys and bot tokens came over without being asked.
Grok Bot joins setup's "Coming from another agent?" step (detected from its desktop app
or a downloaded grok-bot-export file). Bare `hermes migrate` offers the same import on an
existing install; `hermes migrate <agent>` imports from one agent, installing the
agent-importers plugin from the catalog when missing. A plugin too old for the picked
importer is updated once and the import retried, for setup and migrate alike.
`hermes update` ran `git stash push --include-untracked` on every dirty tree,
so any untracked folder in the checkout was hashed into git objects and
deleted from disk, then written back on restore. A 55 GB leftover worktree
copy (2.8M files) made the "stashing before update" step take minutes, and
declining the restore left the whole folder parked in git stash.
- Untracked entries are stashed only when a ref the update can land on
(target, origin/<branch>, local <branch>) has a file at that path, or a
parent/child of it; the rest stay on disk via exclude pathspecs, because a
pull or checkout never refuses on them. Comparison is casefolded so a
case-insensitive filesystem still counts Config.py vs config.py. Forks and
unreadable target trees keep the old stash-everything behaviour (the
upstream sync lands on a ref fetched later).
- An interactive terminal now asks "Keep these changes after updating?"
BEFORE anything is stashed. Yes stashes and restores without a second
prompt; no deletes exactly what would have been stashed, so no stash
entry is left behind. A run with nothing to pull does not ask. Gateway
/update, --yes and non-interactive (Desktop) paths are unchanged apart
from the scoped stash.
Drops the HERMES_STREAM_MAX_LIFETIME override (non-secret behaviour settings
belong in config.yaml) and its docs row; tests now set agent.stream_max_lifetime
in a temp HERMES_HOME config.yaml and read it through the real loader.
A stream cut by agent.stream_max_lifetime was counted as a stale kill, so two
capped long replies latched HERMES_STREAM_STALE_GIVEUP and the next healthy
request was refused with nothing sent. The cut also surfaced as a transport
error ("stream attempt N was superseded", "the endpoint looks unreachable").
- cap kills are marked accounted in the stale breaker but never counted;
- the killed attempt's error becomes StreamLifetimeExceeded (a TimeoutError,
so still retried) naming the setting, and the exhausted notice uses it;
- docs say which transports the cap covers (Chat Completions and Anthropic
Messages; not Codex/Responses or Bedrock) and that it skips the breaker.
The stale-stream detector bounds the gap BETWEEN chunks and resets on every
chunk, so a stream that keeps sending data but never finishes (a gateway
trickling chunks, a runaway generation) is never cut and the turn sits there.
New opt-in agent.stream_max_lifetime (env HERMES_STREAM_MAX_LIFETIME), default
0 = off, so long reasoning streams keep today's behaviour unless the user sets
it. When set, the cap is charged from the start of the current stream attempt,
never resets on chunk arrival, restarts for each retry attempt, and is floored
at the effective stale timeout. Tripping it kills the attempt like a stale
kill: cancel the attempt, abort the request-local client, shut down its socket,
count it once in the cross-turn stale breaker; the retry loop or the
partial-delivery continuation takes over.
Logic lives in agent/stream_max_lifetime.py; the stream monitor calls it from
its poll loop. The Bedrock poll loop is not covered (chat_completion_helpers.py
may not grow).
Port of an upstream idea.
- Classic CLI (and the Desktop slash worker, which runs this handler): `/model reset` switches
back, session-scoped (never --global, even under model.persist_switch_by_default), to
config.yaml's model read fresh at the command, through the normal typed path (guards, confirm,
session-row persist), and drops an armed --once restore. Already on the default: says so; no
model.default: says there is nothing to reset to.
- The /model args_hint lists `reset`.
- TUI: a `/model reset` queued mid-turn shows the default it will adopt, not the word "reset",
and skips the pick-time selection guard (adopting the configured default is not a new pick).
- cli.model.reset_none / reset_no_default in all 17 locales; slash-command and messaging docs.
- Tests: parser invariants, gateway reset of a store-only override after a restart, TUI reset
that adopts config without re-pinning.
Output of website/scripts/generate-skill-docs.py and
scripts/ci/prompt_surface.py render after the skill moves. The default
skills index loses 15 lines (14 skills leave the built-in set, three
become microsoft-office).
These stop loading by default and become one
`hermes skills install official/<category>/<name>` away:
notion, airtable, box (hosted connectors cover them for Portal users),
opencode, design-md, gif-search, songsee, llm-wiki,
hermes-agent-skill-authoring, inspecting-hermes-desktop-dom,
node-inspect-debugger and python-debugpy.
Existing installs keep their copies: the skills sync already re-labels
a byte-identical copy of a moved built-in as an official optional
install. Onboarding first tasks drop the two skills that are no longer
bundled (llm-wiki, design-md), claude-design and popular-web-designs
point at design-md as an optional install, and doc examples use
skills that still ship.
A continuing session replays its stored system prompt verbatim on every turn
so the provider prefix cache stays warm. The gateway restores that prompt from
the session row on each fresh agent, and warm cached agents keep it in memory,
so SOUL.md edits, new or edited skills and project-context changes never
reach a long-running conversation until /new, which also drops the history.
Operators who push profile updates and restart the gateway had no way to make
existing conversations pick them up.
`hermes sessions refresh-prompts [--session ID] [--json]` records a refresh
epoch in the profile's state.db (state_meta, one counter orders profile-wide
and per-session requests). At the start of a continuing session's next turn,
_restore_or_build_system_prompt compares that epoch with the one stamped in
the session's model_config when its prompt was built. When the stored prompt
is older it follows the Bot Chat capability-refresh precedent in the same
function: tools[] pin restored first, skills prompt cache and snapshot
cleared, prompt rebuilt through _build_system_prompt (memory reloaded and
plugin sections re-rendered, as at a compaction boundary), cache break
recorded, on_session_start not fired, new bytes and epoch persisted so the
following turns restore them verbatim. One cache break per request.
Warm agents (gateway agent cache, TUI/Desktop) run the same check from
build_turn_context against the epoch they saw when their prompt was set, so
the verb works with the gateway running. A session first built after a
request is stamped with it and does not rebuild again.
With no request recorded, the stored prompt is reused byte-identically. The
only added work per continuing turn is one state_meta point read. No file
scanning, no config key, no watcher, no mid-turn mutation.
The tools[] pin is kept on purpose: the refresh is about instructions, and
tool changes already reach long sessions at the compaction boundary. The
cache break is recorded as the existing system_prompt_rebuild cause rather
than a new one, which would change the shared-metrics contract and schemas.
Related: #141154 (per-turn source hashing, alternative design), #74622.
The six document skills each carried a copy of a venv bootstrap that ran
`python -m venv --clear` on a shared directory after an unlocked check, so two
agents could erase each other's install, and the pdf skill's optional installs
read a DOCS_ENV that was only set inside a branch.
`hermes pm environment NAME --extra E | --requirement R` exposes PM's existing
isolated environments (pm.ensure_environment) to shell callers: the identity
is re-checked under the environment's install lock, a rebuild lands in a new
generation published by an atomic selection, and the previous generation is
never deleted. It prints only the interpreter path on stdout. --extra reads
the extra's pins from pyproject.toml, so a Hermes update does not build a new
generation unless those pins change.
Every document skill now runs the same one-liner
(`hermes pm environment documents --extra documents --extra documents-pdf`)
when `python` lacks the libraries; the new documents-pdf extra carries
pdfplumber and pypdfium2. OCR libraries get their own named environments.
The no-tmux PTY recipe pauses 0.5 s between the text write and the Enter
write, like the tmux recipe, so the paste guard cannot read Enter as a newline.
HERMES_CONFIG_REMOTE_POLL_SECONDS is gone: the interval is 300 s (the 30 s floor stays), so no
new non-secret HERMES_* env var is needed before config can be read. A plane-served interval is a
later cross-repo change. The environment-variables reference now lists HERMES_CONFIG_REMOTE_URL
and HERMES_CONFIG_INSTANCE_ID next to HERMES_CONFIG_BACKEND, with why each must be env.
Addresses teknium1's P2-2 on #122509.
puts back what that build deliberately left for the remote backend, on
main's seam shape:
- RemoteBackend implements main's protocol (read_user_doc, probe_readable)
and is not a FileBackend; _route returns (backend, home) and explicit
files go through _ExplicitFile, so the is_layer branches are gone.
- One bootstrap: _ensure_bootstrap_env / bootstrap_deployment select the
backend from the process env, the launch home's .env and the managed .env.
#134362's _dotenv_backend_override did not survive its file-only refactor,
so nothing stacks; its rules are now tests (stale shell remote + .env file
boots file; empty .env value resets to file; .env-only remote selects
remote; an absent key keeps the shell value).
- The file-tooling gates main removed (backup/import/snapshot restore,
config edit, migration write-back, config backups, profile clone and
distribution install, raw config editor, xAI migration, gateway --config).
- profile_serve_signature uses the backend version for config.yaml.
- restore_config_model_settings_if_rewritten is a no-op without file tooling.
- PM's dependency runtime reads a home's selection from the local file it
publishes to (config_backend.local_file_layer), so a remote deployment
never needs the plane there or fails PM closed.
- Ratchet: _container_slots/_validate_quoted_containers move to
config_value_checks, _count_cron_jobs to backup_restore, the gateway
--config load to gateway/config_loader.
orphan_install_states only reclaimed installs/<key> when the recorded checkout
was provably deleted (under the data root, or directly in an existing
.worktrees/ dir). A checkout anywhere else (~/.cache/review-*/head, a scratch
clone outside the data root) kept its ~0.5 GB / ~27k-file state forever once
deleted: ~235 of ~300 states on one developer host.
The proof rule stays: a provably deleted checkout is reclaimed at once. A
missing checkout that cannot be proved deleted (it may sit behind a mount
boundary: a container sharing the data root, an unmounted volume) is now
reclaimed once its state has also gone unused for
worktrees.install_state_retention_days (default 14, 0 = keep forever).
"Used" is what the runtime moves, measured on a live install: every sync
recreates inputs/ (and rewrites facts.json on a change), every launch takes a
generation lease (moving its .leases dir). Present checkouts, record-less
states and held states (install lock, generation lease) are never reclaimed;
removal keeps the record-last order, and a part-way removal does not restart
the clock.
The remote-backend recipes in desktop.md and web-dashboard.md wrote the
HERMES_DASHBOARD_BASIC_AUTH_SECRET line inside a quoted heredoc, so .env got the
literal text $(openssl rand -base64 32) instead of a random secret. Write the
credentials with the quoted heredoc and append the secret with a real command
substitution, and tell readers how to spot and replace the literal line.
The basic provider now ignores a signing secret that still contains unexpanded
shell text ($( or a backtick), logs an error, and uses a random per-process key,
so the literal string is never used to sign or verify sessions.
A number that keeps getting spam calls is almost always listed on people-search
sites, so the engine now accepts the number as the starting point, with the FTC
Do Not Call registry as a one-shot alongside the opt-outs.
- intake accepts phone/email-led subjects (one identifier minimum); a missing
name/contact-email is warned, not refused (scans run; opt-outs need them)
- --focus-phone marks the number being scrubbed: added to search vectors and
used as the `phone` disclosure field instead of phones[0]
- brokers with zero runnable search vectors group as `unsearchable` instead of
wedging `unscanned` forever; `fanout` skips them
- `dnc` command + `dnc_register` action in `next` (mirrors `drop`): register
US personal numbers on the National Do Not Call Registry (FTC-verified
steps: 3 numbers per pass, 72h confirmation links, 31 days to take effect,
never expires), surfaced once per subject until `--filed`
- docs: SKILL.md recipe + quick reference, methods.md reverse-phone notes,
README; regenerated the website skill page; corrected the stale "85 tests"
claim (repo-wide test purges left 30) -> 34 with the 4 new hermetic tests
Conflict: hermes_cli/env_loader.py import block. Kept the branch's
left_core_migration.profile_env_names import and main's ConfigBackend
switch (load_yaml_file_readonly no longer imported; _load_secrets_config
reads through config_backend.read_config_doc_readonly).
No main commit since 0c771d7a5ba touches Copilot code; nothing to port.
GLM-5.2 became the silent default (the model Hermes lands on when the user
never picked one) in #64635 as a capable low-cost pick. GLM-5.3 has since
superseded it at about the same price on Nous Portal and OpenRouter, with
the same 1M context, and both curated catalogs already list it.
Move every copy of the default together:
- PREFERRED_SILENT_DEFAULT_MODEL and the OpenRouter "default" description.
- The "default": true label in website/static/api/model-catalog.json,
regenerated with scripts/build_model_catalog.py, so clients rotate from
their cached catalog without a release.
- The TUI's _resolve_model last resort, which hardcoded "z-ai/glm-5.2" and
would drift on every rotation; it now reads the constant from the
data-only models_catalog_static module.
- The example manifest in the model catalog reference docs.
The new TUI test pins the no-model fallback to the constant, and the
manifest contract test is renamed since it checks whatever the constant is.
Provider pages (en + zh-Hans) replace the built-in Copilot sections, table
rows and env rows with a pointer: `hermes plugins install github-copilot`
(labs: built by Nous Research, not supported), auto-installed for profiles
that already use copilot/copilot-acp, sign-in with `hermes auth add copilot`
or COPILOT_GITHUB_TOKEN/GH_TOKEN/GITHUB_TOKEN (gh and Copilot CLI logins are
no longer read). The model-provider plugin guide gets one table of every
ProviderProfile field and hook in providers/base.py, and its examples point at
the labs plugin. The hermes-agent skill references and the
cli-config.yaml.example provider list drop the built-in Copilot rows.
On macOS webbrowser.open can return True with no page the user sees: over SSH osascript opens the browser on the Mac's own screen, and a sandboxed browser may refuse a file: page in a hidden folder. After a private launch, say how to get the link. The docs no longer say an SSH session always prints the link: that holds on the BSDs and illumos. The private-launch docstring notes that on macOS the URL reaches osascript on stdin, so the page mainly protects the BSDs and illumos.
Where nothing checks who redeems a one-use launch link (macOS, the BSDs, illumos, WSL), hermes webapp printed it, and any local user who read it first could redeem it within its 60 s. TCP loopback has no peer-credential call on those platforms. The launcher now writes the link into a 0600 page in the gateway home's user-only webapp folder and opens that page, so the browser launcher's command line carries only the page's path and nothing is printed. It still prints the link where it cannot open a browser and on WSL.
Refs #144648 (WA-12)
The seam had a selector and reserved members that nothing in this PR
uses: HERMES_CONFIG_BACKEND accepted only `file` (every other value
exited), the .env override existed only to decide when to refuse,
UserLayer.locks/provenance and ConfigBackend.locked() were always empty,
and the supports_file_tooling()/require_file_tooling() checks at ten
file-copy sites were always true. All of it is for the remote backend
(#122509), so it lands there with the code that makes it real.
get_config_backend() now returns the file backend. The env var, its
docs row, the dotenv override, ConfigBackendUnavailable and the
file-tooling gates are gone, with the tests that covered them. The
explicit-file routing test now proves a non-config.yaml path never
consults the backend.
probe_config_readable() calls a probe_readable() protocol method
instead of an isinstance(FileBackend) check, and version_token()
documents how it treats an int-led version.
- The environment-variable reference had no row for HERMES_CONFIG_BACKEND,
a selector that stops Hermes at startup when set to anything but
`file`. Added, with where it is read from and a link to the developer
guide.
- hermes_time called the config backend module "dependency-free"; its
file backend imports utils. Say what the fallback actually does.
Teknium: the ElevenLabs variant of text_to_speech is where voice search belongs, not a
separate tts_voices tool. The ElevenLabs schema now carries voice_id plus a find_voices
object (text optional there); other providers' schema is byte-identical to main.
Live search findings folded in: the library is the default source and sorts by a year of
usage (most-used first); use_case (e.g. characters_animation) and sort filters; library
voices with a custom credit rate show credit_rate; the description tells the model the
library matches words literally, so a role word that finds nothing ('dwarf') falls back to
describing the sound ('gravelly old' + filters).