A simple framework for humans. Server-first React, running on the Cloudflare platform. Simple to build. Easy to maintain.
- Tweets 2,918
- Following 94
- Followers 10,297
- Likes 3,167
RedwoodSDK retweeted
this shipped in agents@latest, and I got some of the mcp client stuff working in agents-starter (!!!) might just add it to the base class for everyone (!!!) so you can build your own ui/client/whatever. demoing in the podcast in 5 mins
pr merged, jeremy's kicking the tires to make sure it's all good, will release later today
ok now to poke at making the agents starter an mcp client ootb. this might take a while.
3
1
42
3,550
Most frameworks treat the document as a global: a html page with a head, body, etc, a one-size-fits-all concern. RedwoodSDK treats it as just another component - one you control. Want a different document per route? You're in control!
3
2
36
8,755
RedwoodSDK: "aka my dream of a fullstack toolkit built on CF"
Stuff I'm going to play with as soon as I find time:
- @samgoodwin89's Alchemy (kinda like a TS-native SST)
- @RedwoodJS SDK (aka my dream of a fullstack toolkit built on CF) with RSC support
Cool stuff happening here. Enjoyed chatting a bunch with Sam at React Miami!
1
5
775
Redwood trees are the tallest trees in the world.
They all started as tiny seeds. 🌱
We’ve just crossed 200 stars on GitHub and we’re growing slowly but surely
1
23
1,279
RedwoodSDK retweeted
almost 20 years, and still the biggest thrill is having my friends use (and like!) my software.
3
1
76
2,938
RT @appfactory: In "this week in redwood" I mentioned that we don't see value in writing yet another "vibe coding interface," but I do see…
1
Tutorial: Streaming React Server Function Responses to the Client.
> stream partial responses from the server to the client, enabling real-time updates and improved user experiences.
rwsdk.com/blog/redwoodsdk-st…
5
549
RedwoodSDK retweeted
For a long time, software was something you used made by companies, served to you.
Then the tools got better. The platforms got cheaper. AI lowered the barrier.
And suddenly, people didn’t need permission. They started writing their own tools again: Not just apps, but custom scripts, internal systems, weird ideas made real.
We call these people 'high-agency.'
But I call what they make something else:
Personal Software.
It’s not built to scale. It’s built to serve.
It doesn’t raise a Series A. It scratches an itch.
It’s not SaaS. It’s yours.
1
2
14
1,228
RedwoodSDK retweeted
@RedwoodJS support has dropped in Alchemy with bonus D1 + @DrizzleORM migrations built-in.
Still some rough edges to work out since RWSDK has strong opinions around wrangler, but functional.
This all it takes to bind D1, apply migrations, and deploy to CF 🤗
2
1
13
2,211
RedwoodSDK retweeted
Exciting React news coming in the newsletter today
Make sure to subscribe so you don't miss it 😉
2
2
29
4,333
Check out this quick guide to get started with realtime streaming to client using React Server Components in RedwoodSDK
rwsdk.com/blog/redwoodsdk-st…
13
595
RedwoodSDK retweeted
Cloudflare. Placement = smart.
We split Session Storage & Compute: Your user's data is near them, compute and data are near each other.
If the network is the computer then the framework should work like an operating system and actually think about where the compute goes.
1
3
25
3,350
Cloudflare, Typescript, Vite, React and Web APIs.
The browser is the framework.
The network is the framework.
4
8
179
10,081
> Our stance: there’s no moat in vibe coding. We're more interested in supporting those tools with smarter context, not building another one.
RWSDK is Typescript, Vite, React, and Cloudflare. No magic. A request is traceable from entry to exit. Every byte over the wire is yours.
nitter.catsarch.com/RedwoodJS/status/19146…
5
754
Our standard starter now ships with a set of Cursor rules, please test them out!
github.com/redwoodjs/sdk/tre…
9
594