I have a 'neuve' side project and I'll start writting more about it here. This time the writeup brings some of my experience when developing the browsing aspect of, I stopped telling AI agents what to build. Instead, I carefully created an experiment on the problem. No shared context, no instructions and no specific method in mind and let them figure out how to drive a browsing session based on a goal independently. They converged on similar patterns I've seen other browsing agents use under the hood. But some of the findings and the process I took taught me quite a lot.

I've followed @charles_maddock and the team journey since 2025 and their earlier builds of the closed beta. I'm so happy to see how far the product and the team has evolved and this launch reminds me of how much tallent there is here in Stockholm! Time for me to give @strawberry another spin and see much it has evolved since I last tried! Congrats to the team!

Delete Chrome Delete Granola Delete Claude Strawberry 1.0 is here, the AI browser that saves your team >100h/week

We have presents for you! 🎁 - A new WebMCP Skill with best practices for security, development, & consequential flows - WebMCP Types: TypeScript definitions, with type inference from InputSchema Give em to your agent, it helps scaffold out WebMCP so fresh and so clean clean

Preparing for Launch Day in SF tea houses. Ship all the features you want. People still need to understand why they should install the thing before you can consider it fully shipped!

This is the “Drake vs Kendrick” for devs 🔥🔥

Time to go (tell your agent to) learn Effect!

I feel similarly when I see y'all generating slides and "artwork." So cringe. Everyone outside the bubble is not impressed. You're impressed because you never had the skills nor appreciation. And you come in like everyone should be impressed?

Building and programing is about understanding a problem and its principles, the risk of using AI without that guiding your work is that you don't even know what is being done and will get easily fooled by shining lights and baubles. Get your principles right before delegating the building parts to agents.

One of the pieces of advice I used to give before AI as a staff engineer still holds true in a way. "The best thing as a dev you can practice is detachment, the code you are most proud of today is tomorrows legacy to be removed." In a way this shielded me of being too precious and exploring early.

I always thought it was clear that browsers would be deeply integrated in to a chat/co-work/agent and that the companies building them were making a mistake to build a dedicated browser. The traditional way of using the web has ossified to the point where browsers eek out points per year in market share from each other while not changing much. At the same time, its amazing to see WebMCP being adopted by these Agent Harnesses - we have a web of linked functionality now - but make no mistake, this is the start of a full assault on the browser as the entry point to your work-day. As much as I love web browsers, I think this actually a very good thing for the web and will strengthen it further as one of humanities greatest inventions. People will be able to publish and share their ideas and work, and have everyone discover and work with them at rates that we've not seen in years. Browsers need to get better. The web platform has a chance to evolve too and I hope the agent harness companies can get more involved in shaping web standards. You won't find this in Google search (I don't know why my site's still not visible), but you can also read more on my blog: aifoc.us Also ht to @rachelnabors who has been saying similar thing for a long time too.

The WebMCP Challenge is here. We’ve teamed up with @ChromiumDev, @CloudflareDev, @ShopifyDevs, @vercel, @render, and @Netlify for a 10-day hackathon. Up for grabs: $35,000 in cash prizes, Codex Micros, ChatGPT Pro subscriptions, and more prizes from our supporters.

Where are my creative design-gineer sisters at? NOW IS YOUR TIME

Tune in to the kickoff livestream today at 3pm PT for product demos, example builds, prizes, and more details on how to enter. nitter.siddz.com/i/broadcasts/1qGoNYbWd…

Huuuuggeeee

piped.video/watch?v=fhoJK02o… this channel always nerdsnipes me harder than it has any right to. Damn!

introducing anydoc now your agents get 100x faster local parsing for pdf, docx, pptx & 10 more formats - sub-5ms md conversion - 500 docx files in 1.7s - top quality across all 13 formats - rust-based - open source already powering @firecrawl /parse github.com/firecrawl/anydoc

got it!

Just as a reminder for you to read the code, GPT 5.6 Terra just tried to BS me with a .patch for better-auth instead of doing the correct thing, and a 5.6 SOL reviewer shrugged it off. Always. Read. The. Code.

GPT 5.5 is so BAD at UI/UX and design software it's appalling. I generally prefer 5.5 for hard engineering problems and reviewing its code is generally not a bad experience. But give it ANY interface task and you are in for a world of pain if you minimally care.

Did you know that the .png format was created out of spite? Or that .jpeg just discards like half of the colours in your image because you won't notice? To celebrate last week's launch, I published a chapter on image compression. makingsoftware.com/chapters/…