last week we open sourced:
anydoc: parse 14 document formats, ~5ms per page
pdf-inspector: parses + classifies pdfs, no waiting on OCR
14k stars each, built in rust. now powering @firecrawl /parse, which adds OCR for the hard ones
what should we open source next?
i left Cursor.
after 10 years inside the tech bubble in San Francisco, Cursor felt like the sharpest version of that world – fast, intense, ambitious, full of people trying to pull the future closer.
i’m leaving with gratitude, but also with the feeling that i need a different rhythm.
slower time. different weather. more culture, aliveness, and humans in the everyday.
Asia feels like the right place to begin again.
to stay grounded, experience life more fully, and build freely.
i’ll share what i find along the way!
Introducing OpenRouter for tools ⚒️
Old world: SaaS bundles priced for humans. $139/mo, and you don't even know what's in the box.
New world: agents don't care about vendors. They want the best API for the task - and to pay for the result.
- 2,600 agent-friendly tools: seo/geo, social, leads, ads...
- search by task: see price/request/response, call it
- pay per call, no subscriptions - 0% markup
- Open-source
Try it here: https://t.co/FF0QPjLu45
.@naval: “The opportunities have never been more equal than now.
@elonmusk and @JeffBezos have the same iPhone you do. They don’t have some better version of an iPhone.
They’re eating food that might be marginally better than yours, but it’s basically the same.
You might even have a better diet than them. You probably have more time to go to the gym than them.
They’re not immortal, and they’re not going to be—most likely, not at this time scale.
So you have more youth than them. You have a lot of advantages over them.
The wealth gaps are actually much smaller than people think.
A lot of that is due to mass production, which comes from specialization, labor, and capitalism.
But it’s very easy to overlook that and agitate—because that gets you higher in the status hierarchy with other monkeys.
It makes you look like you’re fighting for noble causes and gives you status, which is really what people are craving these days.
They’re craving status, not money or wealth.
And status is a zero-sum game.
So it’s kind of an evil game to play because there have to be losers for every winner.
And the only way to win is by crushing somebody else down.”
Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing.
Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deeply leveraging AI. This is more or less the culmination of my secret 10-year master plan.
This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug. We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night.
How is that possible? It's the Sandstorm security model, revisited. A "Gadget" is the same thing as a Sandstorm "Grain": a fine-grained app instance. For example, if you have a document editor app, each document runs as a separate instance of the app, in a separate sandbox (one "Gadget").
This means two things, both of which I think are Big Deals:
1. The platform can manage all access control, by controlling who can access the Gadget at all. There is no way the Gadget can accidentally leak itself to an attacker -- even an attacker who has access to other Gadgets based on the same app.
2. Since everyone is running their own copy of the code, everyone can freely *modify* their copy of the code.
Think about #2 a bit more.
What if, when you wanted a new feature in the software you are using, you could just prompt your agent to add it?
This doesn't work in the cloud Software-as-a-Service model, because you are not running your own copy of the app.
Sandstorm tried to change that 10 years ago, but the world wasn't ready, because not enough people had the skills or patience to actually modify their software. AI has changed that. Now you just ask the agent -- the same agent that you are using to help you interact with the Gadget can also modify the code of the Gadget.
And it is so fun.
https://t.co/qzwdrAQhtK
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
https://t.co/fVsRsYFNyC
Every startup should have a daily markdown file called "what_the_market_is_telling_us.md"
It updates every morning from the places where customer truth already lives:
1. Stripe for who pays, upgrades, downgrades, and churns
2. PostHog for what people actually do in the product
3. Intercom or Plain for support tickets/complaints
4. Granola or Gmeet transcriptions for sales calls/ customer interviews
5. HubSpot or Salesforce for CRM notes/lost deal reasons
6. Linear, Jira, or GitHub Issues for bugs and feature requests etc
7. Ideabrowser MCP for outside market signal: startup ideas, trend reports, social/search demand, AI research reports, and builder prompts that show what people are starting to want before it shows up in your own customer data.
Basically, the file should notice what changed in the business this week and not just be this summary of here’s what happened (which I think a lot of people have their agents do).
Why this is valuable:
1. Maybe new buyers are using different words than they were a month ago.
2. Maybe trial users are getting stuck in the same place.
3. Maybe upgraded customers all touched one feature right before they paid.
4. Maybe churned customers keep mentioning setup confusion.
5. Maybe sales calls are suddenly losing to a competitor you used to beat.
6. Maybe support tickets are revealing a workflow your product accidentally became responsible for.
You get the point.
The fastest way to PMF is understanding customers better than anyone else, and the highest signal customer insight is usually a change in behavior.
So I’d have the agent update the file every morning with the pattern it found, the receipts behind it, and the product or GTM decision it might affect.
For example:
“3 customers who churned this week all mentioned setup confusion, and 2 of them never invited a teammate.
This looks more like an activation problem than a pricing problem, so I’d look at team invite and onboarding before building another analytics feature.”
A little helpful tip for all those out there looking to get more from their LLMs.
We've decided to open-source the CRM we built for ourselves at Comp AI.
It's agentic-first, which we mean literally: durable research agents.
MIT license. Built using next, eve, and context.
Only if education could be this interactive ❤️🔥
I've had a looong wish to build something genuinely useful through vibe coding, and I finally did it.
A 3D human anatomy application built with @threejs using GPT 5.6 Sol.
It all started with a single design image that I created using GPT Image 2.0. I then used it to generate every 3D organ image, one by one.
Next, I converted each of those images into 3D models using @tripoai (and no, they didn't sponsor this 😄).
After that, I opened Codex, wrote a master prompt based on the design, and gave it the prompt, the design image, and all the 3D models.
Codex built the first version beautifully, but there was one big problem.
Every single 3D model was nearly 120-150 MB. That obviously wasn't practical for the web and was giving a performance of 16fps.
After a few iterations, Codex optimized each model down to roughly 2–5.5 MB while preserving the visual quality, reducing the total asset size from ~900 MB to just 28.6 MB. And each model loads on demand.
Along the way, Codex also generated those anatomical illustrations showing where each organ sits in the human body, and even created the interactive hotspot markers that explain different parts of every organ. It handled all of that.
The process wasn't exactly one shot, but it also wasn't difficult. You just have to do it step by step.
It genuinely felt like building something that could make learning anatomy much more engaging.
The inspiration came from @DilumSanjaya's 3D animal plant cell project. I remember seeing it and thinking, "I want to build something like this one day."
And I did it :D
Live: https://t.co/gIFgkj8UVB
Code: https://t.co/nijvyWcyxO
I gave my kids a way to chat with their grandparents via WhatsApp.
But without screens!
This box lives in their bedroom, they press the massive blue button to record a voice message, and the message is sent to a group with both grandparents.
It’s two-way so when the grandparents send a message back, there’s a ringtone (that we chose together) and the kids run to their room to listen.
The grandparents even get a “listened” notification with a small headphones WhatsApp reaction.
When the kids are away or asleep, the messages queue until their return.
There are obviously quiet hours at night.
My son and I built this over the past few weeks, iterating on the UX.
The kids and grandparents absolutely love it!
I love that they are in direct contact without me in the middle and without screens.