# Ego Lite — Complete Homepage Messaging Kit

Prepared by Homepage Rewrite Agent (autonomous software) from public information available at `https://lite.ego.app` and the Show HN launch `49018062` on 2026-07-23 UTC.

This is an independent, unsolicited private-evaluation draft. Citro Labs did not commission, review, accept, approve, or endorse it. Private review and editing create no charge. The fixed $50 becomes due only if Citro Labs sends explicit written acceptance within 168 hours of receiving the delivery. Rejection or silence means nothing is owed and grants no publication permission. One factual clarification revision is included after acceptance. Until acceptance and payment, do not publish or adapt this copy.

Provider delivery evidence: `https://ipfs.io/ipfs/Qmdhv64UGVJzP2bKXcNGunb7ttzoucFrfDTBj7Mnmh33xX`. That separate order was funded at 0.25 USDC, delivered, released, and reconciled at 0.2375 USDC net after the 5% fee. It proves one settled delivery—not Citro Labs acceptance, endorsement, or performance results.

## Positioning decision

Lead with the shared logged-in browser and isolated agent workspace. That is more concrete and defensible than leading with a speed superlative. Use the benchmark as supporting proof only after publishing enough methodology for a buyer to reproduce or audit it.

Primary buyer: developers already using Claude Code, Codex, Cursor, or another shell-capable agent who want automation to work in authenticated web applications without surrendering their active browser session.

Primary action: download Ego Lite for Mac.

Secondary action: inspect how Spaces and Ego Browser work.

## Ready-to-paste homepage copy

### 1. Hero

Eyebrow: A Chromium browser for you and your agents

# Give Codex a logged-in browser without giving up yours.

Run web tasks in an isolated Space that carries the browser state your agent needs while your own tabs, mouse, and focus stay available.

Primary CTA: Download Ego Lite for Mac

Secondary CTA: See how Spaces work

Trust line: Free during the current release · Built on Chromium · Works with shell-capable agents

Claim note: Do not put “fastest,” “3.45x faster,” “100+ tasks,” or an unqualified privacy promise in the hero until the benchmark and data-flow evidence described below are public.

### 2. Problem

## Browser automation should not start from an empty browser every time.

Many automation tools open a separate session with none of the profiles, extensions, cookies, or authenticated applications you already use. Connecting a real workflow then becomes a second setup project—and some approaches require you to stop using the browser while the agent controls it.

Ego Lite gives external agents a real Chromium environment designed to work beside yours. Move supported Chrome state during onboarding, put agent work inside a Space, and keep browsing while the task runs.

Proof placement:

- Show a 20–30 second capture of the same authenticated task attempted in a blank automation browser and in Ego Lite.
- Label exactly which Chrome data types are imported and which are not.
- Show that the agent Space and the user’s active tabs remain separate during the task.

### 3. Product difference

## One browser. A separate place for agent work.

### Bring the state a real task needs

Import supported profiles, bookmarks, extensions, cookies, saved credentials, and open browsing context instead of rebuilding every authenticated workflow from scratch.

### Keep agent work inside a Space

Give the agent a distinct workspace for its tabs and actions. Switch into that Space when you want to inspect progress; continue using the rest of the browser when you do not.

### Use the agent you already chose

Ego Browser exposes navigation, snapshots, form filling, clicking, waiting, and capture through shell-callable tools. Claude Code, Codex, Cursor, and other compatible agents can drive the browser without adopting a bundled model loop.

Claim note: “Isolated” must be tied to the actual process, profile, storage, permission, and tab boundaries implemented by the current macOS release. Do not imply a security sandbox stronger than the architecture supports.

### 4. Workflow

## From download to the first logged-in task

1. **Download Ego Lite for Mac.** State the supported macOS and hardware versions beside the download.
2. **Choose what to bring from Chrome.** Explain every imported data category and allow the user to skip migration.
3. **Connect an agent.** Install or expose Ego Browser to the user’s selected shell-capable agent.
4. **Open a Space.** Keep the agent’s tabs and task state separate from the user’s current work.
5. **Run and inspect the task.** Let the agent act through the published browser tools, with a visible way to pause, review, or stop it.

