Skip to content

The agent that grows with you

docs(browser): describe the corrected v52 and Camofox migration rules

Teknium05cf03e9822c
diff --git a/website/docs/reference/environment-variables.md b/website/docs/reference/environment-variables.md
index aecf6c5001c..dba43302610 100644
--- a/website/docs/reference/environment-variables.md
+++ b/website/docs/reference/environment-variables.md
@@ -167,7 +167,7 @@ For native Anthropic auth, Hermes prefers Claude Code's own credential files whe
| `BROWSER_CDP_URL` | Chrome DevTools Protocol endpoint the browser tools attach to instead of launching Chromium (set via `/browser connect`, e.g. `ws://localhost:9222`; same as `browser.cdp_url`) |
| `CAMOFOX_*` | Read only by the Camofox plugin (`hermes plugins install camofox`); core Hermes ignores them. |
| `BROWSER_INACTIVITY_TIMEOUT` | Browser session inactivity timeout in seconds |
-| `AGENT_BROWSER_*` | No longer read. On update, values in the profile's `.env` are copied into config when the key is unset: `AGENT_BROWSER_EXECUTABLE_PATH` → `browser.executable_path`, `AGENT_BROWSER_PROFILE` → `browser.user_data_dir`, `AGENT_BROWSER_ARGS` → `browser.chromium_args`, `AGENT_BROWSER_HEADED` → `browser.headed`, `AGENT_BROWSER_ENGINE` → `browser.engine`. |
+| `AGENT_BROWSER_*` | No longer read. On update, values in the profile's `.env` are copied into config when the key is unset (`browser.engine: auto` and `browser.headed: false` count as unset; a relative `AGENT_BROWSER_PROFILE` becomes an absolute path): `AGENT_BROWSER_EXECUTABLE_PATH` → `browser.executable_path`, `AGENT_BROWSER_PROFILE` → `browser.user_data_dir`, `AGENT_BROWSER_ARGS` → `browser.chromium_args`, `AGENT_BROWSER_HEADED` → `browser.headed`, `AGENT_BROWSER_ENGINE` → `browser.engine`. |
| `FAL_KEY` | Image generation ([fal.ai](https://fal.ai/)) |
| `KREA_API_KEY` | Krea API key for Krea 3 and Krea 2 image generation ([krea.ai](https://krea.ai/)) |
| `GROQ_API_KEY` | Groq Whisper STT API key ([groq.com](https://groq.com/)) |
diff --git a/website/docs/user-guide/configuration.md b/website/docs/user-guide/configuration.md
index 5f99fc2bd8a..93d59095d40 100644
--- a/website/docs/user-guide/configuration.md
+++ b/website/docs/user-guide/configuration.md
@@ -2861,7 +2861,7 @@ toolset with `hermes tools` (or `hermes tools disable browser [--platform NAME]`
See the [browser feature page](./features/browser.md#browser_dialog) for the full dialog workflow.
**Removed keys (migrated automatically).** `browser.backend` is gone — `browser_exec` is the
-only browser path. An old `backend: "off"` is removed on update with a one-time notice to
+only browser path. An old `backend: off` (quoted or not) is removed on update with a one-time notice to
disable the `browser` toolset instead; any other value is removed silently.
`snapshot_threshold`, `record_sessions`, `allow_unsafe_evaluate` and `restrict_evaluate`
belonged to the removed built-in browser tools and no longer have an effect. The
@@ -2870,6 +2870,9 @@ The old `AGENT_BROWSER_*` environment variables are no longer read; on update th
are copied from the profile's `.env` into the matching keys when those keys are unset
(`AGENT_BROWSER_EXECUTABLE_PATH` → `executable_path`, `AGENT_BROWSER_PROFILE` → `user_data_dir`,
`AGENT_BROWSER_ARGS` → `chromium_args`, `AGENT_BROWSER_HEADED` → `headed`, `AGENT_BROWSER_ENGINE` → `engine`).
+`engine: auto` and `headed: false` count as unset, because the environment variable overrode them
+before. A relative `AGENT_BROWSER_PROFILE` was resolved against the working directory, so it is
+written as that absolute path (the working directory at update time).
## Timezone
diff --git a/website/docs/user-guide/features/browser.md b/website/docs/user-guide/features/browser.md
index dddf411c28d..d2817915b0a 100644
--- a/website/docs/user-guide/features/browser.md
+++ b/website/docs/user-guide/features/browser.md
@@ -602,7 +602,10 @@ hermes tools disable browser --platform telegram # one gateway platform
## Camofox
Camofox moved to a plugin: `hermes plugins install camofox`. Existing Camofox
-setups are migrated automatically on update.
+setups (`CAMOFOX_URL` set, or `browser.cloud_provider: camofox`) are migrated automatically on
+update: the plugin is installed and the core `browser` toolset is turned off in that profile.
+A `browser.camofox` block with no `CAMOFOX_URL` is not a Camofox setup. A profile that sets up the
+plugin after the update keeps `browser_exec` alongside it.
## Practical examples