The agent that grows with you
Python aiai-agentai-agentsanthropicchatgptclaudeclaude-codecodexhermeshermes-agentllmnous-researchopenai
docs(api): note browser-extension control's removal; point at browser.cdp_url
Tekniumb04f5a38bb65
diff --git a/website/docs/developer-guide/programmatic-integration.md b/website/docs/developer-guide/programmatic-integration.mdindex cfa6ff772b9..53501465c10 100644--- a/website/docs/developer-guide/programmatic-integration.md+++ b/website/docs/developer-guide/programmatic-integration.md@@ -57,7 +57,7 @@ terminal.resize clipboard.paste image.attach`session.active_list`, `session.activate`, and `session.close` are the process-local live-session controls used by the TUI session switcher. Use `session.list` / `/resume` for saved transcript discovery; use the active-session methods only for sessions that are currently open in the TUI gateway process.-Within one authenticated gateway, resuming or activating a live session attaches another event subscriber rather than replacing the previous connection. Streaming and terminal events go to all attached clients; disconnecting one client does not end a session another client is viewing. Existing submit exclusivity and configured busy-input policy remain in force. Attached clients can steer the session's subagents; browser-controller results still require the connection that registered that controller. This does not enable independent gateway processes to write the same session, nor does it imply durable prompt admission across an owner restart.+Within one authenticated gateway, resuming or activating a live session attaches another event subscriber rather than replacing the previous connection. Streaming and terminal events go to all attached clients; disconnecting one client does not end a session another client is viewing. Existing submit exclusivity and configured busy-input policy remain in force. Attached clients can steer the session's subagents. This does not enable independent gateway processes to write the same session, nor does it imply durable prompt admission across an owner restart.### Model overrides on `session.create`@@ -141,8 +141,6 @@ POST /v1/runs/{id}/steer Inject mid-run guidance at the next tool boundaPOST /v1/runs/{id}/resolve-unknown Acknowledge an exact restart-unknown admissionPOST /v1/runs/{id}/stop Interrupt the runGET /v1/capabilities Machine-readable feature flags-POST /v1/browser-control/register Register a browser controller-GET /v1/browser-control/ws Browser-controller WebSocketGET /v1/models Lists hermes-agentGET /api/model/options Provider-aware picker inventoryGET /health, /health/detailed@@ -150,10 +148,8 @@ GET /health, /health/detailedSetup, headers (`X-Hermes-Session-Id`, `X-Hermes-Session-Key`), and frontend wiring: [API Server](../user-guide/features/api-server).-Browser extensions can opt into the disabled-by-default controller protocol to-drive the exact browser session that opened the Hermes conversation. The API-and dashboard transports share one principal-bound broker and one explicit-capability allowlist; see [Browser-extension control](../user-guide/features/api-server#browser-extension-control).+The browser-extension controller protocol has been removed; to let Hermes drive a browser you+already run, use `browser.cdp_url` or `/browser connect` — see [Browser-extension control (removed)](../user-guide/features/api-server#browser-extension-control-removed).### Model catalog surfacesdiff --git a/website/docs/developer-guide/relay-shared-metrics.md b/website/docs/developer-guide/relay-shared-metrics.mdindex 38c859ae195..7d49802e120 100644--- a/website/docs/developer-guide/relay-shared-metrics.md+++ b/website/docs/developer-guide/relay-shared-metrics.md@@ -477,7 +477,7 @@ itself ships.| `hermes.memory.op.count` | op (`add`/`replace`/`remove`/`read`/`search`/`other`), provider (`builtin`, a bundled memory plugin, else `plugin`), origin (`foreground`/`background_review`), outcome (`success`/`failed`/`rejected`), failure class | Is the learning loop writing memory, who asks for it (the user's turn or the background review), and how often writes are refused or fail, and why. Since package schema v4 `failure_class` names the reason from a closed list mapped from each refusal/failure return of the built-in store: `no_match` (old_text matched no entry), `ambiguous` (it matched several), `over_budget` (the write would pass the char limit), `would_empty` (a batch would remove the last entry), `drift` (the file holds text the store cannot round-trip), `read_failed` (the file exists but cannot be read), `retry_cap` (the per-turn retry budget is spent), `scan_blocked` (the content matched a threat pattern), `missing_content`, `missing_old_text`, `invalid_args`, `stale_entry` (a staged write's entry changed), `disabled` (that target is off in config), `staged` (held for the user's approval), `gate_refused` (the write-approval gate blocked it); `provider_error` / `exception` for a plugin provider's tool that returned an error or raised; `none` on success; `other`/`unknown` otherwise. A batch applies all or none, so every op row of a refused batch carries the class of the op that stopped it. Never the memory text, the old_text or the error message. || `hermes.curator.run.count` | trigger (`scheduled`/`manual`), outcome (`success`/`failed`/`skipped`), archived/merged/patched/created buckets | Does the skill curator run, and does it actually consolidate anything. Dry runs report `skipped`; a scheduled check that finds another process already running the pass records nothing. Never skill names. || `hermes.delegation.run.count` | subagent-count bucket, depth (`1`–`3`, `gte_4`), mode (`foreground`/`background`), outcome (`success`/`partial`/`failed`/`cancelled`) | How wide and deep delegate_task fan-outs go and how often every child finishes. One row per call, however many completion units it splits into. |-| `hermes.execution_backend.count` | kind (`terminal`/`browser`/`code`), backend, outcome, error class | Which sandboxes carry real work and how reliable each is. Terminal backends are the `terminal.backend` values (else `other`); browser backends are `local`, `lightpanda`, `cdp`, `extension` or a bundled cloud provider (else `other`; `camofox` stays in the schema as a legacy label); execute_code is `local` or `remote`. A command's own nonzero exit is still a backend success, but a foreground command that hits its timeout is `failed`/`timeout`; terminal and execute_code calls a guard refuses before they reach the backend, Hermes' own listings for TUI/Desktop path completion, and calls made by the background review and curator forks are not counted. |+| `hermes.execution_backend.count` | kind (`terminal`/`browser`/`code`), backend, outcome, error class | Which sandboxes carry real work and how reliable each is. Terminal backends are the `terminal.backend` values (else `other`); browser backends are `local`, `lightpanda`, `cdp` or a bundled cloud provider (else `other`; `camofox` and `extension` stay in the schema as legacy labels); execute_code is `local` or `remote`. A command's own nonzero exit is still a backend success, but a foreground command that hits its timeout is `failed`/`timeout`; terminal and execute_code calls a guard refuses before they reach the backend, Hermes' own listings for TUI/Desktop path completion, and calls made by the background review and curator forks are not counted. || `hermes.platform.health` | platform, event (`connect_ok`/`connect_failed`/`reconnect`/`disconnect`), error class (`auth`/`network`/`rate_limited`/`config`/`other`) | Which messaging platforms fail to connect or drop, and why. `connect_failed` counts a failed-connect episode once per profile, platform and UTC day (the reconnect watcher's retries are not new rows; the next success ends the episode, and a platform still failing the next day counts again), with the error class of the episode's first failure. Classified from exception types, HTTP statuses and Hermes's own fatal codes, never error text. || `hermes.platform.delivery` | platform, outcome (`sent`/`failed`), failure class (`rate_limited`/`too_long`/`auth`/`network`/`forbidden`/`other`) | How often replies fail to reach the user per platform (one count per logical reply, retries included). || `hermes.gateway.reply_latency` | platform, first-response bucket (`lt_2s` … `gte_60s`) | Time from an accepted inbound message to the first visible reply text (stream first chunk or final message). |diff --git a/website/docs/user-guide/features/api-server.md b/website/docs/user-guide/features/api-server.mdindex 5d55e741677..e927f32e92d 100644--- a/website/docs/user-guide/features/api-server.md+++ b/website/docs/user-guide/features/api-server.md@@ -378,96 +378,17 @@ Returns a machine-readable description of the API server's stable surface for exUse this endpoint when integrating dashboards, browser UIs, or control planes so they can discover whether the running Hermes version supports runs, streaming, cancellation, and session continuity without depending on private Python internals.-## Browser-extension control--Hermes can route browser tools through an authenticated extension that controls-the browser session associated with the current Hermes session. The feature is-disabled by default; set `browser.extension_control.enabled` to `true` to opt in:--```yaml-browser:- extension_control:- enabled: true-```--The local API path also requires the API server bearer key. A controller may-register only for an existing server session. Hermes derives the controller-principal from authenticated server state; a client-supplied `principal_id` is-ignored.--Discover the live contract through `GET /v1/capabilities`. The-`browser_extension_control` object reports whether the feature is enabled, the-protocol version, transport names, and the exact capability allowlist:--```text-controller.noop-browser_back-browser_click-browser_navigate-browser_press-browser_screenshot-browser_scroll-browser_snapshot-browser_tab_activate-browser_tabs-browser_type-```--These are controller-protocol action names, not the agent's tool names (the-agent's browser tools are `browser_exec`, `browser_cdp`, `browser_dialog` and-`browser_vault`). Requested capabilities outside that list are filtered out. Raw CDP, arbitrary-script evaluation, console access, uploads, image extraction, and vision are not-part of the controller protocol.--When a request has no bound controller identity, or when the feature is disabled,-Hermes preserves the existing browser backend. Once the gateway binds a-controller principal and transport family to the request, that extension lane-is authoritative: missing, ambiguous, disconnected, or incapable controllers-fail closed instead of silently switching to a different local/cloud browser.-After an exact controller is selected, its result or error is authoritative and-Hermes never retries the same action through another backend.--### Local API registration--1. Send an authenticated `POST /v1/browser-control/register` with- `protocol_version`, `session_id`, `controller_id`, `browser_profile_id`, and- the requested `capabilities`.-2. Hermes returns a single-use ticket with a 30-second TTL and the filtered,- server-bound controller scope.-3. Open `GET /v1/browser-control/ws` with both WebSocket subprotocols:- `hermes-browser-control-v1` and- `hermes-browser-control-ticket.<ticket>`.--The ticket is never accepted in the query string. Unknown, expired, reused, or-malformed tickets fail before WebSocket upgrade.--### Controller frames--Hermes sends `browser.controller.command` frames containing `command_id`,-`action`, immutable `arguments`, browser/controller ids, and the originating-`tool_call_id`. The controller replies with `browser.controller.result`, the-same `command_id`, an exact boolean `ok`, and either `result` or `error`.-Cancellation and timeout emit `browser.controller.cancel`; late results are-ignored.--An unexpected socket loss marks the controller offline and preserves work-already in flight until each command's original deadline. A reconnect with the-same principal, profile, session, controller id, browser profile, and transport-identity refreshes the transport without admitting new work before any deferred-cancels are flushed. Negotiated capabilities may change on that reconnect; they-are not an identity field. A different controller id or browser profile in the-same authenticated session lane is a hard replacement: old pending work is-cancelled before the successor becomes routable. Send-`browser.controller.detach` on the authenticated controller transport for an-intentional hard detach — that immediately cancels pending work. Merely closing-the socket is treated as a recoverable disconnect.--The authenticated dashboard transport exposes the same registration, result,-heartbeat, capability, and ownership semantics over its Gateway RPC/event-channel. In both transports, selection requires one unambiguous exact match on-principal, profile, session, controller, browser profile, transport family, and-capability. Once selected, a controller failure is authoritative and is never-retried through a different browser backend.+## Browser-extension control (removed)++The browser-extension controller protocol (`POST /v1/browser-control/register`,+`GET /v1/browser-control/ws`, the `/v1/artifacts/*` routes, the dashboard+`browser.controller.*` RPCs and the `browser.extension_control` config key) has+been removed. It routed the old `browser_navigate`/`browser_click`/… tools,+which no longer exist: browser automation is now `browser_exec` over CDP. To let+Hermes drive a browser you already run, point it at that browser's DevTools+endpoint with `browser.cdp_url` in `config.yaml` or `/browser connect` — see+[Your own browser via CDP](./browser#your-own-browser-via-cdp-browser-connect).+Upgrading drops a leftover `browser.extension_control` block from `config.yaml`.## Per-request model selection