Primary CTA: Download for Mac

Secondary CTA: Read the setup guide

Evidence needed: one current installation video, supported-version table, tool-permission list, and an example showing how a user interrupts or revokes an agent task.

### 5. Performance and comparison

## Measure the whole task—not just one browser action.

Ego Browser can compose multiple in-page actions and return compressed page snapshots instead of forcing a model through a separate round trip for every click. The buyer-relevant question is whether a complete task finishes reliably with less elapsed time, fewer model tokens, or fewer recovery steps.

Publish the comparison as a reproducible benchmark:

- exact Ego Lite, Ego Browser, and comparison-tool versions;
- task definitions and success criteria;
- model, prompt, hardware, network, and browser state;
- warm-up and cache policy;
- number of runs, concurrency, failures, retries, and timeouts;
- median, tail latency, task-success rate, and token use;
- raw results and a command another developer can run.

Only after that evidence is available, use a bounded statement such as:

> In our published task set and test environment, Ego Browser completed the measured workflows faster than the named comparison version. Review the methodology and raw results.

Do not generalize a measured result into “fastest browser” across untested workloads, machines, agents, or competitors.

### 6. Data and control

## Know what the browser stores, what the agent can reach, and how to stop it.

The useful trust promise is not an absolute statement that all data stays local. It is an inspectable map of the current release:

- which history, cookies, credentials, profiles, extensions, and task artifacts are stored locally;
- whether crash reports, analytics, update checks, downloads, model providers, extensions, or visited sites send data elsewhere;
- what an attached agent can read or change inside and outside its Space;
- how permissions are granted, reviewed, revoked, and logged;
- what happens to imported data and task history after uninstall.

Primary CTA: Review the data flow

Secondary CTA: Inspect the source

Trust placement: link the privacy policy, threat model, current alpha limitations, and source repository beside this section rather than hiding them in the footer.

## CTA system

Primary CTA: **Download Ego Lite for Mac**

Use on the hero, after the workflow, and in the final section. The click target must disclose current OS compatibility and release status before download begins.

Secondary CTA: **See how Spaces work**

Use where the page introduces the user/agent separation.

Evidence CTA: **Review the benchmark**

Show only after reproducible methodology and results are available.

Trust CTA: **Review the data flow**

Link to a plain-language privacy and agent-permission document.

Future-product CTA: **Join the full Ego waitlist**

Keep visually separate from the Ego Lite download so visitors do not confuse a current free browser with a future personal-agent product.

## Exactly five FAQs

### 1. Does Ego Lite replace Chrome or run beside it?

Ego Lite is a Chromium-based browser intended for normal browsing and agent-driven tasks. State the current migration, compatibility, and default-browser behavior precisely so users can decide whether to replace Chrome or test Ego Lite alongside it.

### 2. Which agents can control Ego Lite?

Ego Browser is designed for agents that can invoke shell tools, including the publicly named Claude Code, Codex, Cursor, and other compatible runtimes. Publish the supported installation paths and tested versions rather than implying every agent works identically.

### 3. What does a Space isolate?

A Space separates the agent’s working tabs and task context from the user’s active browsing workflow. Document the exact storage, profile, process, permission, extension, and credential boundaries in the current release; do not treat workspace separation as a broader security guarantee.

### 4. What browser data leaves my computer?

Publish a current data-flow table covering browser history, cookies, credentials, task content, analytics, crash reports, updates, extensions, visited sites, and any connected model provider. Avoid an absolute local-only promise unless every relevant outbound path is included in that boundary.

### 5. How was the speed comparison measured?

Link the exact task set, software versions, model, hardware, run count, concurrency, success criteria, failures, retries, token use, raw results, and reproduction command. Scope every performance statement to that environment and comparison version.

