Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI-coding-agent teams and platform teams that want a maintained MIT browser-for-AI-agents product with a clean ego-browser JS-callable agent surface (rather than another CLI subprocess layer) and that need authenticated flow access to production SaaS without copy-pasting session cookies, for developers who want to drive Claude Code / Codex / Cursor / custom agents through one browser
Where this stands now
citrolabs/ego-lite ranks #956 of 2402 tracked Radar items by composite score (7.4 against a section median of 5.2). The section currently carries 1295 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-08-14 (46 days in the current window). Signal extremes versus the section: momentum at the 85th percentile; novelty at the 70th percentile.
Who should use it
Who should skip it
Move on from citrolabs/ego-lite if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
citrolabs/ego-lite is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-08-14; the source record was last checked on 2026-08-14. The current verdict is 'try now' with a Silver tier and easy setup difficulty. Across RepoRadar's eight signals, citrolabs/ego-lite is strongest on momentum (8.6) and workflow potential (8.5) and weakest on setup ease (7.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar captured from https://github.com/citrolabs/ego-lite.
How this item is evaluated
The citrolabs/ego-lite record combines a 7.4/10 composite score with separate popularity (100.0), risk (low), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
macOS-only today -- Windows and Linux are on the roadmap but not yet shipping, so cross-platform agent teams should verify their dev fleet before relying on ego-browser as the canonical browser surface; Chrome data migration is opt-in but irreversible -- verify the migration prompt before granting access if you want a clean separation between your personal Chrome profile and the agent-aware browser; the ego-browser skill is portable JS so headless / remote setups are workable, but the heavy-lifting browser binary is macOS-only -- Linux / Windows users will be running the skill against a remote macOS ego (lite) instance until the native ports land; single-vendor (citrolabs) release surface -- watch the release notes and pin ego-browser skill versions explicitly for reproducibility, the same way you would for any narrowly-scoped release pipeline.