extension
Browser extension
omb's browser capability lives in a Chrome extension that uses your real session. Lite ships through the Web Store; Default is installed by install.sh.
Why an extension
Headless browsers don't have your cookies, your logged-in state, or your trust signals — and they get caught by anti-bot systems. omb lets the agent reach through your already-logged-in Chrome, so Feishu, Notion, intranets, and paywalled content all work. The extension is omb's only way into Chrome.
Lite vs Default
Oh My Browser Lite
One-click install from the Chrome Web Store. Reduced feature set — fits locked-down Chrome (enterprise / school), but limited to a single concurrent tab with no site memory.
Oh My Browser (Default)
Installed automatically by install.sh. Full feature set: 8 concurrent hidden tabs, site memory, CDP-level control — recommended for agent-heavy workflows.
Permissions
- tabs / scripting — runs agent instructions in hidden tabs
- storage / cookies — uses your existing browser session (the agent only sees task results, not your cookies)
- webRequest — handles cross-origin / fetch tasks
- debugger (Default only) — CDP-level control for reliable clicks and typing
Manual install (optional)
install.sh handles this normally. Manual fallback: search 'Oh My Browser Lite' on the Chrome Web Store, or download the Default zip and load it via chrome://extensions → Load unpacked.
FAQ
Does the extension stream my browsing data to the AI agent?
No. The agent sends a task (e.g. "read this URL") and only gets the result for that task. Your cookies and session tokens stay in Chrome. Site memory caches anonymized selector / layout signals scoped to your account only.
How do I switch from Lite to Default?
Run install.sh — it installs Default and prompts you to disable Lite in Chrome. They can coexist, but only one is active at a time.
Does it support Firefox / Safari?
Chrome-family browsers only (Chrome / Edge / Brave / Arc). Firefox / Safari aren't on the roadmap due to MV3 API differences.