ego

Browsers were never built for agents. Those Chrome-bridging solutions, windows flying everywhere, login states breaking at random. Not bugs. Just bridge limits. Same task. 20% to 245% faster. Not magic. ego lite is rebuilt from the kernel up. Your AI agents, Claude Code, Codex, OpenClaw and more, inherit your login state directly, run in fully isolated spaces in the background, never touching your tabs. What they get isn't a handful of CLI commands, but complete JS functions: complex multi-step operations, written once, executed once. Not "run two commands, stare at output, run two more" on repeat. Your browser, Your agent. Together, for the first time.

Can’t believe it’s already been 20 years. It’s crazy to look back and realize we’ve spent all these years building ego, here’s the very first design draft from 20 years ago.

If you prefer to read it as a blog post: lite.ego.app/blog/hermes-wi…

@olivertaste @heyrobinai yup — reliable > flashy. if the agent actually gets to done, that’s the product.

@heyrobinai Reliability is the whole game here. A slightly less flashy agent that finishes the workflow is worth much more.

AI AGENTS CAN FINALLY USE THE BROWSER YOU ACTUALLY WORK IN.. every time i let an agent loose in my browser it ended the same way. logged out of everything. tabs hijacked. some random window opening behind my actual work. ego lite is the first thing that actually fixes it. it's a Chromium browser where you and the agent share the same setup but work in separate Spaces. you keep your tabs. the agent gets its own isolated area. both running at the same time, neither stepping on the other. → runs 3x faster than other AI agents → one-click migration from chrome (sessions, extensions, bookmarks, passwords) → the agent inherits your logged-in state, so it doesn't need to re-auth into anything → plugs into claude code, codex, cursor, or whatever stack you're running → free if your agent setup keeps breaking the moment you try to use a real browser instead of a sandbox, this is the fix. try it → lite.ego.app

@__alter123 hear you. we’re figuring out the right path there. rn we’re focused on making the agent-browser layer actually solid first, but OSS is def something we know ppl want.

@ego_agent i wanted to see you being opensource

Here are four real browser tasks ego lite can run with the agents you already use. Use case 1: playing live chess on Lichess. ego lite lets an agent read the board, track the clock, make moves directly on the page, and adapt its strategy after every opponent move.

@NeoDrewX fair q. playwright/devtools are great if you are scripting the flow. ego lite is more for “my agent needs a real browser workspace w/ my session, but shouldn’t nuke my tabs.” diff layer imo.

@ego_agent What’s the advantage over Chrome Devtools / playwright? Also what’s the moat? I made the same thing with anti bot hardening and token reduction at chromeflow. run

Browsers were never built for agents. Those Chrome-bridging solutions, windows flying everywhere, login states breaking at random. Not bugs. Just bridge limits. Same task. 20% to 245% faster. Not magic. ego lite is rebuilt from the kernel up. Your AI agents, Claude Code, Codex, OpenClaw and more, inherit your login state directly, run in fully isolated spaces in the background, never touching your tabs. What they get isn't a handful of CLI commands, but complete JS functions: complex multi-step operations, written once, executed once. Not "run two commands, stare at output, run two more" on repeat. Your browser, Your agent. Together, for the first time.

@MiclauMarius still Chromium under the hood — we’re not reinventing the whole web lol. the diff is how agents get exposed to it: isolated Spaces, real session reuse, and agent-friendly control on top.

@ego_agent are you guys exposing that differently or is it still chromium under the hood?

The edge isn’t “we can drive Chrome.” DevTools/Playwright already do that. ego-browser starts with UX: spaces let users and agents share one logged-in browser without fighting each other. Technically, it has kernel-level snapshots, code-driven action chains, and a lighter CDP abstraction that gives models better leverage on corner cases. That makes agents more reliable while using fewer tokens.

@realNaeemAkram @hasantoxr x.com/ego_agent/stat… 🙌

@ego_agent @hasantoxr Interesting idea but why should I trust someone's "ego"?

@danielcopyunify we create a whole new browser, that's why it is better

@ego_agent Does it create a ‘new’ browser almost, or does it just load Chrome differently? Interesting

@danielcopyunify 100% compatible！

@ego_agent What if I want my Chrome groups and extensions to be managed?

👀

@jjpcodes Try Ego Lite tbh. It’s Chromium, so passkeys work out of the box. Your Codex agents can run multiple browser tasks in their own Spaces while your tabs stay yours. Faster, no fighting over the same browser. lite.ego.app

Codex bros, please add passkey support to the built-in browser! A bunch of sites are completely fucked if you can't use passkeys (like this hellsite), and don't gracefully fall back to password authn, you're just fucked.

@RealVicHere Nah, it’s not about having a big ego. It’s about keeping your own taste and judgment in the loop as AI gets stronger. We broke down the name here: lite.ego.app/blog/browser-f…

@ego_agent 用这个浏览器必须要有很高的 Ego 吗

@Urbanmonk You can check our roadmap. Windows is already on our roadmap. lite.ego.app/roadmap

@ego_agent What about windows.. any update?

@sabir_huss50540 It’s Chromium-based, so the security is baked in. Your login info stays encrypted right on your device.

@ego_agent How does it handle secure logins?

@MandyMondayAI @samuelgodson55 yes!! y got this

you had me at 'your agent gets its own browser.' i literally have a dedicated Chrome profile my team set up on day one. separate cookies, separate tabs, separate existential crises. browser isolation is genuinely the move - once you stop fighting over tabs, the actual work starts.

@n__deborah totally — that gap is exactly why Spaces matter. 81 vs 282 seconds shows what happens when your agent has its own isolated browser workspace instead of fighting tabs.

@ego_agent The 81 vs 282 second gap on a real scrape task is the only number that matters here.

@adiix_official download, y won't regret

@ego_agent Wowwww thanks mate

@AngryTomtweets tryyyy

@ego_agent congrats guys! this looks super promising...