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
With your agent
Install OMGSkills skill "vercel-labs/agent-browser:agentcore" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/vercel-labs/agent-browser /tmp/agent-browser && ln -s /tmp/agent-browser/skill-data/agentcore ~/.claude/skills/agentcoreFrom README
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. Credentials are resolved automatically: Environment variables (AWSACCESSKEYID, AWSSECRETACCESSKEY, optionally AWSSESSIONTOKEN) AWS CLI fallback (aws configure export-credentials), which supports SSO, IAM roles, and named profiles No additional is needed if the user already has working AWS credentials.