How It Works
Instead of starting a browser in Notte’s cloud, you can:- Create a browser session with an external provider
- Get the CDP WebSocket URL from that provider
- Pass the CDP URL to Notte when creating a session
- Use Notte’s features on the external browser
Kernel.sh Integration
Kernel.sh is a browser infrastructure platform optimized for AI agents. Here’s how to use it with Notte:BrowserBase Integration
BrowserBase provides managed browser infrastructure. Connect it to Notte:Benefits of External Providers
When to Use External Providers
Use external browser providers when you need:- Specialized Infrastructure: Provider-specific optimizations or features
- Existing Setup: You already use a browser provider and want to add Notte’s features
- Compliance: Browsers must run in specific regions or under specific conditions
- Custom Configuration: Complex browser setups or extensions
- Cost Optimization: Leverage existing browser infrastructure contracts
When to Use Notte’s Browsers
Use Notte’s built-in browsers when you want:- Simplicity: One-line session creation without managing external services
- Built-in Features: Anti-detection, captcha solving, proxies included
- Integrated Management: Session replay, cookie management, file storage
- Fast Setup: No additional configuration or API keys needed
What Notte Adds to External Browsers
When you connect Notte to an external browser, you get:AI Agents
Use Notte’s Agent to automate complex tasks with natural language
Smart Actions
Execute high-level actions with automatic element detection
Structured Scraping
Extract data into structured formats with AI-powered scraping
Observation API
Get AI-powered page understanding and element analysis
Complete Example: Multi-Provider Setup
Run the same automation across different providers:Supported CDP Features
When using external browsers, Notte supports: ✅ Supported:- Page navigation and interaction via Playwright
- Agent-based automation
- Structured scraping with
scrape() - Action execution with
execute() - Page observation with
observe() - Screenshot capture
- JavaScript execution
- Cookie management
- Session replay recording
- Live viewer
- Notte’s built-in anti-detection (use provider’s features instead)
- Notte’s captcha solving (use provider’s features instead)
- Notte’s proxy management (use provider’s proxies)
Troubleshooting
CDP Connection Failures
If connection fails, verify:- URL Format: Ensure the CDP URL is correct (
ws://orwss://prefix) - Network Access: Check firewalls and network policies
- Browser Availability: Verify the browser is running and accessible
- Timeout: Increase session timeout for slow connections
Browser State Issues
When using external browsers:- Start Fresh: Create new browser instances for each session
- Clean State: Clear cookies and cache between runs
- Session Cleanup: Always close/delete external browser sessions
- Resource Limits: Monitor memory and CPU usage
Authentication
Some providers require authentication in the CDP URL:Provider Comparison
| Feature | Notte Built-in | Kernel.sh + Notte | BrowserBase + Notte |
|---|---|---|---|
| Setup Complexity | Simple | Simple | Medium |
| Anti-detection | ✅ Built-in | ✅ Built-in | ✅ Built-in |
| Captcha Solving | ✅ Optional | ❌ | ❌ |
| Residential Proxies | ✅ Optional | ✅ | ✅ |
| Session Replay | ✅ Yes | ✅ Via Notte | ✅ Via Notte |
| Live Viewer | ✅ Yes | ✅ Yes | ✅ Yes |
| Pricing | Per session | Per session | Per session |
Best Practices
1. Clean Up Resources
Always clean up external browser sessions:2. Handle Errors Gracefully
CDP connections can fail. Always use try-except:3. Choose the Right Provider
- High Volume: Use managed providers (Kernel, BrowserBase)
- Simplicity: Use Notte’s built-in browsers
- Existing Infrastructure: Connect to your current provider setup

