Skip to content

docs: correct v0.5 stop semantics and saved device endpoint #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danew merged 1 commit into from
Nov 11, 2026
Merged

docs: correct v0.5 stop semantics and saved device endpoint #136

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <session-id>` 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 <session-id>` 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
Expand Down
8 changes: 6 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,9 +150,13 @@ Every command that calls the Steel API uses one URL, chosen in this order:
1. `--api-url <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

Expand Down
Loading