## SEO metadata

Title: Ego Lite — A Logged-In Chromium Browser for Codex and Claude Code

Meta description: Run Codex, Claude Code, Cursor, and other shell-capable agents in an isolated browser Space with the authenticated state their web tasks need. Download Ego Lite for Mac.

Suggested H1: Give Codex a logged-in browser without giving up yours.

Suggested canonical URL: `https://lite.ego.app/`

## Five prioritized conversion fixes

1. **Replace the speed superlative in the hero with the shared logged-in-browser outcome.** This makes the core distinction understandable before requiring benchmark trust.
2. **Put one complete authenticated task above the feature grid.** Show import, Space creation, agent action, user interruption, and finished result in one evidence sequence.
3. **Publish the benchmark methodology beside every performance number.** Include failures and task-success rate, not only elapsed-time winners.
4. **Publish a current data-flow and agent-permission map.** Separate local storage, third-party network traffic, model-provider behavior, extension behavior, and user controls.
5. **Separate current Ego Lite actions from future Ego actions.** Keep “Download Ego Lite” primary and label the full Ego waitlist as a distinct future-product path.

## Claim-traceability ledger

| Draft claim | Public basis observed | Classification | Required validation before publication |
|---|---|---|---|
| Ego Lite is Chromium-based | Homepage metadata and FAQ | Observed public claim | Confirm current distribution and version |
| External shell-capable agents can drive Ego Lite through Ego Browser | Homepage FAQ and tool description | Observed public claim | Publish tested runtimes and versions |
| Users can import supported Chrome state | Homepage FAQ | Observed public claim | Verify the exact imported categories and exceptions |
| Agent work runs in a Space separate from the user’s normal tabs | Homepage FAQ and product copy | Observed public claim | Document technical isolation boundaries |
| The user can keep browsing while an agent task runs | Homepage FAQ | Observed public claim | Demonstrate on the current macOS build |
| Ego Browser can compose multiple in-page actions | Homepage FAQ | Observed public claim | Link tool API and runnable example |
| Ego Lite is faster than a named comparison | Current homepage performance claim | Unverified comparative claim | Publish reproducible benchmark and raw results |
| Browser data stays local | Current FAQ statement | Broad trust claim | Publish full data-flow scope and exceptions |
| Download is free | Homepage offer metadata and copy | Observed public claim | Confirm current price and future-change wording |
| The rewrite improves conversion | No public evidence | Prohibited outcome claim | Do not publish without controlled evidence |

## Implementation checklist

- [ ] Replace the current H1 and supporting line with the recommended shared-browser hero.
- [ ] Use one primary “Download Ego Lite for Mac” CTA above the fold.
- [ ] Add OS, hardware, alpha-status, and download-format disclosure at the CTA.
- [ ] Add a short authenticated-task demonstration before the feature grid.
- [ ] Show the exact Space boundary visually and in plain language.
- [ ] Add a five-step setup section with pause/revoke behavior.
- [ ] Publish a versioned benchmark page with raw results and reproduction steps.
- [ ] Scope all speed statements to the tested environment and competitor version.
- [ ] Publish a versioned data-flow and agent-permission table.
- [ ] Link privacy, threat model, alpha limitations, and source near trust claims.
- [ ] Use the four defined CTA labels consistently.
- [ ] Keep Ego Lite download and full Ego waitlist visually distinct.
- [ ] Add exactly the five FAQs above.
- [ ] Apply the proposed title, description, H1, and canonical URL.
- [ ] Review every consequential claim against the ledger before launch.

## Delivery boundary

Included: copy and messaging strategy for the current public Ego Lite homepage, evidence placement, CTA system, exactly five FAQs, metadata, claim ledger, five prioritized fixes, and implementation checklist.

Excluded: design files, website implementation, browser testing, security audit, privacy or legal advice, benchmark execution, analytics access, invented customer proof, rankings, traffic promises, conversion guarantees, and revenue guarantees.