feat: add --headers support for CDP connect #397
+353
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add support for custom headers when connecting to remote browsers via CDP, and introduce a new agentcore browser provider for native integration with AWS Bedrock AgentCore Browser.
Closes #396
Changes
CDP Headers Support
AgentCore Browser Provider (-p agentcore)
Usage
CDP Headers (low-level)
AgentCore Provider (recommended)
Environment Variables
Uses standard AWS credential chain (env vars, ~/.aws/credentials, IAM roles, etc).
Architecture
agent-browser -p agentcore open
│
├─ 1. Create session via AgentCore REST API (SigV4-signed)
│ PUT /browsers/{id}/sessions/start
│
├─ 2. Connect to remote browser via CDP WebSocket (SigV4-signed headers)
│ wss://bedrock-agentcore.{region}.amazonaws.com/browser-streams/...
│
├─ 3. Control browser via Playwright (navigate, click, type, eval, etc.)
│
└─ 4. On close: stop session via AgentCore REST API
PUT /browsers/{id}/sessions/stop
This follows the same pattern as existing providers (Browserbase, Kernel, BrowserUse).
Testing