feat(cli): integrate agent-browser runtime and top-level API tools#38
Merged
feat(cli): integrate agent-browser runtime and top-level API tools#38
Conversation
Relocate Docker-based local browser controls to steel dev start/stop and update browser command descriptions/docs to point local usage to dev commands.
Adds repeatable cold/warm benchmark scenarios with budget thresholds and mock session API wiring for regression checks.
Switches Steel bootstrap injection to --cdp, preserves bare --auto-connect discovery, and rejects mixed attach flags. Bundles upstream daemon dist assets with vendored runtime, auto-sets AGENT_BROWSER_HOME for vendored execution, and adds runtime/cloud smoke validation scripts.
Adds a dependency guard script and wires it into build to prevent accidental playwright installs or lockfile drift away from playwright-core.
…nstall flow - add --api-url support across browser lifecycle and passthrough bootstrap - add steel dev install and explicit local runtime install/start/stop boundaries - improve localhost local-mode guidance and add cloud integration + unit coverage
- add browser compatibility, migration, upstream sync, and reference index docs - update generated CLI docs and docs generator option naming - record authenticated cloud smoke pass in implementation plan
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces major improvements to documentation, command reference clarity, and workflow reliability for the Steel CLI. The most significant changes are a full rewrite and expansion of the
README.mdand documentation files, the addition of new compatibility and migration guides, and updates to GitHub Actions workflows to ensure browser runtime compatibility across platforms before publishing or releasing. The CLI reference documentation now features more accurate command lists, improved template names, and additional details for new and existing commands.Documentation and User Guidance Improvements:
README.mdto clarify installation, usage, endpoint resolution, browser integration, command overview, auto-update logic, and documentation map. Added migration, compatibility, and troubleshooting references.docs/browser-compat.mdto document compatibility betweensteel browserand upstreamagent-browser, including a behavior matrix, known differences, and validation targets.docs/README.mdto clarify the distinction between generated and hand-maintained docs, provide a docs map, and explain regeneration steps.CLI Reference and Command Improvements:
docs/cli-reference.mdby updating the Table of Contents, adding new commands (config,pdf,scrape,screenshot,settings,update,browser live,browser sessions,dev install/start/stop), and refining descriptions. [1] [2] [3]forgetemplates in the CLI reference to usesteel-*-starternaming for clarity and consistency.pdfcommand and support for the--anthropic_keyflag, and improved documentation for existing commands.Workflow Reliability and Cross-Platform Testing:
.github/workflows/npm-publish.ymland.github/workflows/release.ymlto add abrowser-runtime-smokejob that runs browser smoke tests on Ubuntu, macOS, and Windows before publishing or releasing, ensuring cross-platform compatibility. The publish/release jobs now depend on these smoke checks. [1] [2]This pull request introduces several significant improvements to documentation, workflow automation, and command compatibility for the Steel CLI. The most important changes include a major overhaul of theREADME.mdfor clarity and completeness, the addition of a browser compatibility document, updates to the auto-generated CLI reference, and enhancements to CI workflows to ensure cross-platform browser runtime checks.Documentation and Reference Improvements:
README.mdto provide a clearer overview, quick start guides, endpoint resolution details, agent-browser integration, command grouping, and a comprehensive documentation map.docs/browser-compat.mdto document the compatibility matrix and behavioral differences betweensteel browserand upstreamagent-browser, including known differences and deferred mappings.docs/README.mdto clarify the structure and regeneration process for documentation, and to distinguish between generated and hand-maintained docs.docs/cli-reference.mdwith a more accurate table of contents, clearer command descriptions, expanded command coverage (including new and updated commands), and updated template names for theforgecommand. [1] [2] [3] [4] [5]CI Workflow Enhancements:
browser-runtime-smokejob to bothrelease.ymlandnpm-publish.ymlworkflows, running browser runtime smoke tests across Ubuntu, macOS, and Windows, and made publishing/release jobs depend on successful completion of these checks. [1] [2]