ego (lite) はブラウザそのもの、ego は端末を横断して動くあなた専属のエージェントです。
順番待ちリストに参加する
ego lite vs Codex Chrome 拡張機能

Codex Chrome 拡張機能の最良の代替

OpenAI's Codex Chrome extension lets Codex take over tabs in the signed-in Chrome you're using, one browser shared between you and the agent. ego lite gives Codex its own Spaces in a separate browser that inherited your logins, so it works in parallel while your tabs stay yours.

導入している開発者の所属先
GoogleAmazonShopifyTikTokHarvardStanfordUSCUCLA

ego lite が Codex Chrome 拡張機能より優れている理由

Both exist for the same reason: Codex needs logged-in browser context to be useful on real sites. The extension borrows yours. ego lite imports your Chrome profile once and gives Codex a browser of its own. Run /ego-browser inside Codex and it's connected.

The agent never fights you for your browser again

Because every task gets its own Space (a separate workspace inside one browser), Codex can run several tasks in parallel without ever touching the tabs you're using, and there's no permission prompt each time it opens a new site.

The Codex Chrome extension works differently: it takes over your existing Chrome tabs and acts inside the session you're already using, one task at a time. Because the agent is acting inside your live, logged-in browser, OpenAI has Codex ask for approval before touching each new website, so real tasks pause for permission clicks.

6.48x faster, and it finished the task the extension couldn't

Codex Chrome extension acts one click, one keystroke, one tool call at a time, and on real tasks that adds up: ranking OpenAI's X posts took it 9 minutes 24 seconds. On the Expedia flight-booking task, it never finished at all. A safety review blocked it after 15 minutes.

ego lite reads the page as a compressed Snapshot and batches several actions into a few lines of JavaScript per turn. Same two tasks: 87 seconds, and 166 seconds to completion. That's 6.48x faster on the first, and the only one of the two that finished.

Time to finish the same tasks, shorter is better
Task 1: Rank OpenAI's X posts from the last 7 days
87 sego (lite)
564 sCodex Chrome extension
Task 2: Expedia: search, filter, and fill a flight booking
166 sego (lite)
BlockedCodex Chrome extension, after 900 s

Works with Codex, and with everything else, in parallel

The extension only works with Codex, only in official Chrome (not Arc, Brave, or Edge), and it needs the Codex desktop app running and paired before anything works at all.

ego lite works with any code-writing CLI agent (Codex, Claude Code, Cursor, Gemini CLI) and runs several of their tasks in parallel. Switch agents later, and the browser side stays exactly the same.

Works from Codex's terminal: the plugin doesn't

The Codex Chrome extension only works through the Codex desktop app. OpenAI's own GitHub issues confirm that a terminal-only Codex CLI session can't reach the extension at all. The request fails immediately with the error "Browser is not available: extension."

ego lite works the same whether Codex is running in a terminal or as a desktop app: run /ego-browser, and the agent gets a real browser of its own either way.

ego lite Chrome profile import: the same setup whether Codex runs in a terminal or as a desktop app

ego lite vs Codex Chrome 拡張機能

Feature comparison between ego lite and Codex Chrome extension.
機能ego liteCodex Chrome extension
エージェントが働く場所In its own Space: never the tabs you're usingサインイン済みの Chrome の中で、既存のタブを乗っ取ります
実行中も自分の作業を続けられるかYes: parallel Spaces, you browse in yoursNot really: it's driving the browser you're in
対応エージェントCodex、Claude Code、Cursor、Gemini CLI、コードを書く任意の CLI エージェントCodex のみ
必要なブラウザNone: ego lite is the browser (Chromium, macOS)公式 Chrome のみ。Arc、Brave、Edge は不可
セットアップアプリをインストールし、Codex の中で /ego-browser を実行Codex デスクトップアプリを入れ、その Plugins メニューから拡張機能をインストール
ログイン済みサイト (SSO、2FA)Yes: one-click Chrome profile importYes: it acts in your already-signed-in Chrome
権限モデルプロファイルインポートで一度だけログイン状態を許可。どの Space も見守り・引き継ぎ可能Web サイトごとの承認プロンプト、ドメインの許可リスト/ブロックリスト
Extension reliabilityN/A: no native-messaging pairing between an extension and a desktop appOpenAI's own GitHub issues show a recurring pattern of the extension and desktop app disagreeing on connection state, plus native-host registration and handshake timeouts on Windows
エージェントがページをどう操作するかSnapshot input plus batched JavaScript: several actions per turnあなたのタブの中で 1 ステップずつブラウザ操作
Speed on a real task87s vs Codex's 9:24 on the same X-research task; 166s on the same Expedia flight task9:24 on the X-research task; blocked by a safety review after 15 minutes on the Expedia flight task, never finished
価格無料、サブスクリプションなしIncluded with Codex: requires a ChatGPT plan with Codex access
Works from Codex's terminalYes: /ego-browser works the same in a terminal or a desktop appNo: the CLI can't reach the extension backend at all ("Browser is not available: extension")
最終更新 2026年8月04日

