Agentcore

This runs agent-browser sessions on AWS Bedrock AgentCore instead of your local Chrome. The API is identical, you just add a `-p agentcore` flag and it spins up a cloud browser backed by AWS infrastructure. Credentials resolve automatically from your existing AWS setup (environment variables, CLI profiles, SSO). The killer feature is persistent profiles: set `AGENTCORE_PROFILE_ID` and your login sessions survive across runs, which is huge for authenticated workflows. You also get a Live View URL to watch sessions in the AWS Console. Default timeout is one hour but you can extend it. Honestly most useful when you need browser automation in CI/CD or want to avoid local Chrome dependencies.

skills.sh installs: 2.8K
GitHub stars: 29.3K

View on GitHub

Install

$ npx -y skills add vercel-labs/agent-browser --skill agentcore --agent claude-code

Installs into .claude/skills of the current project.

Files

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, optionally AWS_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