If the download doesn't start automatically, you can
ego (lite) is a Chromium-based browser for daily use. Easily import your data and use it daily.
:How can I help today?
/ego-browser Discover Today's Interesting Wikipedia Articles
Finish onboarding, type /ego-browser, and tell your agent what you need. It will run tasks in its own Space.
Both. ego (lite) runs natively on Intel Macs and on Apple Silicon (M1, M2, M3, M4).
You don't need to figure out which chip you have. When you click download, our landing page detects your Mac automatically and serves the right build — Intel or Apple Silicon, so the file you get just works.
If the auto-detection picks the wrong one (rare, but it happens with some browsers, VPNs, or shared machines), the landing page also shows both versions side by side. Pick the other one manually and download again. The wrong .dmg can be moved to Trash — it won't have installed anything.
Not sure which chip your Mac has? Click the Apple logo (top-left) → About This Mac → look for "Chip." Anything starting with "Apple M" is Apple Silicon. Anything that says "Intel" is Intel.
Not yet. ego (lite) runs on macOS today, on both Intel and Apple Silicon. Windows and Linux are on the roadmap, with no firm release date yet.
No. ego (lite) is completely free, and you don't need to sign in or create an account. Download, install, and your agent can drive the browser right away.
Because the whole point of ego (lite) is letting your agent work inside your real browser, not a blank sandbox. Without your Chrome data, ego (lite) collapses into another generic agent browser.
When you choose to migrate during onboarding, ego (lite) copies over:
Once that's in place, your agent can use the Gmail, Notion, LinkedIn, internal tools, banking dashboards, and SaaS admin panels you're already logged into, instead of trying to log in from scratch on every site (which usually breaks on 2FA, SSO, or captchas).
If you skip the migration, ego (lite) still runs, but your agent has to log in to every site itself. That's the exact limitation tools like Browser Use and Vercel's agent-browser have, and it's the main reason people pick ego (lite) over them.
No. ego (lite) copies your Chrome data, it doesn't move it. Your Chrome stays exactly as it was, and you can keep using both browsers in parallel.
After migration, the two browsers don't sync. New logins or extensions you add in Chrome won't appear in ego (lite), and vice versa.
Yes. Open ego (lite) → Settings → Import data, and run the migration again any time.
No extra setup. Installing ego (lite) also installs ego-browser and ego skills, and writes them into your existing agent CLI's skill directory automatically.
If you install via .dmg, onboarding scans your Mac for installed agent CLIs (Claude Code, Codex, Cursor, Continue, Gemini CLI, and others) and wires ego-browser into each one. Open your agent afterward and you can drive the browser right away: ego-browser exposes the browser as a set of in-page JavaScript tools — snapshot, fill, click, wait, navigate, capture — that your agent calls from a JavaScript snippet, composing several steps into a single page-side run.
If you prefer the terminal, run the curl command instead.
No. ego-browser exposes the browser as a set of in-page JavaScript tools — snapshot, fill, click, wait, navigate, capture — that your agent calls from JavaScript snippets, and talks to ego (lite) over CDP (Chrome DevTools Protocol) directly. It doesn't depend on Playwright or Puppeteer and doesn't share their runtime, so it won't collide with browser automation tools you already have installed.
You can keep using your existing stack for headless or cloud workflows, and use ego (lite) for the tasks that need your real logins, your real extensions, and a browser you actually live in.
ego (lite) auto-updates on macOS. New versions download in the background and apply the next time you launch the app — no manual reinstall needed.
ego (lite) is in beta. If something feels off, please tell us, we’re still ironing out the rough edges.