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:

1. Environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, optionally AWS_SESSION_TOKEN)
2. 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: