John Griffin

@vimtor @Cloudflare Oh there’s also the Router component. Seem like such a great fit for Cloudflare

this week i’ll be improving @cloudflare support in sst please open an issue with any problems or features you might want

@vimtor @Cloudflare Love it!

@johng @Cloudflare there are some of these under an experimental flag we’ll make them official this week!

@vimtor @Cloudflare Yeah exactly, parity for those frontends so you can pick either cloud

@johng @Cloudflare you mean components like Astro, SolidStart, etc.?

@petersuhm @adamwathan john-griffin thanks Peter

@johng @adamwathan What's your GitHub handle?

Sending out tons more ui.sh invites today, make sure you look in your spam folder if you're waiting for one 🤞🏻

@SawyerMerritt Hell yes

If Tesla offered this SUV lineup in the US: • Model Y (188" long, two rows) • Model Y L (196" long, three rows) • Cyber SUV (~210" length, same as GMC Yukon, three rows) This would be one hell of an all-electric self-driving capable SUV lineup that would serve the needs of families of pretty much all sizes.

@jackmcdade Crazy, mine just died yesterday too🤦‍♂️ Gonna wait for the MSI MPG 271KRAW16 to come out.

I'm having the worst time trying to replace my LG 5K monitor after the display port died. I tried the new BenQ 5k (MA270S) designed for MacBooks but it sucked – none of the controls were native (e.g. keyboard brightness keys don't work, volume control is on the monitor w/ cheap plastic buttons, etc) and the night shift/true tone implementation was terrible. It felt like a $200 monitor with a $1k price tag. So I returned it and just bought the new Studio Display 2, but it has so many bugs it's ridiculous. It doesn't wake w/ the MBP, I have to unplug and plug it back in. The webcam features don't work (no option for Studio Light, Center Stage, Portrait Mode, etc), and half the time the non-Thunderbolt USB ports don't work. At all. Oh and if you're in clamshell mode you can't control screen brightness or use the webcam at all either. So I submitted a return order and bought a used Studio Display 1 but thought hey, lets try that Nano Texture, I've got some glare. Wellll my eyes are wigging out after just 10 minutes and I can't do it. It's all blurry and I feel a headache coming on. 🫠 How's your week going?

@leerob Thanks, this is a huge improvement. I'm still seeing a difference in Cloud Agents in the model picker - not able to select Auto for example.

Meet the new Cursor! Very excited about this. Wanted to share a bit more of the story of how we landed here, how the product evolved, and some of the technical details on the new interface. I've been coding primarily with agents since Opus 4.5, but hadn't found an interface I loved (including our own). Agent sidebars or CLIs worked but still felt limiting to me. And our first iteration of the "agent window" wasn't good enough yet. So we went back to the drawing board to build a completely new interface for agents in December. The trend seemed pretty clear that increasingly less time would be spent in traditional IDEs. But as we started to dogfood early versions, it was very hard to give up some parts of an editor. Even if agents write 98% of the code, that last 2% of viewing files, debugging, many small edits and refactors, and having all the niceties like go to definition, LSPs, and more were really important. We couldn't remove those. So @ryolu_ and I started prototyping some ideas late Dec for a new interface. It would start simple/zen, but then allow you to still go deeper as needed. And slowly we developed enough conviction to make it real. The Cursor eng/product team then took some of those early ideas and made something 10x better than I imagined. Seriously major kudos to the team! We started fresh with this new UI in a lot of ways. "Deleting the product" is especially important as models continue to improve and the UX needs to be continually rethought. However that doesn't mean you have to throw out *all* the good ideas. Making it easy for existing users to adapt is also very important. In this new interface, we own all the pixels. We were able to design a system/architecture that takes all the learnings from Cursor 1/2 and moves away from some of the VS Code constraints we were limited by. I definitely empathize with feedback that in Cursor 2 we were moving around the UI too much and changing icons/buttons. Agents were taking over more and more work, and they started to break out of the IDE UI. We needed to iterate and try a bunch of things, and that was annoying for those of you expecting a more consistent editor experience. Making this new agent interface as a separate window actually also makes the Cursor 2.0 IDE *better*! Rather than continuing to try and extend the IDE to have agents own the entire UI, we were able to simplify and delete a lot of code by using existing VS Code patterns. Namely, agent chats are now just normal tabs like any other file. This is much more stable and familiar for doing splits/panes and all related keyboard shortcuts. A win-win-win, as they say. But also in this architecture refactor, we were able to address some local vs. cloud divergence and tech debt that had accumulated over time. The core Cursor agent harness is the same across the desktop app, web app, CLI, etc. So there really shouldn't be two code paths like: if (local) { ... } else if (cloud) { ... } Cloud agents were not used much until we gave them the ability to use a computer and record demos of their work, so now that usage has grown considerably in the past few months, it was even more important to nail this abstraction. We think cloud usage will continue to grow and be a big part of 2026. Finally (this is already a long post, oops), we have been able to really focus on performance in the new interface. I'm sure there will still be things to improve (please send them to us) but we've spent considerably more time profiling, investigating, and patching memory/cpu leaks. We are also now using the React Compiler! s/o @potetotes who has also been making a bunch of perf improvements. The end result here is that Cursor 3 feels much more pleasant to use. Faster, more reliable, less UI jank. You get to use all your favorite models, local or cloud, run automations, install plugins, get back demo videos, and more. Give it a try and lmk your feedback! We're gonna be shipping updates quickly in the coming days.

@vimtor @anomalyco @opencode Well deserved, congrats!

i've joined @anomalyco to maintain sst and support @opencode sst has always felt like the right abstraction - making complex but reliable infrastructure easy to use it's an honor to work on that with people i've admired for years

@ephraimduncan Thanks, this is working great!

You can now use Composer 2 in OpenCode with your Cursor Subscription

Great to finally see a new player in this space, will be checking this out.

@DrizzleORM Congrats!

As of today, Drizzle has become the most sustainablest ORM on Earth 🚀 PlanetScale hired entire Drizzle core team to work on Drizzle ORM full-time, which is just… WOW! I mean, I can’t believe this is happening and how amazing this is going to be... Let’s address the most important things: ▪︎ The governance of Drizzle does not and will not change ▪︎ Drizzle remains independent and open-source ▪︎ We will now work more full-timer on Drizzle ORM, Kit and Studio ▪︎ Our social media manager(me) will finally have a salary ▪︎ Drizzle v1 is going to be amazing Thank you all for using Drizzle, without you there won’t be 1.2k GitHub issues and 355 PRs, we’d live a happy life, touching grass ❤️

Claude Code prompt for blocking macOS Tahoe upgrade alerts gist.githubusercontent.com/john-griffin/3…

@mjackson Can’t wait to check it out!

Remix 3 is close now, I can taste it. The result of more than a year of work. It's going to be so good.

@mattpocockuk Yep on OpenCode

Anyone running OpenCode/Codex/Gemini CLI/Copilot CLI in your Ralph setups? Would love to get a primer on how it's working for you.

@BenjDicken Can Vitess customers get something like this please?

DuckDB is an *incredibly* powerful analytics database. A sophisticated SQL query engine paired with extensive file-format compatibility. Pairs amazingly with Postgres. Try it today on PlanetScale.

@motherduck @samlambert Yes!

Something planet-sized is coming. The queries must flow...

@ryanflorence Awesome, any chance that includes testing conventions? Ember was the only front end framework that got it right.

I jumped into some "not Remix 3 UI code" today and it felt ... I dunno ... heavy or rigid? We're working toward the first week of March for an alpha release you can use, it should have the whole breadth of our ambition, from database adapters to theme-able library components