Wasp retweeted
Watching this over my lunch today - @filipsodic has done incredible things alongside the wider team at @WaspLang, I highly recommend checking it out!
The talk I gave at NDC Oslo hosted by @NDC_Conferences became my biggest hit so far (10K+ views)!
Link: youtube.com/watch?v=Vhjo1myK…
I justify why advanced type safety constructs are more "worth it" than ever and show tricks for pushing agents into the "black hole of success" as @mattpocockuk would put it.
Give it a watch!
For all engineers using TypeScript, check out @filipsodic's talk and learn how to turn it into an even better harness for AI agents.
The talk I gave at NDC Oslo hosted by @NDC_Conferences became my biggest hit so far (10K+ views)!
Link: youtube.com/watch?v=Vhjo1myK…
I justify why advanced type safety constructs are more "worth it" than ever and show tricks for pushing agents into the "black hole of success" as @mattpocockuk would put it.
Give it a watch!
We didn't want MCP to win, but alas.
It's looking like the leader for agent connectivity. Full guide on our blog now: wasp.sh/blog/2026/11/03/mcp-…
MCP brutally mogs API as an agent connector.
…or is an API or CLI good enough?
I did a bunch of research into it and I have a fav (it’s MPC). I wrote about why and how you can optimally build all 3 into your app 🔗👇
1
6
327
Wasp is open source, and we welcome contributions.
@MartinSosic shares how to contribute to open-source projects in 2026 and beyond.
Some people are flying with AI, while some are (me) still hand-drawing blog post banners in @tldraw: wasp.sh/blog/2026/08/13/advi…
> "coding is solved"
yet here we are debating whether agents should use useState.
my hot take is that agents won't drop down to machine code like some people predict.
instead, we'll build higher-level abstractions with best practices built-in, so agents write LESS code:
The biggest change in Wasp 0.26 is making it easy to run multiple coding agents at the same time, each in its own worktree.
- No more "port already taken"
- Commands can't overwrite each other
- Nothing to set up
@filipsodic on how it works. 👇
wasp.sh/blog/2026/10/27/wasp…
the wasp cli just got some awesome agent tools, and some more really sweet ones are in the works.
The latest release made Wasp's CLI much friendlier to agents, worktrees, and orchestrators.
I wrote a short feature announcement explaining how we did it: wasp.sh/blog/2026/10/27/wasp…
Our @filipsodic shares how we made Wasp friendlier to agents with our 0.26 release.
Check it out!
The latest release made Wasp's CLI much friendlier to agents, worktrees, and orchestrators.
I wrote a short feature announcement explaining how we did it: wasp.sh/blog/2026/10/27/wasp…
2
129
Wasp retweeted
This is what our framework understands about your app: a full picture, starting from data models to data ops and live data on the wire.
Wasp Studio has always been my pet project, and with AI it's so much easier to try different things out.
A follow-up release: Wasp 0.26.1
Install it with:
npm i -g @wasp.sh/wasp-cli@latest
To address Node.js security vulnerabilities, we are raising the minimum Node version to 24.22.1.
This fixes the October 2026 Node vulnerabilities, including a remote code execution bug in Node's Brotli decoder.
A couple of notes related to this release:
- you can already use any newer Node.js with your current Wasp version
- 0.26.1 moves the minimum, so no one stays on a vulnerable one
- if you deploy with the Dockerfile Wasp generates, 0.26.1 also moves your server image to node:24.22.1, so rebuild and redeploy.
1
109
This week, we shared our road to Wasp 1.0. Until we get there, we'll ship regularly and share more.
Starting with 0.26:
- better for coding agents,
- a new "wasp show" command,
- safer auth defaults, and
- a revamped docs structure.
Full write-up 👇
wasp.sh/blog/2026/10/23/wasp…
Next stop: 1.0!
After 5 years and 100+ releases, Wasp v1.0 is in the works!
ETA: ~6 months
What's coming:
→ Every core feature reworked: Auth, RPC, Jobs, API, Deployment, etc
→ Full Stack Modules: install Stripe like a package, backend included
→ Native Windows, no WSL
→ Production-ready
Details (incl. roadmap): wasp.sh/blog/2026/10/20/wasp…
1
118
Wasp retweeted
After 5 years and 100+ releases, Wasp v1.0 is in the works!
ETA: ~6 months
What's coming:
→ Every core feature reworked: Auth, RPC, Jobs, API, Deployment, etc
→ Full Stack Modules: install Stripe like a package, backend included
→ Native Windows, no WSL
→ Production-ready
Details (incl. roadmap): wasp.sh/blog/2026/10/20/wasp…
Wasp retweeted
One way to think about Wasp: what NixOS is to your operating system, Wasp is to your web app.
You get to declaratively specify the core parts of your app (pages, cron jobs, data operations, email sender, ...) and Wasp will take care of it all working as it should, together.
Current web app stacks feel like a bunch of scripts duct-taped together, completely unaware of each other, just like OS-es did before Nix came around.
Wasp is the first web framework to let you define an explicit "schema" for your web app.
Think of it as a database schema, but for auth, routes, cron jobs, data operations, email sending, and so on.
What your app does isn't anymore buried in the code, config files, and folder conventions, but has its own dedicated layer and lives next to your code.
That's me!
Wasp is the first web framework to let you define an explicit "schema" for your web app.
Think of it as a database schema, but for auth, routes, cron jobs, data operations, email sending, and so on.
What your app does isn't anymore buried in the code, config files, and folder conventions, but has its own dedicated layer and lives next to your code.
5
582
Wasp retweeted
Replying to @MathewTolic
@MathewTolic who is doing Operations with us at @WaspLang is really doing some awesome things with AI lately! I wonder what is the "Operations <> AI" scene right now, encouraged him to share more on Twitter, I think he will have quite some tips to share.












