Agent skill
agentcore
Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.
Install this agent skill to your Project
npx add-skill https://github.com/vercel-labs/agent-browser/tree/main/skills/agentcore
SKILL.md
AWS Bedrock AgentCore
Run agent-browser on cloud browser sessions hosted by AWS Bedrock AgentCore. All standard agent-browser commands work identically; the only difference is where the browser runs.
Setup
Credentials are resolved automatically:
- Environment variables (
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY, optionallyAWS_SESSION_TOKEN) - AWS CLI fallback (
aws configure export-credentials), which supports SSO, IAM roles, and named profiles
No additional setup is needed if the user already has working AWS credentials.
Core Workflow
# Open a page on an AgentCore cloud browser
agent-browser -p agentcore open https://example.com
# Everything else is the same as local Chrome
agent-browser snapshot -i
agent-browser click @e1
agent-browser screenshot page.png
agent-browser close
Environment Variables
| Variable | Description | Default |
|---|---|---|
AGENTCORE_REGION |
AWS region | us-east-1 |
AGENTCORE_BROWSER_ID |
Browser identifier | aws.browser.v1 |
AGENTCORE_PROFILE_ID |
Persistent browser profile (cookies, localStorage) | (none) |
AGENTCORE_SESSION_TIMEOUT |
Session timeout in seconds | 3600 |
AWS_PROFILE |
AWS CLI profile for credential resolution | default |
Persistent Profiles
Use AGENTCORE_PROFILE_ID to persist browser state across sessions. This is useful for maintaining login sessions:
# First run: log in
AGENTCORE_PROFILE_ID=my-app agent-browser -p agentcore open https://app.example.com/login
agent-browser snapshot -i
agent-browser fill @e1 "user@example.com"
agent-browser fill @e2 "password"
agent-browser click @e3
agent-browser close
# Future runs: already authenticated
AGENTCORE_PROFILE_ID=my-app agent-browser -p agentcore open https://app.example.com/dashboard
Live View
When a session starts, AgentCore prints a Live View URL to stderr. Open it in a browser to watch the session in real time from the AWS Console:
Session: abc123-def456
Live View: https://us-east-1.console.aws.amazon.com/bedrock-agentcore/browser/aws.browser.v1/session/abc123-def456#
Region Selection
# Default: us-east-1
agent-browser -p agentcore open https://example.com
# Explicit region
AGENTCORE_REGION=eu-west-1 agent-browser -p agentcore open https://example.com
Credential Patterns
# Explicit credentials (CI/CD, scripts)
export AWS_ACCESS_KEY_ID=AKIA...
export AWS_SECRET_ACCESS_KEY=...
agent-browser -p agentcore open https://example.com
# SSO (interactive)
aws sso login --profile my-profile
AWS_PROFILE=my-profile agent-browser -p agentcore open https://example.com
# IAM role / default credential chain
agent-browser -p agentcore open https://example.com
Using with AGENT_BROWSER_PROVIDER
Set the provider via environment variable to avoid passing -p agentcore on every command:
export AGENT_BROWSER_PROVIDER=agentcore
export AGENTCORE_REGION=us-east-2
agent-browser open https://example.com
agent-browser snapshot -i
agent-browser click @e1
agent-browser close
Common Issues
"Failed to run aws CLI" means AWS CLI is not installed or not in PATH. Either install it or set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY directly.
"AWS CLI failed: ... Run 'aws sso login'" means SSO credentials have expired. Run aws sso login to refresh them.
Session timeout: The default is 3600 seconds (1 hour). For longer tasks, increase with AGENTCORE_SESSION_TIMEOUT=7200.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
vercel-labs/agent-browser
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
vercel-labs/agent-browser
vercel-sandbox
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.
vercel-labs/agent-browser
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
vercel-labs/agent-browser
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
vercel-labs/agent-browser
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
vercel-labs/skills
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Didn't find tool you were looking for?