Today we’re launching Papaya (YC F26)!
Papaya continuously improves the quality of your production AI agents.
When an agent doesn’t do what it is asked, or takes too long, customers get frustrated. As every company gets access to the same intelligence, agent quality becomes the competitive advantage.
Papaya learns how customers use your agent, pinpoints where they run into issues, then opens PRs to fix them and tracks the impact.
Built with @macyymay and @vpfaiz
If you're applying to YC, here are some things to watch out for (common issues from the handful of reviews I have done):
1. Be clear, not clever. Avoid convoluted and long-winded statements.
2. Don't overuse industry-specific language. Assume the person reading doesn't know your industry.
3. Answer questions directly. Like, actually answer the question you were asked!
4. Don't lie.
5. Don't make an answer longer than it needs to be.
https://t.co/MMCd96Euco
i strongly suggest you apply to yc. the deadline is 10 days out.
we didn't have any revenue when we got in. you just need a good idea + team, and a strong application. clarity trumps cleverness.
apply early to give your app a better shot. a lot more folks submit right around the deadline, and it's easy to get lost in the noise.
and if you're applying, i'm always happy to review yours.
how much compute would you personally need in the future?
many of us are extrapolating based on our past usage. you had one laptop, one phone, one cloud machine.
your imagination is limited by what has been. the future is going to be unimaginably different.
YC’s new "Early Access Network" could end up as important as Demo Day!
Incredible energy at the event tonight.
We had over 100 companies (many of them large enterprises) visiting and connecting with YC startups.
This is the first time YC has done something like this, and certainly not the last. For me, this was the best @ycombinator event yet!
how much compute would you personally need in the future?
many of us are extrapolating based on our past usage. you had one laptop, one phone, one cloud machine.
your imagination is limited by what has been. the future is going to be unimaginably different.
y'all are *severely* underestimating the compute needs of the future, even if you’re already accounting for jevons paradox.
compute will be like wealth.
there will be no limit to how much of it you’ll need. and no limit to how much more of it you’ll crave.
i strongly suggest you apply to yc. the deadline is 10 days out.
we didn't have any revenue when we got in. you just need a good idea + team, and a strong application. clarity trumps cleverness.
apply early to give your app a better shot. a lot more folks submit right around the deadline, and it's easy to get lost in the noise.
and if you're applying, i'm always happy to review yours.
YC W27 is open. Apply if you’re early.
On-time deadline is November 2 at 8pm PT. You get a decision by December 11. Late applications are still read.
Most founders wait for the product to look finished. You don’t have to. About 40% of the companies YC funds are still just an idea. Most have no revenue. Only about 7% had more than $50k monthly revenue when they got in. Solo founders are now up to 19% of the batch. Half the companies in a typical batch applied more than once.
Apply if you can:
• show a product that works for one real user
• say who is stuck, and what it costs them, in one sentence
• apply while the numbers are still small
• start before you feel ready
• treat a no as a clearer next try
The batch runs January to March 2027 in San Francisco.
You get the $500K standard deal, $12M in partner credits, partners in the room, and Demo Day.
If you can name the person with the problem, you’re early enough.
y'all are *severely* underestimating the compute needs of the future, even if you’re already accounting for jevons paradox.
compute will be like wealth.
there will be no limit to how much of it you’ll need. and no limit to how much more of it you’ll crave.
@mitsuhiko@steipete there is no way twitter survives this bot army, unless drastic measures are taken. at some point the power users will just give up, right?
Models love reward hacking. Maybe we should just let them!
In our new paper, we let models reward hack during RL but we dictate which parameters learn this behavior. When we disable these parameters for deployment, the model keeps its new capabilities but doesn't hack!