Causeway — sovereign browser bridge. Drives Chromium via CDP, no extensions.
A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in causeway's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
Fix browser restart session loss
Browser restarts were forcefully killing all instances of the browser application, not just the one Repo Wrapped was managing, which corrupted login data and signed out all accounts. The fix now targets only the dedicated browser profile directory on Mac/Linux and sends a graceful shutdown signal first before forcing a kill, allowing login sessions to be properly saved.
Fix browser reconnection after crashes
Fixed a bug where the browser would become unresponsive after the browser process crashed and restarted. The system now properly clears stale browser context IDs during reconnection and retries tab management commands (opening, closing, switching tabs) when the browser is temporarily unavailable, allowing the connection to self-heal automatically.
Fix concurrent agent tab interference
Rewrote the browser connection system to use Chrome's flat CDP sessions instead of a shared "current tab" pointer. Now each agent can independently target specific tabs via target_id without interfering with concurrent operations — for example, two agents can simultaneously navigate different tabs in the same browser process without stepping on each other.
Fix Edge browser connection issues
Fixed connectivity problems when connecting to Microsoft Edge's DevTools server on Windows by using the IPv4 address (127.0.0.1) instead of localhost. This prevents connection timeouts caused by IPv6 resolution attempts to addresses where Edge's server isn't listening, and adds proper timeout handling to DevTools HTTP requests.
Keep reconnect inside the locked profile — no more personal-profile hijack
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.