移行をシームレスに

Already running the Codex Chrome extension? You keep Codex and change what it drives. The switch is a few minutes, and nothing has to be uninstalled.

  1. ego (lite) をダウンロード

    Download ego lite and import your Chrome profile in one click. The signed-in context the extension borrows from Chrome becomes real profile state in a browser Codex can call its own.

  2. /ego-browserで最初のタスクを実行

    エージェントに貼り付ける

    /ego-browser Open ego.app and join the waitlist

    Codex の中で /ego-browser を実行します。デスクトップアプリのプラグインも、拡張機能のペアリングも不要です。

  3. 動作を見る
    4つのブラウザタスクを並べて表示する ego lite Space の概要:Claude Code が Yahoo Finance で Apple 株を追跡し、Codex が cars.com で年式ごとに車をフィルタリングし、Hermes が SaaS のバックオフィス業務を仕上げ、ユーザーが X をスクレイピングし、手が + をタップして新しい Space を開いている

    Re-run a task you'd normally hand the extension (a dashboard read, a form workflow, a multi-tab test) and keep using your own browser while it executes in its Space.

拡張機能に組み込まれたワークフローがあるなら、そのまま残して構いません。ego lite は Chrome と並行して動くため、比較している間も何も壊れません。

それぞれのツールを使うべき場面

ego (lite) を選ぶべきケース

  • You run Codex from a terminal, where the extension's backend isn't reachable from CLI sessions at all. Run /ego-browser and the agent gets a browser regardless.
  • You want Codex running longer, multi-step tasks in its own Spaces, in parallel, while your tabs stay yours.
  • タスクの途中で Web サイトごとの承認プロンプトをクリックし続けるより、プロファイルインポートで一度だけログイン状態を許可したい場合。
  • You use other agents too: the same /ego-browser setup works with Claude Code, Cursor, and Gemini CLI, not just Codex.

Codex Chrome 拡張機能を選ぶべきケース

  • You're already running the Codex desktop app, and the extension is right there in its Plugins menu, with no extra install.
  • You want a quick action on a page you already have open: handing Codex your live Chrome session is the shortest path.
  • OpenAI 公式のガードレールに価値を置く場合。すべてのアクションが、Web サイトごとの承認プロンプトとドメイン許可リストに包まれています。

AI エージェントに本物のブラウザを

無料で Mac 上で動作し、ワンクリックで Chrome のプロファイルをインポートできます。Claude Code、Codex、Cursor、コードを書くあらゆる CLI エージェントに対応しています。

Still weighing your options? See how Codex Chrome extension compares with the other tools in the same space.

よくある質問

The Codex Chrome extension is OpenAI's official way to give Codex a browser, launched in May 2026 and installed through the Codex desktop app's Plugins menu. It lets Codex act in your signed-in Chrome for tasks that need logged-in context (reading dashboards, filling forms, testing sites across tabs) with a genuinely careful permission model: Codex asks before touching each new website, and you manage domain allowlists and blocklists. If you're all-in on Codex and official Chrome, it's a polished, well-scoped tool.

はい。OpenAI は 2026年5月に Codex デスクトップアプリのプラグインシステムの一部として公開し、2026年6月には EEA、英国、スイスにも展開しました。ログイン済みコンテキストが必要なタスクを、サイトごとの許可プロンプト付きで、サインイン済みの Chrome の中で Codex に実行させられます。

使用中のブラウザを占有されずに Codex にブラウザ作業をさせたいなら、答えはイエスです。ego lite はインポートしたログイン情報とともに Codex に専用の Spaces を与え、タスクを並行実行し、しかも無料です。OpenAI の承認プロンプトというガードレール付きで、Chrome の中の公式・単一ベンダーの道筋をあえて選びたいなら、拡張機能に軍配が上がります。

Install ego lite, import your Chrome profile, then run /ego-browser inside Codex. The agent reads pages as compressed Snapshots and executes batched JavaScript in the browser. No extension, no MCP server, no plugin configuration.

No. As of mid-2026 it supports official Chrome only. ego lite sidesteps the question: it is its own Chromium-based browser on macOS, and your existing Chrome profile imports into it in one click.

No. It's bound to the Codex desktop app. OpenAI's own GitHub issues confirm a terminal-only Codex CLI session can't acquire the extension backend at all, failing with "Browser is not available: extension." ego lite doesn't make that distinction: install ego lite and run /ego-browser inside Codex, terminal or desktop app, and the agent gets a real browser either way.

You're not alone. OpenAI's own GitHub issue tracker has a recurring thread of reports where the extension and the Codex desktop app disagree on whether they're connected, plus native-host registration and handshake timeouts, mostly on Windows. That's the tradeoff of pairing a browser extension to a separate desktop app over native messaging. ego lite doesn't have that pairing step: it is the browser Codex drives directly.

Yes. They don't conflict: the extension lives in Chrome, ego lite is a separate browser. A common split: the extension for quick actions in a page you already have open, ego lite for longer parallel tasks you don't want running in your active window.