Fully agree that the original authors made some unsubstantiated and unqualified claims about what was done - which is sad, because it was still a huge accomplishment as i see it.
When AI 'builds a browser,' check the repo before believing the hype
41–50 of 145 posts
Re: When AI 'builds a browser,' check the repo before believing the hype
#42Earlier quoted context omitted.
That implies a throughput of around 16 million tokens per second. Since coding agent loops are inherently sequential—you have to wait for the inference to finish before the next step—that volume seems architecturally impossible. You're bound by latency, not just cost.
The original post claimed they were "running hundreds of concurrent agents": https://cursor.com/blog/scaling-agents
I'd still be surprised if that added up to "trillions" of tokens. A trillion is a very big number.
Re: When AI 'builds a browser,' check the repo before believing the hype
#43FTA: > tools like Cursor can be genuinely helpful as glorified autocomplete and refactoring assistants That suggests a fairly strong anti-AI bias by the author. Anyone who thinks that this is all AI coding tools are today is not actually using them seriously. That's not to say that this exercise wasn't overhyped, but a more useful, less biased article that's not trying to push an agenda would look at what went right,…
Re: When AI 'builds a browser,' check the repo before believing the hype
#44Earlier quoted context omitted.
The original post claimed they were "running hundreds of concurrent agents": https://cursor.com/blog/scaling-agents
It was 2,000 concurrent agents at peak. I'd still be surprised if that added up to "trillions" of tokens. A trillion is a very big number.
Re: When AI 'builds a browser,' check the repo before believing the hype
#45You would think a CEO with a product that caters to developers would know that everyone was going to clone the repo and check his work. He just squandered a whole lot of credibility.
I've yet to see anyone in this space be negatively impacted by their outlandish claims.
They release a new model or add extra sub agents and the slate is wiped clean.
Re: When AI 'builds a browser,' check the repo before believing the hype
#46Re: When AI 'builds a browser,' check the repo before believing the hype
#47Earlier quoted context omitted.
I wish your recent interview had pushed much harder on this. It came across as politely not wanting to bring up how poorly this really went, even for what the engineer intended. They were making claims without the level of rigor to back them up. There was an opportunity to learn some difficult lessons, but—and I don’t think this was your intention—it came across to me as kind of access journalism; not wanting to step…
I just don't think that's the case. The claims they made really weren't that extreme. In the blog post they said: > To test this system, we pointed it at an ambitious goal: building a web browser from scratch. The agents ran for close to a week, writing over 1 million lines of code across 1,000 files. You can explore the source code on GitHub. > Despite the codebase size, new agents can still understand it and make m…
> In the overall genre of CEO's over-hyping their company's achievements this is a pretty weak example
I kind of agree, but kind of not. The tweet isn't too bad when read from an experienced engineer perspective, but if we're being real then the target audience was probably meant to be technically clueless investors who don't and can't understand the nuance.
Re: When AI 'builds a browser,' check the repo before believing the hype
#48There was a story going around about LLMs making minesweeper clones, and they were all terrible in extremely dumb ways. The headline wasn't obvious, so I thought the take that people were getting from it is that AI is making the same dumb mistakes that it was making a year ago. Nope. It was people ranting about how coders are going to be out of a job next week. Meanwhile, none of them can do a minesweeper clone with like 50 working examples online, maybe 8 things you have to do right to be perfect, and 9000 articles about minesweeper and even mathematical papers about minesweeper to make everything about the game and its purpose perfectly clear. And then AI generates buttons that don't do anything and timers that don't stop.
Re: When AI 'builds a browser,' check the repo before believing the hype
#49You would think a CEO with a product that caters to developers would know that everyone was going to clone the repo and check his work. He just squandered a whole lot of credibility.
Management already doesn't trust developers in any way. Why would they believe you, who are clearly just trying to save your job, over a big company who clearly is the future!
Or do you trust your management to make the right decision?
Re: When AI 'builds a browser,' check the repo before believing the hype
#50Just had my manager submit 3 PRs in a language he doesn’t understand (rust) and hasn’t ran or tested and is demanding quick reviews for hundreds of LoCs. These are tools but some people are clueless..