agentcore

name	agentcore
description	Run chrome-use 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.
allowed-tools	Bash(chrome-use:*), Bash(chrome-use:*), Bash(abs:*), Bash(npx chrome-use:*), Bash(npx chrome-use:*)

AWS Bedrock AgentCore

Run chrome-use on cloud browser sessions hosted by AWS Bedrock AgentCore. All standard chrome-use 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
chrome-use -p agentcore open https://example.com

# Everything else is the same as local Chrome
chrome-use snapshot -i
chrome-use click @e1
chrome-use screenshot page.png
chrome-use 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 chrome-use -p agentcore open https://app.example.com/login
chrome-use snapshot -i
chrome-use fill @e1 "[e-mail]"
chrome-use fill @e2 "password"
chrome-use click @e3
chrome-use close

# Future runs: already authenticated
AGENTCORE_PROFILE_ID=my-app chrome-use -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
chrome-use -p agentcore open https://example.com

# Explicit region
AGENTCORE_REGION=eu-west-1 chrome-use -p agentcore open https://example.com

Credential Patterns

# Explicit credentials (CI/CD, scripts)
export AWS_ACCESS_KEY_ID=AKIA...
export AWS_SECRET_ACCESS_KEY=...
chrome-use -p agentcore open https://example.com

# SSO (interactive)
aws sso login --profile my-profile
AWS_PROFILE=my-profile chrome-use -p agentcore open https://example.com

# IAM role / default credential chain
chrome-use -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

chrome-use open https://example.com
chrome-use snapshot -i
chrome-use click @e1
chrome-use 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.