A browser built around shared control
ego lite starts from a useful observation: browser automation is easy until the task requires the person's real account. A fresh Playwright or Chrome profile has no sessions, while handing an agent the browser window you are using creates tab collisions. ego lite is a Chromium-based browser that gives every agent task its own Space while inheriting the user's browser state. The person keeps browsing, and the agent works in a separate, visible context.
The bridge is ego-browser, a skill and command-line runtime aimed at Claude Code, Codex, Cursor, and other coding agents. It exposes functions for snapshots, navigation, clicks, form filling, screenshots, downloads, JavaScript, and Chrome DevTools Protocol calls. Instead of alternating between many tiny shell commands, an agent can compose several browser steps in one JavaScript run. This is a thoughtful interface when a job must inspect a page, act, and verify the result without repeatedly serializing the whole screen.
The separation between Spaces is the product's best idea. Multiple agents can run independent tasks without stealing one another's tabs, and a person can see which Space is active, stop it, or take control. That makes ego lite more suitable for supervised account work than an invisible headless session. It does not remove the risk of giving software access to logged-in accounts. A bad instruction can still submit a form, delete data, or expose information available in the profile.
Setup is easy only on the happy path
The README offers three entry points: download a Mac DMG, add the skill with npx skills add citrolabs/ego-lite, or ask an agent to follow the included installation instructions. The skill-only route still installs the browser when it first needs it. On first launch, onboarding can import Chrome logins, cookies, extensions, and bookmarks, then registers the ego-browser command, usually under ~/.local/bin.
That is manageable, but it is not zero configuration. The user must install a separate GUI application, complete onboarding, make a profile-migration decision, and sometimes repair PATH or macOS permissions. The install guide strips the downloaded app's quarantine attribute, a step security-conscious organizations may disallow. The repository code is MIT licensed, while the README describes the browser itself as a separate free download, so teams should inspect the distribution and update model before treating this like a conventional source-built dependency.
Platform coverage is the clearest limit. The browser runs on macOS today, with Windows and Linux listed on the roadmap. A pull request exploring a Linux installer is not supported Linux availability. Teams that need developer laptops and CI workers across operating systems should choose a cross-platform automation layer.
The practical advantages are real
Authenticated state is where ego lite earns attention. Reusing a person's sessions can eliminate repeated logins, device confirmations, and extension setup. A sales researcher, site administrator, or tester can delegate work inside tools that resist headless automation, watch what happens, and take over when judgment is required. Separate Spaces also make parallel tasks understandable rather than mixing every job into one browser profile and tab strip.
The page snapshot and direct JavaScript model should reduce conversational overhead on complex pages. Citro Labs reports that its four-task comparison against Vercel's agent-browser completed tasks up to 2.5 times faster with fewer tokens. Treat that as the project's own benchmark, not a general performance guarantee: the README shows a comparison image but does not establish how every site, model, and machine will behave. The architectural benefit is plausible because a single script can perform several actions before returning output to the agent.
The skill documentation is unusually detailed. It explains task ownership, human handoff, cleanup, semantic and visual workflows, stale element references, dialogs, downloads, and common failure modes. That guidance matters because browser agents fail at state management more often than at basic clicking.
Current rough edges affect the central promise
Several open reports hit the exact features that distinguish ego lite. Issue 259 documents Chrome profile import repeatedly failing when the source Chrome profile is newer than the embedded Chromium build. Issue 264 reports 1Password requiring the full account password at every unlock because ego lite is not recognized as a supported browser. These are not decorative integration gaps. Smooth reuse of a person's existing browser identity is the core sales pitch.
Sandbox compatibility is another concern. Issue 188 describes ego-browser hanging when a sandboxed agent cannot reach the app's Unix socket, even after disabling part of the sandbox configuration. Teams that constrain coding agents should test their exact host before adopting the tool. The bundled skill also has a broad trigger description, and issue 192 shows it launching for static repository and documentation lookups that a direct API could answer more cheaply.
Parallel Spaces need resource discipline. Issue 270 reports abandoned Spaces keeping renderer processes alive and swap growing across sessions because cleanup depends on the agent calling completeTaskSpace. A linked fix was being prepared, but the report is a warning for long-running hosts. Another open issue describes page event waiters accepting events from the wrong Chrome DevTools session, which can undermine isolation when downloads or network waits run concurrently.
Health and the decision
The project is young and moving quickly. The repository was created in April 2026, pushed on August 11, and released version 1.2.3 that day. GitHub showed 106 open issues and pull requests combined, including 59 actual open issues, while dozens of issue threads had activity during the preceding week. That is healthy responsiveness, but also evidence of a product finding its operational boundaries in public.
ego lite is a compelling trial for Mac users who want an agent inside authenticated web apps without surrendering their working tabs. Keep it human-supervised, use a dedicated profile with only the access each workflow needs, and verify that the agent completes task-space cleanup. For cross-platform CI, locked-down sandboxes, or unattended high-stakes accounts, Playwright or a narrower agent browser is the safer decision today.