Still switching between Codex, Claude Code, and Antigravity?
What if you had an entire AI engineering team PM, Principal Engineer, QA, Security, and Code Review doing the work for you?
And actually SEE what every agent is doing.
Meet Keel 🚀
Free. Open source. Works with your existing Claude Code & Codex accounts.
https://t.co/1N5qEOG4bm
That’s what we thought back in April that’s why our first version was actually a chrome extension… then you realize that chrome has at least 7 layers that slows down the agents loop and agents don’t really need them.. and most importantly CDP is very well know protocol which means you can’t give your agents access to console or runtime without being flagged as bot… long story short extensions sounds easy but it doesn’t really work for agents… that’s why the industry reported 55-60% success rate on agents that uses chrome or chromium where our success rate is 95+%
Well we thought chromium would work for our first version of https://t.co/xilUp9wYyj the we realized the obvs… chromium is 35M lines of code and very bloated and super slow and bad for agents… it was written for humans and then we tried to duck tape agents on top of CDP… while our first version “kinda” worked and we managed to get customers we quickly decided to write our own browser from the ground up in rust… PS we’re a team of googlers and 2 of us where on the chrome core team :) stay tuned!!
@nizzyabi Look closer at regulated industries and healthcare specifically… our customers are calling us RPA V2… RPA solved part of the problem but still painful to maintain that’s why customers are migrating to https://t.co/jQSD6jWoBz
@EXM7777 Now more than ever… a lot of regulated companies are still stuck on old fragmented portals and tools… and the only way to do something meaningful across systems is browser… that’s why we built https://t.co/jQSD6jVQM1
CLI is the new API... If you're not building CLI-first products, it's time to rethink your strategy... Agents love CLIs... They're fast, composable, deterministic, and built for automation... The next generation of software won't be designed for humans first.... It'll be designed for agents.
Build for agents first. Humans second.
I love the reaction when I tell people we didn't use V8, Chromium, or Blink. We wrote our own JS engine, V9 (think V8, but in Rust), and built our networking and rendering from the ground up.
The reaction is always the same:
'Wait… you did what?' 😄
Here's why: today's browsers were built for humans. The next generation needs to be built for humans and agents, with agents at the core, not duct-taped on top of a thousand layers.
If you are crazy enough to believe that you can built 10x better browser than chrome and 100x better control plane than browser-use I’m hiring DM me
@almokhtar_al Yes you should rethink what we took for granted for while… one of the things that people is unthinkable for startup is building new browser from the ground up… every one is using chrome as headless… we didn’t do that we built our own browser from the ground up
"Yes, reinvent the wheel" is my new motto.
For most of my career I heard the same piece of wisdom: don't reinvent the wheel. And early on, it made sense. Why understand how data structures work when Guava exists?
Why build an ORM when Hibernate is right there? But the longer I spent in this industry, the more I learned that generic frameworks aim for 80–90% coverage.
They're built for the median user. They almost never fit your exact needs, so we learned to live with the pain and keep hacking around them, because building our own was too expensive. Why spend months on an ORM when Hibernate is free?
That excuse is gone. The speed of delivering software has changed so dramatically that bending your entire architecture around someone else's library no longer makes sense.
So at Oya, we're reinventing the wheel. On purpose.
- We built our own ADE (Keel).
- Then we built our own browser.
- Then our own GitHub code reviewer.
- And now we're building the control plane to run thousands of those browsers in the cloud.
Here's why it matters for us: Oya Browser is an automation platform for regulated industries. It's not a consumer browser hacked to make agents work. It's built from the ground up for teams who care about HIPAA and SOC 2, where audit trails, session isolation and control over what leaves the machine have to be designed in from day one, not bolted on later.
Every CTO will ask: AI collapsed the cost of building software, not the cost of owning it. If you build your own wheel, you own the maintenance, the patching and the security. For us, that's the point. When you own the whole stack, you can make guarantees a generic tool never could.
And the irony? Reinventing the wheel makes understanding how wheels work matter more than ever. The engineers who know how data structures and ORMs actually work are the ones catching the subtle bugs in AI-written code.
Don't reinvent the wheel? In 2026, maybe it's time that you do.
check https://t.co/eokG79cYqj
#Oya #AI #BrowserAutomation #HIPAA #SOC2 #BuildInPublic
I’m hiring Sr product engineers and Sr Software engineers… our product is https://t.co/xilUp9wqIL an AI Native browser check it out and check our GH https://t.co/IV5h2f0xiP
Remote first, competitive compensation and we’re VC backed.
Interview process:
- Clone the source code
- Find a of bug or enhancement
- Create a PR
- DM me with your resume and the PR link.
This is a Sr role so you must have at least 5 years of experience