ego lite Gives Your Coding Agent Its Own Browser Spaces

Browser automation usually means handing your browser over to an agent. The ego lite README names the failure mode of bridge-style tools like browser-use and agent-browser: they drive a separate browser, your logins rarely carry over intact, and you and the agent end up fighting for control. This 16k-star project takes a different shape — one browser designed from the start for you and your agents to share.

Why This Skill Matters

ego lite gives every agent its own Space: an isolated workspace inside the same browser where the agent runs its task while you keep browsing in yours. The README's example scale: Claude Code enriching 10 leads in 10 parallel Spaces while Codex scrapes 5 competitor sites in 5 more — no collided tabs, and your mouse stays where you left it.

The connection layer is ego-browser, a skill that exposes the browser to any agent CLI (the README names Claude Code, Codex, Cursor, or a custom one) as in-page JavaScript tools: snapshot, fill, click, wait, navigate, capture. Because the agent writes code instead of chaining CLI calls, the README argues complex workflows finish faster with fewer tool calls — its benchmark against Vercel's agent-browser on four complex tasks reports up to 2.5x faster completion with substantially fewer tokens. Snapshots, the structured text a text-only model reads to act on a page, are produced inside a customized browser engine; the README claims they reliably handle deeply nested iframes, a common breaking point for other approaches.

Installation

Pick whichever fits your flow. Downloading the macOS app is the full setup — ego lite adds the ego-browser skill to every agent's skills directory on your machine:

# Or install just the skill; the app install happens on first browser task
npx skills add citrolabs/ego-lite

You can also let your agent do it. Paste this into your agent CLI:

Set up ego lite for me: https://github.com/citrolabs/ego-lite

Read `skills/ego-browser/references/install.md` and follow the steps to install ego lite.

ego lite runs on macOS today; the README says a Windows closed beta is coming soon and Linux is on the roadmap. On first launch it asks one question — whether to migrate your Chrome data. Say yes and your agent inherits your existing logins, cookies, extensions, and bookmarks.

Real Workflow: Delegate a Browser Task Without Losing Your Tabs

1. In your agent CLI, type /ego-browser followed by a space, then describe the task in plain language:

ego-browser follow @ego_agent on x.com for me

2. The agent picks up the ego-browser skill, opens the page in its own Space, reads a Snapshot of the page, acts on it, and reports back — while your own tabs stay untouched.

3. Watch the run from the ego lite window. You can see which Space has an agent running at any moment, and take it over or stop it whenever you want.

Real Workflow: Fan Out Across Parallel Spaces

Give several agents browser work at once and each gets its own Space. A research sweep fits naturally:

Check the pricing pages of these five competitors and extract plan names,
monthly prices, and the top three differentiators on each page.

Each agent works in its own isolated workspace, so five sites get scraped in five Spaces simultaneously without stealing your tabs or each other's.

Tips

• Browsing data, cookies, and everything else the browser holds stay on your device; the README describes the data collection as deliberately narrow, down to simple product signals.
• The ego-browser toolset is snapshot, fill, click, wait, navigate, and capture — the agent composes them as JavaScript in one pass instead of a call-wait-call loop.
• Experience accumulation, which distills successful actions into reusable workflows, is marked "coming soon" in the README — do not plan around it yet.
• The repo contents are MIT licensed; the ego lite browser itself is a separate, free download.

When Not to Use This

If you are on Windows or Linux today, the macOS-only release is a blocker. If you need the agent's browsing to be fully separate from your own identity, note the tradeoff runs the other way here: the design goal is that the agent can reach your real logins and tabs through ego-browser. And if you already have a bridge-based pipeline you like, the README's own comparison table is a vendor claims table — run your own benchmark before switching.

See the leaderboard for more skills.