Some criticize YC-backed PearAI for forking AI code editor Continue, which has the Apache open-source license, and slapping on a ChatGPT-written closed license
A Y Combinator startup named PearAI launched with an X post thread and YouTube video on Saturday and created immediate controversy.
TechCrunchJulie Bort
Context & Ripple Effects
PearAI’s launch controversy exposes a fault line in AI tooling: projects can build on permissively licensed code, but the way they present downstream licensing can quickly become a trust issue for contributors and users.
The episode also fits a wider AI commercialization tension, reflected in OpenAI’s move toward a closed-source, for-profit model. In developer tools, the distinction between an open code base and a proprietary product layer is especially consequential because adoption depends on clear reuse terms.
First-order effects
PearAI faces immediate scrutiny over the license attached to its Continue fork, while developers evaluating the product must determine what terms govern the code they would use or contribute to.
Continue’s Apache licensing becomes central to the dispute: its original project and PearAI’s fork are now more visibly differentiated by governance and licensing posture, not just product features.
Second-order effects
AI coding-tool startups building on open-source projects have stronger incentive to document code provenance and licensing clearly, since ambiguity can undermine developer trust at launch.
The controversy can steer contributors and prospective users toward projects with clearer maintainer governance, making licensing treatment a competitive factor alongside model quality and editor integrations.
Third-order effects
If AI developer tools increasingly commercialize open-source foundations, licensing compliance and transparent attribution could become core parts of product credibility rather than back-office legal details.
The broader market may split more sharply between community-governed tooling and companies that add proprietary layers on top; whether that produces sustainable coexistence depends on clear downstream rights and contributor confidence.
The trend: AI coding products are testing how quickly open-source building blocks can be commercialized without eroding the developer trust that made those foundations valuable.
We were excited to announce our product and company on Twitter yesterday. But you've all helped us understand that we did so in a way that was haphazard at best and at worst offensive to the open-source community that we love. We made two big mistakes. First, we kicked off our
I just quit my 270 000$ job at Coinbase to join the first YCombinator fall batch with my cofounder @not_nang. We're building PearAI, an open source AI code editor. Think a better Copilot, or open source Cursor. But you've heard this spiel already... 🧵⬇️ [image]
Can you completely clone a product, call it yours, and raise half a million in funding? Well, apparently you can now. In a nutshell: John copied James' essay, and then suddenly Timmy came in, copied John's essay, and got the scholarship? Watching Pear AI's drama unfold upon [imag…
@peer_rich @garrytan garry is great. these guys fucked up, they're all working to fix. people are being harsh because it looks bad. they did keep the contributions and credit. they did fuck up the Apache license but it probably had no effect - same as distributing under Apache.
a couple takes on the “vscode continue pearAI YC drama” for context: - i did YC in W19, big fan of YC - i run a large OSS project https://cal.com/ - i have the most respect for @garrytan, who also signed my O1 petition 💪 my takes: - i agree with my cofounder [image]
@garrytan why fund 4 companies (pear, void, continue, melty) doing the same thing? diversifying risk? how can you help each one win if they are cannibalizing each others customers? wouldn't it be better to make one bold bet and genuinely invest in their success vs. just playing i…
@CodeFryingPan On the flip side: it's a launch to remember! You made things right, and thanks to being so public perhaps more future founders will see that sometimes you mess up, and you can reflect & fix it (like now). Good luck w Pear AI and congrats on taking a leap of faith!
@charliermarsh @garrytan It appears that this problem did exist but now they have corrected this issue and it is appropriately using the Apache license. “NOTE FROM FOUNDERS: THIS USED TO BE A CHATGPT RECOMMENDED AND GENERATED EE LICENSE. WE ARE OPEN SOURCED.” https://github.com/.…
one can expect anyone very excited about AI to be excited to overuse the tools. Like PearAI's license, instead of picking some standard one or copying one of their 100 competitors, they opt for ChatGPT to write it [image]
@nikshepsvn YC has 14 equal investing partners who operate independently- it is more like Bell Labs with independent thinkers Any given one of us has wide latitude as generalist investors. We tend to do no competing deals ourselves but also people pivot into each others spaces.
Continue published their repo under Apache 2.0, and open source license that allows commercial use. That's kind of the point of FOSS. Whether you think PearlAI deserves YC funding for this (continue is YC too) is another story. But Pearl did not „steal" code
he is right...if you don't want get forked like this (open source—>enterprise derivative) but still want to be open source, then use a GPL/copyleft license, not Apache. . .it's that simple. . .
@kindgracekind ... I think the main problem is communication style, the influencer-founder humble brag victory lap strategy for product announcement is basically rage bait Another style of writing would have been well received Either way it's free marketing for them
“Show me the incentive, and I'll show you the outcome.” PearAl recklessly attempted to impose a proprietary license (the Pear Enterprise License) on software that was originally released under the Apache open-source license! 😡🤮 Which is copyright infringement and this kind of [im…
They took the https://continue.dev/ repo, stripped the Apache license and replaced it with a proprietary non-FOSS enterprise license that the founder asked ChatGPT to write
Open Source licenses matter. 🧑⚖️ Seems the kerfuffle around PearAI is about VSCode and @continuedev. Let's look at their licenses: VSCode: MIT Continue: Apache 2.0 The MIT license is a true free for all. Apache 2.0 allows anyone to take the code, modify it, redistribute it, and
Oh look, they noticed that it's actually legally problematic to change from an Apache 2.0 license to your own more restrictive one. 10 minutes ago they changed theirs back to Apache 2.0. At least they are taking feedback, I guess? [image]
In fact, originally, PearAI didn't even use Apache. They were straight up like “this is our code now.” Is this what they meant by “ChatGPT-ing the license”? 😭 [image]
lots of shade being thrown around about pear's licensing issues, which could end the business at some point but controversy is certainly gaining them github stars and interest [image]
Don't understand why people are dragging a new project when literally it's open source Apache license and that's *the reason* why open source is awesome
Lol the community note on my tweet.. We are way too open and honest for this slander. Y'all who put this here are trolling. We mention in the first thing of our “About” section of our GitHub that we're a fork of both VSCode and Continue + in many of our yt vids. [image]
Introducing BlueberryAI, the open source AI powered code editor It's a fork of PearAI, which is a fork of Continue, which is a fork of VSCode Investors my DMs are open for the seed round [image]