How Jev Drives Your Own Browser
A walk through the actual code path: what calls what, in which order, and exactly what data moves between the model, the bridge and the browser.
Rajeev Gill
My work sits between product thinking and implementation, with a bias toward systems that make real work less messy.
Based in London. Interested in useful AI, clearer measurement, and software that holds up outside a demo.
Get in touchSelected projects

A measured field guide to every local model installed on Apple Silicon.

A transparent guide to open-source go-to-market software.

A production-ready single-screen judging app built for a live hackathon room.
Recent writing
A walk through the actual code path: what calls what, in which order, and exactly what data moves between the model, the bridge and the browser.
Coding agents generate enormous context — sessions, deliverables, files, decisions. The bottleneck isn't generating more; it's finding what you already made. Here's the small glue layer I built to solve exactly that, and why grep, FTS, and RAG each miss part of the problem.
Almost every browser automation tool claims to be the fastest, the cheapest or the most reliable. I put 34 of them through the same job with the same browser and one independent pass test, then ranked them twice — because speed and real work do not agree.
I am always interested in thoughtful software, analytics, and AI work where the practical details matter.
Email me