# ego (lite) — Full Documentation

> Always free, no set up. Claude Code or Codex runs 100+ browser automation tasks at the same time. The fastest agent browser in our open Real-World Bench.

## Company

ego (lite) is built by Citro Labs. Repository: https://github.com/citrolabs/ego-lite (MIT). Contact via repo issues or @ego_agent on X.

Authors: Aute (Founder & CEO, https://lite.ego.app/team/aute); Brax (Growth, https://lite.ego.app/team/brax); Luz (Founding Engineer, https://lite.ego.app/team/luz).

## Product Overview

ego (lite) is a Chromium browser built for you and your AI agent to work together, making browser automation faster and cheaper, every run.

Existing tools like Browser Use and Vercel's agent-browser are browser automation frameworks. They need a separate browser to drive, logins never carry cleanly, and you and the agent end up fighting for the same tabs. ChatGPT Atlas and Perplexity Comet take the opposite approach: AI-first browsers that ship with their own built-in assistant, which locks you into that one agent.

ego (lite) is one browser designed from the start for you and your AI agent to share — no extra setup, and the agent can always reach your real logins and tabs through ego-browser.

### What Makes ego (lite) Different

1. **Run faster, cost fewer tokens** — Complex browser automation tasks complete faster and on fewer tokens overall (the saving is on the whole task, not per step). Several features stack to make that happen. Each page reaches the agent as a Snapshot, an accessibility tree with stable @N refs, instead of raw HTML. The agent can also run several actions in the page with a few lines of JavaScript, instead of calling one tool at a time and waiting for each result before deciding the next, the way Playwright, Puppeteer, and most browser automation frameworks work.

2. **Spaces** — Workspaces you and your agent can use independently inside the same browser. Group your tabs by project; the agent runs background tasks in a separate Space without stealing focus or touching your active tabs.

3. **Same Chrome, agent-native** — Built on Chromium, imports your Chrome profile in one click (tabs, bookmarks, passwords, extensions, cookies, login sessions, profiles). Use it as your default browser. Your AI agent inherits the same logged-in state, so it doesn't get stuck on captchas, 2FA, or SSO redirects.

4. **ego-browser, open source** — Shell-level entry point for any agent that writes code: ego, Claude Code, Codex, Cursor, Continue, Gemini CLI, Hermes Agent, OpenClaw, OpenCode, or any custom in-house agent. No SDK, no credentials, no platform-specific adapters to maintain.

## Key Capabilities

### Snapshot — Compressed Semantic Input
Instead of feeding the LLM raw HTML (often 10k+ tokens of layout noise), ego (lite) emits an accessibility tree snapshot:
- Stable element refs (@e1, @e2, …) survive minor DOM changes
- Only interactive / labeled elements included
- Typical page snapshot is dramatically smaller than the equivalent HTML
- Works on JS-rendered, login-gated, or interactive content where `fetch` returns shells

The snapshot is built inside our custom Chromium engine, not as a JavaScript shim on stock Chrome, so it reaches into cross-origin iframes, shadow DOM, and third-party SDK widgets (Stripe checkouts, Salesforce embeds, intercom panels, dynamically mounted React portals) that JS-based snapshotters silently drop.

### Multi-action JavaScript
The agent can run several actions in the page with a few lines of JavaScript, instead of calling one tool at a time and waiting for each result before deciding the next. This is the largest contributor to ego (lite) finishing complex browser automation tasks faster and on fewer tokens overall, relative to Playwright, Puppeteer, or other automation frameworks that round-trip a single tool call per action.

### Space — Isolated Workspace
A Space is a workspace partition inside the same browser process. You have your Space (active tabs, projects). The AI agent has its own Spaces (running tasks). Tabs in agent Spaces don't steal focus, don't push notifications into your view, and can be created or destroyed by the agent without affecting your daily browsing. You can run multiple Spaces in parallel — Claude Code in one, Codex in another, you in your own tabs in a third.

### Open ego-browser Runtime
`ego-browser` is the shell-level entry: `ego-browser open`, `ego-browser click @e3`, `ego-browser snapshot`, etc. Any agent that can spawn a child process can drive the browser. Plugs in as a skill into Claude Code, Codex, Cursor, Continue, Gemini CLI, Hermes Agent, OpenClaw, OpenCode, or your custom agent. No SDK to integrate, and you're not locked into a specific model.

## Use Cases

### Free Amazon Price Scraper With Your AI Agent

For authorized Amazon price research, ego (lite) gives Codex, Claude Code, and compatible AI agents a visible browser workflow. The Agent opens selected product or search URLs in separate Spaces and creates a source-linked CSV or Markdown report with displayed prices, sellers, variants, availability, source URLs, and check times. When evaluating a GitHub Amazon scraper, treat the repository as code to inspect and maintain—not as permission to collect data—and compare its runtime, dependency, credential, and API trade-offs with this visible browser route. Page: https://lite.ego.app/solutions/amazon-price-scraper.

For social media lead research, ego (lite) lets an Agent inspect a bounded list of public or authorized social pages and return displayed names, roles, companies, profile URLs, and public contact links with source URLs, checked-at times, evidence, and access status. It does not infer identities, find hidden emails, query purchased enrichment data, read private content, or bypass platform restrictions. Page: https://lite.ego.app/solutions/social-media-scraper.


- **Engineer — E2E testing after a code change** — Reuses the staging cookie already in your browser. The agent runs the full flow in a Space, logs in as the test user, walks every step, and captures screenshots, console errors, and network requests, while you keep coding in Cursor.
- **Marketer — daily competitor pulse** — Same browser already signed into Instagram, LinkedIn, and Facebook. The agent opens parallel tabs across competitors and channels, captures 24h posts and engagement, and writes a daily markdown brief to disk.
- **Sales AE — morning battle card** — Reuses your active LinkedIn, Crunchbase, X, and HubSpot logins. The agent enriches today's inbound leads and rechecks stale prospects in parallel Spaces.
- **PM — daily product pulse** — Already signed into Discord, App Store, Reddit, and your team tools. The agent runs source checks in parallel Spaces (competitor changelogs, X, Product Hunt, Hacker News, your App Store reviews) and writes the daily pulse markdown to your Notion mirror.
- **Job seeker — daily roles and company intel** — Reuses existing logins and saved searches on LinkedIn Jobs, YC Work at a Startup, Wellfound, Levels.fyi, and Glassdoor. The agent scrapes new roles, enriches each with funding round and Glassdoor score, then appends to your tracker.

## Roadmap

Roadmap page: https://lite.ego.app/roadmap. It tracks the current beta priorities, active feature work, and the request flow. The public roadmap can be backed by a Tally embed through `NEXT_PUBLIC_TALLY_ROADMAP_URL`, with feature requests optionally routed through `NEXT_PUBLIC_TALLY_REQUEST_URL`.

## Comparison

| Feature | ego (lite) | Browser Use | agent-browser | ChatGPT Atlas | Perplexity Comet |
|---|---|---|---|---|---|
| Inherits Chrome data | ✓ | — | — | — | — |
| Same browser, separate workspace | ✓ | — | — | — | — |
| Compressed semantic input | ✓ | — | ✓ | — | — |
| Controllable by external agents | ✓ | ✓ | ✓ | — | — |
| Data stored locally | ✓ | ✓ | ✓ | — | — |
| No login friction | ✓ | — | — | ✓ | ✓ |
| Daily-use browser | ✓ | — | — | ✓ | ✓ |
| Free, no subscription | ✓ | ✓ | ✓ | — | — |

## Privacy

- Profile data, cookies, and migrated browser state live on your local disk
- ego (lite) does not upload your browsing data; the only thing it records during setup is whether you opted into Chrome data migration
- The AI agent runs queries through whichever LLM you configure (Claude, OpenAI, …); Citro Labs does not proxy or log those calls
- No third-party advertising, no data sold or used for model training

## FAQ

### What is ego (lite)?

ego (lite) is the agent browser built to share with your AI agents, like Codex or Claude Code. Zero cost, zero config. Let them handle any web automation effortlessly.

Existing tools like Browser Use and agent-browser are browser automation frameworks. They need a separate browser to drive, logins never carry cleanly, and you and the agent end up fighting for the same tabs.

ego (lite) is one browser designed from the start for the two of you to share — no extra setup, and the agent can always reach your real logins and tabs through ego-browser.

### What is an agent browser?

An agent browser is a browser built to be driven by an AI agent instead of only a human. The agent gets a real window, tabs, and (ideally) your logins, rather than a headless instance it has to configure from scratch.

ego (lite) is that agent browser: the same Chromium you use every day, with a Space where Claude Code, Codex, or Cursor can click, fill, and read pages on their own. Compare that to a browser automation framework like Browser Use or Puppeteer, which drives a separate, blank browser instead of the one you're already logged into.

### How is ego (lite) different from Playwright or Puppeteer?

Playwright and Puppeteer are browser automation libraries you embed in code. They drive pages through CSS selectors, which break whenever a site reshuffles its DOM.

ego (lite) is a real browser plus ego-browser. ego-browser is the connection layer between any agent product (Claude Code, Codex, Cursor, or your own) and ego (lite) — it exposes the browser as a set of in-page JavaScript tools: snapshot, fill, click, wait, navigate, capture. The agent writes a JavaScript snippet that composes several steps using those tools, and ego-browser runs it on the page in one pass, instead of the one-tool-at-a-time round trips Playwright and Puppeteer require. The snapshots cost fewer tokens than HTML, and the @N refs stay stable when class names rotate. There's no SDK to integrate, and nothing to install from the Playwright or Puppeteer ecosystem.

### How is ego (lite) different from Browser Use or Vercel's agent-browser?

ego (lite) is a real browser plus ego-browser. Whichever agent you use, whether that's ego, Claude Code, Codex, Cursor, or something else, drives the same browser you use daily. Space keeps the agent's work isolated from yours.

Browser Use is an autonomous agent framework. It bundles its own LLM loop and drives a separate browser instance. You can point it at a real Chrome, but only after you fully close it. Extensions don't load by default. And it has its own pricing tier on top of whatever you already pay for.

Vercel's agent-browser is a CLI that lets your agent control a browser through shell commands, but it ships no browser of its own. The agent doesn't share your daily browser session, so your real logins aren't available to the running task.

### Does ego (lite) work with Claude Code, Codex, and Cursor?

Yes. Any agent that can run a shell command can drive ego (lite) through ego-browser:
• ego, Claude Code, Codex, Cursor, Continue, Gemini CLI
• Hermes Agent, OpenClaw, OpenCode
• Any custom in-house agent you've built

ego-browser installs as a skill into your agent's skill directory during onboarding. The agent then calls browser automation commands the same way it runs any other shell tool. There's no SDK to integrate, and you're not locked into a specific model.

### Can ego (lite) replace Chrome as my main browser?

Yes. ego (lite) is built on Chromium, so the address bar, tab groups, bookmarks, profiles, extensions, downloads, and incognito mode behave the way they do in Chrome. The difference is Space: an isolated workspace where your AI agent runs web automation alongside you, and doesn't touch your tabs unless you let it.

### Can I bring my Chrome bookmarks, passwords, and extensions into ego (lite)?

Yes. ego (lite)'s onboarding migrates the following from Chrome in one click:
• Tabs and tab groups you're using
• Bookmarks and saved passwords
• Browser extensions
• Cookies and login sessions
• Browser profiles

Every site you've already signed into stays signed in, and the agent inherits the same logged-in state. It doesn't need to re-authenticate to Gmail, Notion, LinkedIn, or your internal tools every time it runs a task.

### Can I keep using my browser while the agent runs tasks?

Yes. The agent runs inside Space, an isolated workspace in ego (lite). It works in its own area, so your tabs stay untouched unless you explicitly hand one over. It doesn't take over your mouse or steal focus from whatever you're doing. Switch into Space anytime to watch the agent work, or ignore it and keep working in your own window.

### How does ego (lite) reduce token usage for browser automation?

What gets cheaper is the whole task, not any single step. The savings come from several features stacking together.

The agent can run several actions in the page with a few lines of JavaScript, instead of calling one tool at a time and waiting for each result before deciding the next, the way Playwright, Puppeteer, and most browser automation frameworks work.

Combined, complex browser automation tasks complete faster and on fewer tokens overall.

### Is my data safe when an AI agent uses ego (lite)?

Yes. ego (lite) doesn't upload your browsing data. Your history, cookies, login sessions, and anything the agent reads stay on your own computer. The one thing ego (lite) records during setup is whether you opted into Chrome data migration.

## Article guides & comparisons

- [Playwright MCP for Claude Code: Setup Guide](https://lite.ego.app/article/playwright-mcp-claude-code): Add Playwright MCP to Claude Code, verify the connection, choose browser and login-state settings, and fix missing tools or failed runs.
- [OpenClaw Browser Relay: Setup & Troubleshooting](https://lite.ego.app/article/openclaw-browser-relay): Install OpenClaw Browser Relay, verify the Chrome tab and Gateway connection, and diagnose token, attach, and extension failures safely.
- [Claude in Chrome: Setup, Permissions, and Safety](https://lite.ego.app/article/claude-in-chrome-guide): Set up Claude in Chrome, choose the right permission mode, connect Claude Code or Cowork, fix common failures, and reduce prompt-injection risk.
- [AI Web Scraper Guide: Choose the Right Workflow](https://lite.ego.app/article/ai-web-scraping-tools): Choose an AI web scraper by volume, login state, and cost, then map tools like Browse AI, Firecrawl, and ego (lite) onto no-code, API, or agent-browser routes.
- [Playwright MCP vs CLI: Token Cost, Setup, and Trade-offs](https://lite.ego.app/article/playwright-mcp-vs-cli): Compare Playwright MCP and CLI using official guidance, a verified CLI run, historical token tests, setup steps, session options, and practical trade-offs.
- [Chrome DevTools MCP: Setup, Existing Sessions, and Fixes](https://lite.ego.app/article/devtools-mcp-existing-browser): Set up Chrome DevTools MCP, connect an existing Chrome session, fix Node and profile errors, and understand the security trade-offs before granting access.
- [Playwright vs Selenium: Which Test Framework Fits?](https://lite.ego.app/article/playwright-vs-selenium): Compare Playwright vs Selenium for new and existing test suites: browser coverage, waits, languages, Grid, debugging, migration cost, and team fit.
- [Computer Use Agent: How It Works and How to Control It](https://lite.ego.app/article/computer-use-agent): Understand computer use agents, compare pixel, DOM, protocol, and API control, then design state, approvals, evaluation, and evidence for safe workflows.
- [Codex Chrome Extension: Setup, Permissions, and Fixes](https://lite.ego.app/article/codex-browser-guide): Set up the Codex Chrome extension, choose site permissions, work across browser tabs, enable developer access, and fix connection or profile errors.
- [Browser Agent Security Risks: Threats and Controls](https://lite.ego.app/article/browser-agent-security): Map browser agent security risks from prompt injection to excessive agency, then apply isolation, least privilege, approvals, evidence, and recovery controls.
- [Browser Use vs Codex Browser: AI browser comparison](https://lite.ego.app/article/browser-use-vs-codex-chrome): Compare Browser Use with the new Codex Browser product line. Understand the architectural shift, session handling, and which tool fits your automation tasks.
- [Claude Code browser automation: 5 ways compared](https://lite.ego.app/article/claude-code-browser-5-ways): Compare 6 ways to automate browsers with Claude Code, including the new Cowork built-in browser, for login sessions, token cost, and task fit.
- [Agent Browser vs DevTools MCP vs ego (lite)](https://lite.ego.app/article/agent-browser-vs-devtools-vs-ego): Compare OpenAI Atlas's integrated browser with agent-browser, Chrome DevTools MCP, and ego (lite) for AI agents. Learn which architecture fits login state.
- [Browser Use vs Computer Use: browser agent comparison](https://lite.ego.app/article/browser-use-vs-computer-use): Compare Anthropic's DOM-native browser use tool with pixel-based computer use and real browsers. Learn which approach fits your agent's tasks.
- [GPT-6 Astra Computer Use for Browser Automation: Capabilities, Limits, and Local Alternatives](https://lite.ego.app/article/gpt-6-astra-computer-use): Explore GPT-6 Astra's computer use capabilities from official docs and early reviews, and compare cloud vs local browser agents for your tasks.
- [WebMCP explained: how it changes browser automation (and where it doesn't)](https://lite.ego.app/article/webmcp-vs-browser-automation): Understand WebMCP, Chrome's agent-tool API, origin-trial limits, security, and when to choose WebMCP or real-browser automation for logged-in work.
- [OpenClaw browser automation: control, relay, and profiles](https://lite.ego.app/article/openclaw-browser-control): Learn OpenClaw browser automation with the current quick start, managed, Chrome attach, extension relay, and remote CDP profiles, plus safe logged-in options.
- [AI Scraping Behind Login Walls: X and LinkedIn (2026)](https://lite.ego.app/article/ai-scraping-login-walls): Read-only X and LinkedIn scraping behind login walls: API/OAuth first, real-browser session reuse, evidence fields, and stop conditions.
- [Browser Use vs Stagehand vs ego (lite): A Firsthand Test](https://lite.ego.app/article/browser-use-vs-stagehand-vs-ego): On one matched HN task, Stagehand's AI extract returned wrong rows and Browser Use's local model timed out. See setup friction and where ego (lite) fits.
- [Best AI Browsers and Browser Automation Tools in 2026](https://lite.ego.app/article/best-browser-automation-agents): Compare eleven AI browser automation tools for reliability, token cost, model control, no-code workflows, dynamic DOMs, anti-bot limits, and privacy.
- [Codex for Chrome vs Claude for Chrome: Compared](https://lite.ego.app/article/codex-chrome-vs-claude-chrome): OpenAI and Anthropic built the same shape: an extension that puts their agent in a supported browser. Compare permissions, integrations, reliability, costs, and when an isolated browser fits better.
- [How to connect AI agents to your existing browser](https://lite.ego.app/article/how-agents-connect-existing-browser): Four routes let an AI agent reuse your signed-in browser state, each with a structural cost. ego (lite) combines all four, without losing your window.
- [Browser Use vs Playwright MCP: Which Fits Your Stack](https://lite.ego.app/article/browser-use-vs-playwright-mcp): Compare Browser Use, Playwright MCP, and agent-browser: control surfaces, setup, browser state, and the tradeoffs behind each AI browser automation route.
- [Browser Use vs Playwright for AI browser automation](https://lite.ego.app/article/browser-use-vs-playwright): Playwright is deterministic code; Browser Use is an LLM loop that dropped Playwright for raw CDP. Compare reliability, DOM changes, production scraping, token cost, anti-bot boundaries, and testing.
- [Chrome DevTools MCP vs Claude in Chrome: comparison](https://lite.ego.app/article/devtools-mcp-vs-claude-chrome): One is an open protocol any agent can use free; the other serves paid Claude plans with zero config. The lock-in question, and a decision tree.
- [Selenium MCP: Setup and When to Use Playwright MCP Instead](https://lite.ego.app/article/selenium-mcp-guide): Have Selenium assets? Selenium MCP keeps them working with AI agents; setup takes one command. Starting fresh? Playwright MCP is the stronger default.
- [ChatGPT Browser Use: Cloud Browser vs Your Own Browser](https://lite.ego.app/article/chatgpt-browser-use): What ChatGPT browser use can access today, how cloud and Chrome paths differ, and when to use a local logged-in browser with an agent.
- [Hermes Browser Extension: Connect Agents to Your Browser](https://lite.ego.app/article/hermes-browser-extension): Compare the Hermes browser extension, local gateway, CDP, and CLI routes. Setup cost, login-state boundaries, tab ownership, and the honest ego (lite) alternative.
- [Playwright vs Puppeteer for Web Scraping: 2026 Verdict](https://lite.ego.app/article/playwright-mcp-vs-puppeteer-scraping): Playwright vs Puppeteer scraping guide covering anti-bot boundaries, CAPTCHA and proxy limits, JavaScript rendering, government portals, login sessions, tool choice, resource use, and HTML wait states.
- [Playwright vs Puppeteer for PDF generation](https://lite.ego.app/article/playwright-mcp-vs-puppeteer-pdf): Both render PDFs through the same Chromium print engine, so output ties. The real differences: accessible tagged PDFs, language bindings, and fleet ergonomics.
- [Puppeteer vs Playwright vs Selenium for scraping](https://lite.ego.app/article/playwright-mcp-vs-puppeteer-vs-selenium): Selenium's WebDriver hop, Puppeteer's CDP directness, Playwright's auto-waiting: how each translates into scraping outcomes, and who should pick which.
- [Best MCP for Browser Automation: The 2026 Shortlist](https://lite.ego.app/article/best-mcp-browser-automation): A scored shortlist of browser automation MCP servers on login-state access, token cost, and compatibility, plus the browser that beats them on tokens.
- [Claude Code Browser Testing: A Practical Workflow](https://lite.ego.app/article/claude-code-browser-testing): Where Claude Code genuinely helps web testing (visual bugs, exploratory passes, logged-in flows) and where your test framework stays in charge.
- [Browser extensions vs shared agent browser: which is better?](https://lite.ego.app/article/vendor-extension-vs-shared-browser): Every browser agent decision hides one question: does the agent move into your browser, or get its own with your sessions? Window ownership decides it.
- [Browser Use vs Browserbase: cloud browser comparison](https://lite.ego.app/article/browser-use-vs-browserbase): Browser Use and Browserbase now overlap, but one leads with agent logic and the other with cloud browser infrastructure. Compare setup, pricing, and fit.
- [Headless Browser vs Real Browser for AI Agents](https://lite.ego.app/article/headless-vs-real-browser): Compare headless and real browsers for AI agents: production reliability, authorized session reuse, fingerprint limits, profile isolation, crash recovery, privacy, and cost.
- [DevTools MCP vs Playwright MCP: debugging or automation](https://lite.ego.app/article/devtools-mcp-vs-playwright-mcp): Chrome DevTools MCP wins at debugging (traces, memory, network); Playwright MCP wins at driving (forms, navigation). Compare token context, performance, lightweight setup, auth, DOM versus screenshots, and QA workflows.
- [Playwright MCP Token Problem: Why Snapshots Eat Your Context](https://lite.ego.app/article/playwright-mcp-token-problem): One Salesforce page can cost 114K tokens through Playwright MCP. The cause is the snapshot mechanism, not your config. Three ways out, ranked by savings.
- [Playwright MCP vs Puppeteer for Claude Code](https://lite.ego.app/article/playwright-mcp-vs-puppeteer-claude-code): For Claude Code, one fact settles it: Puppeteer's reference MCP server is deprecated, Playwright's is first-party. When Puppeteer still wins.
- [Is Playwright MCP Good? An Honest Review (2026)](https://lite.ego.app/article/is-playwright-mcp-good): Playwright MCP is free, official, and five minutes to set up. It's also token-hungry and shaky on complex pages. An honest review of where it shines.
- [Playwright MCP Setup Guide: Claude Code, Cursor, and the Zero-Config Alternative](https://lite.ego.app/article/playwright-mcp-setup-guide): Copy-paste Playwright MCP setup for Claude Code, Cursor, and Codex, plus a practical comparison with Chrome DevTools MCP and the zero-config alternative.
- [Best browser MCP for Claude Code: 6 tested options](https://lite.ego.app/article/best-browser-mcp-claude-code): Six browser MCP options for Claude Code, scored on login state, context cost, reliability, security, and price—with practical ways to reduce MCP bloat.
- [Cursor browser automation: MCP, fixes, and alternatives](https://lite.ego.app/article/cursor-browser-automation): Cursor browser automation guide for large-scale data collection, tool visibility fixes, stability, token costs, persistent rules, model choice, visual debugging, and Slack-to-PR workflows.
- [Playwright MCP vs Claude for Chrome: Compared](https://lite.ego.app/article/playwright-mcp-vs-claude-chrome): Playwright MCP is an open protocol any agent can use; Claude for Chrome lives in your real browser but only serves Claude. Compare CAPTCHA handling, SPA reliability, token cost, setup, and the right workflow.
- [How to reduce MCP token usage: 6 proven tactics](https://lite.ego.app/article/reduce-mcp-tokens): Learn how to reduce MCP token usage with HTML preprocessing, memory compaction, lazy-loaded schemas, lean coding-agent workflows, and runaway-cost guardrails.
- [Google Antigravity browser automation: setup and fixes](https://lite.ego.app/article/antigravity-browser-automation): Google Antigravity browser automation guide: manage Gemini quotas, browser connections, loops, reliability, login sessions, privacy, Linux installation, and Remote Control safely.
- [Browser Automation for n8n: Nodes, Browserless, and More](https://lite.ego.app/article/n8n-browser-automation): n8n browser automation guide for Google Maps lead generation, social and real-estate research, low-cost Browserless alternatives, remote local-browser triggers, login sessions, reliability, and approval controls.

## Links

- Website: https://lite.ego.app
- Documentation: https://lite.ego.app/document/
- Roadmap: https://lite.ego.app/roadmap
- Documentation llms.txt: https://lite.ego.app/document/llms.txt
- GitHub: https://github.com/citrolabs/ego-lite
- X / Twitter: https://x.com/ego_agent
- Sitemap: https://lite.ego.app/sitemap.xml
- robots.txt: https://lite.ego.app/robots.txt
- llms.txt: https://lite.ego.app/llms.txt

## Contact

For partnerships, press, or integration questions, open an issue on the GitHub repo or reach @ego_agent on X.