
vercel-sandbox
#25 in Testing & QARun agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app.
Overview
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.From the project's GitHub description
Our editorial assessment of vercel-sandbox is still in review. Facts below come from the repository and our catalogue.
Technical specifications
Each attribute is labelled with where it came from.
Install
A skill is a set of instructions your agent loads. Install it into the agent you use; there is nothing to host.
$ npx skills add https://github.com/vercel-labs/agent-browser --skill vercel-sandbox- Listing
- skills.shInstall counts come from skills.sh.
Alternatives
Also in Testing & QA
Same category, not necessarily equivalent.
google-agents-cli-eval
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimi…
migrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn.
Reviews
Community ratings are kept separate from Beav Scout rankings.
No reviews yet. Community reviews and comments are opening soon; you'll be able to rate vercel-sandbox once signed in.