From 02271e7d78436410de3246ec592235b35345f4be Mon Sep 17 00:00:00 2001 From: Dane Wilson Date: Tue, 10 Nov 2026 17:58:51 -0500 Subject: [PATCH] docs: correct stable release session and endpoint notes --- CHANGELOG.md | 10 ++++++---- README.md | 8 ++++++-- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 286fe1a..69d8904 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -33,10 +33,12 @@ Stable release of the functionality shipped in `v0.5.0-preview.9`. pass `--json`; each command emits one JSON result. - Use `steel browser stop` in place of the former `browser close` command. Review `steel browser start --help` for the current create-time flags. -- Stopping an ID-attached browser session forgets its local attachment without - releasing the cloud session. `browser stop --all` also leaves attached cloud - sessions running. Use an explicit `steel sessions release` target when release - is intended; account-wide release requires `--all`. +- An explicit `browser stop --session ` releases that cloud session, + even when it was only attached by ID. Only `browser stop --all` forgets + ID-attached sessions without releasing them; it also releases other CLI-created + sessions. Do not use either command to detach a borrowed session without + considering ownership. `steel sessions release ` explicitly + releases its target; account-wide release requires `--all`. - `sessions agent-logs --follow` is no longer available. Computer, checkpoint, secret, and environment commands from earlier 0.5 previews have been removed. - `STEEL_ONBOARDING_FROM` remains telemetry metadata. Pass `--from` directly to diff --git a/README.md b/README.md index 5cbb0d5..bb5210c 100644 --- a/README.md +++ b/README.md @@ -150,9 +150,13 @@ Every command that calls the Steel API uses one URL, chosen in this order: 1. `--api-url ` 2. `--local`: `browser.apiUrl` in `~/.config/steel/config.json`, or `http://localhost:3000/v1` 3. `STEEL_API_URL` -4. `https://api.steel.dev/v1` +4. With no explicit override and an active device credential, the API URL saved with that device login +5. Otherwise, `https://api.steel.dev/v1` -URLs on `steel.dev` are Steel Cloud and need an API key. Any other URL is treated as self-hosted. +URLs on `steel.dev` are Steel Cloud and require authentication through device +login or an API key. Any other URL is treated as self-hosted. An explicit +`STEEL_API_KEY` takes precedence over device login and does not activate the +saved-device-endpoint fallback. ## Output and Runtime Notes