What it actually does
Browser automation for agents has a persistent, mundane problem: logins. Frameworks like browser-use drive a separate browser, so your authenticated sessions never carry cleanly, and when they do share a browser you end up fighting the agent for control of the same tabs.
ego lite is a browser designed from the start for both of you. Your agents run tasks in their own Spaces while your tabs stay yours. The agent reaches your real logins and tabs through the `ego-browser` skill, and the maintainers claim tasks complete faster on fewer tokens than framework-driven approaches.
Setup is deliberately minimal — installing the app adds the `ego-browser` skill to every agent's skills directory on the machine, so Codex, Claude Code, and others pick it up without configuration. It is MIT licensed and free to run.
The significant caveat is platform: macOS only today, with Windows and Linux on the roadmap.
Who it's for
- 01
Anyone whose agent automation keeps breaking on login walls
- 02
Sales and marketing teams doing research inside authenticated tools
- 03
Ops people who want an agent to use an internal web app that has no API
- 04
Solo operators who cannot dedicate a second machine to agent browsing
Where it earns its keep
- Letting an agent pull data from an internal dashboard that was never given an API
- Research across sites where you are already logged in, without re-authenticating
- Running several browser tasks in parallel while you keep working in your own tabs
- Automating a recurring extract from a SaaS tool whose export button does not exist
- Cutting token spend on browser tasks compared with framework-driven automation
Use it, or skip it
Reach for it when
- The target site requires a logged-in session and API access is not an option
- You want the agent working in the background without hijacking your browser
- You are on macOS and want zero-config setup across multiple agent clients
- Browser task cost or latency has become a real constraint
Skip it when
- You are on Windows or Linux — support is not there yet
- You need headless browser automation in CI; this is a desktop browser by design
- The site's terms prohibit automated access. Sharing your session does not change what you are permitted to do
- You need fine-grained programmatic control of the page — a framework gives you more surface
10 automations
Ideas, not tutorials. Each one is work a team does by hand today.
- 01Operations
Internal dashboard extract
Pull weekly numbers out of an internal tool that has no API and drop them into a Slack digest every Monday.
- 02Marketing
Authenticated competitor research
Research inside tools that require a login and compile findings into a brief without you re-authenticating each time.
- 03Sales
CRM hygiene sweep
Have the agent walk your CRM in a background Space and flag records with missing owners or stale stages.
- 04Operations
Parallel account checks
Run the same verification across several logged-in accounts simultaneously in separate Spaces.
- 05Finance
Billing portal reconciliation
Log into vendor portals monthly, pull invoices, and reconcile them against your accounting records.
- 06Support
Support ticket enrichment
When a ticket arrives, look the customer up across your authenticated admin tools and attach the context.
- 07Marketing
Job board monitoring
Track competitor hiring behind logged-in job boards to infer where they are investing next.
- 08Founders
Analytics screenshot digest
Capture the same dashboard views weekly and assemble them into a visual report for the leadership review.
- 09Operations
Form-heavy workflow relief
Automate repetitive multi-step form submissions in internal tools, with a human confirming before the final submit.
- 10Engineering
Token cost comparison
Benchmark a recurring browser task here versus your existing framework and report the difference in spend.
Want one of these running by Friday?
LimeDock builds these as real workflows inside your stack — deployed to your cloud, wired into your Slack and CRM, with the code in your repo. You pay a build fee and your own API keys, nothing else.
Source
Repository stats were read from the GitHub API and reflect the last time we refreshed this entry. The editorial breakdown above is LimeDock’s own analysis — we are not affiliated with citrolabs.
https://github.com/citrolabs/ego-lite