← Back to Dashboard Hub

🌐 Chrome Browser Control

Managed Clawd browser instance for automated web interactions. Full CDP (Chrome DevTools Protocol) control.

Browser Status
Active
Instance PID
21621
Open Tabs
2
CDP Port
18800
🖥️ Browser Instance
Clawd Profile (Isolated)
PID: 21621
Status: Running
Started: 2026-01-28 20:28 MST
Uptime: 1 hour 14 min
Profile Path: ~/.clawdbot/browser/clawd/user-data
Executable: /Applications/Google Chrome.app
Version: 144.0.7559.97
🔧 Chrome DevTools Protocol
CDP Status Ready
HTTP Endpoint http://127.0.0.1:18800
Control URL http://127.0.0.1:18791
CDP Enabled ✓ Yes
Browser Detection ✓ Chrome
📑 Open Tabs
Tab 1: Clio Communications
https://app.clio.com/communications
Opened 2026-01-28 21:42:34 MST
Tab 2: Skool Community
https://app.skool.com/
Opened 2026-01-28 21:42:37 MST
🎯 Current Capabilities
✓ Browser Automation
✓ Tab Management
✓ Advanced Features
⚡ Next Steps
Authentication Required

Browser is spawned and tabs are opened, but authentication is needed for Clio and Skool. You'll need to:

  1. Manually log into Clio and Skool in the controlled browser tabs
  2. Or provide credentials so I can automate the login process

Once authenticated, I can fully automate Clio message checking and Skool content updates.

🔗 Open Clio Login 🔗 Open Skool Login
📊 System Information
Process Information
Chrome Path /Applications/Google Chrome.app
User Data Dir ~/.clawdbot/browser/clawd
Process Manager Moltbot (Browser Service)
Profile Type Isolated (Clawd)
Connection Details
Protocol CDP (DevTools)
Port 18800
Control Server 127.0.0.1:18791
Security Local only
🔍 Multiple Chrome Instances on Your System

You have 3 separate Chrome instances running:

1. Your Main Browser (PID 673)
Started: Tuesday 12:00 PM — Your everyday browser with all your tabs and extensions
2. Controlled Moltbot Browser (PID 21621) ⚡ Active
Started: Today 8:28 PM — Isolated automation instance for Clio, Skool, and web tasks
3. Puppeteer Chrome Testing (PID 13342)
Started: Tuesday 1:00 PM — Development/testing instance (older, may be idle)

I control instance #2 for automation. Your main browser remains completely separate and unaffected.

Last updated: • Dashboard v1.0