<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Wasp Blog</title>
        <link>https://wasp.sh/blog</link>
        <description>Wasp Blog</description>
        <lastBuildDate>Tue, 03 Nov 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[MCP vs API vs CLI: How Should AI Agents Connect to Your App?]]></title>
            <link>https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app</link>
            <guid>https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app</guid>
            <pubDate>Tue, 03 Nov 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Should Claude, ChatGPT, and other AI agents use your app through an MCP server, a REST API, or a CLI? When each wins, and how to build all three.]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="tldr">TL;DR<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#tldr" class="hash-link" aria-label="Direct link to TL;DR" title="Direct link to TL;DR" translate="no">​</a></h2>
<p>You’re building a web app and you need to make it agent-friendly, but you’re not sure how. <strong>Should you build an MCP server, a REST API, a CLI, or all three?</strong> And how do you add them so they bring the most value to agents?</p>
<p>To put it simply, an <strong>MCP shines in the agent-native world because it tells agents what they should do, on both the server and client</strong> (e.g. Claude Code or the ChatGPT desktop app), and is better suited for human-in-the-loop tasks. Meanwhile, APIs and CLIs tend to focus on what agents can do, with emphasis mainly on the server.</p>
<p>So, in summary, here is the general advice I'd give to builders when deciding which tools they should expose to agents:</p>
<!-- -->
<ul>
<li class="">
<p><strong>Build a high-quality MCP server and REST API at the same time, on one layer of operations</strong>. Put your server logic in plain functions, and let each surface be a thin adapter over them. Once that layer exists, building any additional surface on top is relatively easy.</p>
</li>
<li class="">
<p><strong>Put most of your care into the MCP server</strong>. That's where agents get the best experience. MCP is a standard built specifically for agents, after all, and the spec continues to improve nicely.</p>
</li>
<li class="">
<p><strong>Use the API for code that runs on its own</strong>. APIs are still great for raw data exports, bulk writes, and anything that runs without an agent, like a nightly sync or another company's integration. Agents also prefer an API when they're writing a script they'll rerun, and many clients don't support code mode for MCP yet.</p>
</li>
<li class="">
<p><strong>A CLI probably isn't necessary</strong>, unless e.g. agents need to read local files when interacting with your app. But it's easy to expose one if you've got a good API as the foundation.</p>
</li>
</ul>
<p>There’s a lot more to creating great agent-facing tools for your web apps, and the article goes into more detail below.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-do-you-make-your-app-usable-by-ai-agents">How do you make your app usable by AI agents?<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#how-do-you-make-your-app-usable-by-ai-agents" class="hash-link" aria-label="Direct link to How do you make your app usable by AI agents?" title="Direct link to How do you make your app usable by AI agents?" translate="no">​</a></h2>
<p>It’s been a wild couple years, and trying to figure out how to build web apps that agents can use isn’t easy. As a developer relations engineer at <a class="" href="https://wasp.sh/">Wasp</a>, I personally didn't know where to start.</p>
<p><strong>Is an API good enough? Is MCP really a necessary solution? Is a CLI really the most performant tool for agents?</strong> And when I do add these tools, how do I add them properly so that they bring the most value to agents?</p>
<p>Those are the questions I set out to answer with this post, and it has two parts:</p>
<ul>
<li class=""><strong>Part 1</strong> explains why I think MCP should get most of your attention, and where an API and a CLI still beat it.</li>
<li class=""><strong>Part 2</strong> shows how you can build all three on top of the same code using an example app as support.</li>
</ul>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/agent-friendly-app/agent-friendly-app.svg" alt="How do you choose the right agent tool(s) for your web app?" class="themedComponent_bsp7 themedComponent--light_A5ZL"><img src="https://wasp.sh/img/agent-friendly-app/agent-friendly-app-dark.svg" alt="How do you choose the right agent tool(s) for your web app?" class="themedComponent_bsp7 themedComponent--dark_LZz2"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">How do you choose the right agent tool(s) for your web app?</figcaption></figure></div>
<p>Although the builder community is still divided on what the <a href="https://x.com/levelsio/status/2031943074151104634?s=20" target="_blank" rel="noopener noreferrer" class="">best tools for agents are</a>, what is clear is that agents are the new users of the web.</p>
<p><a href="https://blog.cloudflare.com/agentic-web/" target="_blank" rel="noopener noreferrer" class="">More than half of internet traffic</a> already isn't human, and daily requests from AI agents are growing like crazy. In 2026 alone agent traffic grew by more than 1,700%. So it makes sense that your apps be as agent-friendly as possible.</p>
<p>To help me figure out how to do that for myself, I built an example app with a dashboard, an MCP server, a REST API, and a CLI. It’s called <a href="https://linkly.wasp.run/" target="_blank" rel="noopener noreferrer" class="">Linkly</a> and it’s an open-source link shortener. I kept the app simple so the focus would stay on the agent side, but it still has everything you’d expect from a full-featured web app: user accounts, logins, a bunch of actions, and docs. Unless I say otherwise, all the examples in this post come from it, and you can find the repo <a href="https://github.com/vincanger/linkly-api-mcp-cli" target="_blank" rel="noopener noreferrer" class="">here</a>.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/agent-friendly-app/two-layers.svg" alt="This diagram is a sneak peek of things to come, e.g. the four surfaces (Dashboard, MCP, API, and CLI) all calling the same createLink operation on the server" class="themedComponent_bsp7 themedComponent--light_A5ZL"><img src="https://wasp.sh/img/agent-friendly-app/two-layers-dark.svg" alt="This diagram is a sneak peek of things to come, e.g. the four surfaces (Dashboard, MCP, API, and CLI) all calling the same createLink operation on the server" class="themedComponent_bsp7 themedComponent--dark_LZz2"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">This diagram is a sneak peek of things to come, e.g. the four surfaces (Dashboard, MCP, API, and CLI) all calling the same createLink operation on the server.</figcaption></figure></div>
<p>To begin, let’s take a closer look at MCP, how it compares to an API or a CLI, and the defining features that separate it from the pack.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="part-1-what-to-build-mcp-vs-api-vs-cli">Part 1: What to build (MCP vs API vs CLI)<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#part-1-what-to-build-mcp-vs-api-vs-cli" class="hash-link" aria-label="Direct link to Part 1: What to build (MCP vs API vs CLI)" title="Direct link to Part 1: What to build (MCP vs API vs CLI)" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-is-mcp">What is MCP?<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#what-is-mcp" class="hash-link" aria-label="Direct link to What is MCP?" title="Direct link to What is MCP?" translate="no">​</a></h3>
<p><a href="https://modelcontextprotocol.io/" target="_blank" rel="noopener noreferrer" class="">MCP (Model Context Protocol)</a> is a standard way to connect and tell an AI agent what it can do with your app. Your app runs an MCP server that lists its actions as <em>tools</em>: each one has a name, a plain-language description of what it does, and the inputs it takes. Anthropic introduced it as an open standard, and it's now supported by pretty much every major AI app, including ChatGPT, Claude, Cursor, Codex, Grok Bot, and VS Code.</p>
<p>In practice, you paste an app's MCP URL into your agent, log in once, and ask it a question that your app would have the answer to. The agent knows right away which tools to use and can call them quickly and easily.</p>
<p>Using Linkly as the example, you ask "how did my launch link do last week?" and the agent calls Linkly's <code>get_link_stats</code> tool and answers with your real numbers. You don't need to copy an API key, read any docs, or write any code.</p>
<p>One thing that’s important to remember is that when you use an agent, there are really two parts:</p>
<ul>
<li class=""><strong>The model</strong> is the AI that reads, reasons, and decides what to do next.</li>
<li class=""><strong>The client</strong> is the app that runs the model: Claude Code, the Codex app, Grok Bot, etc. You might also hear it called the harness or the agent app. The MCP spec calls it the <em>MCP client</em>, so that's the term I'll use from here on out. It connects to your MCP server, loads your tools into the model's context, makes the actual calls when the model asks, stores your logins, and owns the screen you're looking at.</li>
</ul>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/agent-friendly-app/agent-two-parts.svg" alt="Your agent is two parts: the MCP client (harness / app), the interaction layer with the chat window you type into, and the LLM underneath that decides what to do. The client talks to the model and to your MCP server" class="themedComponent_bsp7 themedComponent--light_A5ZL"><img src="https://wasp.sh/img/agent-friendly-app/agent-two-parts-dark.svg" alt="Your agent is two parts: the MCP client (harness / app), the interaction layer with the chat window you type into, and the LLM underneath that decides what to do. The client talks to the model and to your MCP server" class="themedComponent_bsp7 themedComponent--dark_LZz2"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Your agent is two parts: the MCP client (harness / app), the interaction layer with the chat window you type into, and the LLM underneath that decides what to do. The client talks to the model and to your MCP server.</figcaption></figure></div>
<p>An API only ever defines what happens on the server side. It expects a certain set of inputs and gives a defined response. There’s nothing about an API that enforces the harness/agent app to behave a certain way.</p>
<p>MCP, on the other hand, sets a standard for how the server and client should respond to certain tools and workflows, and that's where most of its present and future advantages come from. I’ll explain more about how this works later in the article.</p>
<p>But to put it more broadly, MCP just gives you and your agent a nicer, more curated experience because <strong>it standardizes how things should be done on the server</strong> <em><strong>and</strong></em> <strong>client side</strong>.</p>
<p>MCP is also maturing really fast. The <a href="https://modelcontextprotocol.io/specification/2026-07-28" target="_blank" rel="noopener noreferrer" class="">2026-07-28 revision</a> made the protocol stateless. Clients are tackling context bloat with tool search and <a href="https://www.anthropic.com/engineering/code-execution-with-mcp" target="_blank" rel="noopener noreferrer" class="">code mode</a>, which were the first real gripes developers had with MCP, and rightly so. Connecting lots of servers to one agent is no longer the problem it was just a few months ago.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-mcp-gives-you-that-an-api-cant">What MCP gives you that an API can't<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#what-mcp-gives-you-that-an-api-cant" class="hash-link" aria-label="Direct link to What MCP gives you that an API can't" title="Direct link to What MCP gives you that an API can't" translate="no">​</a></h3>
<p>An API, and its OpenAPI document, describes your server: its endpoints and their inputs and outputs. It says nothing about what the client does on the other side. MCP standardizes both sides, so your server can count on the client doing certain things for your users. In practice, that means:</p>
<ul>
<li class=""><strong>The client handles the login.</strong> MCP comes with a standard way to log in. It's built on OAuth, and the major clients (Claude, ChatGPT, Cursor, Grok Bot) already know how to do it. So you paste an MCP URL into your agent, a page opens in your browser, you log in and click Allow, and that's it. The client keeps the token and sends it with every request, so the model never sees it. An API can use OAuth too, but there's no standard way for an agent to find and complete it, so you usually end up creating an API key and pasting it somewhere the model can read it.</li>
<li class=""><strong>Permissions decide what the model sees, and how it asks for more.</strong> Linkly hides the tools a connection isn't allowed to use, so if the user only granted read access, write tools like <code>create_link</code> never enter the agent's context. If you'd rather show every tool, MCP also has a standard way to ask for a missing permission when a tool needs it by showing your consent screen again, for that permission only (more on that <a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-mcp-server" class="">in Part 2</a>). An API has neither.</li>
<li class=""><strong>Your instructions come along with the tools.</strong> Once connected, Linkly's server tells the client what Linkly is and how its tools fit together, and each tool's description says when to use it and what to do next. The agent can search and load only the tools it needs. With an API, the agent needs your instructions or its entire docs so it can work out what to call with each session. It does that again for every API and every session, and that reading fills up its context.</li>
<li class=""><strong>People can find you from inside the agent.</strong> Claude and ChatGPT both have directories of MCP connectors, so once you're listed, someone can find your app and connect it in a couple of clicks without leaving the chat. An API has nothing like that: someone has to know it exists, find the docs, and set it up keys.</li>
<li class=""><strong>Some agents can only reach you through MCP.</strong> In a normal chat, the model has no shell, and the sandbox blocks most outside hosts by default, so connectors are the easy, supported way in.</li>
<li class=""><strong>Your server can ask the user directly, without going through the model.</strong> When an action needs the user's OK, like deleting a link, your server can have the client ask the user directly, for example by opening a confirmation page. The model never sees the question, so it can't answer for them. An API’s response, even with confirmation, will always be passed through the model. This is the big one, so let's look at it closely.</li>
</ul>
<h4 class="anchor anchorTargetStickyNavbar_gvNQ" id="making-sure-a-human-actually-confirms">Making sure a human actually confirms<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#making-sure-a-human-actually-confirms" class="hash-link" aria-label="Direct link to Making sure a human actually confirms" title="Direct link to Making sure a human actually confirms" translate="no">​</a></h4>
<p>Some actions should never happen without the user having the final say, like deleting something that can't be undone. MCP is the only protocol that’s currently capable of routing confirmation steps straight to the human user via the client. An API or CLI can't, because the question and its response always get routed through the model, and the model could potentially answer it for you.</p>
<p>Here's an example from Linkly. Say you have two short links to <a class="" href="https://wasp.sh/">wasp.sh</a>: an old one from last year's launch, and a new one, <code>/r/wasp</code>, which is printed on your conference badges. You ask your agent to delete the old one, and it picks the wrong one.</p>
<p><strong>With an API</strong>, there's no standard way to ask for confirmation at all, though you can require a parameter like <code>confirm=true</code>. <strong>With a CLI</strong>, you'd require a flag like <code>--yes</code>. Either way, the question goes back to the model, which can just add the parameter itself and follow through with the delete confirmation itself.</p>
<p><strong>With MCP</strong>, Linkly answers the <code>delete_link</code> call with an <a href="https://modelcontextprotocol.io/specification/2026-07-28/client/elicitation" target="_blank" rel="noopener noreferrer" class="">elicitation</a>: a request for the client to open a confirmation page on Linkly. The model is skipped entirely and the client opens the link for you. The page shows the short link, where it goes, and which app asked. You have time to spot <code>/r/wasp</code>, click Cancel, and nothing is deleted. Even though the confirmation step skipped the model, it is still told that you cancelled, so it can go find the right link.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/agent-friendly-app/confirmation-paths.svg" alt="With a confirm flag, the agent sets confirm=true itself and /r/wasp is deleted. With MCP, your app's confirmation page shows /r/wasp, you click Cancel, and nothing is deleted" class="themedComponent_bsp7 themedComponent--light_A5ZL"><img src="https://wasp.sh/img/agent-friendly-app/confirmation-paths-dark.svg" alt="With a confirm flag, the agent sets confirm=true itself and /r/wasp is deleted. With MCP, your app's confirmation page shows /r/wasp, you click Cancel, and nothing is deleted" class="themedComponent_bsp7 themedComponent--dark_LZz2"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">With a confirm flag, the agent sets confirm=true itself and /r/wasp is deleted. With MCP, your app's confirmation page shows /r/wasp, you click Cancel, and nothing is deleted.</figcaption></figure></div>
<p>Think of it like giving an assistant your credit card. If the store asks "are you sure?" at checkout, the assistant just says yes. But if your bank texts <em>your</em> phone to approve the payment, the final confirmation skips your assistant entirely. A <code>confirm=true</code> flag is the checkout question. Elicitation is the text to your phone: the server asks the client, and the client asks you.</p>
<div style="display:flex;justify-content:center;margin:1rem 0"><figure style="width:100%;margin:0"><video width="100%" controls="" aria-label="Claude Code deleting a Linkly link with URL-mode elicitation: you ask it to delete the link, the client opens Linkly's confirmation page, and you decide"><source src="/img/agent-friendly-app/elicitation-delete-link.mp4" type="video/mp4"></video><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Claude Code deleting a Linkly link with URL-mode elicitation: you ask it to delete the link, the client opens Linkly's confirmation page, and you decide.</figcaption></figure></div>
<h4 class="anchor anchorTargetStickyNavbar_gvNQ" id="mcp-apps-and-events">MCP Apps and Events<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#mcp-apps-and-events" class="hash-link" aria-label="Direct link to MCP Apps and Events" title="Direct link to MCP Apps and Events" translate="no">​</a></h4>
<p>And the list of things only MCP can do keeps growing. Take, for example, these two recently added MCP features.</p>
<p>First, is MCP apps, which put UI, like an interactive chart or a form, right in the chat. Here's a different demo I built to show it: a Wasp prototype where the agent and I visually plan a full-stack app's architecture in an editor right inside Claude, and then the agent writes the code once I'm happy with the plan:</p>
<div style="display:flex;justify-content:center;margin:1rem 0"><figure style="width:100%;margin:0"><video width="100%" controls="" aria-label="A Wasp prototype MCP App: planning a full-stack app's architecture with the agent inside a Claude chat, then having it write the code"><source src="/img/agent-friendly-app/mcp-app-wasp-studio.mp4" type="video/mp4"></video><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">A Wasp prototype MCP App: planning a full-stack app's architecture with the agent inside a Claude chat, then having it write the code</figcaption></figure></div>
<p>And <a href="https://mixed-news.com/en/chatgpt-mcp-events-webhooks-draft-spec-work-chats/" target="_blank" rel="noopener noreferrer" class="">MCP Events</a>, which ChatGPT shipped on September 29, let your server tell the agent when something changes, so it can act on it automatically without anyone typing a prompt.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="MCP events being used to ping an agent to resolve issues when a Cloudflare worker errors out" src="https://wasp.sh/img/agent-friendly-app/mcp-events-cloudflare.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">MCP events being used to ping an <a href="https://x.com/mattzcarey/status/2109736726440604042" target="_blank" rel="noopener noreferrer" class="">agent to resolve issues when a Cloudflare worker errors out</a>.</figcaption></figure></div>
<p>Client support for both of these features is still uneven (as of October 2026), so it's important to consider fallbacks. Only some of them can open Linkly's confirmation page, for example, and not all can show an MCP App (Although the major ones like ChatGPT and Claude can). So each feature benefits from a fallback for the clients that lag behind, and the nice thing is that a link to your app is almost always a good one:</p>
<ul>
<li class="">
<p>Linkly can't draw a chart in every chat, so every stats result includes a <code>dashboardUrl</code> that opens the same chart in the app.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Click stats for /r/wasp in Linkly's dashboard, grouped by referrer" src="https://wasp.sh/img/agent-friendly-app/click-stats-by-referrer.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Click stats for /r/wasp in Linkly's dashboard, grouped by referrer</figcaption></figure></div>
</li>
<li class="">
<p>Clients that can't open the confirmation page get the same page as a link in the tool result, for the agent to pass along.</p>
</li>
<li class="">
<p>And instead of a form in the chat, <code>get_dashboard_url</code> can return a link to Linkly's create form, already filled in.</p>
</li>
</ul>
<p>When a client adds support, the better version just starts working for your users.</p>
<p>Needless to say, I'm bullish on the MCP space and think it will blossom into a really cool ecosystem with interesting new workflows for app builders. With that said, there are still times when an API or CLI might be a better fit for agents than an MCP. It just depends on the type of data coming from your app, along with your user's typical workflows.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="when-an-api-or-cli-beats-mcp">When an API or CLI beats MCP<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#when-an-api-or-cli-beats-mcp" class="hash-link" aria-label="Direct link to When an API or CLI beats MCP" title="Direct link to When an API or CLI beats MCP" translate="no">​</a></h3>
<p>None of this means APIs are bad for agents. They're <a href="https://x.com/RhysSullivan/status/2070630745891365008" target="_blank" rel="noopener noreferrer" class="">"probably fine for 90% of applications"</a>: agents call them easily, they're the right tool for raw data exports and bulk jobs, and with a well-written OpenAPI doc, an agent can even turn one into an MCP server for you.</p>
<p>And for some jobs, like bulk updates or exporting raw data, agents are better off writing deterministic tools (e.g. scripts, internal tools, jobs) that call the API directly, rather than going through MCP tools. For example, here are two tasks in Linkly, done both ways:</p>
<table><thead><tr><th>Task (Linkly)</th><th>OpenAPI + a script</th><th>MCP tools</th></tr></thead><tbody><tr><td><strong>A job you'll rerun:</strong> "Tag every link to example.com as <code>partner</code>, and do it again each month"</td><td>List, filter, then <code>PATCH</code> each match. A script anyone on the team can read, rerun, and schedule.</td><td>With code mode, one loop over <code>update_link</code>, but it lives in one conversation. Without it, 300 round trips through the model.</td></tr><tr><td><strong>Curated:</strong> "How did my launch link do last week?"</td><td>One <code>GET /api/v1/links/{id}/stats</code> call.</td><td>One <code>get_link_stats</code> call from any client. Its description tells the model to share the <code>dashboardUrl</code>, which opens an interactive chart in Linkly, and to use <code>get_top_links</code> to compare links.</td></tr></tbody></table>
<p>Notice that the API's advantage isn't really volume. Without code mode, every row an MCP tool returns, and every update, passes through the model's context. But clients with <a href="https://www.anthropic.com/engineering/code-execution-with-mcp" target="_blank" rel="noopener noreferrer" class="">code mode</a> close that gap: the model writes a loop over your tools (that's the "code"), runs it in the client's sandbox (that's the "mode"), and only the result comes back. For an agent doing a job once, that's just as good as a script.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/agent-friendly-app/code-mode-paths.svg" alt="Tagging 300 links through MCP: without code mode, every call and result passes through the model; with code mode, the client runs the loop in a sandbox and only the last line comes back" class="themedComponent_bsp7 themedComponent--light_A5ZL"><img src="https://wasp.sh/img/agent-friendly-app/code-mode-paths-dark.svg" alt="Tagging 300 links through MCP: without code mode, every call and result passes through the model; with code mode, the client runs the loop in a sandbox and only the last line comes back" class="themedComponent_bsp7 themedComponent--dark_LZz2"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Tagging 300 links through MCP: without code mode, every call and result passes through the model; with code mode, the client runs the loop in a sandbox and only the last line comes back</figcaption></figure></div>
<p>It's important to note that not all clients have code mode so far, though. OpenCode turns it on by default, and Codex has it behind a flag. Claude Code and the Claude apps do have tool search on by default though, which loads the tools the model needs for that task only, keeping context cleaner for those that have many MCP servers connected.</p>
<p>Some apps fix this on the server side instead, with a query tool. PostHog, for example, <a href="https://x.com/posthog/status/2109706665033691359" target="_blank" rel="noopener noreferrer" class="">created a read-only <code>executeSql</code> tool</a>, and "Why did signups drop?" went from four separate tool calls to one query. Agents are good at writing SQL, and the database does the heavy lifting instead of the model's context. That only covers reads, though, and it mostly makes sense if your app is all about data (more on that in the <a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-mcp-server" class="">MCP checklist</a>).</p>
<p>What code mode doesn't change, though, is who's calling. A nightly sync, an internal tool, or another company's integration will be better off using an API. And when a job is worth keeping, you probably want your agent to write a script around it, rather than repeatedly calling your tools from within a chat thread.</p>
<p>For the curated task, though, MCP brings a lot of advantages. Both surfaces can answer "How did my launch link do last week?" in one call. But the MCP tool works in any client where you've connected Linkly (e.g. you can't always connect to APIs in agent desktop apps for security reasons), and it comes with the know-how about what to do next, like sharing the chart link or comparing links with an additional <code>get_top_links</code> tool call.</p>
<p>CLIs work well too, but only for agents with a shell. They're definitely at an advantage when an agent needs to interact with local files on the user's own machine, too. If this is the case, a CLI makes sense. A remote MCP server can't read your disk, so to shorten 500 URLs from a file, the agent has to pass every URL through its context, whereas a CLI reads the file itself:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic"># Shorten every URL in a local file</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">cat</span><span class="token plain"> urls.txt </span><span class="token operator" style="color:#393A34">|</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">xargs</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-n1</span><span class="token plain"> linkly links create</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Export every link to a local file</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">linkly links list </span><span class="token parameter variable" style="color:#36acaa">--all</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">--json</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">&gt;</span><span class="token plain"> links.json</span><br></div></code></pre></div></div>
<p>The agent only has to write one line, the data goes straight from your disk to the API without passing through the model, and anyone can rerun it later.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="which-tools-should-you-expose-to-ai-agents">Which tools should you expose to AI agents?<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#which-tools-should-you-expose-to-ai-agents" class="hash-link" aria-label="Direct link to Which tools should you expose to AI agents?" title="Direct link to Which tools should you expose to AI agents?" translate="no">​</a></h3>
<p>To put it simply, an MCP shines in the agent-native world because it tells agents what they <em>should</em> do, on both the server and client, and is better suited for human-in-the-loop tasks. Meanwhile, APIs and CLIs tend to focus on what agents <em>can</em> do, with emphasis mainly on the server.</p>
<p>So, in summary, here is the general advice I'd give to builders when deciding which tools they should expose to agents:</p>
<p><strong>Build a high-quality MCP server and REST API at the same time, on one layer of operations.</strong> Put your server logic in plain functions, and let each surface be a thin adapter over them. Once that layer exists, building any additional surface on top is relatively easy.</p>
<p><strong>Put most of your care into the MCP server.</strong> That's where agents get the best experience. MCP is a standard built <em>specifically</em> for agents, after all.</p>
<p><strong>Use the API for code that runs on its own.</strong> APIs are still great for raw data exports, bulk writes, and anything that runs without an agent, like a nightly sync or another company's integration. Agents also prefer an API when they're writing a script they'll rerun, and many clients don't support code mode for MCP yet.</p>
<p><strong>A CLI probably isn't necessary</strong>, unless e.g. agents need to read local files when interacting with your app. But it's easy to expose one if you've got a good API as the foundation.</p>
<p>Now that we’ve got the theoretical guideline out of the way, it’s time to build this into your app. Part 2 below gives you a structured walkthrough, along with feature checklists, and uses the Linkly code and repo as a reference, so you can be sure you’re bringing the most value to agents as you build these tools into your app.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="part-2-how-to-build-it-a-guide-you-can-hand-to-your-agent">Part 2: How to build it (a guide you can hand to your agent)<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#part-2-how-to-build-it-a-guide-you-can-hand-to-your-agent" class="hash-link" aria-label="Direct link to Part 2: How to build it (a guide you can hand to your agent)" title="Direct link to Part 2: How to build it (a guide you can hand to your agent)" translate="no">​</a></h2>
<p data-copy-section-button="true">Want your coding agent to build this into your app? Copy this whole section and paste it into your agent along with your request.<!-- --> <button type="button" class="button button--primary button--sm">Copy this guide for your agent</button></p>
<p>Here’s the order I'd build everything in, which is also the order the rest of this section follows:</p>
<ol>
<li class=""><a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-foundation-operations-underneath-every-surface" class=""><strong>Put your logic in operations</strong></a><strong>,</strong> one function per action, so every surface is a thin adapter over the same code.</li>
<li class=""><a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-mcp-server" class=""><strong>Expose them through MCP</strong></a><strong>,</strong> with task-shaped tools and good descriptions written for the model.</li>
<li class=""><a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-rest-api" class=""><strong>And through REST</strong></a><strong>,</strong> with an OpenAPI document generated from the same schemas.</li>
<li class=""><a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#one-oauth-server-in-front-of-both" class=""><strong>Put OAuth in front of your MCP server</strong></a>, and let people choose each permission. Your API can use the same server, but agents calling it will mostly use personal access tokens for now.</li>
<li class=""><a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#destructive-actions-wait-for-the-human-for-oauth-connections" class=""><strong>Make destructive actions wait for the human</strong></a>, at least for OAuth connections.</li>
<li class=""><a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#a-cli-if-your-users-have-shells" class=""><strong>Add a CLI</strong></a>, if your users really need it.</li>
<li class=""><a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#help-agents-find-you-from-your-domain" class=""><strong>Help agents find your agent-facing tools</strong></a> from your domain alone.</li>
</ol>
<p>Each of the sections below goes into detail on one of these steps: how Linkly does it, with the actual code, plus a list of rules I'd follow and the mistakes I'd avoid.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-foundation-operations-underneath-every-surface">The foundation: operations underneath every surface<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-foundation-operations-underneath-every-surface" class="hash-link" aria-label="Direct link to The foundation: operations underneath every surface" title="Direct link to The foundation: operations underneath every surface" translate="no">​</a></h3>
<p>By splitting your app into two layers, every surface you build gets the same logic underneath:</p>
<ol>
<li class=""><strong>Operations:</strong> your business logic, one function per thing a user can do.</li>
<li class=""><strong>Surfaces:</strong> thin adapters that expose those operations to each kind of caller.</li>
</ol>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/agent-friendly-app/two-layers.svg" alt="Four callers land on the same createLink operation" class="themedComponent_bsp7 themedComponent--light_A5ZL"><img src="https://wasp.sh/img/agent-friendly-app/two-layers-dark.svg" alt="Four callers land on the same createLink operation" class="themedComponent_bsp7 themedComponent--dark_LZz2"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Four callers land on the same createLink operation</figcaption></figure></div>
<p>When you click "Create link" in Linkly's dashboard, it calls the exact same <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/links/service.ts#L80-L111" target="_blank" rel="noopener noreferrer" class=""><code>createLink</code></a> function that an agent calls through MCP, or a script calls through the REST API.</p>
<p>Everything that makes your app <em>your app</em> lives in the operation: <a class="" href="https://wasp.sh/blog/2022/11/29/permissions-in-web-apps">who's allowed to do what</a>, what counts as valid input, the business rules, and the error messages. Here's <code>createLink</code>, simplified:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">async</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">function</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">createLink</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">principal</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> Principal</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> input</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> LinkInput</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> prisma </span><span class="token punctuation" style="color:#393A34">}</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> Deps</span><span class="token punctuation" style="color:#393A34">)</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token builtin">Promise</span><span class="token operator" style="color:#393A34">&lt;</span><span class="token plain">LinkOut</span><span class="token operator" style="color:#393A34">&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">requireScope</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">principal</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"links:write"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// who's allowed</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> data </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">parseInput</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">LinkInput</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> input</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// what counts as valid input</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">data</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">slug</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">assertSlugFree</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">prisma</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> data</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">slug</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// the rules: a taken slug throws a "conflict" error</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">toLinkOut</span><span class="token punctuation" style="color:#393A34">(</span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> prisma</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">link</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">create</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> data</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">...</span><span class="token plain">data</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> userId</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> principal</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">userId </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// ...otherwise, retry random slugs until one is free</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><br></div></code></pre></div></div>
<p>Every operation has this shape: who's calling (a <code>Principal</code>, more on that in the <a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#one-oauth-server-in-front-of-both" class="">OAuth section</a>), the input, and its dependencies, like the database. There's no <code>req</code>, <code>res</code>, or MCP anywhere in it, so any surface can call it, and you can test it without starting a server.</p>
<p>Each surface just translates by turning its own kind of login into a <code>Principal</code>, passing the input along, and formatting the result. In Linkly, that's one line per surface:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// Dashboard (an operation)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">runOperation</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=&gt;</span><span class="token plain"> links</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">createLink</span><span class="token punctuation" style="color:#393A34">(</span><span class="token function" style="color:#d73a49">sessionPrincipal</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">context</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> args</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> deps</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// REST API: POST /api/v1/links</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">res</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">status</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">201</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">json</span><span class="token punctuation" style="color:#393A34">(</span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> links</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">createLink</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">principal</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> req</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">body </span><span class="token operator" style="color:#393A34">??</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> deps</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// MCP server: the create_link tool</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function-variable function" style="color:#d73a49">handler</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">principal</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> input</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=&gt;</span><span class="token plain"> links</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">createLink</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">principal</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> input</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> deps</span><span class="token punctuation" style="color:#393A34">)</span><br></div></code></pre></div></div>
<p>Errors stay consistent too. A taken slug is one error in the operation, and <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/shared/errors.ts" target="_blank" rel="noopener noreferrer" class="">each surface shows it its own way</a>, e.g. a toast in the dashboard, a <code>409</code> from the API, a tool error the agent can read and retry, and exit code 6 in the CLI.</p>
<p>The one thing to watch out for is someone adding a feature to one surface and forgetting the others. So Linkly has a few plain unit tests that fail when the surfaces drift apart. The <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/mcp/parity.test.ts#L10-L35" target="_blank" rel="noopener noreferrer" class="">main one</a> is just a list: every dashboard operation maps to an MCP tool or to a written reason it's dashboard-only, like "consent has to come from the human". <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/tests/cliParity.test.ts" target="_blank" rel="noopener noreferrer" class="">Similar</a> <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/tests/destructiveFlags.test.ts" target="_blank" rel="noopener noreferrer" class="">tests</a> cover the CLI and the REST API. Gaps are fine, as long as each one is a decision and not something someone forgot.</p>
<p>If you already have an app, your logic probably lives in controllers or UI code, and you don't have to move it all at once. Pick the 3–5 actions an agent would use most. For Linkly, that's creating a link, listing links, and getting a link's stats. Move each one into an operation, point your dashboard at it first so your own users test it, and then exposing it to agents is just adding adapters.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-mcp-server">The MCP server<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-mcp-server" class="hash-link" aria-label="Direct link to The MCP server" title="Direct link to The MCP server" translate="no">​</a></h3>
<p>Once your operations exist, the MCP server and the REST API are two thin layers over the same functions, so you can build them in whichever order you like. The difference is who reads them. A REST API is read by a developer, or their agent, who reads the docs and then writes code. MCP tools are read by the model every time it decides what to call. So most of the work in an MCP server is in how the tools are described.</p>
<p>A tool's description has to carry the know-how, not just the reference, e.g. when to use this tool instead of a similar one, what to do after it, and what to show the user. If you just generate one tool per endpoint, you get the API reference without some core benefits of MCP. Here's <code>create_link</code> in full:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// src/links/mcp.ts</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">defineTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"create_link"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  title</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Create a link"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  toolset</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"links"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  scope</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"links:write"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  description</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token string" style="color:#e3116c">"Creates a short link that redirects to `destinationUrl`. Omit `slug` for a random 7-character one; a taken slug returns a conflict error. Returns the new link with its `shortUrl` to share. To change it later use update_link."</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  input</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    destinationUrl</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> destinationUrlSchema</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    slug</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> slugSchema</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">optional</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">describe</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"Custom slug (3–40 chars of a-z, 0-9, '-'). Omit it for a random one."</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    title</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> titleSchema</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">optional</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">describe</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"Optional human-readable label for the link."</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    tags</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> tagsSchema</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">optional</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">describe</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"Up to 10 tags (each up to 30 chars) for grouping and filtering. Stored lowercase."</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  output</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> LinkOut</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">shape</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  annotations</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> readOnlyHint</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">false</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> destructiveHint</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">false</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> idempotentHint</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">false</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> openWorldHint</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">false</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function-variable function" style="color:#d73a49">handler</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">principal</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> input</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=&gt;</span><span class="token plain"> links</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">createLink</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">principal</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> input</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> deps</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><br></div></code></pre></div></div>
<p>The input schemas and the permission (<code>scope</code>) are the same ones every other surface uses. What's written just for MCP is the description, which says what happens with a taken slug, what comes back, and which tool to use next, and the annotations, which tell the client whether the tool only reads or changes something.</p>
<p>Here's the checklist I'd hold any MCP server to:</p>
<ul>
<li class=""><strong>Descriptions say when to use the tool</strong> <em><strong>instead of</strong></em> <strong>a related one</strong>, and what to do after common errors.</li>
<li class=""><strong>Cover every capability</strong> while avoiding near-duplicate tools the model has to choose between.</li>
<li class=""><strong>Don't merge across a permission or risk boundary.</strong> Reading a link and deleting it stay separate tools.</li>
<li class=""><strong>Decide what happens when a connection is missing a permission.</strong> Linkly hides the tools whose permission the user didn't grant (simple, works in every client). The MCP spec also suggests using a <a href="https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization#step-up-authorization-flow" target="_blank" rel="noopener noreferrer" class="">step-up flow</a>: you list every tool, and when one gets called without the right permission, the client asks the user for just that permission and retries.</li>
<li class=""><strong>Add annotations and output schemas to every tool, and instructions to the server.</strong> The instructions are a few sentences the client hands the model up front: what your app is, and how its tools fit together.</li>
<li class=""><strong>Add a "who am I" tool.</strong> Linkly's <code>whoami</code> returns the account, its permissions, and whether deletes need confirmation, so an agent can check what it's allowed to do before it tries.</li>
<li class=""><strong>Accept the identifiers people actually use.</strong> People know a Linkly link by its slug, not its ID, so every tool that takes a link accepts either one.</li>
<li class=""><strong>Make every error say what to do next.</strong> When a link doesn't exist, Linkly answers: <code>not_found: Link "abc" not found. Use list_links to find valid IDs or slugs.</code></li>
<li class=""><strong>Link back to your app.</strong> Many of Linkly's tool results include a <code>dashboardUrl</code>, so the user can open the same view in the dashboard.</li>
<li class=""><strong>Leave tool search and code mode to the client.</strong> Most clients already load only the tools they need, and more are adding code mode, so expose plain, well-described tools instead of hiding them behind your own <code>search()</code> and <code>execute()</code>.</li>
<li class=""><strong>Add tools for your docs.</strong> Linkly's <code>search_docs</code> and <code>read_doc</code> let agents look up how the product works before they guess.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-rest-api">The REST API<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-rest-api" class="hash-link" aria-label="Direct link to The REST API" title="Direct link to The REST API" translate="no">​</a></h3>
<p>The REST API has less to invent, but a few things still matter most for agents and the code they write:</p>
<ul>
<li class=""><strong>Generate the OpenAPI document from the same schemas</strong> the operations validate with, so the documented inputs can't drift from the real ones.</li>
<li class=""><strong>Put the permissions and the login in the OpenAPI document.</strong> Each Linkly operation lists the scope it needs, and the document explains both ways to log in, a personal access token or OAuth. An agent can work out what token it needs without asking.</li>
<li class=""><strong>Mark risk with <code>x-destructive</code>.</strong> The HTTP method doesn't tell an agent what's dangerous, since a <code>POST</code> can be just as irreversible as a <code>DELETE</code>. So every Linkly operation has an <code>x-destructive</code> field, and it's <code>true</code> only for <code>DELETE /links/{id}</code>.</li>
<li class=""><strong>Return one error shape.</strong> Every Linkly error is <code>{ "error": { "code": "conflict", "message": "…" } }</code> with the matching status, so code can branch on <code>code</code> and an agent can read the same message the MCP tool would give it.</li>
<li class=""><strong>Paginate with cursors.</strong> A cursor marks where the last page ended, so a script walking through thousands of links doesn't skip or repeat any when new ones are added along the way, which page numbers can't promise.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="one-oauth-server-in-front-of-both">One OAuth server in front of both<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#one-oauth-server-in-front-of-both" class="hash-link" aria-label="Direct link to One OAuth server in front of both" title="Direct link to One OAuth server in front of both" translate="no">​</a></h3>
<p>Here's what connecting to Linkly looks like for an agent. The user pastes Linkly's MCP URL into their client, a browser window opens on Linkly, they log in if they need to, and they see this:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Linkly's consent screen with permissions asking whether to allow Claude Code (claude.ai) to access your Linkly account" src="https://wasp.sh/img/agent-friendly-app/consent-screen.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Linkly's consent screen with permissions asking whether to allow Claude Code (claude.ai) to access your Linkly account.</figcaption></figure></div>
<p>That's the whole setup. Nobody creates a token or copies it anywhere, and nobody has to register an OAuth app in a dashboard first. The client keeps the token and attaches it to every request on its own, so the model never sees it.</p>
<p>Two things make that work without any setup:</p>
<ul>
<li class=""><strong>The client finds the login from the URL alone.</strong> Its first request has no token, so Linkly answers with a <code>401</code> that points to a metadata document, and that document says where to log in and where to get tokens.</li>
<li class=""><strong>The client's ID is a URL.</strong> This is called CIMD (Client ID Metadata Documents). Claude Code's ID, for example, is a URL on claude.ai that points to a small JSON file with its name and where to send the user back after they log in. Linkly fetches that file the first time it sees the client, so any client can connect without registering first. It's also where the "App address" on the consent screen comes from, which is the domain the user is really trusting.</li>
</ul>
<p>If you want to see every step, including where each code and token is along the way, here's the full flow:</p>
<figure style="margin:1.5rem 0"><iframe src="/img/agent-friendly-app/cimd-oauth-flow.html?embed=1" title="Step through how an MCP client logs in with CIMD OAuth" loading="lazy" style="width:100%;height:900px;border:0;display:block;color-scheme:light"></iframe><figcaption style="font-size:0.9em;margin-top:0.5rem"><a href="https://wasp.sh/img/agent-friendly-app/cimd-oauth-flow.html">Open the walkthrough on its own page →</a></figcaption></figure>
<h4 class="anchor anchorTargetStickyNavbar_gvNQ" id="permissions">Permissions<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#permissions" class="hash-link" aria-label="Direct link to Permissions" title="Direct link to Permissions" translate="no">​</a></h4>
<p>The checkboxes on the consent screen come from Linkly's <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/shared/scopes.ts" target="_blank" rel="noopener noreferrer" class="">one list of permissions</a>, the same list the operations check with <code>requireScope</code>. A few rules make them work well:</p>
<ul>
<li class=""><strong>Ticking write also ticks read.</strong> Updating a link sends the whole link back as a result, so a connection that can change links can already see them anyway.</li>
<li class=""><strong>Grants are checked on every request.</strong> If a user unticks "View click analytics" on the Connected apps page, those tools are gone on the agent's next call.</li>
<li class=""><strong>Users can take permissions away later, but never add more than the app asked for.</strong></li>
<li class=""><strong>Tokens are short-lived.</strong> Access tokens last an hour, and refresh tokens are replaced every time they're used. If an old refresh token shows up again, Linkly assumes it was stolen and revokes the connection.</li>
</ul>
<p>However someone logs in, they end up as the same kind of caller, a <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/shared/principal.ts" target="_blank" rel="noopener noreferrer" class=""><code>Principal</code></a>, so the operations never need to know how.</p>
<h4 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-rest-api-can-use-the-same-server">The REST API can use the same server<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-rest-api-can-use-the-same-server" class="hash-link" aria-label="Direct link to The REST API can use the same server" title="Direct link to The REST API can use the same server" translate="no">​</a></h4>
<p>Agents don't log in to APIs with OAuth on their own yet. MCP clients run this flow because the MCP spec tells them how to find the login and what to send, and there's nothing like that for a plain REST API. So today, when an agent calls Linkly's API, the user creates a personal access token in Linkly's settings, picks its permissions, and hands it over.</p>
<p>Linkly still puts <code>/api/v1</code> behind the same OAuth server, because once the server exists it costs almost nothing, and other callers need it. A CLI can open the browser to log in, the way <code>gh auth login</code> does, so the token never gets pasted into a chat. And if another developer's app wants to act for Linkly users, OAuth is the standard way to do it. Each token only works on the surface it was issued for, so an MCP token won't work on the API.</p>
<p>If your auth provider supports the MCP authorization spec, use it. Otherwise, everything here is standard OAuth, so a coding agent can build it from Linkly's <a href="https://github.com/vincanger/linkly-api-mcp-cli/tree/main/src/oauth" target="_blank" rel="noopener noreferrer" class=""><code>src/oauth/</code></a> folder.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="destructive-actions-wait-for-the-human-for-oauth-connections">Destructive actions wait for the human, for OAuth connections<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#destructive-actions-wait-for-the-human-for-oauth-connections" class="hash-link" aria-label="Direct link to Destructive actions wait for the human, for OAuth connections" title="Direct link to Destructive actions wait for the human, for OAuth connections" translate="no">​</a></h3>
<p>In Part 1, I showed why the confirmation has to come from your server and not from a flag the model can set. Here's how Linkly builds it. (In the Part 1 video, Claude Code was in auto mode, where it approves most tool calls without asking me, and the delete still waited for me.)</p>
<div style="display:flex;justify-content:center;margin:1rem 0"><figure style="width:100%;margin:0"><video width="100%" controls="" aria-label="Claude Code deleting a Linkly link with URL-mode elicitation"><source src="/img/agent-friendly-app/elicitation-delete-link-2.mp4" type="video/mp4"></video><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Claude Code deleting a Linkly link with URL-mode elicitation</figcaption></figure></div>
<p><strong>Start with a</strong> <a class="" href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents"><strong>confirmation page in your app</strong></a><strong>.</strong> When an agent calls <code>delete_link</code>, Linkly doesn't delete anything yet. It saves a <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/deeplinks/pendingActions.ts" target="_blank" rel="noopener noreferrer" class="">pending deletion</a> and makes a <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/deeplinks/ui/ConfirmActionPage.tsx" target="_blank" rel="noopener noreferrer" class="">page</a> that shows the short link, where it goes, and which app asked. Only the user who owns the link can confirm it there, logged in to Linkly, and the page works once and expires after 15 minutes. Every surface uses this same page.</p>
<p><strong>Then get the user to that page.</strong> How depends on who's calling:</p>
<ul>
<li class=""><strong>MCP clients that support URL-mode elicitation</strong> open the page for the user. Linkly checks what each request says the client supports.</li>
<li class=""><strong>Every other MCP client</strong> gets the page as a link in the tool result (<code>status: "confirmation_required"</code> with a <code>confirmUrl</code>), and the agent passes it along. The REST API does the same with a <code>202 Accepted</code>. This is weaker, since it depends on the agent sharing the link, but the agent still can't confirm for you.</li>
<li class=""><strong>The CLI</strong> refuses to delete without <code>--yes</code>, and the error tells the agent exactly what to run:</li>
</ul>
<div class="language-text codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-text codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token plain">Refusing to delete without --yes. Re-run: linkly links delete summer-sale --yes</span><br></div></code></pre></div></div>
<p>The agent can add <code>--yes</code> itself, so this one only prevents accidents and makes the delete easy to spot in the command your agent asks to run.</p>
<p>I'd build the link version first, since it works in every client, and then add URL mode on top of it.</p>
<p><strong>Why a page and not a form?</strong> MCP elicitation can also ask a question with a form in the chat, but then the answer comes from the client, and your server has to trust it. With a page, the confirmation happens in your app, in the user's own session, so you check your own record of what they clicked. I'd use a form for low-stakes questions like "Tag these 12 links as <code>partner</code>?", and a page for anything that needs the real user, like deletes, payments, or connecting another account. And marking the tool with <code>destructiveHint</code> isn't enough on its own, because it's only a hint: some clients ask the user and some don't.</p>
<p><strong>A few details that took me a while to get right:</strong></p>
<ul>
<li class="">
<p><strong>Wait a little for the click.</strong> Clients retry the call as soon as the page opens, usually before the user has clicked anything. So instead of asking again, Linkly waits up to 20 seconds for the decision, and after a few rounds falls back to the link.</p>
</li>
<li class="">
<p><strong>Don't trust what comes back with the retry.</strong> The question goes out with a <code>requestState</code> that the client sends back with the answer. Sign it, tie it to the user and the pending deletion, and let each deletion be confirmed only once.</p>
</li>
<li class="">
<p><strong>Let each connection choose.</strong> The consent screen's "Require confirmation for destructive actions" toggle is on by default. Dashboard sessions and personal access tokens delete right away, because in the dashboard you're already the human, and a script has to run without anyone clicking. The catch is that an agent you hand a PAT can also delete without asking you, and since that's how most agents call the API right now, it's worth keeping in mind.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Linkly's Connected apps page: a 'Connect an AI agent' card with the MCP server URL and a prompt to copy, and Claude Code listed with its permissions, a Confirm deletions toggle, and a Revoke button" src="https://wasp.sh/img/agent-friendly-app/connected-apps.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Linkly's Connected apps page: a "Connect an AI agent" card with the MCP server URL and a prompt to copy, and Claude Code listed with its permissions, a Confirm deletions toggle, and a Revoke button</figcaption></figure></div>
</li>
<li class="">
<p><strong>Offer a way back.</strong> <code>delete_link</code>'s description ends with "Consider update_link with archived: true instead if they might want it back." An archived link stops redirecting, but nothing is lost.</p>
</li>
</ul>
<p>And since each surface marks deletes its own way (<code>x-destructive</code> in the OpenAPI doc, <code>destructiveHint</code> on the MCP tool, and <code>--yes</code> on the CLI), Linkly has a <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/tests/destructiveFlags.test.ts" target="_blank" rel="noopener noreferrer" class="">test</a> that checks they all agree.</p>
<p>The code for all of this is in the repo: <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/deeplinks/pendingActions.ts" target="_blank" rel="noopener noreferrer" class=""><code>src/deeplinks/pendingActions.ts</code></a> for the pending deletion, <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/mcp/confirmations.ts" target="_blank" rel="noopener noreferrer" class=""><code>src/mcp/confirmations.ts</code></a> for URL-mode elicitation and the retries, and <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/cli/src/program.ts#L151" target="_blank" rel="noopener noreferrer" class=""><code>cli/src/program.ts</code></a> for the CLI's <code>--yes</code>.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="a-cli-if-your-users-have-shells">A CLI, if your users have shells<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#a-cli-if-your-users-have-shells" class="hash-link" aria-label="Direct link to A CLI, if your users have shells" title="Direct link to A CLI, if your users have shells" translate="no">​</a></h3>
<p>In <a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#when-an-api-or-cli-beats-mcp" class="">Part 1</a>, I said a CLI is mostly worth it if your users have agents with a shell on their own machine, especially for working with local files. If that's you, here's how Linkly's is built.</p>
<p>Linkly's CLI is just a client of the REST API, with its types <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/cli/src/api.ts" target="_blank" rel="noopener noreferrer" class="">generated from the OpenAPI document</a>. Most of what makes it work well for agents comes down to a few rules:</p>
<ul>
<li class=""><strong>Never prompt.</strong> An agent can't answer an interactive prompt, so the command would just hang. If input is missing, return an error that names the flag to add instead.</li>
<li class=""><strong>Print JSON when piped,</strong> in the shape the API documents, and add a <code>--json</code> flag for when it isn't.</li>
<li class=""><strong>Send errors to stderr, with exit codes an agent can branch on:</strong> <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/cli/src/errors.ts#L2-L10" target="_blank" rel="noopener noreferrer" class="">2 for usage, 3 unauthorized, 4 forbidden, 5 not found, 6 conflict</a>.</li>
<li class=""><strong>Write <code>--help</code> with examples.</strong> That's how an agent figures out how to use your CLI.</li>
</ul>
<p>Linkly's CLI logs in with a personal access token (<code>linkly auth login --token lk_pat_...</code>, or <code>LINKLY_TOKEN</code>), saved in a config file only you can read. Since the REST API sits behind the same OAuth server, a CLI could open a browser to log in instead, the way <code>gh auth login</code> and <code>gcloud auth login</code> do. Linkly's CLI doesn't do that yet, though.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="help-agents-find-you-from-your-domain">Help agents find you from your domain<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#help-agents-find-you-from-your-domain" class="hash-link" aria-label="Direct link to Help agents find you from your domain" title="Direct link to Help agents find you from your domain" translate="no">​</a></h3>
<p>Say a user tells their agent to "use myapp.com". The agent fetches your homepage, and if it's a single-page app, all it gets back is an empty <code>&lt;div id="root"&gt;</code> and a script tag, with nothing to follow. Once an agent has your MCP URL, the <code>401</code> from the <a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#one-oauth-server-in-front-of-both" class="">OAuth section</a> takes it the rest of the way, but there's no single standard yet for getting from a domain to that URL. Different agents look in different places, so I'd cover all of them. They're cheap, and Linkly does each one:</p>
<ul>
<li class="">
<p><strong>An <code>llms.txt</code> at the root of your domain.</strong> It's a short Markdown file that tells an agent how to connect. Linkly <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/discovery/llmsTxt.ts" target="_blank" rel="noopener noreferrer" class="">generates it at build time</a> from the same paths and docs the app uses, so it can't go stale.</p>
</li>
<li class="">
<p><strong>A prerendered landing page with a visible "For AI agents" section.</strong> Agents usually fetch your page and read it as text, so the text needs to be in the HTML before any JavaScript runs. Linkly <a class="" href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering">prerenders its homepage and docs</a> (<a class="" href="https://wasp.sh/docs/advanced/prerendering"><code>prerender: true</code></a> on the route in Wasp), and the homepage has a <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/app/HomePage.tsx#L45-L63" target="_blank" rel="noopener noreferrer" class="">"For AI agents" card</a> with the MCP URL and a link to <code>llms.txt</code>.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Linkly's prerendered homepage with a 'For AI agents' card that gives the MCP server URL and the llms.txt URL" src="https://wasp.sh/img/agent-friendly-app/homepage-for-ai-agents.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Linkly's prerendered homepage with a "For AI agents" card that gives the MCP server URL and the llms.txt URL</figcaption></figure></div>
</li>
<li class="">
<p><strong>Your OpenAPI document at well-known places.</strong> Linkly serves it at <code>/.well-known/openapi.json</code> for agents that guess that path, lists it in <code>/.well-known/api-catalog</code> (RFC 9727, the one registered path for this), and adds a <code>Link: &lt;…/openapi.json&gt;; rel="service-desc"</code> header to <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/shared/http.ts#L38-L42" target="_blank" rel="noopener noreferrer" class="">every <code>/api/v1</code> response</a>. Code that follows links finds the document from any API call.</p>
</li>
</ul>
<p>The <code>llms.txt</code> only says what the OpenAPI document can't: which way to connect, what to do without OAuth, and the rules. Here's Linkly's, trimmed:</p>
<div class="language-markdown codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-markdown codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token title important punctuation" style="color:#393A34">#</span><span class="token title important"> Linkly</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token blockquote punctuation" style="color:#393A34">&gt;</span><span class="token plain"> Linkly shortens links and counts their clicks. Everything the dashboard can do, an AI agent can do too: through Linkly's MCP server, or through its REST API.</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token title important punctuation" style="color:#393A34">##</span><span class="token title important"> MCP (recommended)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token list punctuation" style="color:#393A34">-</span><span class="token plain"> </span><span class="token url" style="color:#36acaa">[</span><span class="token url content" style="color:#36acaa">MCP server</span><span class="token url" style="color:#36acaa">](</span><span class="token url" style="color:#36acaa">https://myapp.com/mcp</span><span class="token url" style="color:#36acaa">)</span><span class="token plain">: use this if you support MCP. Log in with OAuth in the user's browser: there's no API key to copy and no client registration.</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token title important punctuation" style="color:#393A34">##</span><span class="token title important"> REST API</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token list punctuation" style="color:#393A34">-</span><span class="token plain"> </span><span class="token url" style="color:#36acaa">[</span><span class="token url content" style="color:#36acaa">OpenAPI document</span><span class="token url" style="color:#36acaa">](</span><span class="token url" style="color:#36acaa">https://myapp.com/api/v1/openapi.json</span><span class="token url" style="color:#36acaa">)</span><span class="token plain">: every endpoint, the scope each one needs, which operations are destructive (</span><span class="token code-snippet code keyword" style="color:#00009f">`x-destructive`</span><span class="token plain">), and how to log in.</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token list punctuation" style="color:#393A34">-</span><span class="token plain"> If you can't do OAuth, ask the user for a personal access token from </span><span class="token url" style="color:#36acaa">[</span><span class="token url content" style="color:#36acaa">Tokens</span><span class="token url" style="color:#36acaa">](</span><span class="token url" style="color:#36acaa">/settings/tokens</span><span class="token url" style="color:#36acaa">)</span><span class="token plain">, with only the scopes the task needs.</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token title important punctuation" style="color:#393A34">##</span><span class="token title important"> Rules</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token list punctuation" style="color:#393A34">-</span><span class="token plain"> Never ask the user for their Linkly password. Log in with OAuth, or ask for a personal access token.</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token list punctuation" style="color:#393A34">-</span><span class="token plain"> Ask the user before any operation marked </span><span class="token code-snippet code keyword" style="color:#00009f">`x-destructive: true`</span><span class="token plain">, such as deleting a link.</span><br></div></code></pre></div></div>
<p>The password rule matters more than it looks. With the user's password, an agent could log in as them directly and skip the consent screen, along with every permission the user would have picked there.</p>
<p>All of this is still guesswork on the agent's side, though. The most reliable way in is a URL the user hands over themselves, so Linkly's Connected apps page also has a <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/oauth/ui/ConnectionsPage.tsx#L75-L94" target="_blank" rel="noopener noreferrer" class="">"Connect an AI agent" card</a> with the MCP URL and a ready prompt to copy: "Read <a href="https://myapp.com/llms.txt" target="_blank" rel="noopener noreferrer" class="">https://myapp.com/llms.txt</a> and connect to my Linkly account."</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="hardening-for-agent-callers">Hardening for agent callers<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#hardening-for-agent-callers" class="hash-link" aria-label="Direct link to Hardening for agent callers" title="Direct link to Hardening for agent callers" translate="no">​</a></h3>
<p>Once agents can use your app, it has a new kind of caller, one that reads everything you send it and retries whenever something fails. Here are two risks I'd plan for, and one habit I'd pick up.</p>
<ul>
<li class=""><strong>Prompt injection through your own data.</strong> Everything your tools return ends up in the model's context, and the model can't always tell data apart from instructions. So it's worth asking who can write the text your tools send back. In Linkly, anyone who clicks a short link controls the <code>Referer</code> header, and referrers show up in <code>get_link_stats</code>. That's a stranger's text landing in the user's agent. So Linkly <a href="https://github.com/vincanger/linkly-api-mcp-cli/blob/main/src/analytics/clicks.ts#L26-L34" target="_blank" rel="noopener noreferrer" class="">only keeps the hostname</a>, like <code>news.ycombinator.com</code>, and while it stores the visitor's user agent, it never returns it. You can't filter out every planted instruction, so limit what outsiders can write, and keep the earlier defenses in place. That way, even an agent that gets fooled can only do what the user allowed, and it still can't delete anything without them.</li>
<li class=""><strong>Retries and loops.</strong> Agents retry a lot, and a confused one can call the same tool over and over. Rate-limit per connection, not just per user, so one runaway agent doesn't lock the user out of their own dashboard. And answer with a <code>429</code> and a <code>Retry-After</code> header, so the agent knows to wait instead of trying again right away. Linkly doesn't do this yet, since I left rate limiting out to keep the example small, but I'd add it before letting real agents in.</li>
<li class=""><strong>Test with a few real clients, not just one.</strong> I'd start with Claude Code on localhost, then use a tunnel for claude.ai and ChatGPT, since they only connect to a public HTTPS URL. Clients really do differ, for example in which ones can open the delete confirmation page.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-state-of-mcp-october-2026">The state of MCP (October 2026)<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#the-state-of-mcp-october-2026" class="hash-link" aria-label="Direct link to The state of MCP (October 2026)" title="Direct link to The state of MCP (October 2026)" translate="no">​</a></h2>
<p>Most of what's in this post should hold up for a long time: operations underneath, task-shaped tools on top, one login for every surface, and destructive actions that wait for the human. The details around them are still moving quickly, though. Here's where things stand as of October 2026:</p>
<ul>
<li class=""><strong>The protocol went stateless</strong> in the 2026-07-28 revision, and clients are still catching up.</li>
<li class=""><strong>CIMD is the recommended way for clients to identify themselves,</strong> and Dynamic Client Registration is deprecated, but CIMD itself is still an IETF draft, and client support varies.</li>
<li class=""><strong>Elicitation, MCP Apps, and Events work in some clients and not others.</strong> URL-mode elicitation, for example, works in the Claude Code CLI, in Codex and OpenCode with a setting turned on, and not yet in ChatGPT (which does support form mode), Claude Desktop, or claude.ai. Events shipped in ChatGPT, while the spec for them is still a draft.</li>
<li class=""><strong>Code mode</strong> is spreading through agent frameworks and servers like Cloudflare's, but the current advice is to let the MCP client implement tool search and code mode, not the MCP server. On the client side, OpenCode does code mode by default and Codex has it behind a flag, while Claude Code and the Claude apps stick to tool search for now.</li>
<li class=""><strong>WebMCP could bring tools into the browser.</strong> It's a proposed browser API that lets a web page register its own tools, so an agent browsing your site can call them instead of clicking around and reading screenshots. ChatGPT's desktop browser <a href="https://x.com/OpenAIDevs/status/2092344959248761263" target="_blank" rel="noopener noreferrer" class="">added support in August</a>, so ChatGPT and Codex can use those tools when you visit a compatible site. Claude doesn't support it yet. It's still an experimental W3C proposal in a Chrome origin trial, though, so <a href="https://x.com/hot_town/status/2092481550096924926?s=20" target="_blank" rel="noopener noreferrer" class="">I think it's worth learning about and I'd keep an eye on it</a>.</li>
</ul>
<p>None of that changes the design, and it's why every feature in this post has a <a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#mcp-apps-and-events" class="">fallback</a>, which is almost always a link. When a client adds support, the better version just starts working for your users.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="go-build-your-own">Go build your own<a href="https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app#go-build-your-own" class="hash-link" aria-label="Direct link to Go build your own" title="Direct link to Go build your own" translate="no">​</a></h2>
<p>If you want to build this yourself, the easiest way is to hand this post, and the Linkly repo, to your coding agent as a reference. <a href="https://github.com/vincanger/linkly-api-mcp-cli" target="_blank" rel="noopener noreferrer" class="">The repo</a> has every piece from this post, and its <a href="https://github.com/vincanger/linkly-api-mcp-cli#where-to-find-things" target="_blank" rel="noopener noreferrer" class="">README</a> shows where each one lives.</p>
<p>Linkly is built with <a class="" href="https://wasp.sh/">Wasp</a>, and a lot of the plumbing here, like turning <a class="" href="https://wasp.sh/docs/features/data/operations/overview">operations</a> into MCP tools and REST routes, or running the OAuth server, is <a class="" href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module">the kind of thing we'd like Wasp to handle for you automatically</a>. So <a class="" href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming">look out for these features</a> as part of the Wasp framework in the future!</p>
<p>Needless to say, I'm a big fan of where these tools are headed, especially MCP. Agents are going to be a big part of how people use your app, and it's a good time to start building for them.</p>
<p>If you want to try Wasp in the meantime, install the CLI with <code>npm i -g @wasp.sh/wasp-cli</code>, check out the <a href="https://github.com/wasp-lang/wasp" target="_blank" rel="noopener noreferrer" class="">GitHub repo</a>, and come say hi on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a>.</p>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>ai agents</category>
            <category>mcp</category>
            <category>api</category>
            <category>webdev</category>
        </item>
        <item>
            <title><![CDATA[Wasp Is Now Friendlier To AI Agents]]></title>
            <link>https://wasp.sh/blog/2026/10/27/wasp-agent-friendly</link>
            <guid>https://wasp.sh/blog/2026/10/27/wasp-agent-friendly</guid>
            <pubDate>Tue, 27 Oct 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Wasp 0.26 makes it easy for agents to work on different tasks in your Wasp project at the same time using Git worktrees. You can now have your orchestrator run multiple worktrees and agents, each using wasp start and wasp start db without stepping on each other's toes.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/banner.webp" alt="The Wasp logo connected to three terminal windows, each running wasp start in a different Git worktree on its own port." class="themedComponent_bsp7 themedComponent--light_A5ZL"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/banner-dark.webp" alt="The Wasp logo connected to three terminal windows, each running wasp start in a different Git worktree on its own port." class="themedComponent_bsp7 themedComponent--dark_LZz2"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>Wasp 0.26 improves support for agent orchestrators and running multiple instances of a Wasp project in Git worktrees:</p>
<ul>
<li class="">Incompatible Wasp commands no longer interfere with each other. For example,
executing <code>wasp build</code> when <code>wasp start</code> is already running won't corrupt the
generated code.</li>
<li class="">Wasp no longer runs into <em>"Port is already taken"</em> errors when agents
spin up multiple dev servers across worktrees. Both <code>wasp start</code> and <code>wasp start db</code>
now dynamically look for free ports.</li>
</ul>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-are-git-worktrees-and-why-do-agent-orchestrators-need-them">What are Git worktrees and why do agent orchestrators need them?<a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#what-are-git-worktrees-and-why-do-agent-orchestrators-need-them" class="hash-link" aria-label="Direct link to What are Git worktrees and why do agent orchestrators need them?" title="Direct link to What are Git worktrees and why do agent orchestrators need them?" translate="no">​</a></h2>
<p>Before we dig into the new features, let's quickly discuss agent orchestrators and Git worktrees.</p>
<p>If you know all about this, feel free to skip right to the <a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#whats-new-in-wasp" class="">next section</a>. If not, here's a refresher:</p>
<ul>
<li class="">An <strong>agent orchestrator</strong> is a tool for coordinating agents. It helps you assign tasks to agents and keep track of their work, without juggling thirteen terminal windows and losing your mind. Examples of popular agent orchestrators are <a href="https://github.com/herdrdev/herdr" target="_blank" rel="noopener noreferrer" class="">Herdr</a>, <a href="https://github.com/raine/workmux" target="_blank" rel="noopener noreferrer" class="">Workmux</a>, and <a href="https://www.conductor.build/" target="_blank" rel="noopener noreferrer" class="">Conductor</a>.</li>
<li class=""><strong><a href="https://git-scm.com/docs/git-worktree" target="_blank" rel="noopener noreferrer" class="">Git worktrees</a></strong> are a Git feature that lets you check out multiple branches of a Git project at the same time, each branch in its own directory.</li>
</ul>
<p>Developers use agent orchestrators to simultaneously work on multiple features. The usual workflow looks like this:</p>
<ol>
<li class="">The orchestrator gives each agent an isolated Git worktree.</li>
<li class="">Each agent works on a feature inside its worktree.</li>
<li class="">The orchestrator lets you know whenever an agent needs your input.</li>
<li class="">When a feature is done, you review the diff and use the orchestrator to merge it into <code>main</code>, deleting the agent's worktree.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="whats-new-in-wasp">What's new in Wasp?<a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#whats-new-in-wasp" class="hash-link" aria-label="Direct link to What's new in Wasp?" title="Direct link to What's new in Wasp?" translate="no">​</a></h2>
<p>Previous versions of Wasp didn't have great out-of-the-box support for orchestrator workflows.
You <em>could</em> set them up, but the process was more involved than we would have liked.</p>
<p>With Wasp 0.26, you can let your agents loose in as many Git worktrees as you want.
They'll stay out of each other's way.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-to-use-this">How to use this?<a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#how-to-use-this" class="hash-link" aria-label="Direct link to How to use this?" title="Direct link to How to use this?" translate="no">​</a></h2>
<p>There's nothing special you need to do.
Just keep running Wasp commands as you've always done and leave the rest to Wasp.</p>
<p>Read on to understand what makes this experience possible.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="wasp-commands-no-longer-fight-over-the-file-system">Wasp commands no longer fight over the file system<a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#wasp-commands-no-longer-fight-over-the-file-system" class="hash-link" aria-label="Direct link to Wasp commands no longer fight over the file system" title="Direct link to Wasp commands no longer fight over the file system" translate="no">​</a></h3>
<p>Before Wasp 0.26, running multiple Wasp commands in the same project could cause them to write over each other's outputs.
For example, executing <code>wasp build</code> would break an already running instance of <code>wasp start</code>.</p>
<p>Wasp 0.26 prevents such conflicts:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/commands-in-same-project.svg" alt="Before Wasp 0.26, wasp start and wasp build both read and wrote .wasp/out and corrupted its contents. After Wasp 0.26, Wasp blocks the second command." class="themedComponent_bsp7 themedComponent--light_A5ZL" style="width:500px"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/commands-in-same-project-dark.svg" alt="Before Wasp 0.26, wasp start and wasp build both read and wrote .wasp/out and corrupted its contents. After Wasp 0.26, Wasp blocks the second command." class="themedComponent_bsp7 themedComponent--dark_LZz2" style="width:500px"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Conflicting commands in the same project: Wasp now blocks the second one instead of letting it corrupt the output.</figcaption></figure></div>
<p>If someone runs two different commands that write to the same files, Wasp catches it and prints a clear error message.
Both you and your agents can then decide what to do about it:</p>
<div class="terminal"><div class="terminal__header"><div class="terminal__dots"><span></span><span></span><span></span></div><span class="terminal__title">Terminal 1</span><div class="terminal__dots" style="visibility:hidden"><span></span><span></span><span></span></div></div><pre class="terminal__body"><span class="terminal__ansi-prompt">$ </span><span class="terminal__ansi-default">wasp start</span>
<!-- -->
<span class="terminal__ansi-yellow">🐝 --- Starting compilation and setup phase. Hold tight... ------------------------</span>
<!-- -->
<span class="terminal__ansi-yellow">🐝 --- Compiling wasp project... --------------------------------------------------</span>
<!-- -->
<span class="terminal__ansi-yellow">[</span><span class="terminal__ansi-default">  </span><span class="terminal__ansi-yellow">Wasp</span><span class="terminal__ansi-default">  </span><span class="terminal__ansi-yellow">]</span><span class="terminal__ansi-default"> Starting npm install</span>
</pre></div>
<div class="terminal"><div class="terminal__header"><div class="terminal__dots"><span></span><span></span><span></span></div><span class="terminal__title">Terminal 2</span><div class="terminal__dots" style="visibility:hidden"><span></span><span></span><span></span></div></div><pre class="terminal__body"><span class="terminal__ansi-prompt">$ </span><span class="terminal__ansi-default">wasp build</span>
<!-- -->
<span class="terminal__ansi-red">❌ --- [Error] Wasp project is already in use: ------------------------------------</span>
<!-- -->
<span class="terminal__ansi-red">Another Wasp command (PID 12345) is already running for this project. Stop it before running this command.</span>
</pre></div>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="wasp-projects-no-longer-fight-over-ports">Wasp projects no longer fight over ports<a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#wasp-projects-no-longer-fight-over-ports" class="hash-link" aria-label="Direct link to Wasp projects no longer fight over ports" title="Direct link to Wasp projects no longer fight over ports" translate="no">​</a></h3>
<p>Before Wasp 0.26, running <code>wasp start</code> and <code>wasp start db</code> in multiple worktrees was... problematic.
All clients would fight over port 3000, all servers over 3001, and all databases over 5432. This led to many <em>"Port is already taken"</em> errors.</p>
<p>Wasp 0.26 solves this problem with dynamic port allocation.</p>
<p>If you've built a bespoke system for handling port conflicts, it's finally time to retire it.
Just run the commands you want to run, and Wasp takes care of the rest:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic"># Starts the client and the server on the first two free ports it finds.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># It starts looking at 3000 and goes up.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">wasp start</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Starts the dev database on the first free port it finds.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># It starts looking at 5432 and goes up.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">wasp start db</span><br></div></code></pre></div></div>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/commands-in-different-projects.svg" alt="Before Wasp 0.26, two worktrees of the same repo tried to use ports 5432, 3001, and 3000 and the second one failed with port taken errors. After Wasp 0.26, the database in the second worktree gets 5433, the client 3002, and the server 3003." class="themedComponent_bsp7 themedComponent--light_A5ZL" style="width:100%"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/commands-in-different-projects-dark.svg" alt="Before Wasp 0.26, two worktrees of the same repo tried to use ports 5432, 3001, and 3000 and the second one failed with port taken errors. After Wasp 0.26, the database in the second worktree gets 5433, the client 3002, and the server 3003." class="themedComponent_bsp7 themedComponent--dark_LZz2" style="width:100%"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Two worktrees running at the same time: each process now takes the next free port.</figcaption></figure></div>
<p>That said, there are three things to keep in mind.</p>
<ul>
<li class="">First, your Wasp processes will no longer always run on the same ports (i.e., <code>3000</code> for the client, <code>3001</code> for the server, and <code>5432</code> for the dev database).
They'll run on the first available ports starting from those, so pay attention to where Wasp tells you they're listening.</li>
<li class="">Second, since each worktree gets its own database, working in many worktrees means having many databases.
Databases are not terribly useful without data, so we recommend you <a class="" href="https://wasp.sh/docs/features/data/databases#seeding-the-database">seed them</a>.</li>
<li class="">Third, because Wasp now manages the ports and URLs in development, setting them yourself (e.g., <code>server.port</code> in <code>vite.config.ts</code> or <code>PORT</code> in <code>.env.server</code>) is an error.
This is a <strong>breaking change.</strong> Check the <a class="" href="https://wasp.sh/docs/migration-guide">migration guide</a> for the full list of changes and how to update your project.
If your app needs to be reachable at a different address (e.g., a LAN hostname or an HTTPS tunnel), use the new <code>--client-url</code> and <code>--server-url</code> flags instead.</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="bonus-feature">Bonus feature<a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#bonus-feature" class="hash-link" aria-label="Direct link to Bonus feature" title="Direct link to Bonus feature" translate="no">​</a></h3>
<p>Wasp 0.26 allows you to specify the exact development ports you want Wasp to use for your client, server, and database.
The client and server flags work for both <code>wasp start</code> and <code>wasp build start</code>:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token plain">wasp start --client-port </span><span class="token number" style="color:#36acaa">4000</span><span class="token plain"> --server-port </span><span class="token number" style="color:#36acaa">5000</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">wasp build start --client-port </span><span class="token number" style="color:#36acaa">4000</span><span class="token plain"> --server-port </span><span class="token number" style="color:#36acaa">5000</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">wasp start db --db-port </span><span class="token number" style="color:#36acaa">6000</span><br></div></code></pre></div></div>
<p>If any of those ports is taken, Wasp will fail instead of looking for alternatives.
The reasoning is that you care about your process running on those specific ports, so it's better to explicitly fail than silently start listening elsewhere.
It's therefore up to you to either free those ports up, specify different ports, or remove the port arguments.</p>
<p>The <code>--db-port</code> flag was contributed by <a href="https://github.com/Nihal-Ahamed-MS" target="_blank" rel="noopener noreferrer" class="">Nihal Ahamed</a>.
Thanks for all the patience during the design changes and reviews, Nihal!</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="try-it-out">Try it out<a href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly#try-it-out" class="hash-link" aria-label="Direct link to Try it out" title="Direct link to Try it out" translate="no">​</a></h2>
<p>Parallel worktree support is live in Wasp 0.26. If you're not on it yet, update your Wasp CLI:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">npm</span><span class="token plain"> i </span><span class="token parameter variable" style="color:#36acaa">-g</span><span class="token plain"> @wasp.sh/wasp-cli</span><br></div></code></pre></div></div>
<p>If you haven't set up worktrees for your Wasp project yet, the <a class="" href="https://wasp.sh/docs/advanced/git-worktrees">Git worktree setup</a> guide walks you through it.</p>
<p>Wasp 0.26 also brings <code>wasp show</code>, safer auth defaults, and a new docs structure. Check out the <a class="" href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog">Wasp 0.26 changelog</a> for the full list.</p>
<p>We'd love to hear how it works for you - come chat with us on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a>!</p>]]></content:encoded>
            <author>filip@wasp-lang.dev (Filip Sodić)</author>
            <category>wasp</category>
            <category>ai</category>
            <category>agents</category>
            <category>claude-code</category>
            <category>fullstack</category>
        </item>
        <item>
            <title><![CDATA[Wasp 0.26: parallel worktrees, wasp show, docs updates, and safer auth defaults]]></title>
            <link>https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog</link>
            <guid>https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog</guid>
            <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Wasp 0.26 gives each app its own set of ports, so each coding agent can run your app in its own Git worktree. It also adds wasp show.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The command wasp version printing 0.26.0" src="https://wasp.sh/img/blog/2026-10-23-wasp-0-26-changelog/banner.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>On our <a class="" href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming">road to Wasp 1.0</a>, we are shipping incremental releases, each adding more toward our vision of Wasp as a full-stack JS/TS framework that is liked and useful for humans and agents alike.</p>
<p>Wasp 0.26 is out.</p>
<p>This release lets you run several Wasp apps on one machine at once, so each coding agent can work in its own worktree.</p>
<p>Additionally, each app in a parallel worktree now gets its own set of ports, auth flows are getting safer defaults, the docs structure has been revamped, and <code>wasp show</code> now prints your app as Wasp sees it.</p>
<p>More on these below, so let’s dive in! 🐝</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="parallel-worktrees-ports-and-ai-assisted-dev-friendliness">Parallel worktrees, ports and AI-assisted dev friendliness<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#parallel-worktrees-ports-and-ai-assisted-dev-friendliness" class="hash-link" aria-label="Direct link to Parallel worktrees, ports and AI-assisted dev friendliness" title="Direct link to Parallel worktrees, ports and AI-assisted dev friendliness" translate="no">​</a></h2>
<p>When you run several coding agents like Claude Code or Codex in parallel, a common setup is to give each one its own Git worktree. Until this release, only one of those worktrees could run your app.</p>
<p>That’s because <code>wasp start</code> would always use the fixed ports <code>3000</code> and <code>3001</code>, and <code>wasp start db</code> would always use <code>5432</code>.</p>
<p>In reality, users ran multiple instances and port clashing was a real issue: <code>wasp start db</code>, for example, would simply give up when <code>5432</code> was taken. So now, <code>wasp start</code> picks the first available ports on its own. It’ll start with <code>3000</code> and <code>3001</code> as before and then work its way up. Similarly, <code>wasp start db</code> will do the same, starting at <code>5432</code>, and <code>wasp start</code> will then find the port your database ended up on.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/commands-in-different-projects.svg" alt="Before Wasp 0.26, two worktrees of the same repo tried to use ports 5432, 3001, and 3000 and the second one failed with port taken errors. After Wasp 0.26, the database in the second worktree gets 5433, the client 3002, and the server 3003." class="themedComponent_bsp7 themedComponent--light_A5ZL" style="width:100%"><img src="https://wasp.sh/img/blog/2026-10-27-wasp-agent-friendly/commands-in-different-projects-dark.svg" alt="Before Wasp 0.26, two worktrees of the same repo tried to use ports 5432, 3001, and 3000 and the second one failed with port taken errors. After Wasp 0.26, the database in the second worktree gets 5433, the client 3002, and the server 3003." class="themedComponent_bsp7 themedComponent--dark_LZz2" style="width:100%"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Two worktrees running at the same time: each process now takes the next free port.</figcaption></figure></div>
<p>This also means that each agent can get its own DB instance and can avoid the hassle of sharing the data.</p>
<p>Once you’ve created a new worktree, to set it up, you can just run <code>wasp install</code> and copy your <code>.env</code> files. If your <code>.env.server</code> has a <code>DATABASE_URL</code>, leave it out, so the worktree gets its own dev database instead of the shared one. Then start the database in one terminal and the app in another:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic"># Terminal 1: keeps the database running</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">wasp start db</span><br></div></code></pre></div></div>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic"># Terminal 2</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">wasp db migrate-dev</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">wasp start</span><br></div></code></pre></div></div>
<p>If you need a fixed port, that’s also possible and you can pass <code>--client-port</code>, <code>--server-port</code> or <code>--db-port</code> values. A special h/t to our community contributor for the last one, <a href="https://github.com/Nihal-Ahamed-MS" target="_blank" rel="noopener noreferrer" class="">@Nihal-Ahamed-MS</a>.</p>
<p>Also, Wasp now manages your dev ports and URLs, so if you set <code>WASP_SERVER_URL</code> or <code>WASP_WEB_CLIENT_URL</code> in <code>.env.server</code>, <code>REACT_APP_API_URL</code> in <code>.env.client</code>, or <code>server.port</code> in <code>vite.config.ts</code> manually, it will now fail.</p>
<p>We explain more and what to remove in <a href="https://wasp.sh/docs/0.26/migration-guide" target="_blank" rel="noopener noreferrer" class="">our migration guide to 0.26</a>.</p>
<p>And your coding agent can benefit from the same setup - you can just prompt it to start the app in its own worktree and check the changes it’s making there, while your app can stay open and running in another one.</p>
<p>To see in more detail how 0.26 makes Wasp friendlier to AI agents, including how Wasp now stops two commands from writing over each other’s files, check out <a class="" href="https://wasp.sh/blog/2026/10/27/wasp-agent-friendly">Filip’s deep dive on agent orchestrators and worktrees</a>.</p>
<p>To upgrade, run the following:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">npm</span><span class="token plain"> i </span><span class="token parameter variable" style="color:#36acaa">-g</span><span class="token plain"> @wasp.sh/wasp-cli@latest</span><br></div></code></pre></div></div>
<p>We also suggest you take a look at <a class="" href="https://wasp.sh/docs/advanced/git-worktrees#running-worktrees-at-the-same-time">our worktree guide</a> and if you get stuck or want to share your experiences with us, drop by <a href="https://discord.gg/zXPANMXrZp" target="_blank" rel="noopener noreferrer" class="">our Discord server</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-wasp-show-command">The <code>wasp show</code> command<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#the-wasp-show-command" class="hash-link" aria-label="Direct link to the-wasp-show-command" title="Direct link to the-wasp-show-command" translate="no">​</a></h2>
<p>We’ve seen users having very large Wasp app’s spec files and others have had specs spanning multiple other files making it difficult to see all your routes or queries in one place.</p>
<p>We changed that by introducing <code>wasp show spec</code> command. Running it will now print out your app the same way Wasp sees it - all your pages, routes, entities, actions, queries, APIs, CRUDs and even jobs.</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token plain">$ wasp show spec</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">..</span><span class="token plain">.</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">Routes</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  Name         Path     Destination  Loading</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  LoginRoute   /login   LoginPage    Lazy</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  RootRoute    /        MainPage     Lazy</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  SignupRoute  /signup  SignupPage   Lazy</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">Queries</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  Name      Import                             Entities</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  getTasks  </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> getTasks </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> from </span><span class="token string" style="color:#e3116c">"./src/queries"</span><span class="token plain">  Task</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">..</span><span class="token plain">.</span><br></div></code></pre></div></div>
<p>If you want to see more information about your last build, you can run <code>wasp show build</code>.</p>
<p>Just remember to run both of these commands in your project folder and if you want the output in a more structured way, just add <code>--json</code> and get it like that.</p>
<p>The new wasp show replaces our older wasp info so if you depend on it and your code gets the value from it, switch it to <code>wasp show build --json</code> and then read the value from <code>lastCompile.waspVersion</code>.</p>
<p>And, again, agents will benefit from this structured output, too. You can quickly ask them which pages require auth or which queries and actions use a specific entity before changing that entity, avoiding conflicts and issues down the road.</p>
<p>You can find both commands in our <a class="" href="https://wasp.sh/docs/advanced/cli#project-commands">CLI reference</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="improved-docs-structure">Improved docs structure<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#improved-docs-structure" class="hash-link" aria-label="Direct link to Improved docs structure" title="Direct link to Improved docs structure" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img style="width:340px" alt="The six sections of the Wasp 0.26 docs sidebar: Getting started, Tutorial, Features, Advanced, Deployment and Migration guides" src="https://wasp.sh/img/blog/2026-10-23-wasp-0-26-changelog/docs-sidebar-0-26.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">The new docs sidebar in Wasp 0.26</figcaption></figure></div>
<p>We improved our <a class="" href="https://wasp.sh/docs">docs</a> structure significantly as well.</p>
<p>In our previous version, 0.25, we had 11 top-level sections like Data Model, Project Setup or Miscellaneous. In 0.26 we regrouped them so it’s faster to find a page when you know what you are looking for.</p>
<p>The structure is now streamlined to 6 sections: Getting started, Tutorial, Features, Advanced, Deployment, and Migration guides.</p>
<p>We also shortened the names of numerous pages - for example, Custom HTTP API Endpoints is now just API routes.</p>
<p>Older links still work, all the newly moved pages redirect correctly, and the older docs keep their structure. Agents will also see the same structure since our <a href="https://wasp.sh/llms.txt" target="_blank" rel="noopener noreferrer" class="">llms.txt</a> files follow the new sidebar.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="safer-auth-defaults">Safer auth defaults<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#safer-auth-defaults" class="hash-link" aria-label="Direct link to Safer auth defaults" title="Direct link to Safer auth defaults" translate="no">​</a></h2>
<p>Our users trust Wasp when it comes to auth - we make all those flows for you, so figuring out any issues and polishing some rough edges is our job. In 0.26 we are fixing several of those.</p>
<p>When you reset your password now, the account will be logged out on every device. Password reset will check the token before the new password, so someone without a valid link can’t probe your password rules.</p>
<p>Also, the resend limit for verification emails will now check the time when the last verification email went out, and not the last password reset email.</p>
<p>We also improved how we are handling more global and internationalized addresses like <code>jürgen@münchen.de</code> or those written in UPPERCASE. Additionally, <code>onBeforeSignup</code> now runs before <code>userSignupFields</code> for every supported signup method.</p>
<p>All this ships by default in 0.26 and no changes are needed from your side. The only thing that could possibly break your e2e tests is that email fields now use <code>type="text"</code>, so select them with <code>input[name="email"]</code> instead of <code>input[type="email"]</code> if those were part of your testing scripts.</p>
<p>You can read more in our <a class="" href="https://wasp.sh/docs/features/auth/overview">auth docs</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="on-our-road-to-wasp-10">On our road to Wasp 1.0<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#on-our-road-to-wasp-10" class="hash-link" aria-label="Direct link to On our road to Wasp 1.0" title="Direct link to On our road to Wasp 1.0" translate="no">​</a></h2>
<p>Before we get to the upgrade details: as we said at the top, we're on our <a class="" href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming">road to Wasp 1.0</a>. If you want to know the moment it lands, leave your email below and we'll let you know.</p>
<div id="signup" class="mb-6 flex flex-col items-start space-y-3 rounded-lg border border-yellow-500/25 bg-yellow-500/20 p-8"><p class="text-xl font-semibold">Get an email when Wasp 1.0 lands!</p><form class="self-stretch sm:flex"><input aria-label="Email address" type="email" required="" autocomplete="email" placeholder="you@awesomedev.com" class="w-full appearance-none border-2 border-wasp-black bg-wasp-white px-4 py-2.5 font-mono text-sm text-wasp-black placeholder:text-wasp-g4 focus:outline-none focus:ring-2 focus:ring-wasp-yellow-dark" value=""><div class="mt-3 sm:ml-3 sm:mt-0"><button type="submit" class="w-full whitespace-nowrap border-2 border-wasp-black bg-wasp-yellow px-5 py-2.5 font-mono text-sm font-bold uppercase tracking-wide text-wasp-black transition duration-150 ease-out hover:bg-wasp-yellow-dark">Subscribe</button></div></form></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="before-you-upgrade">Before you upgrade<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#before-you-upgrade" class="hash-link" aria-label="Direct link to Before you upgrade" title="Direct link to Before you upgrade" translate="no">​</a></h2>
<p>With 0.26, we have introduced some more breaking changes. Our <a href="https://wasp.sh/docs/0.26/migration-guide" target="_blank" rel="noopener noreferrer" class="">0.26 migration guide</a> covers most of them, but here are a few for your reference.</p>
<ul>
<li class="">Wasp now type-checks your code directly when it compiles, so <code>wasp compile</code>, <code>wasp start</code> and <code>wasp build</code> stop on TypeScript errors. It checked your code before too, so most apps won't see new errors. If you get any, fix them before you continue.</li>
<li class=""><code>tsconfig.src.json</code> needs an update, and custom Dockerfiles must copy the generated <code>types</code> directory.</li>
<li class="">Deployed servers now need a <code>PORT</code> environment variable.</li>
<li class="">The server's liveness check moved from <code>GET /</code> to <code>GET /up</code>. Point your health checks at <code>/up</code>.</li>
<li class="">The database flags of <code>wasp deploy fly</code> now start with <code>db-</code>, for example <code>--db-vm-size</code>. Fly CLI 0.4.82 and Railway CLI 5.28.0 are the new minimum versions.</li>
<li class="">Internal server-only import paths moved under <code>wasp/server/...</code>. If your app imported one, switch to a documented import such as <code>wasp/server/auth</code>.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="full-list-of-changes-and-improvements">Full list of changes and improvements<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#full-list-of-changes-and-improvements" class="hash-link" aria-label="Direct link to Full list of changes and improvements" title="Direct link to Full list of changes and improvements" translate="no">​</a></h2>
<ul>
<li class="">Custom APIs now support the <code>PATCH</code> and <code>HEAD</code> methods.</li>
<li class="">New Fly.io and Railway databases now use PostgreSQL 18. <code>wasp deploy fly</code> also has new <code>--db-vm-memory</code>, <code>--db-vm-cpus</code> and <code>--db-vm-cpu-kind</code> options.</li>
<li class="">You can now change more of <code>tsconfig.src.json</code>, such as <code>strict</code>, <code>target</code> and <code>lib</code>.</li>
<li class=""><code>Link</code> and <code>NavLink</code> now accept the same <code>search</code> values as <code>routes.X.build</code>, and <code>wasp/client/router</code> exports <code>LinkProps</code> and <code>NavLinkProps</code>.</li>
<li class="">New projects no longer open the browser on <code>wasp start</code>.</li>
<li class="">We fixed Wasp commands in projects with many files under <code>src/</code>. Previously, they could fail with "Too many open files".</li>
<li class="">We fixed <code>wasp start</code> and <code>wasp db</code> commands that hung in some edge cases.</li>
<li class="">We fixed TypeScript incremental builds. Previously, they could miss updated types.</li>
<li class="">The compiler now escapes user input in the code it generates.</li>
<li class="">We fixed Railway databases created with <code>--db-image</code>. Previously, they had no persistent volume. Existing databases are unchanged.</li>
<li class="">We upgraded the internal <code>morgan</code> package to fix three CVEs. Wasp's usage was not affected.</li>
</ul>
<p>The full list is in the <a href="https://github.com/wasp-lang/wasp/releases/tag/v0.26.0" target="_blank" rel="noopener noreferrer" class="">GitHub release notes</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="wasp-0261-security-follow-up">Wasp 0.26.1 security follow-up<a href="https://wasp.sh/blog/2026/10/23/wasp-0-26-changelog#wasp-0261-security-follow-up" class="hash-link" aria-label="Direct link to Wasp 0.26.1 security follow-up" title="Direct link to Wasp 0.26.1 security follow-up" translate="no">​</a></h2>
<p>On October 21, Node.js published its <a href="https://nodejs.org/en/blog/vulnerability/october-2026-security-releases" rel="nofollow noopener noreferrer" target="_blank">October 2026 security releases</a>, with fixes for several vulnerabilities. One of them is a bug in Node's Brotli decoder that can lead to remote code execution.</p>
<p>So on October 23 we shipped Wasp 0.26.1. It raises the minimum Node.js version to 24.22.1, the 24.x release with those fixes. A few things to know:</p>
<ul>
<li class="">Wasp 0.26.0 already works with any newer Node.js, so you can update Node.js on your machine right away.</li>
<li class="">0.26.1 moves the minimum, so no one stays on a vulnerable Node.js version.</li>
<li class="">If you deploy with the Dockerfile Wasp generates, 0.26.1 also moves your server image to Node.js 24.22.1, so rebuild and redeploy.</li>
</ul>
<p>To upgrade, run:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">npm</span><span class="token plain"> i </span><span class="token parameter variable" style="color:#36acaa">-g</span><span class="token plain"> @wasp.sh/wasp-cli@latest</span><br></div></code></pre></div></div>
<p>More details are in the <a href="https://github.com/wasp-lang/wasp/releases/tag/v0.26.1" target="_blank" rel="noopener noreferrer" class="">0.26.1 release notes</a>.</p>]]></content:encoded>
            <category>wasp</category>
            <category>update</category>
            <category>changelog</category>
            <category>ai agents</category>
            <category>webdev</category>
        </item>
        <item>
            <title><![CDATA[Wasp 1.0 is coming]]></title>
            <link>https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming</link>
            <guid>https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming</guid>
            <pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[After 5+ years, Wasp 1.0 is officially in the works. Learn why we stayed pre-1.0 so long, what changed, and what you can expect from 1.0.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Wasp 1.0 is coming" src="https://wasp.sh/img/blog/2026-10-20-wasp-1-0-is-coming/wasp-1-0-is-coming-banner.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>The time has come: Wasp 1.0 is now officially in the works! ETA: ~6 months.</p>
<p>Even though still young in framework-years, Wasp has been around for some time now (&gt;5y), with <a href="https://github.com/wasp-lang/wasp/releases" target="_blank" rel="noopener noreferrer" class="">over 100 releases</a>, <a class="" href="https://wasp.sh/#showcases">user stories</a> ranging from startups to Fortune 500 companies, $5M raised in funding so far, and a team of currently 8 people and growing behind it plus all the awesome people from our community (<a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">waspeteers</a>).</p>
<p>And yet, for years now, we kept Wasp in Beta. Read on to learn why, what changed, and what you can expect from 1.0.</p>
<!-- -->
<div id="signup" class="mb-6 flex flex-col items-start space-y-3 rounded-lg border border-yellow-500/25 bg-yellow-500/20 p-8"><p class="text-xl font-semibold">Get an email when Wasp 1.0 lands!</p><form class="self-stretch sm:flex"><input aria-label="Email address" type="email" required="" autocomplete="email" placeholder="you@awesomedev.com" class="w-full appearance-none border-2 border-wasp-black bg-wasp-white px-4 py-2.5 font-mono text-sm text-wasp-black placeholder:text-wasp-g4 focus:outline-none focus:ring-2 focus:ring-wasp-yellow-dark" value=""><div class="mt-3 sm:ml-3 sm:mt-0"><button type="submit" class="w-full whitespace-nowrap border-2 border-wasp-black bg-wasp-yellow px-5 py-2.5 font-mono text-sm font-bold uppercase tracking-wide text-wasp-black transition duration-150 ease-out hover:bg-wasp-yellow-dark">Subscribe</button></div></form></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-freedom-of-beta">The freedom of Beta<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#the-freedom-of-beta" class="hash-link" aria-label="Direct link to The freedom of Beta" title="Direct link to The freedom of Beta" translate="no">​</a></h2>
<p>For a long time, we didn't have an exact set of features in mind that would allow us to say Wasp is now 1.0.</p>
<p>We always knew what we wanted though, and believed we would recognize it when we got there: <strong>the "fullstackiest", managed experience of building web apps</strong> there is.
The experience of writing only the code you care about, at the level of detail you want, and the rest being taken care of for you.
All expressed purely in code, flexible, free and easy to deploy anywhere.</p>
<p>That led us to some unconventional choices when designing Wasp:</p>
<ul>
<li class=""><strong>We designed our own custom declarative language</strong> for describing a web app at a high level (the "Spec") and its own custom compiler.
(psst, that <a class="" href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake">was a bit of a mistake</a> though).</li>
<li class=""><strong>Our definition of "full-stack" is broader</strong> than usual for JS frameworks, fully capturing frontend, backend, database, and deployment, and really everything that falls in between.</li>
<li class="">Even though it is currently based on React + Node + Prisma, the underlying machinery has always been <strong>designed to allow adding support for other stacks</strong> in the future, in large part thanks to the aforementioned Spec and compiler.</li>
</ul>
<p>Being in Beta gave us the freedom to explore all these concepts unhindered by the weight and responsibility of maintaining a &gt;=1.0 version of a framework (although we did end up following a lot of "production" practices already in Beta: looking at you, brave people who couldn't be stopped from deploying to production).</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="ready-for-10">Ready for 1.0<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#ready-for-10" class="hash-link" aria-label="Direct link to Ready for 1.0" title="Direct link to Ready for 1.0" translate="no">​</a></h2>
<p>What makes Wasp ready for 1.0 now? After all this time, I dare say the picture crystallized into something much clearer.</p>
<ul>
<li class=""><strong>We found the right shape for <a class="" href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec">the "Spec"</a></strong> (went from our custom language to TypeScript) without giving up on our vision (this was a big one!).</li>
<li class=""><strong>We developed an intuition for how to balance</strong> managed experience with flexibility.</li>
<li class=""><strong>We collected a lot of feedback</strong> on all the major features of Wasp (Auth, RPC, Jobs, Routing, API, Entities, Deployment, etc) and know what people care about and how to get there.</li>
<li class="">We are now fully <strong>committed to bringing the <a class="" href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module">Full Stack Modules</a></strong> to life, the crown of the "fullstackiest" experience we are aiming for.</li>
</ul>
<p>We can now see the exact road, paved with GitHub issues, to Wasp 1.0, and it feels right.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-roadmap">The roadmap<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#the-roadmap" class="hash-link" aria-label="Direct link to The roadmap" title="Direct link to The roadmap" translate="no">​</a></h2>
<p>You can check the exact roadmap on <a href="https://github.com/orgs/wasp-lang/projects/5" target="_blank" rel="noopener noreferrer" class="">GitHub</a>.
It consists of epics, and each of those further develops into sub-epics and specific issues.</p>
<p>Roughly, we can break down the epics in the roadmap into:</p>
<ul>
<li class=""><strong>General polish</strong> (DX).</li>
<li class=""><strong>Rework of core features</strong> (Routing, Auth, RPC, etc).</li>
<li class=""><strong>Production readiness work</strong> (core deps policy, perf/scaling docs, native Win support, etc).</li>
<li class=""><strong>Novel features</strong> (Full Stack Modules, RBAC, etc).</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="general-polish-dx">General polish (DX)<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#general-polish-dx" class="hash-link" aria-label="Direct link to General polish (DX)" title="Direct link to General polish (DX)" translate="no">​</a></h3>
<p>While in Beta, we focused a lot on innovating and testing different ideas, and often prioritized those over the rough edges.</p>
<p>However, when accumulated, rough edges become annoying, so one big class of tasks for 1.0 is a lot of smaller, targeted improvements, mostly DX focused.</p>
<p>Some of these are: making Wasp work better with agent orchestrators, nicer output in the terminal, nicer docs, faster <code>npm install</code>, etc.</p>
<p>Check <a href="https://github.com/wasp-lang/wasp/issues/2884" target="_blank" rel="noopener noreferrer" class="">Epic #2884</a> for more details.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="rework-of-core-features">Rework of core features<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#rework-of-core-features" class="hash-link" aria-label="Direct link to Rework of core features" title="Direct link to Rework of core features" translate="no">​</a></h3>
<p>We never lacked ideas on how to make each of the core Wasp features better (Auth, RPC, Jobs, Email Sender, WebSockets, API, Deployment, etc), but for many of these it was hard to prioritize them while working on bigger framework-spanning improvements (e.g. Spec).</p>
<p>For 1.0, we will bring each of these to a new level! Most of the ideas are already written down in a lot of detail in related GitHub issues, and while some features will require only a smaller touch-up, some will go through a major rework.</p>
<p>For example, <strong><a class="" href="https://wasp.sh/docs/features/auth/overview">Auth</a></strong> will move away from Lucia and add highly requested features like account merging, 2FA, magic links, passkeys, etc. Also, as it currently stands, we will almost certainly reshape it into a more modular implementation that will, next to Wasp Auth, allow using BetterAuth, Clerk, WorkOS or any other auth provider that can implement our auth interface.</p>
<p>Another big one is <strong><a class="" href="https://wasp.sh/docs/deployment/overview">Deployment</a></strong>: we are looking to simplify <code>wasp build</code> to produce a single server, which will unlock many other things. We are also exploring the smoothest option out there for free hosting of Wasp apps and will be adding it as one of the options in our one-command deploy: <code>wasp deploy &lt;provider&gt;</code>, while also making the current options (Fly, Railway) more robust.</p>
<p>For a full list, see the <a href="https://github.com/orgs/wasp-lang/projects/5/views/1?filterQuery=label%3A%22major+feature%22" target="_blank" rel="noopener noreferrer" class="">major features planned for 1.0</a> in our roadmap.”</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="production-readiness-work">Production readiness work<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#production-readiness-work" class="hash-link" aria-label="Direct link to Production readiness work" title="Direct link to Production readiness work" translate="no">​</a></h3>
<p>These are non-feature-specific tasks related to bringing Wasp to the level we expect from a &gt;=1.0 framework.</p>
<p>A big one is the <strong>core deps policy</strong>: from 1.0 onwards we will have a strict policy on how current we keep our core deps (e.g. never more than 6 months behind the latest, which keeps us up to date while avoiding bleeding-edge hiccups).</p>
<p>Then there are <strong>docs on performance and scaling</strong>: while a lot of this just comes down to the underlying stack (React, Node, Prisma), some of it is also Wasp specific, and we want to make it very clear and easy to understand what you can expect from Wasp in this regard.</p>
<p>And also <strong>native Windows support</strong>! Wasp works on WSL on Windows, but having it run directly on Windows is something you would expect from a 1.0 framework, right?</p>
<p>Check <a href="https://github.com/wasp-lang/wasp/issues/2888" target="_blank" rel="noopener noreferrer" class="">Epic #2888</a> for more details.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="novel-features">Novel features<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#novel-features" class="hash-link" aria-label="Direct link to Novel features" title="Direct link to Novel features" translate="no">​</a></h3>
<p>And finally, we are not giving up on innovating just because we are closing in on 1.0.</p>
<p>The star here is <strong>FSMs</strong> (<a href="https://github.com/wasp-lang/wasp/issues/2873" target="_blank" rel="noopener noreferrer" class="">Full Stack Modules</a>): the ability to define and distribute modular, vertical slices of your web app, e.g. Stripe payments, file upload, AI chat, etc. Imagine libraries, but frontend + backend + database + Spec + even deployment in the future, all type-safe and configurable. It's something we are extremely excited about and have been slowly preparing for quite some time now. We wrote more about the idea in <a class="" href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module">JavaScript still can't ship a full-stack module</a>.</p>
<p>FSMs might not sound like a 1.0 thing right off the bat, but we see them becoming so integral to how Wasp apps will be built that we want to have them, and their effects on Wasp's API, in place before 1.0.</p>
<p>By the way, we are open to ideas for a better name since LLMs keep thinking we are talking about Finite State Machines.</p>
<p>And then we have some more exciting ideas (well, popular requests really) like <strong>RBAC</strong> (Role-Based Access Control), a <strong>modular database layer</strong> that would allow support for Drizzle, <strong>Wasp Studio</strong> (visual representation of your codebase + Wasp dev tooling), etc.
These are more of a stretch goal and might or might not yet be fully stable in 1.0, but we would love to at least have them as experimental features by then.</p>
<p>You can find these under the <a href="https://github.com/orgs/wasp-lang/projects/5/views/1?filterQuery=status%3AIdeas" target="_blank" rel="noopener noreferrer" class="">Ideas column</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="see-you-there">See you there<a href="https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming#see-you-there" class="hash-link" aria-label="Direct link to See you there" title="Direct link to See you there" translate="no">​</a></h2>
<p>We won't be waiting to ship all of these improvements as one big release; instead, we will constantly be releasing as we merge them, so you will be hearing from us quite a bit as we go and will be able to benefit from them immediately. Once we complete all of them, we will declare Wasp 1.0.</p>
<p>If you have any additional ideas on what you would love to see in Wasp 1.0, let us know on our <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a> or on <a href="https://github.com/wasp-lang/wasp/issues" target="_blank" rel="noopener noreferrer" class="">GitHub</a>!</p>
<p>That's it, the destination is locked in: next stop, Wasp 1.0! See you there!</p>]]></content:encoded>
            <author>martin@wasp-lang.dev (Martin Sosic)</author>
            <category>wasp</category>
            <category>update</category>
        </item>
        <item>
            <title><![CDATA[How to Build a Secure AI Agent for Your SaaS (with Flue)]]></title>
            <link>https://wasp.sh/blog/2026/08/18/flue-react-for-agents</link>
            <guid>https://wasp.sh/blog/2026/08/18/flue-react-for-agents</guid>
            <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Build a secure AI agent for your SaaS with Flue, a TypeScript agent framework: lock the agent to the logged-in user and confirm deletes.]]></description>
            <content:encoded><![CDATA[<p>Everybody is trying to add AI to their SaaS right now. And a chatbot that just answers questions isn't enough anymore: users expect the assistant to actually <em>do</em> things inside the app. Create records, update them, kick off workflows, all on behalf of whoever is logged in.</p>
<p>That last part is the tricky bit. The moment an agent can touch user data, you have to be really careful that it only ever touches <em>this</em> user's data, and that it can't nuke anything without explicit confirmation.</p>
<p>This is where agent frameworks come in. They handle the loop of sending messages to a model, letting it call tools, persisting the conversation, and exposing it all over HTTP, so you don't have to build that plumbing yourself. There are a lot of them out there right now, and I tried a few, but the one I particularly liked is <a href="https://flueframework.com/" target="_blank" rel="noopener noreferrer" class="">Flue</a>, a TypeScript agent framework from the folks over at <a href="https://astro.build/" target="_blank" rel="noopener noreferrer" class="">Astro</a>.</p>
<p>To put it through its paces, I built a real integration with it, and the whole thing is open source: <a href="https://github.com/vincanger/flue-open-saas" target="_blank" rel="noopener noreferrer" class="">github.com/vincanger/flue-open-saas</a>. Feel free to grab the code and use it in your own app.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-i-built">What I built<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#what-i-built" class="hash-link" aria-label="Direct link to What I built" title="Direct link to What I built" translate="no">​</a></h2>
<p>On the surface, it looks like your typical AI chatbot: it sits in a sidebar, you type at it, it types back. But this agent can also manage the logged-in user's task list and generate a daily schedule from it. I can throw a multi-step request at it, like "add a new task called <em>present Flue in a video</em>, check off <em>integrate a Flue agent into Open SaaS</em>, and generate a schedule for today", and it works through the tools one by one, ticks off each item, and the task list UI on the left updates live as it goes.</p>
<p><img decoding="async" loading="lazy" alt="The agent updating the task list UI live" src="https://wasp.sh/assets/images/agent-updates-ui-20b17c43749f2a51f5ab044b68415d81.webp" width="948" height="527" class="img_qXxT"></p>
<p>The app itself is built on top of <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>, our free, open-source SaaS template, so it already comes with auth, a database, and a demo task app. That gave me a realistic setup to plug an agent into: a real logged-in user, real user data, and real consequences if the agent gets it wrong.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-flue">Why Flue?<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#why-flue" class="hash-link" aria-label="Direct link to Why Flue?" title="Direct link to Why Flue?" translate="no">​</a></h2>
<p>Writing Flue feels like writing <a href="https://react.dev/" target="_blank" rel="noopener noreferrer" class="">React</a>, but for agents. And after building this integration, I think that mental model (plus two other things) makes it a really interesting approach. Let's go through all three:</p>
<ol>
<li class=""><strong>The React mental model</strong> — agents are functions with hooks that re-run on every message.</li>
<li class=""><strong>Batteries included</strong> — persistence, HTTP routing, and (the centerpiece of this post) the primitives to lock an agent to the logged-in user.</li>
<li class=""><strong>Versatility</strong> — the same framework people use for CI, repo, and workflow automations works great inside a web app.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="reason-1-the-react-mental-model">Reason 1: The React mental model<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#reason-1-the-react-mental-model" class="hash-link" aria-label="Direct link to Reason 1: The React mental model" title="Direct link to Reason 1: The React mental model" translate="no">​</a></h2>
<p>If you've used React, you know about hooks. <a href="https://flueframework.com/docs/guide/agent-hooks/" target="_blank" rel="noopener noreferrer" class="">Agent Hooks</a> are the core of the new version of Flue, and agents run a lot like React components: when a message comes in, the agent function <strong>re-runs</strong>, the hooks inside it get re-evaluated, and the result of that render decides which model and which tools are available <em>for that turn</em>.</p>
<p>Here's the skeleton of the agent I built (we'll fill in the interesting parts as we go):</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token string" style="color:#e3116c">'use agent'</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  useDelivery</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  useInitialData</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  useModel</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  usePersistentState</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  useTool</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@flue/runtime'</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">function</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">SaasAssistant</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">useModel</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'anthropic/claude-sonnet-5'</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> userId </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token generic-function function" style="color:#d73a49">useInitialData</span><span class="token generic-function generic class-name operator" style="color:#393A34">&lt;</span><span class="token generic-function generic class-name punctuation" style="color:#393A34">{</span><span class="token generic-function generic class-name"> userId</span><span class="token generic-function generic class-name operator" style="color:#393A34">:</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name builtin">string</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name punctuation" style="color:#393A34">}</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name operator" style="color:#393A34">|</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name keyword" style="color:#00009f">undefined</span><span class="token generic-function generic class-name operator" style="color:#393A34">&gt;</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token operator" style="color:#393A34">?.</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// ...hooks for state and tools...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string string" style="color:#e3116c">You are the in-app assistant of a SaaS application, acting on</span><br></div><div class="token-line" style="color:#393A34"><span class="token template-string string" style="color:#e3116c">    behalf of the authenticated user with id "</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">userId</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">". ...</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><br></div></code></pre></div></div>
<p>It's just a function. <code>useModel</code> picks the model, <code>useTool</code> mounts tools, and the string you return is the system prompt. If you've internalized "UI is a function of state" from React, this is the same idea one level up: <strong>the agent's capabilities are a function of state</strong>. This make it really easy for a lot of us web devs to grasp how the framework works, and it's what makes the security story below come together nicely.</p>
<p>There is one deliberate difference from React though: state doesn't always reset between renders. Flue gives you <code>usePersistentState</code>, so even when the agent re-renders on a new message (or a new HTTP request entirely) your state survives with the conversation. We'll check that out in a minute.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="reason-2-batteries-included-or-locking-an-agent-to-the-logged-in-user">Reason 2: Batteries included (or: locking an agent to the logged-in user)<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#reason-2-batteries-included-or-locking-an-agent-to-the-logged-in-user" class="hash-link" aria-label="Direct link to Reason 2: Batteries included (or: locking an agent to the logged-in user)" title="Direct link to Reason 2: Batteries included (or: locking an agent to the logged-in user)" translate="no">​</a></h2>
<p>I'm a batteries-included framework kind of person (I work on <a href="https://wasp.sh/" target="_blank" rel="noopener noreferrer" class="">Wasp</a>, so, no surprises there). Flue has a lot of features under the hood that just work. You can write a capable agent in very few lines of code.</p>
<p>But rather than list features, let me show you the one problem where the batteries really mattered, because it's the problem every SaaS developer hits the moment their chatbot grows: <strong>how do you make sure the agent only acts on the logged-in user's data?</strong></p>
<p>In other agent frameworks I've tried, this is where things get awkward. You end up threading user IDs through prompt templates, or bolting auth checks onto every tool, in order to make sure prompt injection isn't a threat. In Flue, it was genuinely simple, and it worked with two hooks.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="useinitialdata-identity-gets-baked-in-once-immutably"><code>useInitialData</code>: identity gets baked in, once, immutably<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#useinitialdata-identity-gets-baked-in-once-immutably" class="hash-link" aria-label="Direct link to useinitialdata-identity-gets-baked-in-once-immutably" title="Direct link to useinitialdata-identity-gets-baked-in-once-immutably" translate="no">​</a></h3>
<p>When the server sends the <em>first</em> message of a conversation, it can attach an <code>initialData</code> payload. Flue bakes that data into the conversation <strong>on creation, immutably</strong>. It can never be changed afterwards, not by the browser, not by the model, not by later messages.</p>
<p>So on the server side of my SaaS app, the send-message endpoint pulls the user ID from the verified auth session and passes it along:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token function-variable function" style="color:#d73a49">sendAgentMessage</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">async</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">args</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> context</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token operator" style="color:#393A34">!</span><span class="token plain">context</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">user</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">throw</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">new</span><span class="token plain"> </span><span class="token class-name">HttpError</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">401</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> conversationId </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string string" style="color:#e3116c">user-</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">context</span><span class="token template-string interpolation punctuation" style="color:#393A34">.</span><span class="token template-string interpolation">user</span><span class="token template-string interpolation punctuation" style="color:#393A34">.</span><span class="token template-string interpolation">id</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">-main</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">fetch</span><span class="token punctuation" style="color:#393A34">(</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">env</span><span class="token template-string interpolation punctuation" style="color:#393A34">.</span><span class="token template-string interpolation constant" style="color:#36acaa">FLUE_URL</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">/agents/assistant/</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">conversationId</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    method</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'POST'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    headers</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> Authorization</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string string" style="color:#e3116c">Bearer </span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">env</span><span class="token template-string interpolation punctuation" style="color:#393A34">.</span><span class="token template-string interpolation constant" style="color:#36acaa">FLUE_SEND_SECRET</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    body</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">JSON</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">stringify</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      kind</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'user'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      body</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> args</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">body</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token comment" style="color:#999988;font-style:italic">// Bound on the conversation's first message; immutable after.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      initialData</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> userId</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> context</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">user</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">id </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>The user ID comes from the server's session so the browser can't manipulate it in any way. And on the agent side, reading it back is one hook:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> userId </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token generic-function function" style="color:#d73a49">useInitialData</span><span class="token generic-function generic class-name operator" style="color:#393A34">&lt;</span><span class="token generic-function generic class-name punctuation" style="color:#393A34">{</span><span class="token generic-function generic class-name"> userId</span><span class="token generic-function generic class-name operator" style="color:#393A34">:</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name builtin">string</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name punctuation" style="color:#393A34">}</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name operator" style="color:#393A34">|</span><span class="token generic-function generic class-name"> </span><span class="token generic-function generic class-name keyword" style="color:#00009f">undefined</span><span class="token generic-function generic class-name operator" style="color:#393A34">&gt;</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token operator" style="color:#393A34">?.</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token operator" style="color:#393A34">!</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// No trusted identity? The agent's only instruction is to refuse.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> 'This conversation carries no trusted user identity</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> so you must</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    refuse every request to read or change data</span><span class="token operator" style="color:#393A34">...</span><span class="token plain">'</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><br></div></code></pre></div></div>
<p>Then every tool is a factory that closes over that trusted <code>userId</code>:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">useTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token function" style="color:#d73a49">listTasks</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">useTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token function" style="color:#d73a49">createTask</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">useTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token function" style="color:#d73a49">updateTaskStatus</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">useTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token function" style="color:#d73a49">saveSchedule</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>Notice what <em>isn't</em> happening here: the user ID never appears in any tool's input schema. The model can still pick which tool to use, but we've already baked in the user. There's no prompt-injection phrasing, no "actually my user id is 42", that can change whose data these tools touch.</p>
<p>Here are examples that show you what NOT to do, and how to easily guard against it in Flue:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// ❌ The naive way: userId is part of the tool's input schema</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">defineTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'list_tasks'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  description</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"List a user's tasks."</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  input</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> v</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">object</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    userId</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> v</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">string</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain">   </span><span class="token comment" style="color:#999988;font-style:italic">// ← the MODEL fills this in. Prompt-injection alert!</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">async</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">run</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> data </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> output</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> db</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">task</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">findMany</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> where</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> userId</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> data</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">userId </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// ✅ The right way: userId is closed over, not in the schema</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token function-variable function" style="color:#d73a49">listTasks</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">userId</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token builtin">string</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=&gt;</span><span class="token plain">   </span><span class="token comment" style="color:#999988;font-style:italic">// ← trusted value from useInitialData</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">defineTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'list_tasks'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    description</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"List all of the user's tasks."</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// no input schema at all so the model has nothing to fill in</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">async</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">run</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> signal </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> output</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">waspFetch</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'/api/agent/tasks'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> userId</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> signal </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="conditional-tools-the-delete-confirmation-flow">Conditional tools: the delete confirmation flow<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#conditional-tools-the-delete-confirmation-flow" class="hash-link" aria-label="Direct link to Conditional tools: the delete confirmation flow" title="Direct link to Conditional tools: the delete confirmation flow" translate="no">​</a></h3>
<p>The second trick is my favorite. You'll recall that agent capabilities are a function of state. That means you can mount tools <em>conditionally</em>.</p>
<p>I wanted "delete all completed tasks" to require explicit confirmation from the user. This means something like making them reply with the exact phrase <code>delete my completed tasks</code> before the deletion can happen.</p>
<p>Here's the whole mechanism in action:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain">deletionApproved</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> setDeletionApproved</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">usePersistentState</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token string" style="color:#e3116c">'deletionApproved'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token boolean" style="color:#36acaa">false</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">useTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'record_approval'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  description</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string string" style="color:#e3116c">Call this ONLY after the user has themselves typed the</span><br></div><div class="token-line" style="color:#393A34"><span class="token template-string string" style="color:#e3116c">    exact phrase "</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation constant" style="color:#36acaa">APPROVAL_PHRASE</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">" in their message.</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">async</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">run</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> normalized </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> lastUserMessage</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">trim</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">toLowerCase</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">normalized </span><span class="token operator" style="color:#393A34">!==</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">APPROVAL_PHRASE</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">throw</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">new</span><span class="token plain"> </span><span class="token class-name">Error</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'Approval NOT recorded: ask the user to type the exact phrase.'</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">setDeletionApproved</span><span class="token punctuation" style="color:#393A34">(</span><span class="token boolean" style="color:#36acaa">true</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'Approval recorded for one deletion.'</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// The destructive tool is only *mounted* once approval is recorded:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">deletionApproved</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">useTool</span><span class="token punctuation" style="color:#393A34">(</span><span class="token function" style="color:#d73a49">deleteAllCompletedTasks</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">userId</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">setDeletionApproved</span><span class="token punctuation" style="color:#393A34">(</span><span class="token boolean" style="color:#36acaa">false</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><br></div></code></pre></div></div>
<p>BTW, That <code>lastUserMessage</code> comes from another nice hook, <code>useDelivery</code>, that lets you inspect what was actually delivered to the agent over HTTP, so the check runs against what the user really typed.</p>
<p>It's cool that Flue makes secure, conditional tool calling an easy <code>if</code> statement.</p>
<p>When approval hasn't been given, the delete tool isn't "discouraged" or "guarded by the prompt" (e.g. <em>"if it doesn't exist, don't do this..."</em>). The agent literally cannot call it, no matter how creatively someone asks. Once the deletion runs, the callback flips the flag back and the tool unmounts again so that approval is valid for exactly one deletion.</p>
<p>This whole flow was super easy to build, and it gives you an agent limited to a specific set of tools, with a conditional, stateful approach to the dangerous ones.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="and-persistence-is-just-there">And persistence is just... there<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#and-persistence-is-just-there" class="hash-link" aria-label="Direct link to And persistence is just... there" title="Direct link to And persistence is just... there" translate="no">​</a></h3>
<p>One more battery worth mentioning is that every conversation gets a key.</p>
<p>Essentially the key is your agent's name plus a conversation ID (mine is <code>user-{id}-main</code> in this case).</p>
<p>Flue persists the full history and state of the conversation under that key. What this means in practice is that your conversation is a "stateful URL". So when you hit the same URL tomorrow, or a week later, the agent picks up right where it left off.</p>
<p>For example, here's Monday:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">curl</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-X</span><span class="token plain"> POST https://my-app.com/agents/assistant/user-42-main </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">-H</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Authorization: Bearer </span><span class="token string variable" style="color:#36acaa">$SEND_SECRET</span><span class="token string" style="color:#e3116c">"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">-d</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'{ "kind": "user", "body": "add a task: prep the investor demo" }'</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># → "Added! You now have 3 open tasks."</span><br></div></code></pre></div></div>
<p>...and here's Wednesday, same URL:</p>
<div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">curl</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-X</span><span class="token plain"> POST https://my-app.com/agents/assistant/user-42-main </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">-H</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Authorization: Bearer </span><span class="token string variable" style="color:#36acaa">$SEND_SECRET</span><span class="token string" style="color:#e3116c">"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">-d</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'{ "kind": "user", "body": "did I ever finish that demo prep?" }'</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># → "'prep the investor demo' is still open. Want me to mark it done?"</span><br></div></code></pre></div></div>
<p>The great part is that there's no need for a session token, history payload,
or to resend anything else. Just hit the same URL! For a chat sidebar in a SaaS, that's exactly the behavior you want.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="reason-3-its-versatile">Reason 3: It's versatile<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#reason-3-its-versatile" class="hash-link" aria-label="Direct link to Reason 3: It's versatile" title="Direct link to Reason 3: It's versatile" translate="no">​</a></h2>
<p>If you've seen other Flue examples floating around, they're mostly from a different world: CI workflows, repo-cleanup bots, automations that run one-off tasks. That's the world Flue seems to be best known for.</p>
<p>What I wanted to check is how it behaves in a full-stack web app, and it works really well, because exposing an agent over HTTP is a one-liner:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> createAgentRouter </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@flue/runtime/routing'</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">app</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'/agents/assistant'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">createAgentRouter</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">SaasAssistant</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>That mounts the agent at a route, and on the client, Flue's SDK gives you a live handle on the conversation:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> useFlueAgent </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@flue/react'</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> createFlueClient </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@flue/sdk'</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> client </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">createFlueClient</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  url</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation constant" style="color:#36acaa">FLUE_URL</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">/agents/assistant/user-</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">user</span><span class="token template-string interpolation punctuation" style="color:#393A34">.</span><span class="token template-string interpolation">id</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">-main</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> agent </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">useFlueAgent</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> client </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p><code>agent.messages</code> streams in with the message text, the tool calls, and their states, so you can render the "🔧 create_task · done" chips in the chat, and react to them.</p>
<p>In my app, whenever a tool call completes, I invalidate the relevant queries so the task list next to the chat refreshes itself the moment the agent touches it. That's the "UI updates live on the left" magic from the demo, and it's about ten lines of client code.</p>
<p>So the same framework covers both realms: the automation scripts people already use it for, and a web app with auth, streaming, and a real database behind it. If you learn it once, you get to use it in both (and I like that!).</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="wrapping-up">Wrapping up<a href="https://wasp.sh/blog/2026/08/18/flue-react-for-agents#wrapping-up" class="hash-link" aria-label="Direct link to Wrapping up" title="Direct link to Wrapping up" translate="no">​</a></h2>
<p>The three things that I think make Flue a genuinely interesting take on agent frameworks:</p>
<ul>
<li class=""><strong>The React mental model</strong> makes agents feel like something you already know how to write — a function of state, re-rendered per message.</li>
<li class=""><strong>Batteries included</strong> means the hard, boring parts — persistence, HTTP exposure, and above all <em>binding an agent to a trusted identity</em> — are one hook away instead of a subsystem you build yourself.</li>
<li class=""><strong>Versatility</strong> means the CI-workflow crowd and the web-app crowd are using the same tool.</li>
</ul>
<p>The example I built is completely open source: <a href="https://github.com/vincanger/flue-open-saas" target="_blank" rel="noopener noreferrer" class="">github.com/vincanger/flue-open-saas</a>. It's built on top of <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>, our free, open-source SaaS template, which comes full-featured with auth, payments (Stripe, Lemon Squeezy, Polar), file uploads with S3, this demo app, docs, and a blog!</p>
<p>And if you'd rather see all of this in action, here's a video walkthrough of the integration:</p>
<div style="text-align:center;width:100%;display:inline-block"><iframe width="100%" height="400" src="https://www.youtube.com/embed/J8fb713Y5dg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen=""></iframe></div>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>ai agents</category>
            <category>flue</category>
            <category>react</category>
            <category>saas</category>
            <category>typescript</category>
        </item>
        <item>
            <title><![CDATA[A Maintainer's Advice on Contributing to Open Source in 2026]]></title>
            <link>https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026</link>
            <guid>https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026</guid>
            <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[My advice as an open-source maintainer on how to build trust as a new open-source contributor in 2026.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Two people holding hands while surrounded by binary code." src="https://wasp.sh/img/blog/2026-08-13-advice-for-contributing-in-2026/banner.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-ideal-contributor">The ideal contributor<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#the-ideal-contributor" class="hash-link" aria-label="Direct link to The ideal contributor" title="Direct link to The ideal contributor" translate="no">​</a></h2>
<p>As an open-source maintainer, you imagine the ideal contributor as an individual that is excited about your project, uses it and understands it, and wants to contribute to make it better for themselves, others, or because of an exciting technical problem.
You get to share ideas with them, learn from each other, maybe even get to know them a bit as a person in the process, and they inspire you to do better work. A profoundly human, intellectual interaction, inspiring and fulfilling, sometimes even resulting in a life-long relationship.</p>
<p>When that happens, it is an amazing experience, absolutely my favorite part of building open-source software.</p>
<p>I still remember when Craig, whom we didn't know yet then, came out of nowhere and <a href="https://github.com/wasp-lang/wasp/issues/109#issuecomment-841235518" target="_blank" rel="noopener noreferrer" class="">shared his proposal</a> for formal language grammar for Wasp, a proper <a href="https://github.com/wasp-lang/wasp/files/6478938/wasplang.pdf" target="_blank" rel="noopener noreferrer" class="">Latex document</a>: I had to take a week to refresh my knowledge of type inference and language grammars just to be able to respond. The whole team looked together at that document, not believing the work put into it. He ended up doing 3 summer internships in a row with us, implementing a big part of Wasp compiler and language server, and was a delight to work with.</p>
<p>Or, another, more recent situation, when I got somewhat stuck on pushing Windows support for Wasp forward, and <a href="https://github.com/wasp-lang/wasp/pull/3020#issuecomment-3192811586" target="_blank" rel="noopener noreferrer" class="">@nodtem66 came in</a> with investigation and experiments of his own, effectively unblocking me and becoming a brainstorming partner for driving the feature forward. I remember being impressed by the thoroughness of the work from his side, there was that level of rigor to it that took me back to the uni times, and it was quite an inspiration at the moment.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-reality">The reality<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#the-reality" class="hash-link" aria-label="Direct link to The reality" title="Direct link to The reality" translate="no">​</a></h2>
<p>However, for every such interaction, there is probably 10x or more low-quality contributions.</p>
<p>And I don't mean low-quality because the contributor is missing technical knowledge, but low-quality because motivation was never right: no real interest for the project, focus instead being on merging the PRs for the sake of merging them, to pump up the author's GitHub account or CV with the proof of contributing to popular open-source repos, or to win some kind of award (e.g. during Hacktoberfest).</p>
<p>What I find most demotivating regarding such low-quality interactions is that when I see a new PR, I can't help but get excited: maybe this is a "good" one, the one where rich, inspiring interaction will happen. But what most likely follows is a dissapointment, and this is a part of what grinds the open-source maintainers down with time.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-ai-made-it-worse">How AI made it worse<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#how-ai-made-it-worse" class="hash-link" aria-label="Direct link to How AI made it worse" title="Direct link to How AI made it worse" translate="no">​</a></h2>
<p>The main thing that changed for worse recently though, with the rise of AI, is that it became very easy to create open-source contributions that look good at first, but there is no real substance or quality behind them.</p>
<p>Before, one could quickly assess the PR for quality: if it looked complex and good, the person behind it for sure had to put the effort and obtain a certain level of understanding of the codebase and the subject matter.
Effort was put in, so you didn't feel bad putting effort from your side also, while reviewing it.</p>
<p>Now, you often just can't know till you dive in deeper.</p>
<p>Good example is Craig's contribution of a Latex document with the new formal grammar for Wasp that I mentioned above. When Craig submitted that in 2021, I didn't think twice about investing a whole week of my own time to be able to review that PR properly. I was brimming with excitement. Even though I knew nothing about Craig.</p>
<p>Today, if I received such a contribution, my first assumption would be that it was AI generated, with no deep understanding of the matter by the author. I wouldn't dare invest a week, or even a day of my own time, to evaluate it.</p>
<p>And to be clear, it's not even about purely evaluating the correctness of the submitted work: maybe it is correct, maybe it works well, maybe it is even well designed. The problem is, I can't rely on the person behind it. I can't hope that there will be a rich, fulfilling cooperation coming out of this, resulting in new ideas, in growing together, creating something together. And if so, if the whole contribution is indeed primarily AI driven, then what is the point? If I wanted to tackle it myself like that, I will prompt my own AI, likely with a better prompt and better context.</p>
<p>This sucks. It sucks that my first assumption these days on seeing a contribution is that it is AI generated, and I wish it wasn't so, but that is how it is at the moment. It sucks for the maintainers, and it also sucks for the honest contributors that are putting in the real work.</p>
<p>What can one do then, as a new contributor to an open-source project, to surpass this?
I thought about this recently, and I believe it comes down to a single thing: <strong>building trust</strong>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-to-build-trust-as-a-new-open-source-contributor">How to build trust as a new open-source contributor<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#how-to-build-trust-as-a-new-open-source-contributor" class="hash-link" aria-label="Direct link to How to build trust as a new open-source contributor" title="Direct link to How to build trust as a new open-source contributor" translate="no">​</a></h2>
<p>Before, that was relatively easy: a well-crafted, quality PR would get you a long way.</p>
<p>Today, more is needed, and I will give some ideas below on how to do this, that would do it for me as an open-source maintainer.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="be-sincere-be-human">Be sincere, be human<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#be-sincere-be-human" class="hash-link" aria-label="Direct link to Be sincere, be human" title="Direct link to Be sincere, be human" translate="no">​</a></h3>
<p>Be an honest human and treat others as such.</p>
<p>This is it really. It was always important, but now it is crucial. Everything else stems from it.</p>
<p>Don't treat the project and people behind it as resources or means to an end, e.g. just for getting a notch for your CV. Instead find a project for which you have an honest interest, and it will immediately show.</p>
<p>Also don't be shy to engage in conversation. Maintainers are also humans and will appreciate sincere interaction.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="coommunicate-your-motivation">Coommunicate your motivation<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#coommunicate-your-motivation" class="hash-link" aria-label="Direct link to Coommunicate your motivation" title="Direct link to Coommunicate your motivation" translate="no">​</a></h3>
<p>Communicate why you are excited about the project, what you have used it for so far, why you want to contribute. You might think it is obvious, but it's often not. It helps maintainers "place you", figure out how to best direct you, what they can expect from you.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="dont-use-ai-for-writing-eg-pr-descriptions">Don't use AI for writing (e.g. PR descriptions)<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#dont-use-ai-for-writing-eg-pr-descriptions" class="hash-link" aria-label="Direct link to Don't use AI for writing (e.g. PR descriptions)" title="Direct link to Don't use AI for writing (e.g. PR descriptions)" translate="no">​</a></h3>
<p>Don't let the AI write for you, or even enhance your writing. This goes for any text others will have to read really. Better to have it not be perfect, than to make others doubt if there is a human behind that text or not. Even if you are not native speaker and are just using AI to "fix" your text: either prompt it to only fix the most minor grammar issues, or use something else like Grammarly, to ensure it doesn't change your tone.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="own-the-contribution">Own the contribution<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#own-the-contribution" class="hash-link" aria-label="Direct link to Own the contribution" title="Direct link to Own the contribution" translate="no">​</a></h3>
<p>Check the specific project's contributing guidelines, but most projects won't mind you using AI, as long as you own the contribution: you should own and stand behind every line of code and every decision in your PR, exactly as if no AI was involved. That means you've read it, run it, understood it, and you can explain and defend it under review.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="start-with-easier-smaller-issues">Start with easier, smaller issues<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#start-with-easier-smaller-issues" class="hash-link" aria-label="Direct link to Start with easier, smaller issues" title="Direct link to Start with easier, smaller issues" translate="no">​</a></h3>
<p>Pick issues that are not demanding on maintainers to review, so they can get to know you and your work before having to invest a lot of time. Make it as easy as possible to review, and explain your reasoning and approach.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="agree-with-maintainers-on-what-to-work-on-before-you-start">Agree with maintainers on what to work on before you start<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#agree-with-maintainers-on-what-to-work-on-before-you-start" class="hash-link" aria-label="Direct link to Agree with maintainers on what to work on before you start" title="Direct link to Agree with maintainers on what to work on before you start" translate="no">​</a></h3>
<p>Learn which issues would maintainers be happy with you taking on. Old issues might have become irrelevant, issues requiring a lot of "taste" for the project or issues touching core parts of the project might be quite mentally taxing to review, etc.</p>
<p>That said, just asking "what are good issues for a beginner" might not be enough. Some repos might have those organized and ready, but many don't, and it also depends on your skills and interests.</p>
<p>What is better is to come already with some suggestions of your own and ask if any of these would be right to start with. While also explaining why each of these is interesting to you and why you would like to tackle it. Even if none of those are a good starting issue, maintainers will now have a much better idea of what you are looking for and will be able to more easily suggest some other issue.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="use-the-project">Use the project<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#use-the-project" class="hash-link" aria-label="Direct link to Use the project" title="Direct link to Use the project" translate="no">​</a></h3>
<p>Ideally, this would be the reason why you want to contribute: you are a user that wants to give back, make it better for themselves and others.</p>
<p>But even if this is not the case and you want to contribute for some other reason, e.g. because you really like the tech stack and want to gain some experience with it, you should take some time to use the project and learn about it, understand it better.</p>
<p>This will also help with coming up with the ideas for the issues you want to contribute to: you will identify parts of the project you think could be better, and can start from there.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="final-thoughts">Final thoughts<a href="https://wasp.sh/blog/2026/08/13/advice-for-contributing-in-2026#final-thoughts" class="hash-link" aria-label="Direct link to Final thoughts" title="Direct link to Final thoughts" translate="no">​</a></h2>
<p>While it is harder to establish trust as an open-source contributor these days than it was before due to AI, there is a silver lining to it: solution is to be more human and more mindful, which was always the right way to do it.</p>]]></content:encoded>
            <author>martin@wasp-lang.dev (Martin Sosic)</author>
            <category>open source</category>
            <category>ai</category>
        </item>
        <item>
            <title><![CDATA[Wasp now supports Resend for sending emails]]></title>
            <link>https://wasp.sh/blog/2026/08/03/wasp-resend-email-provider</link>
            <guid>https://wasp.sh/blog/2026/08/03/wasp-resend-email-provider</guid>
            <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Wasp 0.25 adds Resend as a first-class email sender provider: set provider to Resend, add your API key, and start sending emails from your full-stack app.]]></description>
            <content:encoded><![CDATA[<p>Wasp 0.25 adds <a href="https://resend.com/" target="_blank" rel="noopener noreferrer" class="">Resend</a> as a first-class email sender provider, right next to Mailgun, SendGrid, and SMTP. Set <code>provider: "Resend"</code>, add your API key, and you're sending emails. Big thanks to community contributor <a href="https://github.com/jamiedavenport" target="_blank" rel="noopener noreferrer" class="">Jamie Davenport</a>, who built the whole thing!</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-resend">Why Resend<a href="https://wasp.sh/blog/2026/08/03/wasp-resend-email-provider#why-resend" class="hash-link" aria-label="Direct link to Why Resend" title="Direct link to Why Resend" translate="no">​</a></h2>
<p>Resend has quickly become one of the most loved email APIs among developers, and it's easy to see why: a clean API, a generous free tier, and great DX around domain setup and debugging. It's also the team behind <a href="https://react.email/" target="_blank" rel="noopener noreferrer" class="">React Email</a>, so it fits naturally into the React + Node.js world Wasp lives in.</p>
<p>It's been one of our most requested integrations for a while. You could already use Resend with Wasp over SMTP, but now it's a first-class provider: no SMTP credentials, no extra packages, just the official Resend SDK wired in for you.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-to-use-it">How to use it<a href="https://wasp.sh/blog/2026/08/03/wasp-resend-email-provider#how-to-use-it" class="hash-link" aria-label="Direct link to How to use it" title="Direct link to How to use it" translate="no">​</a></h2>
<p>Set the provider to <code>Resend</code> in your <code>main.wasp.ts</code> file:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockTitle_gul4">main.wasp.ts</div><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> app </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"myApp"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  emailSender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">    provider</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Resend"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    defaultFrom</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Example"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      email</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"hello@itsme.com"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><br></div></code></pre></div></div>
<p>Then grab an API key from the <a href="https://resend.com/api-keys" target="_blank" rel="noopener noreferrer" class="">Resend dashboard</a> and add it to your <code>.env.server</code> file:</p>
<div class="language-properties codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockTitle_gul4">.env.server</div><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-properties codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token plain">RESEND_API_KEY=</span><br></div></code></pre></div></div>
<p>That's the whole setup. Now you can send emails from anywhere on the server:</p>
<div class="language-ts codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockTitle_gul4">src/actions/sendEmail.ts</div><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-ts codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> emailSender </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"wasp/server/email"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// In some action handler...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> info </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> emailSender</span><span class="token punctuation" style="color:#393A34">.</span><span class="token function" style="color:#d73a49">send</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  to</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"user@domain.com"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  subject</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Saying hello"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  text</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Hello world"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  html</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Hello &lt;strong&gt;world&lt;/strong&gt;"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>And since <code>emailSender</code> is what Wasp uses under the hood for everything email-related, this also covers your <a class="" href="https://wasp.sh/docs/features/auth/email/overview">email authentication</a> flows - verification emails and password resets now go through Resend too, with zero extra code.</p>
<p>As with all Wasp providers, switching is a one-line change. Started on SMTP and want to move to Resend (or the other way around)? Change the <code>provider</code> field, swap the env variables, and everything else keeps working.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="built-by-the-community">Built by the community<a href="https://wasp.sh/blog/2026/08/03/wasp-resend-email-provider#built-by-the-community" class="hash-link" aria-label="Direct link to Built by the community" title="Direct link to Built by the community" translate="no">​</a></h2>
<p>This feature was contributed by <a href="https://github.com/jamiedavenport" target="_blank" rel="noopener noreferrer" class="">Jamie Davenport</a>, who took it from idea to merged PR (<a href="https://github.com/wasp-lang/wasp/pull/4381" target="_blank" rel="noopener noreferrer" class="">#4381</a>): the provider implementation, env variable validation, and docs. This is exactly the kind of contribution that makes open source fun - thanks, Jamie! 🙏</p>
<p>If you'd like to see your name here next time, check out our <a href="https://github.com/wasp-lang/wasp/blob/main/CONTRIBUTING.md" target="_blank" rel="noopener noreferrer" class="">contributing guide</a> or come say hi on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a> - we're always happy to help you find a good first issue.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="try-it-out">Try it out<a href="https://wasp.sh/blog/2026/08/03/wasp-resend-email-provider#try-it-out" class="hash-link" aria-label="Direct link to Try it out" title="Direct link to Try it out" translate="no">​</a></h2>
<p>Resend support is live in Wasp 0.25. If you're not on it yet, update your Wasp CLI:</p>
<div data-track-event="Install Command: Copy" class="contents"><div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">npm</span><span class="token plain"> i </span><span class="token parameter variable" style="color:#36acaa">-g</span><span class="token plain"> @wasp.sh/wasp-cli</span><br></div></code></pre></div></div></div>
<p>Then set <code>provider: "Resend"</code>, add your API key, and send your first email. Check out the <a class="" href="https://wasp.sh/docs/features/email#resend">email sending docs</a> for the full reference.</p>
<p>We'd love to hear how it works for you - come chat with us on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a>!</p>]]></content:encoded>
            <author>matija@wasp-lang.dev (Matija Sosic)</author>
            <category>wasp</category>
            <category>email</category>
            <category>resend</category>
            <category>webdev</category>
            <category>fullstack</category>
        </item>
        <item>
            <title><![CDATA[Buzz + Wasp: from one chat message to a deployed full-stack app]]></title>
            <link>https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app</link>
            <guid>https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app</guid>
            <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[I typed one message into a chat channel in Buzz and an agent scaffolded, deployed, and shipped a live full-stack CRM with Wasp. Here's the recipe, written so a human or an agent can follow it.]]></description>
            <content:encoded><![CDATA[<p><img decoding="async" loading="lazy" alt="The original Prompt in Buzz" src="https://wasp.sh/assets/images/prompt-9592bd89548a195f893189d70b6b232c.webp" width="3024" height="1964" class="img_qXxT"></p>
<p>A couple of weeks ago I typed this into a chat channel:</p>
<blockquote>
<p>spin up a simple CRM app using the Wasp full-stack framework and deploy it to Railway</p>
</blockquote>
<p>Then I went back to what I was doing. Before I'd even checked in on it, an agent named Fizz had scaffolded the app, wired up auth and a Postgres database, pushed the code to a repo, deployed it to Railway, and posted back <strong>screenshots and a live URL</strong>.</p>
<p><img decoding="async" loading="lazy" alt="The deployed Buzz CRM dashboard" src="https://wasp.sh/assets/images/crm-ca209f911b742686a6e79b711ee9c4aa.webp" width="2880" height="1692" class="img_qXxT"></p>
<!-- -->
<p>When I showed the chat log on a podcast, the host's reaction was: <em>"That's insane. We're kind of glossing over it, but look what we built. It's live on the internet already."</em></p>
<p><a href="https://www.youtube.com/watch?v=jGSgzBkzrY" target="_blank" rel="noopener noreferrer" class=""><img decoding="async" loading="lazy" alt="The Startup Ideas podcast reaction" src="https://wasp.sh/assets/images/podcast-30ee7d235ee32c84fcc29d4712e120a6.webp" width="3022" height="1800" class="img_qXxT"></a></p>
<p>That app is still live: <a href="https://buzz-crm-client-production.up.railway.app/" target="_blank" rel="noopener noreferrer" class="">buzz-crm-client-production.up.railway.app</a>. The code is here: <a href="https://github.com/vincanger/buzz-crm" target="_blank" rel="noopener noreferrer" class="">github.com/vincanger/buzz-crm</a>.</p>
<p>This post is the recipe, so you can do it yourself. And if even the recipe feels like work, skip to the <a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#too-lazy-good" class="">last section</a> and make your agent follow it for you.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="whats-happening-here">What's happening here?<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#whats-happening-here" class="hash-link" aria-label="Direct link to What's happening here?" title="Direct link to What's happening here?" translate="no">​</a></h2>
<p>Two awesome tools are meeting in the middle:</p>
<p><strong><a href="https://buzz.xyz/" target="_blank" rel="noopener noreferrer" class="">Buzz</a></strong> is the free, open-source, agent-native chat platform from Jack Dorsey's team at Block. Agents aren't bolted-on integrations, they're teammates in your channels, running on the coding subscriptions you already pay for (Claude Code, Codex, whatever). You talk to them; they do the work and report back where everyone can see it.</p>
<p><strong><a href="https://wasp.sh/" target="_blank" rel="noopener noreferrer" class="">Wasp</a></strong> is our full-stack TypeScript framework. You declare the big pieces (auth, database, jobs, deployment) at the config level, and Wasp wires them up. That's pleasant for humans, but it turns out to be <em>huge</em> for agents: fewer decisions means fewer wrong decisions, and shipping is one command the agent can actually run instead of forty minutes of dashboard clicking.</p>
<p>So you're getting a chat + agent orchestration platform where agents finish tasks + a framework that does the heavy lifting!</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-recipe">The recipe<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#the-recipe" class="hash-link" aria-label="Direct link to The recipe" title="Direct link to The recipe" translate="no">​</a></h2>
<p>Each step ends with a ✅ check, so you (or your agent, see below) know it actually worked before moving on.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="1-get-buzz-and-plug-in-an-agent">1. Get Buzz and plug in an agent<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#1-get-buzz-and-plug-in-an-agent" class="hash-link" aria-label="Direct link to 1. Get Buzz and plug in an agent" title="Direct link to 1. Get Buzz and plug in an agent" translate="no">​</a></h3>
<p>Download Buzz from <a href="https://buzz.xyz/" target="_blank" rel="noopener noreferrer" class="">buzz.xyz</a> (free). On first run it detects the coding harnesses installed on your machine (Claude Code, Codex, Cursor, OpenCode, Hermes, etc. ) and connects them, so your agents run on the subscription you already have. Create a channel, add an agent.</p>
<p>✅ <strong>Check:</strong> say hi to your agent in a channel and get a reply.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="2-install-wasp">2. Install Wasp<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#2-install-wasp" class="hash-link" aria-label="Direct link to 2. Install Wasp" title="Direct link to 2. Install Wasp" translate="no">​</a></h3>
<div data-track-event="Install Command: Copy" class="contents"><div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">npm</span><span class="token plain"> i </span><span class="token parameter variable" style="color:#36acaa">-g</span><span class="token plain"> @wasp.sh/wasp-cli@latest</span><br></div></code></pre></div></div></div>
<p>One catch worth knowing up front: Wasp needs a recent Node (0.24 requires ≥ 24.14.1), and agent runtimes sometimes ship their own older Node on PATH. If the agent hits a version error, tell it to use your nvm-installed Node explicitly (that one line fixes the most common failure in this whole flow).</p>
<p>✅ <strong>Check:</strong> <code>wasp version</code> prints a version.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="3-send-the-message">3. Send the message<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#3-send-the-message" class="hash-link" aria-label="Direct link to 3. Send the message" title="Direct link to 3. Send the message" translate="no">​</a></h3>
<p>Mine, nearly verbatim:</p>
<div class="language-sh codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-sh codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token operator" style="color:#393A34">&gt;</span><span class="token plain"> spin up a simple CRM app using the Wasp full-stack framework</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token operator" style="color:#393A34">&gt;</span><span class="token plain"> deploy it to Railway. </span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token operator" style="color:#393A34">&gt;</span><span class="token plain"> send screenshots and the live URL when it's up.</span><br></div></code></pre></div></div>
<p>A good prompt here names three things: <strong>the framework</strong> (so the agent doesn't hand-roll an Express app), <strong>the deploy target</strong> (Wasp has one-command deploys to Railway and Fly), and <strong>proof of done</strong> (screenshots + URL, make the agent show its work).</p>
<p>✅ <strong>Check:</strong> the agent replies with a plan and starts working. Now leave it alone.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="4-trust-but-verify-the-deploy">4. Trust, but verify the deploy<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#4-trust-but-verify-the-deploy" class="hash-link" aria-label="Direct link to 4. Trust, but verify the deploy" title="Direct link to 4. Trust, but verify the deploy" translate="no">​</a></h3>
<p>Here's the honest part. Deploy CLIs sometimes report success while the build is still running, the agent sees exit code 0, declares victory, and posts a URL that 404s. So the finish line is not "the deploy command succeeded." The finish line is:</p>
<p>✅ <strong>Check:</strong> the app URL returns a real page (have the agent poll the deploy status until it leaves <code>BUILDING</code>, then curl the URL), and the agent posts a screenshot of the logged-in app.</p>
<p>That's the whole recipe. Mine took one message and a coffee's worth of waiting.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="then-keep-talking-this-is-the-actual-magic">Then keep talking (this is the actual magic)<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#then-keep-talking-this-is-the-actual-magic" class="hash-link" aria-label="Direct link to Then keep talking (this is the actual magic)" title="Direct link to Then keep talking (this is the actual magic)" translate="no">​</a></h2>
<p>The deploy isn't the end; it's the beginning of a conversation that never leaves your team's context.</p>
<p><img decoding="async" loading="lazy" alt="The CRM&amp;#39;s deals pipeline view" src="https://wasp.sh/assets/images/pipeline-c32f7276f2d3f065f73217841d82d8c7.webp" width="2880" height="1704" class="img_qXxT"></p>
<p>"Add a kanban view for deals." "The contacts table needs search." Teammates join the channel, argue about what's missing, and tag the agent (which has the entire history of the project <em>in the chat</em>). The repo, the decisions, the screenshots, and the discussion all live in one place. No handoff documents, no "wait, why did we do it this way?", scroll up.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="real-talk-gotchas">Real-talk gotchas<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#real-talk-gotchas" class="hash-link" aria-label="Direct link to Real-talk gotchas" title="Direct link to Real-talk gotchas" translate="no">​</a></h2>
<p>We're an honest bunch, so: this is early-preview territory, and these three things will save you an afternoon.</p>
<ul>
<li class=""><strong>Node versions.</strong> The #1 stumble. Agent harnesses can ship their own Node; Wasp wants a recent one. Tell the agent which Node to use if it errors (see step 2).</li>
<li class=""><strong>"Deployed" isn't deployed.</strong> Exit code 0 from a deploy CLI can just mean "upload accepted." Make the agent verify with a real HTTP request (step 4).</li>
<li class=""><strong>Buzz is young.</strong> Workflows/automations are still rough, and chatting through a relay is slower than working in a terminal directly. For a complex existing codebase, use your harness straight. For going zero-to-shipped with your team watching? This flow is unbeatable.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-wasp-is-the-right-tool-for-agents">Why Wasp is the right tool for agents<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#why-wasp-is-the-right-tool-for-agents" class="hash-link" aria-label="Direct link to Why Wasp is the right tool for agents" title="Direct link to Why Wasp is the right tool for agents" translate="no">​</a></h2>
<p>Agents are great at writing application code and mediocre at plumbing decisions (which auth library, how to structure the deploy, where the job queue goes).</p>
<p>Wasp moves exactly those decisions into a declarative config with sane defaults, and gives back one-command answers for the scary parts (e.g. <code>wasp deploy railway launch</code>). The agent's effort goes into what makes <em>your app unique</em> (the data model, the pages, the features) instead of boilerplate. That's why one message was enough.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="too-lazy-good">Too lazy to follow the recipe? Good.<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#too-lazy-good" class="hash-link" aria-label="Direct link to Too lazy to follow the recipe? Good." title="Direct link to Too lazy to follow the recipe? Good." translate="no">​</a></h2>
<p>Just give your agent a raw, AI-friendly copy of this post:</p>
<div class="language-text codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-text codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token plain">https://raw.githubusercontent.com/wasp-lang/wasp/release/web/blog/2026-07-30-buzz-wasp-one-message-app.mdx</span><br></div></code></pre></div></div>
<p>…paste it to your Buzz agent, and say: <strong>"follow this recipe and build me a [your app idea]."</strong> The ✅ checks above are written so an agent can verify each step itself (including not trusting the deploy CLI). The blogpost <em>is</em> the runbook. Report back with what you shipped.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="try-it">Try it<a href="https://wasp.sh/blog/2026/07/30/buzz-wasp-one-message-app#try-it" class="hash-link" aria-label="Direct link to Try it" title="Direct link to Try it" translate="no">​</a></h2>
<p><a href="https://wasp.sh/" target="_blank" rel="noopener noreferrer" class="">Install Wasp</a> → grab <a href="https://buzz.xyz/" target="_blank" rel="noopener noreferrer" class="">Buzz</a> → send the message. If you ship something, tag <a href="https://twitter.com/wasplang" target="_blank" rel="noopener noreferrer" class="">@wasplang</a>, we collect these.</p>
<p>*Want the longer story? I talked through the whole Buzz + Wasp workflow on two podcasts: <a href="https://www.youtube.com/watch?v=P1KpxzLVg7c" target="_blank" rel="noopener noreferrer" class="">Agent Native, with Riley Brown</a>. and <a href="https://www.youtube.com/watch?v=jGSgzBkzrY" target="_blank" rel="noopener noreferrer" class="">The Startup Ideas, with Greg Isenberg</a> and ook *</p>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>buzz</category>
            <category>ai agents</category>
            <category>ai</category>
            <category>full-stack</category>
        </item>
        <item>
            <title><![CDATA[Made with Wasp: how Searchcraft built a full-stack SaaS around their Rust search engine]]></title>
            <link>https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft</link>
            <guid>https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft</guid>
            <pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Searchcraft, a Rust search engine and Algolia alternative, built its customer dashboard on Wasp and Open SaaS: auth, billing and analytics.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Searchcraft - a Rust-based search engine, with its Wasp-powered customer dashboard" src="https://wasp.sh/img/blog/2026-07-20-made-with-wasp-searchcraft/searchcraft-hero.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="tldr">TL;DR<a href="https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft#tldr" class="hash-link" aria-label="Direct link to TL;DR" title="Direct link to TL;DR" translate="no">​</a></h2>
<ul>
<li class=""><strong><a href="https://searchcraft.io/" target="_blank" rel="noopener noreferrer" class="">Searchcraft</a></strong> is a search engine written in Rust: an Algolia / Elasticsearch alternative that's light enough to run full-text search over all of English Wikipedia <a href="https://www.youtube.com/watch?v=SjuPn6_yl2s" target="_blank" rel="noopener noreferrer" class="">on a single Raspberry Pi</a>.</li>
<li class="">Their full-stack customer dashboard (auth, billing, analytics, index management) is built with <strong>Wasp</strong> and the <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a> template.</li>
<li class="">They could have built the SaaS layer themselves, but chose not to, so their engineering time stays in the Rust engine where they actually compete.</li>
<li class="">Wasp compiles to standard React + Node.js + Prisma, deployed on their own AWS and CI/CD. No lock-in, no restructuring.</li>
</ul>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-is-searchcraft">What is Searchcraft?<a href="https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft#what-is-searchcraft" class="hash-link" aria-label="Direct link to What is Searchcraft?" title="Direct link to What is Searchcraft?" translate="no">​</a></h2>
<p><a href="https://searchcraft.io/" target="_blank" rel="noopener noreferrer" class="">Searchcraft</a> is a search engine written in Rust, built for product search, site search, and content discovery, competing with Elasticsearch, Algolia, OpenSearch, and Solr on a simple bet: <strong>search should be fast to integrate, light on resources, and easy to run.</strong></p>
<p>How light on resources? Their CTO, Don, runs full-text search over the <em>entire English Wikipedia</em> on a single Raspberry Pi. That's the engine's whole personality in one image: it doesn't need a cluster to be useful.</p>
<p>The team is small and bootstrapped: a handful of engineers who spent years running a dev agency before going all-in on their own product. That history matters here, because they shipped client work in Next.js, Nuxt, and Angular, whatever stack the client brought.</p>
<p>And they're in production. Their first customer is a publisher running 22 local news sites with around 4 million active readers, rolling out site by site, with e-commerce and B2B SaaS next in line. Searchcraft ships as a managed cloud service or self-hosted, with SDKs for JavaScript, TypeScript, and PHP.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="every-engine-needs-a-chassis---so-they-chose-wasp">Every engine needs a chassis - so they chose Wasp<a href="https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft#every-engine-needs-a-chassis---so-they-chose-wasp" class="hash-link" aria-label="Direct link to Every engine needs a chassis - so they chose Wasp" title="Direct link to Every engine needs a chassis - so they chose Wasp" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The onboarding screen: import documents from a feed URL, a file, or WordPress" src="https://wasp.sh/img/blog/2026-07-20-made-with-wasp-searchcraft/vektron-documents-onboarding.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">The onboarding screen - Searchcraft's design is super cool!</figcaption></figure></div>
<p>Searchcraft's plan is developer-led growth: a developer who finds it at 2am has to get from curiosity to a working search box on their own. That means sign-up, orgs, roles, indexes, API keys, analytics, billing. <strong>A full, production-ready SaaS application (auth, database, background jobs, emails, payments, admin) wrapped around the thing you actually sell.</strong></p>
<p>They could have built it, but chose not to. The SaaS layer is a hundred solved problems that still take months to solve again and then ask for maintenance forever, and every hour on auth flows and CRUD plumbing is an hour not spent on relevance ranking, ingestion speed, or memory footprint, the things Searchcraft actually competes on.</p>
<p>The answer came from inside the house: Don, the CTO, had been following Wasp. <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>, Wasp's open-source template, meant auth, payments, and an admin panel existed on day one, as code they own, not services they rent. And they evaluated it like engineers: everything Wasp generates is standard React, Node.js, and Prisma they could read, trust, and run themselves, no magic to open up. <strong>It's their code</strong>, and it compiles to one integrated stack built to keep holding together as the app grows.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-they-built-the-full-stack-customer-dashboard">What they built: the full-stack customer dashboard<a href="https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft#what-they-built-the-full-stack-customer-dashboard" class="hash-link" aria-label="Direct link to What they built: the full-stack customer dashboard" title="Direct link to What they built: the full-stack customer dashboard" translate="no">​</a></h2>
<p>The dashboard is Searchcraft's control room, "a product within a product," where customers run everything from document ingestion to search tuning, team management, and analytics.</p>
<p>Three moments show what's actually running under the UI, because the dashboard isn't a static admin panel, it's a full-stack app where Wasp is doing real work end to end:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Organization dashboard with live usage stats, conversion and retention scores" src="https://wasp.sh/img/blog/2026-07-20-made-with-wasp-searchcraft/vektron-dashboard-analytics.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">What's behind this screen: server-side queries turning raw search events into live stats and multi-tenant access control, all in one Wasp codebase.</figcaption></figure></div>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Application view with the index registry and total searches chart" src="https://wasp.sh/img/blog/2026-07-20-made-with-wasp-searchcraft/vektron-app-searches.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">What's behind this screen: a multi-tenant index registry in Prisma, kept in sync with the Rust engine over one API, with search events rolled up into the time windows above. The chart is React; the plumbing is Wasp's type-safe operations.</figcaption></figure></div>
<div style="display:flex;justify-content:center;margin:1rem 0"><figure style="width:100%;margin:0"><video width="100%" controls="" aria-label="Organization settings with subscription plans and upgrades"><source src="/img/blog/2026-07-20-made-with-wasp-searchcraft/vektron-subscription-settings.mp4" type="video/mp4"></video><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">What's behind this screen: subscription plans and upgrades, the billing machinery every SaaS needs and nobody wants to hand-roll, running in the same Wasp app and wired into the quotas from the first screen.</figcaption></figure></div>
<p>Around those three screens sits the rest of a real SaaS: an ingestion pipeline that infers the schema as it pulls documents in, crew management with roles, access keys as managed secrets, and a code-snippets page that takes a frontend dev from API key to working search box in minutes. Multi-tenant, role-based, revenue-carrying, and it looks the part. For a search company, the user portal <em>is</em> the brand.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-it-runs-wasp-next-to-rust">How it runs: Wasp next to Rust<a href="https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft#how-it-runs-wasp-next-to-rust" class="hash-link" aria-label="Direct link to How it runs: Wasp next to Rust" title="Direct link to How it runs: Wasp next to Rust" translate="no">​</a></h2>
<p>The shape is the interesting part. On one side, the Searchcraft engine and its supporting services (provisioning, ingestion), all Rust, all theirs. On the other, the customer dashboard: a Wasp app (React + Node.js + Prisma) that talks to the engine over an API. Customer apps consume search through the SDKs and never know the portal exists.</p>
<p>Here's the architecture, drawn by the Searchcraft team:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Architecture diagram: the customer dashboard (Wasp app), Searchcraft Server (Rust), provisioning and ingestion services (Rust), SDKs, customer apps" src="https://wasp.sh/img/blog/2026-07-20-made-with-wasp-searchcraft/searchcraft-architecture.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">The dashboard, a Wasp app, handles users, configuration, and analytics; the Searchcraft engine and its Rust services do the search. One API connects them, and customer apps reach search through the SDKs.</figcaption></figure></div>
<p><strong>Two systems, one product, one API between them.</strong></p>
<p>Wasp didn't ask them to restructure anything; it slotted in next to the architecture they already had. If your real product lives in Rust, Go, Python, or Java, this is the part that applies to you.</p>
<p><strong>Deployment, their way.</strong> Wasp comes with one-line deployment commands for popular hosts, but teams keep full freedom over where the app runs. Searchcraft already had infrastructure on AWS, so that's where it went: their own CI/CD on Bitbucket Pipelines, client and server deploying separately onto the setup they already trust. Because a Wasp app compiles to portable artifacts, both doors stay open, and having that choice was part of the point.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="whats-next">What's next<a href="https://wasp.sh/blog/2026/07/20/made-with-wasp-searchcraft#whats-next" class="hash-link" aria-label="Direct link to What's next" title="Direct link to What's next" translate="no">​</a></h2>
<p>Searchcraft is expanding the platform: Searchcraft Cloud, a self-hosted Core for teams running their own infrastructure, more SDKs, and AI-powered Search Result Summaries, with more coming for LLM-native search:</p>
<blockquote>
<p><strong>"We are building in MCP support so that you can connect it to an LLM if you want."</strong></p>
</blockquote>
<p>Search that agents can talk to, from an engine small enough to run anywhere: it's a good bet, and they get to make it because their engineering time goes into the engine, not the app around it. That was the whole trade: the hard problems stay in Rust, where their edge is, and the SaaS layer lives in a Wasp app they fully own.</p>
<p>If you're in the same spot (a real product in a custom backend, and you need a full-stack dashboard around it), that's the conversation <a class="" href="https://wasp.sh/">Wasp</a> wants to have with you.</p>
<hr>
<p><em>Thanks to the Searchcraft team for the walkthroughs, the diagram, and the stories. Check out <a href="https://searchcraft.io/" target="_blank" rel="noopener noreferrer" class="">Searchcraft</a>!</em></p>]]></content:encoded>
            <author>matija@wasp-lang.dev (Matija Sosic)</author>
            <category>showcase</category>
            <category>wasp</category>
            <category>saas</category>
            <category>rust</category>
            <category>web dev</category>
        </item>
        <item>
            <title><![CDATA[Why design matters for a web framework: a 7-year evolution]]></title>
            <link>https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework</link>
            <guid>https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework</guid>
            <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[After five years of improvised design, Wasp rebranded as a technical spec: blueprints, monospace type, three colors and only sharp corners.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The Wasp mark across four labeled eras on a timeline: 2019 STIC (an actual stick), 2019 'wasp' (the rename, three triangles), 2020 Alpha (the =} arrives, in a circle), and 2026 today (bulked up + locked in a square)" src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/rebrand-logo-progression-real.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p><a href="https://wasp.sh/" target="_blank" rel="noopener noreferrer" class="">Wasp</a> is a full-stack web framework for React and Node.js (imagine Rails for TypeScript, but with frontend included and wired up out-of-the-box), and we've been building it for a little over five years (as a full-time thing). For almost all of that time, we saw design and "branding" as something we shouldn't spend too much time on.</p>
<p>A framework is mostly code, we thought: you drive it from a CLI and your editor, there is little visual to look at, and these days an agent reads the docs for you half the time anyway. The most loved frameworks kind of prove the point, with Django and Rails famous and famously plain.</p>
<p>Turns out we were wrong, though not in the way you'd expect. What made design start to matter wasn't users or growth - it was us, the people building Wasp and the community around it.</p>
<p>This is the story of how we figured that out, and of the rebrand it led to, which shipped as part of Launch Week #12 - the same week Wasp went <a class="" href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec">fully TypeScript-native</a>.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="five-years-of-not-having-a-design">Five years of not having a design<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#five-years-of-not-having-a-design" class="hash-link" aria-label="Direct link to Five years of not having a design" title="Direct link to Five years of not having a design" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;flex-direction:column;align-items:stretch"><figure style="margin:0;position:relative"><div style="display:grid;grid-template-columns:repeat(2, 1fr);gap:8px"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/alpha-landing-atf.webp" alt="Wasp's first proper landing page from the Alpha launch in March 2021" class="no-default-zoom" style="width:100%;height:auto;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5)"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/current-wasp-sh.webp" alt="Today's wasp.sh hero after the 2026 rebrand" class="no-default-zoom" style="width:100%;height:auto;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5)"></div><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.6em;text-align:center">Same product, five years apart. Very different vibes.</figcaption></figure></div>
<p>Wasp has always had a logo, colors and fonts (ok, the fonts were whatever shipped with Docusaurus). So when I say we didn't have a design, I mean we never sat down to think about it as a whole. There was no central story, no backbone holding everything together, just a bunch of pages that happened to be ours.</p>
<p>Here's how it typically went down: with every big release (v0, Alpha, Beta), I'd sit down and convince Martin (my twin brother and co-founder) to let me "rebrand" Wasp. And every single time, I'd do almost the exact same thing: look around for some inspiration (thanks, Supabase), then patch, okay, <em>steal</em>, a few sections together into something that looked decent enough, and ship it.</p>
<p>And early on, that was the right call. When you're still proving the product deserves to exist, obsessing over a design system is a great way to burn weeks you don't really have. Plenty of founders do the opposite. They polish pixels on something nobody wants yet (and we witnessed that many times) and we were determined not to be them.</p>
<p>But design debt compounds, just like code debt does. Over five years, Wasp itself grew up <em>a lot</em>, and it grew much faster than its design did, until at some point it just overgrew it. The framework got serious, but the brand stayed improvised. You can kind of watch it happen across our old landing pages:</p>
<div class="figure-container" tabindex="0" style="display:flex;flex-direction:column;align-items:stretch;outline:none"><figure style="margin:0;position:relative"><div style="display:flex;justify-content:space-between;align-items:baseline;margin-bottom:8px"><div style="font-family:IBM Plex Mono, monospace;font-weight:600;font-size:15px">stic (before it was called wasp), 2019</div><div style="font-family:IBM Plex Mono, monospace;font-size:12px;letter-spacing:0.08em;opacity:0.6">01<!-- --> /<!-- --> <!-- -->04</div></div><div style="position:relative;overflow:hidden"><div style="display:flex;transform:translateX(-0%);transition:transform 0.35s ease"><div style="flex:0 0 100%;display:flex;justify-content:center;align-items:center"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/stic-landing-page.webp" alt="The stic-era landing page from 2019: minimal black-and-white Bulma styling, 'STIC' navbar, and the tagline 'Specification To Implementation Compiler'" class="no-default-zoom" style="max-width:100%;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5);box-sizing:border-box"></div><div style="flex:0 0 100%;display:flex;justify-content:center;align-items:center"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/alpha-landing-atf.webp" alt="The Alpha-era Wasp landing page from March 2021: '.wasp (alpha)' navbar, hero 'A simple language for developing full-stack web apps with less code', code preview on the right with React, Node.js and Prisma logos" class="no-default-zoom" style="max-width:100%;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5);box-sizing:border-box"></div><div style="flex:0 0 100%;display:flex;justify-content:center;align-items:center"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/pre-rebrand-landing-atf.webp" alt="The pre-rebrand Wasp landing page from October 2025: a Launch Week #11 announcement bar at the top, yellow gradient hero with 'Develop full-stack web apps faster', and a code preview on the right" class="no-default-zoom" style="max-width:100%;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5);box-sizing:border-box"></div><div style="flex:0 0 100%;display:flex;justify-content:center;align-items:center"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/current-wasp-sh.webp" alt="Today's wasp.sh hero after the 2026 rebrand: blueprint paper background, big monospace headline 'A truly full-stack TypeScript framework that just works.', main.wasp.ts code preview on the right" class="no-default-zoom" style="max-width:100%;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5);box-sizing:border-box"></div></div><button disabled="" aria-label="Previous" style="position:absolute;top:50%;left:8px;transform:translateY(-50%);width:40px;height:40px;border:1.5px solid var(--wasp-k);background:var(--wasp-y);color:var(--wasp-k);cursor:not-allowed;opacity:0.35;display:flex;align-items:center;justify-content:center;font-family:monospace;font-weight:700;font-size:20px;padding:0;z-index:5">‹</button><button aria-label="Next" style="position:absolute;top:50%;right:8px;transform:translateY(-50%);width:40px;height:40px;border:1.5px solid var(--wasp-k);background:var(--wasp-y);color:var(--wasp-k);cursor:pointer;opacity:1;display:flex;align-items:center;justify-content:center;font-family:monospace;font-weight:700;font-size:20px;padding:0;z-index:5">›</button></div><div style="display:flex;justify-content:center;flex-wrap:wrap;gap:8px;margin-top:16px"><button type="button" aria-label="Go to slide 1: stic (before it was called wasp), 2019" aria-current="true" title="stic (before it was called wasp), 2019" style="width:150px;height:94px;padding:0;border:2.5px solid var(--wasp-y);outline:1px solid var(--wasp-k);background:transparent;cursor:pointer;overflow:hidden;transition:border-color 0.15s, transform 0.15s;transform:scale(1.05);box-sizing:border-box"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/stic-landing-page.webp" alt="" class="no-default-zoom" draggable="false" style="width:100%;height:100%;object-fit:cover;object-position:top center;display:block;pointer-events:none"></button><button type="button" aria-label="Go to slide 2: Alpha, March 2021" aria-current="false" title="Alpha, March 2021" style="width:150px;height:94px;padding:0;border:1.5px solid var(--wasp-g5);outline:none;background:transparent;cursor:pointer;overflow:hidden;transition:border-color 0.15s, transform 0.15s;transform:none;box-sizing:border-box"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/alpha-landing-atf.webp" alt="" class="no-default-zoom" draggable="false" style="width:100%;height:100%;object-fit:cover;object-position:top center;display:block;pointer-events:none"></button><button type="button" aria-label="Go to slide 3: Pre-rebrand, October 2025" aria-current="false" title="Pre-rebrand, October 2025" style="width:150px;height:94px;padding:0;border:1.5px solid var(--wasp-g5);outline:none;background:transparent;cursor:pointer;overflow:hidden;transition:border-color 0.15s, transform 0.15s;transform:none;box-sizing:border-box"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/pre-rebrand-landing-atf.webp" alt="" class="no-default-zoom" draggable="false" style="width:100%;height:100%;object-fit:cover;object-position:top center;display:block;pointer-events:none"></button><button type="button" aria-label="Go to slide 4: Today, 2026" aria-current="false" title="Today, 2026" style="width:150px;height:94px;padding:0;border:1.5px solid var(--wasp-g5);outline:none;background:transparent;cursor:pointer;overflow:hidden;transition:border-color 0.15s, transform 0.15s;transform:none;box-sizing:border-box"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/current-wasp-sh.webp" alt="" class="no-default-zoom" draggable="false" style="width:100%;height:100%;object-fit:cover;object-position:top center;display:block;pointer-events:none"></button></div></figure></div>
<p>And once our design felt broken, there was little motivation to keep it right, so it just kept getting worse. At one point we needed to show a roadmap on the site, so Martin just screenshotted our GitHub project board and pasted it straight in. Low-res, rounded corners not quite matching, with some random background bleeding out around the edges. It stayed up like that for an embarrassingly long time:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="A screenshot of Wasp's GitHub project board pasted straight into the landing page, low-resolution and visibly mismatched with the surrounding light theme" src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/martin-gh-roadmap-on-landing.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Our roadmap section. Yes, that is just a screenshot of our GitHub project. Not even properly cropped.</figcaption></figure></div>
<p>Or take the "How does it work?" section right below it. The diagram was originally drawn as a transparent SVG, which broke once the site got a dark mode, so someone slapped a white background behind it to "fix" it. Now it looked fine on the dark version, and noticeably worse everywhere else. Add the orange highlight pills next to the copy, styled in a completely different visual language than anything else on the page, and the whole thing kind of looked like three different sites stitched together:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="An older 'How does it work?' section on wasp.sh: the diagram uses the old yellow-circle logo, a soft yellow gradient behind it, and highlight pills styled inconsistently with the rest of the page" src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/broken-how-it-works.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Our old "How it works" section, broken in a few different ways.</figcaption></figure></div>
<p>At some point we just started to feel bad about how unpolished it looked. We couldn't really tell you what users made of it (probably not much), but we could feel it ourselves: Wasp had grown into a serious product that people use for <a class="" href="https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2">serious things</a>, and it was about time it started looking like one.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="looking-unpolished-made-us-feel-unpolished">Looking unpolished made us feel unpolished<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#looking-unpolished-made-us-feel-unpolished" class="hash-link" aria-label="Direct link to Looking unpolished made us feel unpolished" title="Direct link to Looking unpolished made us feel unpolished" translate="no">​</a></h2>
<p>There was also another reason for finally taking design seriously, harder to pin down, but looking back it's pretty obvious.</p>
<p>Looking unpolished slowly does something to you. Every time we shipped a great feature next to a website that looked like a slightly abandoned student project, it sent a quiet little signal we never really meant to send: that maybe we don't actually care all that much. And that signal doesn't only go out to users; it also comes back in. A product that looks like nobody sweated the details slowly starts to <em>feel</em> like one to the people building it, even when, internally, the opposite is completely true.</p>
<p>You don't really notice it on any given day, but over five years it compounds. You hesitate a bit before posting the screenshot. You add a caveat before the demo (<em>"ignore how it looks for a second, just look at what it does"</em>). You quietly stop wanting to share Wasp with someone whose opinion you actually care about, because they might judge the wrapper instead of the thing inside. And it gets hard to pour your full energy into something you're a tiny bit embarrassed by.</p>
<p>So in a real sense, a good part of this rebrand wasn't for users at all. It was for us. We wanted to be able to look at every surface Wasp touches and not flinch, and to feel like the way Wasp looks finally matches how much we actually care about it. Looking back, that's not really vanity but basic hygiene, and we should've done it sooner.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-product-changed-so-the-skin-had-to">The product changed, so the skin had to<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#the-product-changed-so-the-skin-had-to" class="hash-link" aria-label="Direct link to The product changed, so the skin had to" title="Direct link to The product changed, so the skin had to" translate="no">​</a></h2>
<p>When we <a class="" href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake">made the call to go all-in on TypeScript</a>, we knew it wasn't a facelift. It changed what Wasp fundamentally <em>is</em>: not a custom language you have to learn, but a framework that meets you where you already are.</p>
<p>That forced an uncomfortable question: if someone landed on wasp.sh today, would they actually see that? Honestly, no. The old look still said "quirky side project with a custom language", while the new Wasp is something else: a serious, full-stack TypeScript framework you'd reach for to build a real product. The caterpillar was getting its wings (ok, wasp, but you get the idea), and it couldn't really keep wearing the old skin.</p>
<p>So instead of asking ourselves "what looks nice?", we ended up asking a much better question: <strong>what is Wasp, actually?</strong></p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="wasp-is-a-spec-so-the-brand-is-a-blueprint">Wasp is a spec. So the brand is a blueprint.<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#wasp-is-a-spec-so-the-brand-is-a-blueprint" class="hash-link" aria-label="Direct link to Wasp is a spec. So the brand is a blueprint." title="Direct link to Wasp is a spec. So the brand is a blueprint." translate="no">​</a></h2>
<p>The core idea behind Wasp has always been the same, DSL or no DSL: you declare <em>what</em> your app is (routes, pages, auth, jobs, the whole skeleton), and Wasp handles all the plumbing under the hood. The high-level spec you define in TypeScript is essentially an engineering drawing of your application, and the framework just builds it.</p>
<p>(Quick side note: "Wasp" itself stands for <strong>W</strong>eb <strong>A</strong>pplication <strong>SP</strong>ecification - which is basically how we've always thought about it.)</p>
<p>But before we landed there, we explored a <em>lot</em> of other directions. Some internal attempts (mostly me prompting Nano Banana), and we also briefly worked with a few designers who came back with their own takes. AI turned out to be genuinely useful in this phase: you can iterate on entire landing-page mockups in a few minutes and quickly see what does and what doesn't feel like Wasp, and build intuition for what you like. Here's one of mine:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="An early Wasp landing-page mockup prompted by Matija through Nano Banana: a blueprint-paper hero 'Your application's schematic, engineered by wasp', a 'Functional Monolith' system diagram, and a 'Patterns, The Sharp Path' sidebar exploring squared =} logo variants" src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/matija-nano-banana-mockup.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">One of my early Nano Banana runs. Already leaning hard into the schematic / blueprint angle that ended up shaping the final brand.</figcaption></figure></div>
<p>And here's a small sample of what the designers sent over:</p>
<div class="figure-container" style="display:flex;flex-direction:column;align-items:stretch"><figure style="margin:0;position:relative"><div style="display:grid;grid-template-columns:repeat(2, 1fr);gap:8px"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/concept-1.webp" alt="Designer concept 1: monospace hero on Blueprint Paper with mosaic feature cards" class="no-default-zoom" style="width:100%;height:auto;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5)"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/concept-2.webp" alt="Designer concept 2: dense grid layout with thick black borders and yellow accents" class="no-default-zoom" style="width:100%;height:auto;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5)"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/concept-3.webp" alt="Designer concept 3: pill-shaped CTAs over a dark feature grid, italic 'faster' wordmark" class="no-default-zoom" style="width:100%;height:auto;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5)"><img src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/concept-4.webp" alt="Designer concept 4: large yellow =} mark in a cell-grid composition with monospace table-like blocks" class="no-default-zoom" style="width:100%;height:auto;display:block;cursor:zoom-in;border:1px solid var(--wasp-g5)"></div><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.6em;text-align:center">(Click to zoom): A few of the directions designers came back with. Honestly, none of them really clicked for us, probably because the process happened too much in isolation from us.</figcaption></figure></div>
<p>After cycling through enough of these, the visual direction we wanted got pretty obvious. Wasp's brand should look like what it is: <strong>a technical spec</strong>. Blueprints, schematics, annotated diagrams: the kind of stuff engineers draw before they go and build.</p>
<p>That single idea ended up driving basically everything in the new identity:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The new Wasp brand system: monospace type, the squared =} mark, Wasp Yellow / Ink Black / Blueprint Paper colors, and schematic illustrations" src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/rebrand-system.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">The new Wasp brand system.</figcaption></figure></div>
<p><strong>Monospace first.</strong> Our primary typeface is JetBrains Mono, backed by IBM Plex Mono. Monospace is the native typography of our world and we just really like how it looks. We were deliberating about using monospace literally everywhere, but in the end decided to settle on titles and subtitles, while the body text in the docs and the blog is IMB Plex Sans - easier on the eyes, but still feels close to the monospace aesthetic.</p>
<p><strong>Three colors, and that's it.</strong> Wasp Yellow (#F5C842), Ink Black (#111), and a warm paper tone we call Blueprint Paper (#F7F5F0). Yellow and black because, well, wasp. Paper because real engineering drawings live on paper, not on gradients.</p>
<p><strong>Sharp corners, visible structure.</strong> 90° angles, 2px strokes, no rounded-blob softness anywhere. Our illustrations aren't there to decorate the page. They're schematics: boxes, connectors, annotations, the architecture of your app drawn like a circuit diagram.</p>
<p><strong>The mark.</strong> The <code>=}</code> symbol, set in a solid square. It's pulled straight from code, works at any size from a favicon to a billboard, and if you squint a bit it still reads as a wasp's wings and antennae. It didn't arrive fully formed, though. The project actually started life as <em>stick</em> (yes, there was a literal photo of a wooden stick), then <em>stic</em> (Specification to Implementation Compiler), and finally <em>wasp</em>. The <code>=}</code> itself only showed up around the Alpha launch in 2020, sitting inside a yellow circle. The 2026 rebrand was basically the moment we finally squared it off and stopped fiddling with it:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The Wasp mark across four eras: STIC (2019, a stick), wasp (2019, three triangles), Alpha (2020, the =} in a yellow circle), and today (2026, the =} bulked up and locked in a square)" src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/rebrand-logo-progression-real.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">The Wasp mark, from a stick to a square.</figcaption></figure></div>
<p><strong>Light, on purpose.</strong> One thing we very deliberately kept: Wasp stays light theme-first. It would have been the easy, default move to go dark-mode-everything and look like every other devtool out there. But people have always told us that Wasp's look feels <em>happy</em> (warm and approachable in a category that mostly reads as cold and serious), and we didn't want to just throw that away to become another Linear clone. The world already has plenty of near-black landing pages with a purple gradient on top. Blueprint paper is bright, optimistic, and it's ours.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="constraints-are-the-whole-point---both-in-design-and-code">Constraints are the whole point - both in design and code<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#constraints-are-the-whole-point---both-in-design-and-code" class="hash-link" aria-label="Direct link to Constraints are the whole point - both in design and code" title="Direct link to Constraints are the whole point - both in design and code" translate="no">​</a></h2>
<p>Here's the part we honestly didn't expect: the best thing about the new brand isn't really how it looks, but how <em>fast</em> it now makes us move.</p>
<p>Two fonts, three colors, one illustration style, and only sharp corners. It sounds restrictive on paper, and it is, but in the best possible way. Before, no one really knew what to reach for, so everyone would just do their own thing each time. Now there's almost nothing to decide. A launch banner, a chart for Twitter, a docs page, a sticker - they all kind of assemble themselves from the same small kit. It's actually the same philosophy as Wasp itself: strong defaults and clear structure don't limit you - they free you up to focus on the parts that actually matter.</p>
<p>We even wrote ourselves a proper brandbook in the end, partly because we genuinely needed one, and partly because after five years of winging it, it just felt really, really good to finally have one.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The Wasp brandbook color-system page: five vertical stripes showing Wasp Yellow (#F5C842), Ink Black (#111111), Paper (#F7F5F0), Gray (#777777), and Tint (#FFF3CC), with the squared =} mark set on the yellow column" src="https://wasp.sh/img/blog/2026-07-13-why-design-matters-for-a-web-framework/rebrand-brandbook.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">The color-system page from our brandbook.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="we-shipped-it-like-a-rolling-release">We shipped it like a rolling release<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#we-shipped-it-like-a-rolling-release" class="hash-link" aria-label="Direct link to We shipped it like a rolling release" title="Direct link to We shipped it like a rolling release" translate="no">​</a></h2>
<p>We didn't flip a switch one morning and unveil a finished new site. We rolled it out the same way we ship software: piece by piece, swapping new parts in while the old ones were still live.</p>
<p>So for a while, wasp.sh was a bit of a Frankenstein (honestly, it kind of still is). A shiny new hero sitting on top of an old footer, new buttons next to old cards, fonts not quite agreeing with each other across the page. It looked pretty rough, but the old site already looked rough, so a half-migrated version was still a step up, not a regression. The bar, luckily for us, was very forgiving.</p>
<p>And honestly, the awkwardness actually helped. Having a half-finished site sitting out in the open was a little embarrassing, which was kind of the whole point. Nobody really wants a Frankenstein page on the internet with their name on it, so we kept sprinting to fix the next piece before too many people saw it in that state. The embarrassment basically became a deadline we couldn't ignore.</p>
<p>And it was the only realistic way we were ever going to get it done. If we'd waited to perfect every pixel and ship it all at once, we'd genuinely still be waiting today. Wasp moves too fast for a big-bang redesign. By the time it was "done", half of it would already be stale. Shipping it in pieces is what actually kept us moving.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="designing-it-changed-what-we-think-wasp-is">Designing it changed what we think Wasp is<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#designing-it-changed-what-we-think-wasp-is" class="hash-link" aria-label="Direct link to Designing it changed what we think Wasp is" title="Direct link to Designing it changed what we think Wasp is" translate="no">​</a></h2>
<p>Another thing we found really valuable about this whole process had nothing to do with how anything looked.</p>
<p>To draw a thing, you first have to know what the thing actually <em>is</em>. So every design decision kept bouncing back at us as a product question: who is this really for, what do we stand for, what do we actually want to say. Before we knew it, the rebrand had quietly turned into a rewrite. We reworked our words, our positioning, our whole story, and then the new words changed the design, and the new design changed the words again. The two kept reshaping and reinforcing each other.</p>
<p>That loop is exactly why we're glad we didn't just hand this whole thing off to someone external. An agency can absolutely make you <em>look</em> good. What it can't really do is the part that turned out to matter most: the way designing the brand forces you to understand, and sometimes redraw, the product itself. That kind of thing only really happens when the people building the product are also the ones drawing it.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-do-you-think">What do you think?<a href="https://wasp.sh/blog/2026/07/13/why-design-matters-for-a-web-framework#what-do-you-think" class="hash-link" aria-label="Direct link to What do you think?" title="Direct link to What do you think?" translate="no">​</a></h2>
<p>The new look is now live on <a href="https://wasp.sh/" target="_blank" rel="noopener noreferrer" class="">wasp.sh</a>, across our docs, and everywhere else Wasp shows up. Like everything we ship, it'll keep evolving, and we'd love your honest take: the good, the bad, and the "did it really have to be monospace?".</p>
<p>Come tell us on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a>, <a href="https://twitter.com/WaspLang" target="_blank" rel="noopener noreferrer" class="">Twitter/X</a>, or <a href="https://github.com/wasp-lang/wasp" target="_blank" rel="noopener noreferrer" class="">GitHub</a>. 🐝</p>]]></content:encoded>
            <author>matija@wasp-lang.dev (Matija Sosic)</author>
            <category>wasp</category>
            <category>design</category>
            <category>branding</category>
            <category>rebrand</category>
            <category>web dev</category>
        </item>
        <item>
            <title><![CDATA[Roll your own file-based router in under 50 lines of code]]></title>
            <link>https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router</link>
            <guid>https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router</guid>
            <pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Build a file-based router for Wasp in under 50 lines of TypeScript: page.tsx routes, route groups, auth and prerender folders, dynamic segments.]]></description>
            <content:encoded><![CDATA[<p>Nowadays, web frameworks come with ✨ magic ✨. Some more than others, but all of them have some. The magic is usually in the form of conventions: do things their way and the framework helps you out; wander off the happy path and you're on your own.</p>
<!-- -->
<p>One of the main tricks they pull is quietly turning your folder structure into a config file. Create <code>app/about-us/page.tsx</code> in a Next.js app and <code>https://localhost:3000/about-us</code> magically starts working. Rename the file, and the URL changes with it. The framework is reading your file tree and turning it into a routing table.</p>
<p>That is called <strong>file-based routing</strong>, and it's usually magic your framework either hands you or it doesn't; and when it does, you rarely get to customize it, the conventions are baked in. Want a folder name to carry special meaning, or a <code>logged-in.tsx</code>/<code>logged-out.tsx</code> split per route? Your only option is to post a feature request and wait, or go without.</p>
<p>In Wasp, we really like explicitness, so we've resisted shipping a file-based router. That's changing now, but of course, we're not just adding the magic conventions and moving on. We're giving you a way to choose and design your own magic.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="wait-whats-wasp">Wait, what's Wasp?<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#wait-whats-wasp" class="hash-link" aria-label="Direct link to Wait, what's Wasp?" title="Direct link to Wait, what's Wasp?" translate="no">​</a></h2>
<p>Wasp is a batteries-included full-stack web framework for TypeScript. It covers your frontend, backend, and database as one cohesive whole.</p>
<p>And one of our core ideas is that the entry point to all this full-stack goodness is through an explicit <strong>Spec</strong>. Instead of hiding your app's structure behind implicit conventions, you declare its features (like routes, authentication, queries, cron jobs, etc) directly in code. Wasp then compiles and stitches these pieces together:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> app</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> route</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> page </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// `type: ref` means we just want to point to these files, not execute them now:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">MainPage</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/pages/MainPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">UserPage</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/pages/LoginPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// Some example configurations, we'll skip them in the future:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"my-app"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  wasp</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> version</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"^0.24.0"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  auth</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> userEntity</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"User"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> google</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// The spec is where you declare your app's features:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"MainRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">MainPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"LoginRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/login"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">UserPage</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>We chose this approach because explicit code is easier to reason about than hidden magic. This transparency makes the codebase easier to navigate for your team, and it gives AI code assistants a clear, structured map of your application to work with.</p>
<p>That explicitness is the whole philosophy, and it's exactly why we've deliberately never shipped file-based routing. We just didn't want to bake that pile of implicit conventions into the framework.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-spec-is-just-a-program">The Spec is just a program<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#the-spec-is-just-a-program" class="hash-link" aria-label="Direct link to The Spec is just a program" title="Direct link to The Spec is just a program" translate="no">​</a></h2>
<p>But here's the part that makes it exciting. We recently <a class="" href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec">updated our spec</a> so that it lives in a <code>main.wasp.ts</code> file. And instead of being a static JSON file that the framework reads, it is just <strong>a standard Node.js program</strong>, written in TypeScript. You can pull in libraries from npm, read from disk, call an API, use environment variables, anything! The only rule is that you export an <code>app</code> at the end. That's all we need.</p>
<p>So the Spec is explicit, but it's also <em>programmable</em>. And nothing says those <code>route</code> and <code>page</code> calls have to be typed out by hand.</p>
<p>That's the entire trick. You can write a function that walks your <code>src/</code> folder and returns the same <code>route</code> and <code>page</code> objects you'd otherwise write manually. File-based routing stops being internal magic, and becomes a few lines of ordinary code that live in your repo, that you can read, and more importantly, customize.</p>
<p>So even though we never shipped file-based routing, "we didn't ship it" doesn't mean "you can't have it". You add it yourself, with exactly the conventions you want. You get the best of both worlds, and nobody has to argue about defaults. Sorry if you liked the arguing.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-simplest-possible-router">The simplest possible router<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#the-simplest-possible-router" class="hash-link" aria-label="Direct link to The simplest possible router" title="Direct link to The simplest possible router" translate="no">​</a></h2>
<p>Let's build that. Because the route list is just an array of objects, the simplest possible "router" is one we write out by hand:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// The `ref` helper is the dynamic version of `with { type: "ref" }` imports, so we'll use it to build programmatically.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> app</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> page</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> route</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> ref </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token string" style="color:#e3116c">"RootRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token function" style="color:#d73a49">ref</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> importDefault</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"RootPage"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/page.tsx"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token string" style="color:#e3116c">"AboutUsRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token string" style="color:#e3116c">"/about-us"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token function" style="color:#d73a49">ref</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> importDefault</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"AboutUsPage"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/about-us/page.tsx"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>That's a functioning router already, but the unsatisfying part is that we had to type it out ourselves. So let's <em>generate</em> it instead, by looking at the project files.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-step-up-generate-the-routes-from-the-filesystem">The step up: generate the routes from the filesystem<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#the-step-up-generate-the-routes-from-the-filesystem" class="hash-link" aria-label="Direct link to The step up: generate the routes from the filesystem" title="Direct link to The step up: generate the routes from the filesystem" translate="no">​</a></h2>
<p>We'll pick a very simple convention: <strong>a <code>page.tsx</code> inside a folder makes it a route.</strong> So <code>src/about-us/page.tsx</code> serves <code>https://my-app.com/about-us</code>, and <code>src/page.tsx</code> serves <code>https://my-app.com/</code>.</p>
<p>Here's the whole thing:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> page</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> ref</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> route </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> pascalCase </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"es-toolkit"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> globSync </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"node:fs"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports operator" style="color:#393A34">*</span><span class="token imports"> </span><span class="token imports keyword module" style="color:#00009f">as</span><span class="token imports"> path</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"node:path"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token function-variable function" style="color:#d73a49">fileBasedRoutes</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">baseDir</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token builtin">string</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">globSync</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"**/page.tsx"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> cwd</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> baseDir </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">sort</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Make the list stable between runs</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">map</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">filePath</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> absoluteFilePath </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> path</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">resolve</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">baseDir</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> filePath</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> urlRoute </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">split</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">path</span><span class="token punctuation" style="color:#393A34">.</span><span class="token property-access">sep</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">slice</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">0</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">-</span><span class="token number" style="color:#36acaa">1</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Removes the "page.tsx" part</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">join</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> routeName </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">pascalCase</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">urlRoute</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">||</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Root"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">routeName</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">Route</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token string" style="color:#e3116c">"/"</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">+</span><span class="token plain"> urlRoute</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token function" style="color:#d73a49">ref</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            importDefault</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">routeName</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">Page</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> absoluteFilePath</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>That's the entire idea. Find every <code>page.tsx</code>, turn its folder path into a URL path and a name, and produce the <code>route()</code>s. For the route name we can even <a href="https://es-toolkit.dev/reference/string/pascalCase.html" target="_blank" rel="noopener noreferrer" class="">lean on an npm package</a> to get a clean name; it's just an ordinary npm dependency, like in any Node project.</p>
<p>There's nothing clever going on here, it's plain filesystem glue. An inexperienced dev could write this without much trouble. It never reaches into Wasp's internals, and it only calls the same public <code>route</code>, <code>page</code>, and <code>ref</code> functions you'd use by hand.</p>
<p>Wiring it into your app is one line:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// main.wasp.ts</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> app </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> fileBasedRoutes </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./lib/file-based-routes.wasp"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">fileBasedRoutes</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"src"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// Any other Specs your app uses (job(), query(), action(), ...)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p><code>fileBasedRoutes</code> returns an array of route objects, and we drop it straight into <code>spec</code>. Voilà, you have file-based routing!</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="everything-wasp-already-does-still-works">Everything Wasp already does still works<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#everything-wasp-already-does-still-works" class="hash-link" aria-label="Direct link to Everything Wasp already does still works" title="Direct link to Everything Wasp already does still works" translate="no">​</a></h2>
<p>Because we're producing normal <code>route</code> and <code>page</code> spec objects, the rest of Wasp neither knows nor cares that they were generated. So all the features you'd expect keep working, including <a class="" href="https://wasp.sh/docs/features/pages-and-routes#link-component">type-safe links</a>:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> </span><span class="token imports maybe-class-name">Link</span><span class="token imports"> </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"wasp/client/router"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">function</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">MainPage</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token tag punctuation" style="color:#393A34">&lt;</span><span class="token tag punctuation" style="color:#393A34">&gt;</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain-text">      </span><span class="token tag punctuation" style="color:#393A34">&lt;</span><span class="token tag" style="color:#00009f">h1</span><span class="token tag punctuation" style="color:#393A34">&gt;</span><span class="token plain-text">Main page</span><span class="token tag punctuation" style="color:#393A34">&lt;/</span><span class="token tag" style="color:#00009f">h1</span><span class="token tag punctuation" style="color:#393A34">&gt;</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain-text">      </span><span class="token tag punctuation" style="color:#393A34">&lt;</span><span class="token tag class-name" style="color:#00009f">Link</span><span class="token tag" style="color:#00009f"> </span><span class="token tag attr-name" style="color:#00a4db">to</span><span class="token tag attr-value punctuation attr-equals" style="color:#393A34">=</span><span class="token tag attr-value punctuation" style="color:#393A34">"</span><span class="token tag attr-value" style="color:#e3116c">/about-us</span><span class="token tag attr-value punctuation" style="color:#393A34">"</span><span class="token tag punctuation" style="color:#393A34">&gt;</span><span class="token plain-text">About us</span><span class="token tag punctuation" style="color:#393A34">&lt;/</span><span class="token tag class-name" style="color:#00009f">Link</span><span class="token tag punctuation" style="color:#393A34">&gt;</span><span class="token plain-text"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain-text">    </span><span class="token tag punctuation" style="color:#393A34">&lt;/</span><span class="token tag punctuation" style="color:#393A34">&gt;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><br></div></code></pre></div></div>
<p>The <code>&lt;Link&gt;</code> component is fully typechecked with the routes your function generated. Generate a route from a folder, and you will get autocomplete and type errors for it everywhere. Nice.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="now-make-it-yours-route-groups">Now make it yours: route groups<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#now-make-it-yours-route-groups" class="hash-link" aria-label="Direct link to Now make it yours: route groups" title="Direct link to Now make it yours: route groups" translate="no">​</a></h2>
<p>Here's where it gets fun. This is <em>your</em> code, so bend it to your project. Say you want <strong>route groups:</strong> folders that organize your files without showing up in the URL. The usual convention is to wrap them in parentheses, like <code>(marketing)</code>.</p>
<p>It's a one-line filter:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">ROUTE_GROUP_REGEX</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">^</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\(</span><span class="token regex regex-source language-regex char-set class-name" style="color:#36acaa">.</span><span class="token regex regex-source language-regex quantifier number" style="color:#36acaa">*</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\)</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">$</span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Wrapped in parentheses</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> urlRoute </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">split</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">path</span><span class="token punctuation" style="color:#393A34">.</span><span class="token property-access">sep</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">slice</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">0</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">-</span><span class="token number" style="color:#36acaa">1</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Removes the "page.tsx" part</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">filter</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">!</span><span class="token constant" style="color:#36acaa">ROUTE_GROUP_REGEX</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">test</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Remove any route groups</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">join</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>Now <code>src/(marketing)/about-us/page.tsx</code> still serves <code>/about-us</code>, but you can keep your marketing pages tidily grouped.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="a-convention-for-prerender-and-auth">A convention for prerender and auth<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#a-convention-for-prerender-and-auth" class="hash-link" aria-label="Direct link to A convention for prerender and auth" title="Direct link to A convention for prerender and auth" translate="no">​</a></h2>
<p>Now let's say that in your project, there are two settings you're reaching for constantly: marking a page as auth-required, or marking it for prerendering. Let's invent a convention for both, reusing the route-group syntax we just added: an <code>(auth)</code> group makes everything inside require auth, and a <code>(prerender)</code> group marks pages for prerendering.</p>
<p>We detect those folders and thread the result into the spec objects:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> isPrerender </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">includes</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"(prerender)"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> isAuth </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">includes</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"(auth)"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">routeName</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">Route</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token string" style="color:#e3116c">"/"</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">+</span><span class="token plain"> urlRoute</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">ref</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      importDefault</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">routeName</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">Page</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> absoluteFilePath</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> isAuth </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> prerender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> isPrerender </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>These are <em>your</em> conventions. Don't like parentheses for this? Use a <code>.auth.tsx</code> suffix, a <code>"use auth"</code> directive, or a config file next to the page; whatever reads best for your team. The spec doesn't dictate the shape, you do!</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="dynamic-and-optional-segments">Dynamic and optional segments<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#dynamic-and-optional-segments" class="hash-link" aria-label="Direct link to Dynamic and optional segments" title="Direct link to Dynamic and optional segments" translate="no">​</a></h2>
<p>Wasp routing also supports <a class="" href="https://wasp.sh/docs/features/pages-and-routes#dynamic-segments">dynamic</a> (<code>:id</code>) and <a class="" href="https://wasp.sh/docs/features/pages-and-routes#optional-segments">optional</a> (<code>:id?</code>) segments. Written out in the spec by hand, they look like this:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"ProductRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/products/:productId"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">ProductPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"ArticleRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/articles/:slug?"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">ArticlePage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><br></div></code></pre></div></div>
<p>The <code>:</code> character is not allowed in file paths, so let's copy Next.js's bracket syntax for this: <code>[productId]</code> becomes <code>:productId</code>, and <code>[[productId]]</code> becomes <code>:productId?</code>:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">DYNAMIC_SEGMENT_REGEX</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">^</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\[</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">(</span><span class="token regex regex-source language-regex char-set class-name" style="color:#36acaa">.</span><span class="token regex regex-source language-regex quantifier number" style="color:#36acaa">*</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">)</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\]</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">$</span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Wrapped in square brackets</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">OPTIONAL_SEGMENT_REGEX</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">^</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\[</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\[</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">(</span><span class="token regex regex-source language-regex char-set class-name" style="color:#36acaa">.</span><span class="token regex regex-source language-regex quantifier number" style="color:#36acaa">*</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">)</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\]</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\]</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">$</span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Wrapped in two square brackets</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> urlRoute </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">split</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">path</span><span class="token punctuation" style="color:#393A34">.</span><span class="token property-access">sep</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">slice</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">0</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">-</span><span class="token number" style="color:#36acaa">1</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Removes the "page.tsx" part</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">filter</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">!</span><span class="token constant" style="color:#36acaa">ROUTE_GROUP_REGEX</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">test</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Remove any route groups</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">map</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> part</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">replace</span><span class="token punctuation" style="color:#393A34">(</span><span class="token constant" style="color:#36acaa">OPTIONAL_SEGMENT_REGEX</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">":$1?"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Convert optional segments</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">map</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> part</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">replace</span><span class="token punctuation" style="color:#393A34">(</span><span class="token constant" style="color:#36acaa">DYNAMIC_SEGMENT_REGEX</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">":$1"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Convert dynamic segments</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">join</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>Or you can invent your own syntax. The point is that it's just code, so you do you.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="45-lines-later">45 lines later<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#45-lines-later" class="hash-link" aria-label="Direct link to 45 lines later" title="Direct link to 45 lines later" translate="no">​</a></h2>
<p>We're done!</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> page</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> ref</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> route </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> pascalCase </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"es-toolkit"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> globSync </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"node:fs"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports operator" style="color:#393A34">*</span><span class="token imports"> </span><span class="token imports keyword module" style="color:#00009f">as</span><span class="token imports"> path</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"node:path"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">ROUTE_GROUP_REGEX</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">^</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\(</span><span class="token regex regex-source language-regex char-set class-name" style="color:#36acaa">.</span><span class="token regex regex-source language-regex quantifier number" style="color:#36acaa">*</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\)</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">$</span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Wrapped in parentheses</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">DYNAMIC_SEGMENT_REGEX</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">^</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\[</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">(</span><span class="token regex regex-source language-regex char-set class-name" style="color:#36acaa">.</span><span class="token regex regex-source language-regex quantifier number" style="color:#36acaa">*</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">)</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\]</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">$</span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Wrapped in square brackets</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token constant" style="color:#36acaa">OPTIONAL_SEGMENT_REGEX</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">^</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\[</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\[</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">(</span><span class="token regex regex-source language-regex char-set class-name" style="color:#36acaa">.</span><span class="token regex regex-source language-regex quantifier number" style="color:#36acaa">*</span><span class="token regex regex-source language-regex group punctuation" style="color:#393A34">)</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\]</span><span class="token regex regex-source language-regex special-escape escape" style="color:#36acaa">\]</span><span class="token regex regex-source language-regex anchor function" style="color:#d73a49">$</span><span class="token regex regex-delimiter" style="color:#36acaa">/</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Wrapped in two square brackets</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> </span><span class="token function-variable function" style="color:#d73a49">fileBasedRoutes</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">baseDir</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token builtin">string</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">globSync</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"**/page.tsx"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> cwd</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> baseDir </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">sort</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Make the list stable between runs</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">map</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">filePath</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> absoluteFilePath </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> path</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">resolve</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">baseDir</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> filePath</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> isPrerender </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">includes</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"(prerender)"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> isAuth </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">includes</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"(auth)"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> urlRoute </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> filePath</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">split</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">path</span><span class="token punctuation" style="color:#393A34">.</span><span class="token property-access">sep</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">slice</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">0</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">-</span><span class="token number" style="color:#36acaa">1</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Removes the "page.tsx" part</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">filter</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">!</span><span class="token constant" style="color:#36acaa">ROUTE_GROUP_REGEX</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">test</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Remove any route groups</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">map</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> part</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">replace</span><span class="token punctuation" style="color:#393A34">(</span><span class="token constant" style="color:#36acaa">OPTIONAL_SEGMENT_REGEX</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">":$1?"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Convert optional segments</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">map</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">part</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token arrow operator" style="color:#393A34">=&gt;</span><span class="token plain"> part</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">replace</span><span class="token punctuation" style="color:#393A34">(</span><span class="token constant" style="color:#36acaa">DYNAMIC_SEGMENT_REGEX</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">":$1"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Convert dynamic segments</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">join</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> routeName </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">pascalCase</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">urlRoute</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">||</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Root"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">routeName</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">Route</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token string" style="color:#e3116c">"/"</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">+</span><span class="token plain"> urlRoute</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token function" style="color:#d73a49">ref</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            importDefault</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">${</span><span class="token template-string interpolation">routeName</span><span class="token template-string interpolation interpolation-punctuation punctuation" style="color:#393A34">}</span><span class="token template-string string" style="color:#e3116c">Page</span><span class="token template-string template-punctuation string" style="color:#e3116c">`</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> absoluteFilePath</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> isAuth </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> prerender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> isPrerender </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>That's it. You can start using these conventions as you see fit. For example, with the folder layout below:</p>
<div class="language-text codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-text codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token plain">src/</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">├── (prerender)/</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">│   └── (marketing)/</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">│       ├── page.tsx</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">│       └── about-us/</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">│           └── page.tsx</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">├── products/</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">│   └── [productId]</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">│       └── page.tsx</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">└── (auth)/</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    └── dashboard/</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        └── page.tsx</span><br></div></code></pre></div></div>
<p>...our function produces this spec:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">fileBasedRoutes</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"src"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// the above call ⬆️ will turn into the following specs ⬇️</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"RootRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">RootPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> prerender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"AboutUsRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/about-us"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">AboutUsPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> prerender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"ProductIdRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/products/:productId"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">ProductIdPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"DashboardRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/dashboard"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">DashboardPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>Add more files in that <code>(auth)</code>, and those pages become auth-required; name a folder <code>[[slug]]</code> and you get an optional segment. We've covered the most useful bits of Wasp's routing and exposed them through an entirely new API surface, and all of it lives in under 50 lines you can read end to end in a minute.</p>
<p>And the same trick isn't limited to routes. Because the spec is just data your program returns, you can generate any of it the same way: <code>api()</code>, <code>query()</code>, <code>job()</code>, or <code>action()</code>, all from your own file layout. With other frameworks you might need weird hacks or an escape hatch to do this, but in Wasp there's nothing to escape from.</p>
<p>This is the whole reason we keep going on about the spec being a first-class, programmable thing. It means that file-based routing didn't have to become a Wasp feature with a dozen options and an opt-out. It just became a small file you can control. <a class="" href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec">Meta-meta-framework, anyone?</a></p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="roll-your-own">Roll your own<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#roll-your-own" class="hash-link" aria-label="Direct link to Roll your own" title="Direct link to Roll your own" translate="no">​</a></h2>
<p>Want a more full-featured file-based router than the version above? We are building one you can use or learn from: <a href="https://github.com/wasp-lang/file-based-routing" target="_blank" rel="noopener noreferrer" class="">wasp-lang/file-based-routing</a>. We're still working on it, but it has quite a few more features than the one here. Other people might create their own libraries, and you can use those too!</p>
<p>But the whole point of this post is that you don't have to use anyone's library. Run <code>wasp new</code>, copy our starting example, and build the conventions that fit <em>your</em> project.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-future">The future<a href="https://wasp.sh/blog/2026/07/01/roll-your-own-file-based-router#the-future" class="hash-link" aria-label="Direct link to The future" title="Direct link to The future" translate="no">​</a></h2>
<p>The same "spec is just a program" idea doesn't stop at routing. We're actively working on <a class="" href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module">full-stack modules</a>: the idea that you'll be able to pull libraries that don't only contain backend or frontend code, but full-stack code, defined as a Spec. File-based routing might be a part of those specs in the future! But it all goes towards giving you the magic of conventions without losing control and explicitness when you want it.</p>
<p>If you come up with something good, we'd genuinely love to see it, come share it on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">our Discord</a>!</p>]]></content:encoded>
            <category>wasp</category>
            <category>typescript</category>
            <category>routing</category>
            <category>file-based routing</category>
            <category>full-stack</category>
        </item>
        <item>
            <title><![CDATA[JavaScript still can't ship a full-stack module]]></title>
            <link>https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module</link>
            <guid>https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module</guid>
            <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Why JavaScript lacks true full-stack modules, what Rails and Laravel get right, and how Wasp can bring that pattern to JS.]]></description>
            <content:encoded><![CDATA[<p>Imagine if there were a way for us to somehow ship a <em>full-stack</em> package that you could plug into your app. Client code, backend code, webhooks, and database models all wired up and ready to go. I know I'd love that. Just install one complete module and the whole thing just works.</p>
<!-- -->
<p>Take payments, for example. Normally, we install the Stripe SDK or some nice payments UI library, but it always requires manual wiring. And that wiring bit, figuring out how to integrate libraries written by different people, is one of the most annoying parts of the job.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Different ways to write a full-stack feature" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/banner.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Different ways you can write a full-stack feature.</figcaption></figure></div>
<p>Yeah yeah, I know what you are thinking. LLMs are writing most of the code these days, who cares? <strong>Ok, but it's already been established: what's good for humans is good for LLMs. They like to be lazy too.</strong></p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="agents-love-working-with-legos">Agents love working with legos<a href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module#agents-love-working-with-legos" class="hash-link" aria-label="Direct link to Agents love working with legos" title="Direct link to Agents love working with legos" translate="no">​</a></h2>
<p>Opus, GPT, and the rest of the models out there adore "legos" (pre-built pieces of functionality): they speed up the scaffolding process and result in more secure apps. You shouldn't trust your agent with hand-rolled components, especially with parts that need to be vetted (auth, payments...). When you trust the agent with that, you pay for more tokens and have no idea where the security holes are.</p>
<p>But imagine those agents had access to well-tested, full-stack implementations of auth, payments, file upload, admin dashboard, etc. Ideally, these packaged legos would hide most of the complexity from us and offer our agents control knobs for the most important configuration. For example, the agents would only be dealing with 2 env variables and maybe 2 or 3 lines of config for tested, reliable, and secure Google auth.</p>
<p>Matt Pocock talks about how LLMs struggle when a feature is split across too many layers and too much ad hoc glue. He focuses on the concept of "deep modules" from <a href="https://www.amazon.com/Philosophy-Software-Design-John-Ousterhout/dp/1732102201" target="_blank" rel="noopener noreferrer" class="">A Philosophy of Software Design</a> as one of the methods that help agents work in your codebase. We can define deep modules as a standalone part of our app that exposes a simple way to use it (a <em>thin interface</em>), but hides all the internal complexities of the actual implementation.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Matt Pocock video about preparing codebases for AI" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/matt-pocock-deep-modules.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"><a href="https://youtu.be/uC44zFz7JSM?si=uike3KKy_fbc01TU" target="_blank" rel="noreferrer noopener" class="">“Your codebase is NOT ready for AI (here's how to fix it)”</a></figcaption></figure></div>
<p>The legos I described are nothing more than deep modules themselves, having a thin interface for the agent to interact with while the complexity is tucked away.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="legos-have-a-name-full-stack-modules">Legos have a name: full-stack modules<a href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module#legos-have-a-name-full-stack-modules" class="hash-link" aria-label="Direct link to Legos have a name: full-stack modules" title="Direct link to Legos have a name: full-stack modules" translate="no">​</a></h2>
<p>While developing <a class="" href="https://wasp.sh/">Wasp</a>, a JS full-stack framework, we keep researching other ecosystems (Rails, Laravel, Django, etc.) and finding ways how they figured out developer productivity. We kept finding these reusable legos, so we gave them a name: "full-stack modules". Let's define what we mean by that exactly.</p>
<p>We usually talk about applications in two ways:</p>
<ol>
<li class="">One is by technical layers: backend server, frontend client, database.</li>
<li class="">The other is by vertical slices: a complete feature that runs through the whole stack. Payments is our standard example: backend logic, the button the user clicks, and the database model that stores the state. A full-stack module is one of these vertical slices.</li>
</ol>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Technical layers compared with vertical slices in an application" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/technical-layers-vs-vertical-slices.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Technical layers vs vertical slices of an application.</figcaption></figure></div>
<p>In Rails and Laravel, you can install packages that ship a slice like this. Add the package and payments are covered. You are not assembling a model, a backend, and a UI by hand. You can install one package which was developed against the stable shape of these frameworks.</p>
<p>That is a real advantage developers in Rails and Laravel ecosystems have, and it matters even more in the AI age. You ship faster if you don't spend days figuring out payments. You are also safer if you lean on a battle-tested package instead of something you wrote (or generated) under time pressure. The same logic applies to LLMs. We rarely review every line they produce. So, the less custom glue we ask them to write, the better.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="researching-full-stack-modules-in-11-frameworks">Researching full-stack modules in 11 frameworks<a href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module#researching-full-stack-modules-in-11-frameworks" class="hash-link" aria-label="Direct link to Researching full-stack modules in 11 frameworks" title="Direct link to Researching full-stack modules in 11 frameworks" translate="no">​</a></h2>
<p>To better understand the common patterns, I wanted to "feel" how full-stack modules work elsewhere. I can read the docs only so much, so I prefer playing around with code, trying to make some changes and see what kind of pushback the API will give me.</p>
<p>I gathered all the frameworks/libraries/tools that sounded interesting to me and looked like they had something to teach me. Then I sketched an app that would somehow use a full-stack module.</p>
<p>To make it easy to compare, I created a static HTML prototype and tried to flesh out the requirements:</p>
<ul>
<li class="">users can sign up / log in</li>
<li class="">they can browse products</li>
<li class="">they can buy products with Stripe</li>
<li class="">they can see their purchased items</li>
</ul>
<p>In all of the frameworks, we want to see the same webshop (same design, same capabilities).</p>
<div style="display:flex;justify-content:center;margin:1rem 0"><figure style="width:100%;margin:0"><video width="100%" controls="" aria-label="Demo of the payments module in Django"><source src="/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/fsm.mp4" type="video/mp4"></video><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Demo of the payments module in Django</figcaption></figure></div>
<p>Our webshop is made out of auth, payments, and products modules. In this exercise, we told the agent that the "payments" module <em>must be implemented</em> as a full-stack module. The idea was for the module to be reusable, and it can't make any assumptions about where it will be used.</p>
<p>We took all these requirements and built the same app in 11 different frameworks. See the list here: <a href="https://fsm-research.static.miho.dev/" target="_blank" rel="noopener noreferrer" class="">https://fsm-research.static.miho.dev</a></p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="How host apps use a payments module in different frameworks" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/payments-module-frameworks.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">How the host app uses the payments module in different frameworks.</figcaption></figure></div>
<p>Playing around with the same webshop across different frameworks helped us understand how full-stack modules can be implemented. Different frameworks had different levels of support, which made the experience more or less enjoyable.</p>
<p>For example:</p>
<ol>
<li class="">In some frameworks, sharing a full-stack feature is much more polished.<!-- -->
<ol>
<li class="">For example, in Orchard Core, you define a <code>Startup</code> class which has the ability to register services, database migrations, and add client and server routes as soon as the payments module is registered.</li>
<li class="">In Rails, once you install the <code>payments</code> engine, based on the Rails folder conventions, you get views, models, controllers, etc. automatically registered.</li>
</ol>
</li>
<li class="">But in some, the experience of sharing a module was more hands-on.<!-- -->
<ol>
<li class="">My experience with RedwoodJS was a bit less smooth. I had to install the package twice, once in the <code>web</code> app and then again in the <code>api</code> app. I had to manually define queries and re-export pages to get them registered.</li>
</ol>
</li>
</ol>
<p>Some of that is due to the design of the frameworks (e.g. serverless-first assumptions), some of it was due to wanting to allow more flexibility (e.g. database implementation is not owned by the framework).</p>
<p>For fun, we built a (very subjective) tier list of frameworks we tried based on their level of support for what we call full-stack modules: <a href="https://fsm-research.static.miho.dev/fsm-tier-list" target="_blank" rel="noopener noreferrer" class="">https://fsm-research.static.miho.dev/fsm-tier-list</a></p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Tier list showing support for full-stack modules across frameworks" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/full-stack-modules-tier-list.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Tier list of support for full-stack modules in various frameworks. JS frameworks are highlighted in yellow.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-there-are-no-full-stack-modules-in-js">Why there are no full-stack modules in JS<a href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module#why-there-are-no-full-stack-modules-in-js" class="hash-link" aria-label="Direct link to Why there are no full-stack modules in JS" title="Direct link to Why there are no full-stack modules in JS" translate="no">​</a></h2>
<p>Hm, if full-stack modules are so great, why aren't they a JS standard? I think it's useful to first define what full-stack modules need to be viable in an ecosystem.</p>
<p>Full-stack modules need:</p>
<ol>
<li class="">A way to ship runtime code (React components, Node.js server code, etc.)</li>
<li class="">A way to ship glue (code that describes how pieces fit together)</li>
<li class="">A way to distribute an installable unit</li>
</ol>
<p>JavaScript ecosystem has no shortage of great libraries, and in great part that's due to how easy it is to ship code with <code>npm</code>. I'd say that sorts out points 1 and 3: it's easy to ship and install libraries.</p>
<p>But, it's impossible to ship "glue" code, the code that connects, e.g. the Stripe SDK on the backend, the payment button, and your database storage layer. I mean, how could it work if there are so many different standards for every little thing in JS?</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="A full-stack module shipped as an npm package" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/npm-full-stack-module.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">A full-stack module shipped as an npm package.</figcaption></figure></div>
<p>There is no standard full-stack layer you can rely on when shipping a library, so you can't really ship full-stack libraries.</p>
<p>One of the core reasons is that many popular frameworks are frontend-first, and nobody dares to own the full-stack concept: client, server, and the database. You need to opt into owning (and accept the maintenance burden) everything if you want to provide a consistent development surface.</p>
<p>When you have some stable surface, your libraries can actually make assumptions and be "braver", e.g. they can assume how the routing works or how to expose webhooks in your app.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="wasp-is-doing-something-about-it">Wasp is doing something about it<a href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module#wasp-is-doing-something-about-it" class="hash-link" aria-label="Direct link to Wasp is doing something about it" title="Direct link to Wasp is doing something about it" translate="no">​</a></h2>
<p>So what are we doing about it? We are building a truly full-stack framework. We control the frontend, the backend, and the database layer. That puts us in a good position to ship a full-stack module system on a predictable stack, and later grow it into a registry.</p>
<p>The core feature of Wasp is its spec file, a TypeScript config where you describe your app's features like client routing, server queries and actions, async jobs, etc. You still write React and Node.js to implement your features, while Wasp's spec file is where you write the "glue" code.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The Wasp Spec file defines application wiring code in one place" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/wasp-spec-file.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">You define all the wiring code in one place: the Wasp Spec file.</figcaption></figure></div>
<p>The cool thing about the "glue" code being written in a TypeScript spec file means that we can also package it alongside the React and Node.js code. We then arrive at a full-stack module.</p>
<p>One package which ships:</p>
<ul>
<li class="">React and Node.js code,</li>
<li class="">and the spec file that explains how to wire it all together.</li>
</ul>
<p>I can hear you saying "This is all very exciting, but let's see some code", so, okay, okay, let's take a quick look at some of the technical details. Beware, this is all very experimental, but the concept is solid.</p>
<p>Let's see how we can extract a full-stack feature from your Wasp app, so you can reuse it in the next project or even across all your company's internal tooling.</p>
<p>Here's an example Wasp spec file:</p>
<div class="language-typescript codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-typescript codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// main.wasp.ts</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// Regular Wasp app: the app owns the payments wiring.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> action</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> api</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> app</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> page</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> query</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> route </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> LandingPage </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/landing-page/LandingPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> PricingPage </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/payment/PricingPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> CheckoutResultPage </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/payment/CheckoutResultPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> generateCheckoutSession</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> getCustomerPortalUrl </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/payment/operations"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> paymentsMiddlewareConfigFn</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> paymentsWebhook </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/payment/webhook"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"LandingPageRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">LandingPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> prerender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// Payments "glue" code</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"PricingPageRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/pricing"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">PricingPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      prerender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token string" style="color:#e3116c">"CheckoutResultRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token string" style="color:#e3116c">"/checkout"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">CheckoutResultPage</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">query</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">getCustomerPortalUrl</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"User"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">generateCheckoutSession</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"User"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">api</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"POST"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/payments-webhook"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> paymentsWebhook</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"User"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      middlewareConfigFn</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> paymentsMiddlewareConfigFn</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>We see that to implement payments we need:</p>
<ul>
<li class="">two client pages: <code>/pricing</code> and <code>/checkout</code></li>
<li class="">two operations: <code>getCustomerPortalUrl</code> and <code>generateCheckoutSession</code></li>
<li class="">and a webhook endpoint at <code>/payments-webhook</code></li>
</ul>
<p>For each of those pieces, we also have runtime code in files like <code>PricingPage.tsx</code> and <code>operations.ts</code>.</p>
<p>So if we wanted to share this as an installable full-stack feature, we need to package both the runtime and the spec code. This way, Wasp knows how to wire the feature once installed.</p>
<p>Let's say we shipped <code>stripePayments</code> as an <code>npm</code> package. This is how using the full-stack module would look:</p>
<div class="language-typescript codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-typescript codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// main.wasp.ts</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// Wasp app with a full-stack payments module.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> app</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> page</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> route </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> stripePayments </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@acme/stripe-payments/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> LandingPage </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/landing-page/LandingPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"LandingPageRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">LandingPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> prerender</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">stripePayments</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"Payments"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> User</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"User"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      plans</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        hobby</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          kind</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"subscription"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          priceIdEnvVar</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"PAYMENTS_HOBBY_SUBSCRIPTION_PLAN_ID"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        pro</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          kind</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"subscription"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          priceIdEnvVar</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"PAYMENTS_PRO_SUBSCRIPTION_PLAN_ID"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        credits10</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          kind</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"credits"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          amount</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token number" style="color:#36acaa">10</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          priceIdEnvVar</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"PAYMENTS_CREDITS_10_PLAN_ID"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>In our example, you:</p>
<ul>
<li class="">import <code>stripePayments</code> from <code>@acme/stripe-payments/spec</code>,</li>
<li class="">configure it with your app's payment plans,</li>
<li class="">get the client pages, operations, and webhook endpoints set up automatically!</li>
</ul>
<p>One extra fun fact: since the spec file is written in TypeScript, you can even fetch the info about your payment plans from a CMS or an API.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Installing a full-stack module in a Wasp application" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/installing-wasp-full-stack-module.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Installing a full-stack module in Wasp.</figcaption></figure></div>
<p>Full-stack modules will not fit every use case. So there should be escape hatches:</p>
<ol>
<li class="">Shipping FSMs as npm packages gives authors flexibility to expose lower-level primitives. Users can rewire the high-level design without rewriting the implementation.</li>
<li class="">And of course, you can take the FSM code as a reference implementation and tweak it, reimplement pieces of it, etc.</li>
<li class="">Or even better, fork it with your tweaks and maintain an internal version specific to your organisation that you can use across your internal apps.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="open-saas-could-become-open-anything">Open SaaS could become Open Anything<a href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module#open-saas-could-become-open-anything" class="hash-link" aria-label="Direct link to Open SaaS could become Open Anything" title="Direct link to Open SaaS could become Open Anything" translate="no">​</a></h2>
<p>At Wasp, we've built and maintain the most popular open-source SaaS boilerplate starter, <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>.</p>
<p>It's already packed with features:</p>
<ul>
<li class="">payments</li>
<li class="">auth methods</li>
<li class="">file upload</li>
<li class="">an LLM wrapper example</li>
<li class="">etc.</li>
</ul>
<p>But we're reluctant to add new ones, because it's already common for users to delete many features from the template to customize it (which is pretty meh from a DX perspective).</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Open SaaS, Wasp's open-source SaaS starter" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/open-saas.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Our open-source and free SaaS starter.</figcaption></figure></div>
<p>Let's imagine what full-stack modules would mean for starters like these. Instead of shipping a starter with <em>all the features</em>, you could maybe start with a nice design system and tell users to install <em>features</em> they need. A user building an LLM-powered site with subscriptions would only install the payments and LLM full-stack modules. Some other user might install only the admin panel and S3 file uploads full-stack modules, etc.</p>
<p>And those are only the modules we thought of so far. Imagine when the ecosystem has hundreds of community built modules, this starter becomes the most powerful starter in the world. And of course, the same modules could be used by any Wasp app out there.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Concept design for a full-stack module registry" src="https://wasp.sh/img/blog/2026-06-22-javascript-still-cant-ship-a-full-stack-module/module-registry.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">A concept for a future full-stack module registry.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="conclusion">Conclusion<a href="https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module#conclusion" class="hash-link" aria-label="Direct link to Conclusion" title="Direct link to Conclusion" translate="no">​</a></h2>
<p>We've seen in other ecosystems how powerful these legos/full-stack modules are. Developers and LLMs that use them get more done plus have higher confidence in their apps.</p>
<p>We think it's possible to bring the same idea to the JS ecosystem.</p>
<p>The pieces we need to make it happen:</p>
<ul>
<li class="">a stable full-stack surface to work against,</li>
<li class="">a way to ship together React components, Node.js code, and the "glue" code.</li>
</ul>
<p>And that's exactly what we want to build with Wasp. <a href="https://x.com/WaspLang" target="_blank" rel="noopener noreferrer" class="">Follow us on X</a> or join our <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a> to follow along.</p>]]></content:encoded>
            <author>miho@wasp-lang.dev (Mihovil Ilakovac)</author>
            <category>wasp</category>
            <category>javascript</category>
            <category>full-stack</category>
            <category>ai</category>
            <category>typescript</category>
        </item>
        <item>
            <title><![CDATA[Made with Wasp, Vol. 2 - from video editing to daycare lesson planning]]></title>
            <link>https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2</link>
            <guid>https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2</guid>
            <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Four paid SaaS apps built with Wasp: CutCue for streamers, Brick for UK landlords, ChatBuster for Shopify stores and PlanRelief for daycare.]]></description>
            <content:encoded><![CDATA[<div class="figure-container"><div class="app-showcase-grid" style="background:#F5C842;padding:14px;display:grid;grid-template-columns:1fr 1fr;gap:12px;border:3px solid #111;box-sizing:border-box"><a href="https://cutcue.io/" target="_blank" rel="noreferrer noopener" style="display:block"><img alt="CutCue" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-cutcue.webp" style="display:block;width:100%;height:auto;border:3px solid #111;box-sizing:border-box"></a><a href="https://onbrick.co.uk/" target="_blank" rel="noreferrer noopener" style="display:block"><img alt="Brick" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-brick.webp" style="display:block;width:100%;height:auto;border:3px solid #111;box-sizing:border-box"></a><a href="https://chatbuster.com/" target="_blank" rel="noreferrer noopener" style="display:block"><img alt="ChatBuster" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-chatbuster.webp" style="display:block;width:100%;height:auto;border:3px solid #111;box-sizing:border-box"></a><a href="https://planrelief.io/" target="_blank" rel="noreferrer noopener" style="display:block"><img alt="PlanRelief" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-planrelief.webp" style="display:block;width:100%;height:auto;border:3px solid #111;box-sizing:border-box"></a></div><style>@media (width<=640px){.app-showcase-grid{grid-template-columns:1fr!important}}</style></div>
<p>Welcome to Day 3 of <a class="" href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec">Launch Week #12</a>, a.k.a. Community Day. This is the one where we step out of the way and let the Waspeteers do the talking. 🐝</p>
<p>We get one question more than any other: <em>"okay, but what do people actually build with Wasp?"</em> Today's the answer.</p>
<p>Four apps, four verticals that have basically nothing to do with each other (video tooling, UK property tech, e-commerce, and early-childhood education), all paid, all in production, all built by people from the Wasp community. It's been a minute since <a class="" href="https://wasp.sh/blog/2023/06/28/what-can-you-build-with-wasp">Vol. 1 back in 2023</a>, and the bar has moved. Let's get into it.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="cutcue---the-ai-editing-intern-for-streamers-wasp--python-workers"><a href="https://cutcue.io/" target="_blank" rel="noopener noreferrer" class="">CutCue</a> - the AI editing intern for streamers (<em><strong>Wasp + Python workers</strong></em>)<a href="https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2#cutcue---the-ai-editing-intern-for-streamers-wasp--python-workers" class="hash-link" aria-label="Direct link to cutcue---the-ai-editing-intern-for-streamers-wasp--python-workers" title="Direct link to cutcue---the-ai-editing-intern-for-streamers-wasp--python-workers" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><div style="background:#F5C842;padding:14px;border:3px solid #111;box-sizing:border-box;display:inline-block"><img style="display:block;border:3px solid #111;box-sizing:border-box" alt="CutCue landing page - 'Stop scrubbing. Start cutting.' AI tool that auto-generates timestamped markers from audio and video" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-cutcue.webp"></div><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p><strong>Try it out:</strong> <a href="https://cutcue.io/" target="_blank" rel="noopener noreferrer" class="">cutcue.io</a>  ·  <strong>Pricing:</strong> €29 to €189/mo</p>
<p>Imagine you just streamed for six hours on Twitch and now you have to pull the three best clips for YouTube. Normally that's an evening of scrubbing the VOD with a coffee. Drop the recording into CutCue and you get back a timeline already marked up with <strong>highlights, chapter breaks, brand mentions, moments that could lose you ad revenue (e.g. swearing), and chat peaks</strong>, automatically.</p>
<div style="display:flex;justify-content:center;margin:1rem 0"><figure style="width:100%;margin:0"><video width="100%" controls="" aria-label="Short demo video of CutCue interpreting a Twitch VOD and marking up the timeline"><source src="/img/blog/2026-06-17-made-with-wasp-vol-2/cutcue-demo-video.mp4" type="video/mp4"></video><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">CutCue interpreting a VOD in real time.</figcaption></figure></div>
<p>The cool bit: the markers don't sit in some web dashboard you have to copy-paste from. CutCue exports straight into <strong>Premiere Pro, DaVinci Resolve, Vegas, Audacity, and Reaper</strong>, so they show up exactly where your timeline expects them. You open your editor, and the AI's homework is already on the canvas.</p>
<p>Under the hood: a <strong>Wasp app orchestrating four to five Dockerized Python workers</strong> (audio extraction, chapter detection, fingerprinting, queue management), self-hosted on Hetzner, built stateless from day one so it can scale horizontally when it needs to. The kicker: shipped by a backend-heavy engineer who'd never written React before this project.</p>
<blockquote>
<p>"I described it usually as a baseline or a toolkit, the foundation for my project, which takes over the important stuff like session management, user payment, all the things which usually take a long time to build yourself and make stable and secure."</p>
<p><em>- the CutCue founder</em></p>
</blockquote>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="brick---a-website-builder-for-uk-property-operators"><a href="https://onbrick.co.uk/" target="_blank" rel="noopener noreferrer" class="">Brick</a> - a website builder for UK property operators<a href="https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2#brick---a-website-builder-for-uk-property-operators" class="hash-link" aria-label="Direct link to brick---a-website-builder-for-uk-property-operators" title="Direct link to brick---a-website-builder-for-uk-property-operators" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><div style="background:#F5C842;padding:14px;border:3px solid #111;box-sizing:border-box;display:inline-block"><img style="display:block;border:3px solid #111;box-sizing:border-box" alt="Brick landing page - 'The property site you've been putting off. Live in five minutes.' Website builder for UK property operators" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-brick.webp"></div><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p><strong>Try it out:</strong> <a href="https://onbrick.co.uk/" target="_blank" rel="noopener noreferrer" class="">onbrick.co.uk</a>  ·  <strong>Pricing:</strong> £45 to £119/mo</p>
<p>Picture this: you're a UK landlord with three properties, and a prospective tenant just asked for your website. You... don't have one. Brick is the fastest way out of that conversation.</p>
<p>You tell it your business name and what kind of property you run (rent-to-rent, serviced accommodation, HMO, deal sourcing, development), and it spins up a full website in about five minutes: <strong>AI-generated copy</strong> tuned to your niche, a <strong>chatbot that captures leads</strong> while you're at a viewing, <strong>GDPR pages, SSL, daily backups</strong>, the lot. Each property niche gets its own template, so the sites don't all look the same.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Brick's visual editor: section forms on the left ('About Section' with badge text, section title, and paragraph fields), live website preview on the right showing a polished property-management hero" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/brick-editor.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Brick features a full-fledged no-code website editor! Really cool.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="chatbuster---the-ai-chat-that-closes-the-sale-live-on-shopify-and-wordpress"><a href="https://chatbuster.com/" target="_blank" rel="noopener noreferrer" class="">ChatBuster</a> - the AI chat that closes the sale, live on Shopify and WordPress<a href="https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2#chatbuster---the-ai-chat-that-closes-the-sale-live-on-shopify-and-wordpress" class="hash-link" aria-label="Direct link to chatbuster---the-ai-chat-that-closes-the-sale-live-on-shopify-and-wordpress" title="Direct link to chatbuster---the-ai-chat-that-closes-the-sale-live-on-shopify-and-wordpress" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><div style="background:#F5C842;padding:14px;border:3px solid #111;box-sizing:border-box;display:inline-block"><img style="display:block;border:3px solid #111;box-sizing:border-box" alt="ChatBuster landing page - 'The chat that closes the sale.' AI chat trained on your Shopify or WooCommerce store" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-chatbuster.webp"></div><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p><strong>Try it out:</strong> <a href="https://chatbuster.com/" target="_blank" rel="noopener noreferrer" class="">chatbuster.com</a>  ·  <strong>Pricing:</strong> from $40/mo  ·  <strong>Where:</strong> Shopify App Store + WordPress.org</p>
<p>If you've ever shopped on a Shopify store and pinged the chat widget at midnight to ask <em>"do you ship to Canada?"</em>, ChatBuster is the thing on the other end. Except now it's AI, trained on <strong>the merchant's actual catalog, theme, and policies</strong>, so it answers with the right number, the right policy, and the right SKU.</p>
<p>Under the hood: <strong>live catalog sync</strong> (SKUs, prices, stock update as the merchant updates), <strong>proactive prompts</strong> you can trigger on scroll or schedule, and <strong>order tracking</strong> through the store's API. A merchant installs it from the <strong>Shopify App Store</strong> or <strong>WordPress.org</strong> (the WP plugin went live in May 2026), flips one toggle, and it's working five minutes later. No developer required.</p>
<p>And it's not theoretical. Real merchants are already leaving five-star reviews:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Two five-star reviews from real Shopify merchants using ChatBuster, both praising how easy it was to set up" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/chatbuster-reviews.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Five-star reviews from Shopify merchants.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="planrelief---ai-lesson-plans-for-daycare-and-early-years-educators"><a href="https://planrelief.io/" target="_blank" rel="noopener noreferrer" class="">PlanRelief</a> - AI lesson plans for daycare and early-years educators<a href="https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2#planrelief---ai-lesson-plans-for-daycare-and-early-years-educators" class="hash-link" aria-label="Direct link to planrelief---ai-lesson-plans-for-daycare-and-early-years-educators" title="Direct link to planrelief---ai-lesson-plans-for-daycare-and-early-years-educators" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><div style="background:#F5C842;padding:14px;border:3px solid #111;box-sizing:border-box;display:inline-block"><img style="display:block;border:3px solid #111;box-sizing:border-box" alt="PlanRelief landing page - 'Generate lesson plans. Instantly.' AI-powered lesson plans for educators of ages 0 to 12" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/app-planrelief.webp"></div><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p><strong>Try it out:</strong> <a href="https://planrelief.io/" target="_blank" rel="noopener noreferrer" class="">planrelief.io</a>  ·  <strong>Pricing:</strong> free to try  ·  <strong>For:</strong> educators of ages 0 to 12</p>
<p>Imagine you're a daycare teacher and you spent the afternoon watching kids in the play corner. You jot down <em>"Mia experimented with mixing colours."</em> PlanRelief takes that one-line observation, plus a theme you pick ("rainbows and seasons"), and generates <strong>a full lesson plan</strong>: learning objectives, materials list, assessment strategies, the activity flow, ready to hand to a supervisor.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="PlanRelief 'Pick a Lesson Plan' menu with two toddler-friendly activities: 'Big Button App Board Play' and 'Sort, Stick, and Swap App Icons,' generated from the topic 'learn building web apps'" src="https://wasp.sh/img/blog/2026-06-17-made-with-wasp-vol-2/planrelief-lesson-options.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">I typed 'learn building web apps' as the topic. The AI took it seriously and came back with toddler-grade activities involving big buttons and Velcro icon boards. Respect.</figcaption></figure></div>
<p>The pitch line is exactly what you'd want it to be: <em>"paperwork done in minutes, not hours."</em> Free to try, no credit card.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="build-anything-with-wasp-ship-it-and-get-paying-customers">Build anything with Wasp, ship it, and get paying customers<a href="https://wasp.sh/blog/2026/06/17/made-with-wasp-vol-2#build-anything-with-wasp-ship-it-and-get-paying-customers" class="hash-link" aria-label="Direct link to Build anything with Wasp, ship it, and get paying customers" title="Direct link to Build anything with Wasp, ship it, and get paying customers" translate="no">​</a></h2>
<p>Four apps, zero overlap. Creator tools, property tech, e-commerce, classroom. All paid SaaS. All running in production. All built on the same framework you can install with one command.</p>
<p>That's the whole point of Community Day, really: when we say Wasp is a real fullstack framework, we mean <em>real</em>. Apps in real verticals, with real customers paying real money. The lineup looks very different from <a class="" href="https://wasp.sh/blog/2023/06/28/what-can-you-build-with-wasp">Vol. 1</a>, and it'll look very different again the next time we do this.</p>
<p>If you've built something on Wasp that should be in Vol. 3, come say hi on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a> or <a href="https://twitter.com/WaspLang" target="_blank" rel="noopener noreferrer" class="">X/Twitter</a>. We'd love to feature you next time.</p>
<p>And if you haven't started yet, you're one command away:</p>
<div data-track-event="Install Command: Copy" class="contents"><div class="language-bash codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-bash codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">npm</span><span class="token plain"> i </span><span class="token parameter variable" style="color:#36acaa">-g</span><span class="token plain"> @wasp.sh/wasp-cli@latest</span><br></div></code></pre></div></div></div>
<p>See you on Day 4. 🐝</p>]]></content:encoded>
            <author>matija@wasp-lang.dev (Matija Sosic)</author>
            <category>launch-week</category>
            <category>showcase</category>
            <category>community</category>
            <category>wasp</category>
            <category>saas</category>
            <category>web dev</category>
        </item>
        <item>
            <title><![CDATA[Wasp now lets you write your full-stack logic as a spec in TypeScript]]></title>
            <link>https://wasp.sh/blog/2026/06/15/wasp-typescript-spec</link>
            <guid>https://wasp.sh/blog/2026/06/15/wasp-typescript-spec</guid>
            <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Wasp replaced its custom DSL with the TypeScript Spec: you define your full-stack app in main.wasp.ts and can split it into files and use loops.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Wasp's new TypeScript Spec: a main.wasp.ts file defining the whole app — title, wasp version, auth, and a spec list with route/page/query calls — all in TypeScript" src="https://wasp.sh/img/blog/2026-06-15-wasp-typescript-spec/banner.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p><a class="" href="https://wasp.sh/">Wasp</a> is an opinionated, <strong>batteries-included</strong> full-stack JS/TS web app framework, built around the concept of an explicit spec for defining full-stack features of your app.</p>
<p>Today is a big day: we dropped our custom spec language and replaced it with a new, TypeScript-native way to define your full-stack app at a high level: the <a class="" href="https://wasp.sh/docs/features/spec">TypeScript Spec</a>!</p>
<!-- -->
<p>Read on for the why and the what, or if you want to try it out right now, go to <a class="" href="https://wasp.sh/docs/quick-start">the quick start guide</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="quick-recap-of-the-last-5-years">Quick recap of the last 5 years<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#quick-recap-of-the-last-5-years" class="hash-link" aria-label="Direct link to Quick recap of the last 5 years" title="Direct link to Quick recap of the last 5 years" translate="no">​</a></h2>
<p>Wasp is an opinionated, <strong>batteries-included</strong>, <strong>truly full-stack, spec-driven</strong> JS/TS web app framework, in spirit similar to RoR/Laravel/Django/Meteor, but reimagined from scratch for modern JS.</p>
<p><strong>“Truly full-stack”</strong> because Wasp covers frontend, backend, and the database; Wasp’s goal is to capture the web app development end-to-end, in its entirety, as one cohesive whole.</p>
<p><strong>“Spec-driven”</strong> because of Wasp’s unique, central concept of the <strong>spec</strong> (specification). It's in the name: Web App SPecification == Wasp.</p>
<p>Spec is a dedicated logic layer where you define your app at the full-stack level, that ties all parts of the stack together, and then you implement it all in the underlying technologies you are used to: React, Node, Prisma, … .
It is the place where you are not writing frontend, backend, or database logic, you are writing "full-stack" logic.</p>
<p>So far, the spec layer in Wasp was implemented as a standalone language (DSL), with our own custom compiler and tooling. <a class="" href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake">Turns out that was more trouble than it was worth</a>, and it started blocking us in further growing Wasp into what we want it to become, so by popular demand, we switched to spec in TypeScript!</p>
<p>Read on to learn more about it, how it works and what it unlocks.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-wasp-typescript-spec">The Wasp TypeScript Spec<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#the-wasp-typescript-spec" class="hash-link" aria-label="Direct link to The Wasp TypeScript Spec" title="Direct link to The Wasp TypeScript Spec" translate="no">​</a></h2>
<p>You write the <a class="" href="https://wasp.sh/docs/features/spec">Wasp TypeScript Spec (TS Spec)</a> in <code>*.wasp.ts</code> files by constructing the <code>app</code> spec object.</p>
<p>You do so by using the spec constructors from <code>@wasp.sh/spec</code>: <code>page</code>, <code>route</code>, <code>query</code>, <code>job</code>, <code>api</code>, … . That is your "vocabulary" that you use to specify the parts of your web app, and then compose them all together into one big <code>app</code> spec object.</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> app</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> page</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> query</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> route </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> </span><span class="token imports maybe-class-name">MainPage</span><span class="token imports"> </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/MainPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// React</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> getTasks </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/tasks"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Node.js</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  wasp</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> version</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"^0.24.0"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  title</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ToDo App"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  auth</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    userEntity</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"User"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    methods</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> google</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> gitHub</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> email</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    onAuthFailedRedirectTo</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/login"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"RootRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">MainPage</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">query</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">getTasks</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"Task"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>Wasp takes the spec and the rest of your code (React, Node.js, <code>schema.prisma</code>, …), and builds them into a full-stack app.</p>
<p>In the example above, this app will have:</p>
<ul>
<li class="">Full-stack auth working out of the box (supporting Google, GitHub, or email &amp; password auth).</li>
<li class="">The <code>src/MainPage.tsx</code> React component mounted as the home page at <code>/</code>.</li>
<li class="">The <code>getTasks</code> function from <code>src/tasks.ts</code> made callable from the client (e.g. from <code>MainPage.tsx</code>) via RPC, either directly or via TanStack Query.</li>
</ul>
<blockquote>
<p>💡 If you used the old Wasp DSL, you might be thinking at this point "hey this looks the same as before, maybe even a bit more verbose". True, but this is where the similarities stop, and exciting new possibilities start: read on.</p>
</blockquote>
<p>While writing the spec, you are just writing TypeScript.<br>
<!-- -->You can use third-party libraries, you can split the spec into multiple TypeScript files, you can define your own helper functions, use for loops, read from the disk, inspect env vars, you can organize your app vertically by features together with their spec, launch a rocket, … .<br>
<!-- -->The only thing Wasp requires from you is that you export an <code>app</code> spec object from the <code>main.wasp.ts</code> file.</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockTitle_gul4">main.wasp.ts</div><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> readFile </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"fs/promises"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> app</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> page</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> route </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> authSpec </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/auth/auth.wasp"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> cardsSpec </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/cards/cards.wasp"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">MainPage</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/cards/MainPage"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">Layout</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/Layout"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"waspello"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// A Trello clone app made with Wasp!</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  wasp</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> version</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"^0.24.0"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  title</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">(</span><span class="token keyword" style="color:#00009f">await</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">readFile</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"appTitle.txt"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"utf-8"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">trim</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Reading from disk.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  auth</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    userEntity</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"User"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    methods</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      usernameAndPassword</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      google</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    onAuthFailedRedirectTo</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/login"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  client</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    rootComponent</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token maybe-class-name">Layout</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"MainRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">MainPage</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token comment" style="color:#999988;font-style:italic">// Parts of specification extracted into their own files.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    authSpec</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    cardsSpec</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockTitle_gul4">src/cards/cards.wasp.ts</div><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// A specification for the "cards" functionality.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> action</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> query</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">type</span><span class="token plain"> </span><span class="token class-name">Spec</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> withFields </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"../utils.wasp"</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Custom helper function.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> createCard</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"> updateCard </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./cards"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"></span><br></div><div class="token-line" style="color:#393A34"><span class="token imports">  createList</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"></span><br></div><div class="token-line" style="color:#393A34"><span class="token imports">  createListCopy</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"></span><br></div><div class="token-line" style="color:#393A34"><span class="token imports">  deleteList</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"></span><br></div><div class="token-line" style="color:#393A34"><span class="token imports">  getListsAndCards</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"></span><br></div><div class="token-line" style="color:#393A34"><span class="token imports">  updateList</span><span class="token imports punctuation" style="color:#393A34">,</span><span class="token imports"></span><br></div><div class="token-line" style="color:#393A34"><span class="token imports"></span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./lists"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> cardsSpec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token maybe-class-name">Spec</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token spread operator" style="color:#393A34">...</span><span class="token method function property-access" style="color:#d73a49">withFields</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"List"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">createList</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">updateList</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token spread operator" style="color:#393A34">...</span><span class="token method function property-access" style="color:#d73a49">withFields</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"Card"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">createCard</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">updateCard</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token spread operator" style="color:#393A34">...</span><span class="token method function property-access" style="color:#d73a49">withFields</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"List"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Card"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">query</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">getListsAndCards</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">deleteList</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">"Log"</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">createListCopy</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>Those <code>with { type: ref }</code> imports you might have noticed in the code examples above?<br>
<!-- -->That is how you connect the spec with the implementation (currently React, Node.js, Prisma), how you connect the full-stack "story" with the specific parts of the stack.<br>
<!-- -->A bit of bundler magic happens there: <code>with { type: ref }</code> imports don't actually get evaluated, so no importing really happens, but instead they get transformed into objects that "reference" the import for later evaluation, that you then pass to the spec. You can even construct these directly as objects, inline, if you wish (useful if you are creating them dynamically): <code>ref({ import: "getTasks", from: "./src/queries" })</code>.</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// Ref import</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> getTasks </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/tasks"</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ref"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// gets transformed by bundler into</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> getTasks </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">ref</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">import</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"getTasks"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"./src/tasks"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// where `ref` comes from</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> ref </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@wasp.sh/spec"</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>That's it really! Wasp gives you the building blocks, and you do what you want with them, with the full power of TypeScript behind you.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="do-not-try-this-at-home-implementing-file-based-routing-in-ts-spec">Do <del>not</del> try this at home: implementing file-based routing in TS Spec<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#do-not-try-this-at-home-implementing-file-based-routing-in-ts-spec" class="hash-link" aria-label="Direct link to do-not-try-this-at-home-implementing-file-based-routing-in-ts-spec" title="Direct link to do-not-try-this-at-home-implementing-file-based-routing-in-ts-spec" translate="no">​</a></h2>
<p>An example of what is uniquely doable with Wasp's new TypeScript Spec (and wasn't possible with the old DSL): implementing file-based routing.</p>
<p>By default, Wasp doesn't come with file-based routing: instead, you define your routes explicitly in the spec:</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// ...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"MainRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">Main</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"SignupRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/signup"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">SignupPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"LoginRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/login"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">LoginPage</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// ...</span><br></div></code></pre></div></div>
<p>But, let's say you want file-based routing nevertheless. With the new TypeScript spec you can do that in Wasp!</p>
<p>You could create, let's say, a <code>fileRouter.wasp.ts</code> that exports a helper function that reads the contents of the <code>src/</code> dir and based on dirs and files produces an array of <code>route</code> and <code>page</code> spec objects.</p>
<p>For example, a file at path <code>src/pages/(auth)/report/[id].tsx</code> could result in</p>
<div class="language-tsx codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-tsx codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"ReportRoute"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/report/:id"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token maybe-class-name">ReportPage</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><br></div></code></pre></div></div>
<p>Import that function in your <code>main.wasp.ts</code> and add its output to the <code>app.spec</code> array, and that is it, you implemented your own custom file-based routing! What does this make Wasp: a meta-meta-framework?</p>
<p>If you are interested in the exact implementation, stay tuned: we will be publishing it as a separate post soon. If you implement it on your own in the meantime though, please share it with us, we would love to see how you did it!</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-specification-at-all">Why spec(ification) at all?<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#why-specification-at-all" class="hash-link" aria-label="Direct link to Why spec(ification) at all?" title="Direct link to Why spec(ification) at all?" translate="no">​</a></h2>
<p>We mentioned the "spec" so many times in this article, but why should you care about it?</p>
<p>Why do we at Wasp care about it so much that we have spent years making and remaking the whole web framework around this idea, when every other "normal" JS web framework out there is focusing on data fetching, hydration strategies, tight integration with the UI library, … ?</p>
<p>All web frameworks, by definition, capture the domain/essence of what a web app is, give it structure, introduce their concepts, and then let you fill in the gaps, effectively separating the <strong>specification</strong> (what you want) from the <strong>implementation</strong> (how you want it).
This lets you focus on the details of your business logic, what your app is really about (essential complexity), and implement it exactly how you want it, while the framework handles the rest of the details for you (accidental complexity) as you specified it.</p>
<p>What we are doing with the spec(ification) at Wasp though, is making that specification a <strong>first-class citizen</strong> in your app.</p>
<p>It's not convention based (e.g. magic names, dir structure, …), it's not implicit, it's not tied up in the runtime of the underlying stack.
Instead, it is <strong>explicit, malleable, programmable, standalone, stack-agnostic, extendable</strong>. It has its own Turing-complete logic layer (thank you TypeScript), and just as you could write frontend or backend logic so far, now you can also write "app"/"full-stack" logic next to it. That logic has its own standalone runtime and can affect how the rest of the code is used and generated.</p>
<p>This means you can organize your spec as you want, you can reuse it, <strong>share/distribute</strong> it.</p>
<p>Right now the Wasp spec comes with a predefined "vocabulary": <code>route</code>, <code>query</code>, <code>job</code>, … , but we are excited about the idea of <strong>"extensible spec"</strong>: being able to add your own "words" to it.</p>
<p>Or, imagine being able to take the whole <strong>vertical slice of your app, truly full-stack</strong> (fe, be, db, env, even infra), and making it a reusable, distributable unit with a defined interface (in spec) that can then be used and configured from anybody's spec. We are working on this currently under the working name of <a href="https://github.com/wasp-lang/wasp/issues/2873" target="_blank" rel="noopener noreferrer" class="">Full Stack Modules</a> (FSMs).</p>
<p>Additionally, although now implemented in TypeScript, spec is standalone and therefore also <strong>stack and language agnostic</strong>. We could support writing (additional) backend logic in Python, Go or Rust in the future, you would just specify them in the spec (e.g. as queries and actions). We could add other frontend libraries next to React and spec wouldn’t change.</p>
<p><strong>To summarize</strong>: we are doing the "spec" because we are excited about what gets unlocked when you make full-stack logic a "first-class" citizen in a batteries-included web framework.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="spec-and-ai">Spec and AI<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#spec-and-ai" class="hash-link" aria-label="Direct link to Spec and AI" title="Direct link to Spec and AI" translate="no">​</a></h2>
<p>Per design, as a full-stack, batteries-included framework, Wasp is in a position to work great with AI, due to the same reasons as Ruby on Rails, Laravel and others: less code to write, stronger constraints, clear best practices, one cohesive codebase, ... .</p>
<p>Wasp's spec, however, brings additional promise of serving as a central place where one can easily get a high-level overview of the app and the intention behind it, before getting lost in the implementation. Not just for AI, but also for you, especially if leaning harder into the "vibes".</p>
<p>Spec-driven approach to AI engineering is a popular method these days, with tools like <a href="https://github.com/Fission-AI/OpenSpec/" target="_blank" rel="noopener noreferrer" class="">OpenSpec</a> or <a href="https://github.com/github/spec-kit" target="_blank" rel="noopener noreferrer" class="">GitHub Spec Kit</a>, where you write down the specification in Markdown files.<br>
<!-- -->Wasp's spec takes this a level further: your spec is an actual, compiled part of your app, not Markdown files that drift with time. It is though much more constrained in what it can express at the moment, but we are excited to see how it evolves (e.g. once we make it extensible).</p>
<p>Finally, there is the possibility of <a href="https://github.com/wasp-lang/wasp/issues/2873" target="_blank" rel="noopener noreferrer" class="">Full Stack Modules</a>, that Wasp spec unlocks: imagine being able to have truly full-stack pieces that you can test in isolation, reuse / distribute, and know they work? This means you can give AI bigger building blocks than normal, and ensure some things just can't get messed up: if I am using a Stripe payments full-stack module, AI can't just mess it up by accident.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="spec-and-you">Spec and you<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#spec-and-you" class="hash-link" aria-label="Direct link to Spec and you" title="Direct link to Spec and you" translate="no">​</a></h2>
<p>If you find all this interesting, we would love to hear from you (you can find us in our <a href="https://discord.com/invite/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord server</a>). This is the first iteration of the new TypeScript spec and any feedback helps us improve it: what you liked, what you didn't, what you would like to see in the future, anything goes.</p>
<p>You can try Wasp quickly by running <code>npm i -g @wasp.sh/wasp-cli@latest</code>, then <code>wasp new</code>, and then just follow the instructions, or go to our <a class="" href="https://wasp.sh/docs">docs</a> for detailed instructions and a tutorial.</p>
<p>If you are wondering why some part of Wasp is the way it is or how we plan to evolve it, you might find some answers quickly in our <a href="https://github.com/wasp-lang/wasp/issues" target="_blank" rel="noopener noreferrer" class="">GitHub issues</a>: we capture all our future ideas and plans there in the open (all ready for Cloudflare to slop-fork us, and then some). For a more high-level overview, there is <a href="https://github.com/orgs/wasp-lang/projects/5" target="_blank" rel="noopener noreferrer" class="">Wasp Roadmap</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="whats-next">What's next?<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#whats-next" class="hash-link" aria-label="Direct link to What's next?" title="Direct link to What's next?" translate="no">​</a></h2>
<p>Wasp works as it is: we know of people selling startups made with Wasp, building internal apps in Fortune 500 companies, using it in banks. But we are still keeping Wasp in Beta till we fully flesh out the spec side of the story and also bring all the parts of it to the level we are satisfied with.</p>
<p>There are a couple of main categories of improvements we are chasing at the moment:</p>
<ol>
<li class=""><strong>Spec</strong>: Further improving TS Spec design (e.g. bring data models into it), Full Stack Modules, spec extensibility, …</li>
<li class=""><strong>Wasp 1.0</strong>: Refurbishing core parts of Wasp (Auth, Operations, Jobs, Db, Routing/rendering, …) to bring them up to speed with the rest of Wasp, tightening our deployment/production features, …</li>
<li class=""><strong>Width</strong>: Explore adding support for other ORMs (e.g. Drizzle), other frontend libraries (e.g. Svelte, Vue), better support for mobile, maybe even add some infra as code and also support for other backend languages, …</li>
</ol>
<p>As mentioned above, you can find much more detail on all of these in our <a href="https://github.com/wasp-lang/wasp/issues" target="_blank" rel="noopener noreferrer" class="">GitHub issues</a> and on the <a href="https://github.com/orgs/wasp-lang/projects/5" target="_blank" rel="noopener noreferrer" class="">Wasp Roadmap</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="credits">Credits<a href="https://wasp.sh/blog/2026/06/15/wasp-typescript-spec#credits" class="hash-link" aria-label="Direct link to Credits" title="Direct link to Credits" translate="no">​</a></h2>
<p>Big thanks to everybody who put in the time and effort to help us deliver the TS Spec and supported us on the way! Special thanks to <a href="https://github.com/Reikon95" target="_blank" rel="noopener noreferrer" class="">@Reikon95</a>, <a href="https://github.com/Genyus" target="_blank" rel="noopener noreferrer" class="">@Genyus</a>, <a href="https://github.com/devagrawal09" target="_blank" rel="noopener noreferrer" class="">@devagrawal09</a>, <a href="https://github.com/AlemTuzlak" target="_blank" rel="noopener noreferrer" class="">@AlemTuzlak</a>, and the whole Wasp community, especially the amazing people on our Discord server.</p>]]></content:encoded>
            <author>martin@wasp-lang.dev (Martin Sosic)</author>
            <category>wasp</category>
            <category>typescript</category>
            <category>fullstack</category>
            <category>update</category>
        </item>
        <item>
            <title><![CDATA[Wasp Launch Week #12 - TS Spec aka MeTSamorphosis 🐛🦋]]></title>
            <link>https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec</link>
            <guid>https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec</guid>
            <pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Launch Week #12: Wasp drops its DSL for TS Spec, so you write the app in TypeScript. It adds prerendering, a rebrand and easier deploys.]]></description>
            <content:encoded><![CDATA[<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Launch Week 12 - MeTSamorphosis" src="https://wasp.sh/img/blog/2026-06-05-wasp-launch-week-12-ts-spec/lw12-banner.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>A few weeks ago, we published a post with a title that raised a few eyebrows: <a class="" href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake"><em>"5 years and $5M later: inventing our own programming language was a mistake."</em></a> Five years. One whole DSL. And we said it out loud, in public, on the internet, where it stays forever.</p>
<p>A lot of you wrote in afterwards (<a href="https://www.reddit.com/r/programming/comments/1tc02h0/5_years_and_5m_later_inventing_a_new_programming/" target="_blank" rel="noopener noreferrer" class="">179, to be precise</a>). Some to commiserate, some to cheer, a couple to ask if we were okay (we are, thank you). But the most common question by far was the obvious one:</p>
<p><strong>"Okay… so what are you going to do about it?"</strong></p>
<p>This is the moment where we answer that.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="caterpillars-dont-apologize-for-being-caterpillars-">Caterpillars don't apologize for being caterpillars 🐛<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#caterpillars-dont-apologize-for-being-caterpillars-" class="hash-link" aria-label="Direct link to Caterpillars don't apologize for being caterpillars 🐛" title="Direct link to Caterpillars don't apologize for being caterpillars 🐛" translate="no">​</a></h2>
<p>They just turn into something cooler, with wings (I know this doesn't work 100% for wasps, but <em>licentia poetica</em>, right?).</p>
<p>Welcome to <strong>Launch Week #12</strong>, a.k.a. <strong>MeTSamorphosis</strong>: the week Wasp finally sheds the DSL and emerges in its <strong>true, fully TypeScript-native</strong> form. No more learning a config language to use a framework. No more "wait, why is this a <code>.wasp</code> file?" Just TypeScript, all the way down, the same language you're already writing the rest of your app in.</p>
<p><strong>This is the biggest shift in Wasp's history, so TS Spec is unapologetically the star of this launch</strong>. But it's far from the only thing we've got for you. There's pre-rendering/SSR support, a brand-new look for Wasp, and a few more surprises landing across the week. TS Spec leads the way, but none of the rest is filler.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="but-first---thank-you">But first - Thank you!<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#but-first---thank-you" class="hash-link" aria-label="Direct link to But first - Thank you!" title="Direct link to But first - Thank you!" translate="no">​</a></h3>
<p>Before we dive in, none of what's coming this week happens without you. The community around Wasp has never felt more alive, more people are shipping real apps with it than ever, and we don't take that for granted. So, genuinely: thank you. 🙏</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-cocoon-cracks-open-on-monday-june-15-️">The cocoon cracks open on Monday, June 15 🗓️<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#the-cocoon-cracks-open-on-monday-june-15-%EF%B8%8F" class="hash-link" aria-label="Direct link to The cocoon cracks open on Monday, June 15 🗓️" title="Direct link to The cocoon cracks open on Monday, June 15 🗓️" translate="no">​</a></h2>
<p>There's no launch party without a nice, cozy community call to kick it all off! We're assembling on <strong>Monday, June 15th, 8 AM PT / 11 AM ET / 5 PM CET</strong>. Martin and I will be there live to walk you through TS Spec, take your questions, and probably get a little emotional about it.</p>
<p>Make sure to <a href="https://discord.gg/zXPANMXrZp" target="_blank" rel="noopener noreferrer" class="">register for the event on our Discord</a> and smash that "Interested" button so you don't miss it.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Register for the kickoff call" src="https://wasp.sh/img/blog/2026-06-05-wasp-launch-week-12-ts-spec/lw12-register.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">See you there, fellow metamorphosee. (Not a word. It is now.)</figcaption></figure></div>
<p>Here's some of what's hatching this week. A few of these are locked and loaded. A couple are still in the cocoon and might land later, or show up as a surprise. 🤫</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="-the-big-one---adiós-dsl-ts-spec-is-here">🦋 The Big One - Adiós DSL, TS Spec is here<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#-the-big-one---adi%C3%B3s-dsl-ts-spec-is-here" class="hash-link" aria-label="Direct link to 🦋 The Big One - Adiós DSL, TS Spec is here" title="Direct link to 🦋 The Big One - Adiós DSL, TS Spec is here" translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="main.wasp.ts in the new TS Spec — your whole app config defined in TypeScript: imports, app({...}), auth, and a spec list with route/page/query calls" src="https://wasp.sh/img/blog/2026-06-05-wasp-launch-week-12-ts-spec/ts-spec-example.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">A taste of the new TS Spec: imports up top, app shell in the middle, your routes, pages and queries below - all in one (or more) type-checked TypeScript files.</figcaption></figure></div>
<p>This is the one. After five years, Wasp is now a <strong>TypeScript framework, end to end</strong>. You define your app (pages, routes, auth, jobs, the works) in TypeScript, with full type-safety and editor support, instead of a separate DSL you had to learn first.</p>
<p>We'll publish the full announcement to kick things off, walking through what changed, why it's better, and how to migrate. If you've ever wanted Wasp's superpowers without the "wait, what's this file" tax, this is the one for you.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="GitHub issue #3778 'Moving from the DSL to TS spec' — landing very soon (June 15!)" src="https://wasp.sh/img/blog/2026-06-05-wasp-launch-week-12-ts-spec/dsl-ts-issue.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Spoon, my friend. Very spoon.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="-new-wings---ssr--pre-rendering">⚡ New wings - SSR &amp; pre-rendering<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#-new-wings---ssr--pre-rendering" class="hash-link" aria-label="Direct link to ⚡ New wings - SSR &amp; pre-rendering" title="Direct link to ⚡ New wings - SSR &amp; pre-rendering" translate="no">​</a></h2>
<p>A fresh form needs a fresh set of wings. We're also showing off <strong>server-side rendering / pre-rendering in Wasp</strong>: better SEO, faster first paint, and all the things you've been (politely, mostly) asking us for.</p>
<p>It's already live, so you don't even have to wait for the launch — check out <a class="" href="https://wasp.sh/docs/advanced/prerendering">the prerendering docs</a> and try it on your app today.</p>
<p>Vinny also put together a video walking through it end to end. Keep an eye on YouTube for <em>"Wasp now supports prerendering."</em> 📺</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Lighthouse scores for a prerendered Wasp app: 98 Performance, 92 Accessibility, 96 Best Practices, 92 SEO" src="https://wasp.sh/img/blog/2026-06-05-wasp-launch-week-12-ts-spec/wasp-prerendering.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Lighthouse scores for an Open SaaS landing page with prerendering turned on. Not bad. 💪</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="-the-swarm---community-day">🐝 The swarm - Community Day<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#-the-swarm---community-day" class="hash-link" aria-label="Direct link to 🐝 The swarm - Community Day" title="Direct link to 🐝 The swarm - Community Day" translate="no">​</a></h2>
<p>A Wasp tradition we love: the spotlight goes to <strong>you</strong>, the builders.</p>
<p>We're dropping <strong>"Made with Wasp, Vol. 2"</strong>, a fresh roundup of genuinely cool apps people shipped on Wasp, plus videos and write-ups from community members on what they built and how Wasp helped. Real users showing real things hits different than us claiming Wasp is good, so we'll let them do the talking.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Tweet exchange: Catalin asks for the simplest, most effective full-stack tech stack; Kyle replies '@WaspLang by @MatijaSosic hands down!'" src="https://wasp.sh/img/blog/2026-06-05-wasp-launch-week-12-ts-spec/wasp-testimonial-kyle.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Kyle gets it. 🫡</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="-new-look-who-dis---the-rebrand">🎨 New look, who dis - the Rebrand<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#-new-look-who-dis---the-rebrand" class="hash-link" aria-label="Direct link to 🎨 New look, who dis - the Rebrand" title="Direct link to 🎨 New look, who dis - the Rebrand" translate="no">​</a></h2>
<p>A metamorphosis you can <em>see</em>. Wasp is getting a brand-new look (new visual identity, new vibe, the whole thing), and Boi's TS suit is just the start of it.</p>
<p>We'll also show you the new brand and, more interestingly, the story behind it: we'll talk through why we did it, how we got there, and what we were going for. (Spoiler: we have… opinions about monospace fonts.)</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Wasp's new landing page: 'A truly full-stack TypeScript framework that just works' with a code sample on the right" src="https://wasp.sh/img/blog/2026-06-05-wasp-launch-week-12-ts-spec/wasp-new-lp-screenshot.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Look at me. I am the designer now.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="-out-into-the-world---easier-deploys">🚀 Out into the world - easier deploys<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#-out-into-the-world---easier-deploys" class="hash-link" aria-label="Direct link to 🚀 Out into the world - easier deploys" title="Direct link to 🚀 Out into the world - easier deploys" translate="no">​</a></h2>
<p>A framework is only as good as the places it can fly to, so we've been working on making Wasp even easier to deploy to more of your favorite platforms. We're not spilling all the details yet, but if there's a host you've been wishing was one click away, keep an eye out. 👀</p>
<p>And because we can't help ourselves, there might be <em>one more thing</em> tucked away for you, too. You'll have to show up to find out.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="see-you-on-the-other-side-of-the-cocoon-">See you on the other side of the cocoon 🐝<a href="https://wasp.sh/blog/2026/06/05/wasp-launch-week-12-ts-spec#see-you-on-the-other-side-of-the-cocoon-" class="hash-link" aria-label="Direct link to See you on the other side of the cocoon 🐝" title="Direct link to See you on the other side of the cocoon 🐝" translate="no">​</a></h2>
<p>That's the week: the molt, the wings, the swarm, the new look, and the take-off. We've been working toward this one for a long time, and we honestly can't wait to show you.</p>
<p>As always, we want <strong>all</strong> of your feedback: the good, the bad, and the "did Boi really need a suit." So come find us on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a>, <a href="https://twitter.com/WaspLang" target="_blank" rel="noopener noreferrer" class="">Twitter/X</a>, or <a href="https://github.com/wasp-lang/wasp" target="_blank" rel="noopener noreferrer" class="">GitHub</a>. We're there.</p>
<p>To stay in the loop, <a href="https://twitter.com/WaspLang" target="_blank" rel="noopener noreferrer" class="">follow us on X</a> and <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">join the Discord</a>. See you Monday. 🐝🐝</p>]]></content:encoded>
            <author>matija@wasp-lang.dev (Matija Sosic)</author>
            <category>launch-week</category>
            <category>update</category>
        </item>
        <item>
            <title><![CDATA[How To Build A SaaS with AI. Without Getting Stuck.]]></title>
            <link>https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck</link>
            <guid>https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck</guid>
            <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Build a SaaS with AI without getting stuck: start on a boilerplate, let the agent ask questions first, build in vertical slices, test each one.]]></description>
            <content:encoded><![CDATA[<p>Someone on <a href="https://www.reddit.com/r/vibecoding/comments/1su03dk/vibe_coded_for_6_months_my_codebase_is_a_disaster/" target="_blank" rel="noopener noreferrer" class="">r/vibecoding</a> posted something last week that I've been thinking a lot about. His post is titled: <em>"vibe coded for 6 months. my codebase is a disaster."</em></p>
<p><img decoding="async" loading="lazy" alt="r/vibecoding post titled &amp;quot;vibe coded for 6 months. my codebase is a disaster.&amp;quot;" src="https://wasp.sh/assets/images/reddit-vibe-coded-disaster-8b31aaf8b7e51cc1fe14fb4ed54a5fd8.webp" width="1614" height="812" class="img_qXxT"></p>
<p>Interestingly, he was able to build a functioning SaaS with paying customers, but he encountered endless problems whenever he tried to modify the app in any way.</p>
<!-- -->
<p>So he tried to onboard a developer to help him. The dev opened the repo, went quiet for two minutes, and said: <em>"what is this."</em></p>
<p>Six months of prompting led to a Frankenstein's monster of a codebase that is such a tangled mess, he's probably better off starting over from scratch. In his words, <em>"nobody was thinking about structure. the AI just kept adding. new file here, duplicate function there, 3 different ways to handle the same thing across the codebase."</em></p>
<p>As the creator and maintainer of <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>, I get a lot of people asking for help when building a SaaS with AI. And they get stuck for the same handful of reasons. Usually one of two ways: the first 70% comes together almost too easily and the last 30% becomes next to impossible, or you ship something that works, but you lack any understanding of what you built (like the redditor above), and therefore don't understand what you need to do to modify, extend, or improve your app.</p>
<p>So, with that in mind, let's look at some of my favorite ways you can avoid these problems, build something you understand, and stay in control.</p>
<blockquote>
<p>📺 <strong>Prefer to watch?</strong> I walk through all five of these workflow tips with live demos in <a href="https://youtu.be/0DpqHItVkYs" target="_blank" rel="noopener noreferrer" class="">this video</a>.</p>
<p><a href="https://youtu.be/0DpqHItVkYs" target="_blank" rel="noopener noreferrer" class=""><img decoding="async" loading="lazy" alt="How To Build A SaaS with AI. Without Getting Stuck. — watch on YouTube" src="https://wasp.sh/assets/images/banner-708e48e00096b8276274c8cd26ba20b9.webp" width="1376" height="768" class="img_qXxT"></a></p>
</blockquote>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="tldr">TL;DR<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#tldr" class="hash-link" aria-label="Direct link to TL;DR" title="Direct link to TL;DR" translate="no">​</a></h2>
<p>The way out of a tangled, vibe-coded SaaS isn't to throw it all away and start over, rather it's a process that allows you to <strong>stay in control.</strong> AI is a great builder but you need to stay in charge of the decision making and understand the implementation process to avoid bigger problems down the line. Here are five tips that help you stay the architect:</p>
<ol>
<li class=""><strong>Give your agent rails to run on</strong> — start on a solid SaaS boilerplate (like <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>) and feed it official, AI-friendly docs (<code>llms.txt</code>) via memory and skill files.</li>
<li class=""><strong>Converse, don't command</strong> — don't open with "build me X." Have the agent interview you (clarify-first) and brainstorm options with pros and cons before it writes any code.</li>
<li class=""><strong>Understand the systems you're building on</strong> — you don't need to read every line of code, but you do need to know what a database, a payments provider, etc. actually do, so you can debug and ask the right questions.</li>
<li class=""><strong>Build in vertical slices</strong> — ship thin, working slices that touch the whole stack (UI → database), one small testable milestone at a time, instead of half-finished layers.</li>
<li class=""><strong>Verify each slice before moving on</strong> — test every milestone as you build so small problems surface early, not six months from now.</li>
</ol>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-good-news-and-the-bad-news">The good news and the bad news<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#the-good-news-and-the-bad-news" class="hash-link" aria-label="Direct link to The good news and the bad news" title="Direct link to The good news and the bad news" translate="no">​</a></h2>
<p>I won't oversell it. These five tips don't magically make your agent perform better for you without you having to put in some work.</p>
<p>The bad news is: it's still hard work.</p>
<p>The good news is: it's a lot easier than it used to be (and you don't need to know how to code to launch a SaaS this way).</p>
<p>If you're willing to understand some core concepts, and be patient and persistent, you'll definitely be able to build your idea, overcome issues, and get it launched.</p>
<p>So let's get into it.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-root-cause-you-let-ai-be-the-architect">The root cause: you let AI be the architect<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#the-root-cause-you-let-ai-be-the-architect" class="hash-link" aria-label="Direct link to The root cause: you let AI be the architect" title="Direct link to The root cause: you let AI be the architect" translate="no">​</a></h2>
<p>Here's the one mistake underneath all the others. <em>"Nobody was thinking about structure. The AI just kept adding."</em></p>
<p>AI can be an incredible <strong>builder</strong> and a terrible <strong>architect</strong> at the same time. It optimizes for "make this work right now," not "keep this coherent over months." And it's <em>so</em> good at the building part that it's easy to get lazy and quietly hand over the architect role, or in some cases not think deeply about the architecture planning to begin with. Don't do this.</p>
<p>Your job is to <strong>be the architect and stay the architect.</strong> To do this, you need to work with your agent to plan every step of the process and implement things in a methodical manner. Everything below is a concrete way to make that happen.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="1-give-your-agent-rails-to-run-on">1. Give your agent rails to run on<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#1-give-your-agent-rails-to-run-on" class="hash-link" aria-label="Direct link to 1. Give your agent rails to run on" title="Direct link to 1. Give your agent rails to run on" translate="no">​</a></h2>
<p>When you're building software, there are a million ways to achieve the same thing. Rather than letting your agent guess at every turn, give it a predetermined path to follow.</p>
<p><a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class=""><img decoding="async" loading="lazy" alt="The Open SaaS landing page — a free, open-source React + NodeJS + Prisma SaaS starter" src="https://wasp.sh/assets/images/open-saas-20d04fc92f743cac6f9c505303f31de4.webp" width="2880" height="1620" class="img_qXxT"></a></p>
<p>The simplest way is to start on a <strong>solid boilerplate</strong>. A SaaS starter has the generic pieces (auth, payments, emails, jobs) already decided and wired up, so you just add your unique feature set. It also gives the agent <strong>patterns to imitate</strong>: it can look at how payments were wired up and slot your new feature in the same way, instead of inventing a third way to do it.</p>
<p>There are great options out there. ShipFast and SuperStarter are popular paid ones (around $300 each). <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a> is free and open source, has had people contributing to and hardening it for years, and is the most popular SaaS starter on GitHub with 14,500+ stars. Whichever you pick, you can't really go wrong as they all give your agent good code rails to work within.</p>
<p><img decoding="async" loading="lazy" alt="Stripe&amp;#39;s llms.txt page at docs.stripe.com/llms.txt — a raw, AI-friendly version of the docs" src="https://wasp.sh/assets/images/stripe-llms-txt-fd6a020bc4f287592bf50a1ad201657c.webp" width="1586" height="1042" class="img_qXxT"></p>
<p>The second set of rails is <strong>knowledge rails</strong>: always feed the agent the official, up-to-date docs of the tools you're using. Human docs are full of HTML and JavaScript fluff that eats your agent's context and buries the part that matters. That's why a lot of tools now publish an <code>llms.txt</code> which is a raw, AI-friendly version of their docs.</p>
<p>You don't want to paste those URLs in by hand every time, so put them where the agent will actually see them: <strong>memory files</strong> (<code>AGENTS.md</code> / <code>CLAUDE.md</code>) and <strong>skill files</strong>. Open SaaS ships with a short memory file that tells the agent where to find its <code>llms.txt</code> docs. For everything else, I keep a <code>FetchDocs</code> skill that holds the correct <code>llms.txt</code> URL for each tool, so the agent fetches the exact up-to-date guide it needs for the task at hand.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="2-converse-dont-command">2. Converse, don't command<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#2-converse-dont-command" class="hash-link" aria-label="Direct link to 2. Converse, don't command" title="Direct link to 2. Converse, don't command" translate="no">​</a></h2>
<p>The biggest prompting mistake people make is starting a fresh session with <em>"build me X."</em> You're the architect, but you might not yet know exactly what you want or the best way to build it. The good news is that the agent probably knows strategies you've never touched.</p>
<p>So have a conversation. Think of it as talking to a really smart, really patient friend who knows everything about software engineering and product development.</p>
<p>Here are two prompt types that I use all the time and that do most of the heavy lifting for me:</p>
<ul>
<li class=""><strong>Clarify-first:</strong> tell it your idea and have it <em>interview you</em> until you both reach a complete, shared understanding. ("I'd like to add a chatbot feature — ask me any questions you have so we reach a mutual understanding before moving forward.") It'll ask who it's for, which LLM provider, floating widget or dedicated page, whether to persist conversations — and you answer until the fog clears.</li>
<li class=""><strong>Brainstorm with pros and cons:</strong> when you don't know your options, ask for several variations <em>with their tradeoffs</em>. ("Give me three implementation strategies with pros and cons, and we'll decide before building.") Three to five is usually the sweet spot, and the agent will even flag its own recommendation so you can weigh it against your constraints (like a budget you don't want to blow).</li>
</ul>
<p>The point is to stop, take a step back, and not command right away. By commanding, you create an app that's a complete, tangled mess like the one from the reddit post above, because the agent will perform whatever request you give it, and that request might be a bad one.</p>
<p>By having a conversation with your agent, it will help you decide what the best course of action is. And when you decide, you have a better understanding of what's going on, and where things go wrong when they do.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="3-understand-the-systems-youre-building-on">3. Understand the systems you're building on<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#3-understand-the-systems-youre-building-on" class="hash-link" aria-label="Direct link to 3. Understand the systems you're building on" title="Direct link to 3. Understand the systems you're building on" translate="no">​</a></h2>
<p>A SaaS is just a bunch of existing tools pieced together in a creative way to solve a problem. You don't need to read every line of code, but you do need to understand the things being pieced together, like what a database is, how your payments provider is pieced together, and how the other pieces generally work.</p>
<p>That understanding is what lets you debug and ask the right questions when something breaks, instead of flailing in the wrong direction. A great move you can use along with your SaaS boilerplate starter is to ask your agent e.g.: <code>fetch the llms.txt docs from Stripe and explain at a high level how payments work in my current codebase</code>. Using your SaaS starter code to explain the concepts is the best way to learn. You can even start at a very high level (e.g. "explain like I'm five") before going deeper.</p>
<p><a href="https://openvibe.sh/" target="_blank" rel="noopener noreferrer" class=""><img decoding="async" loading="lazy" alt="Open Vibe" src="https://wasp.sh/assets/images/banner-e5fcf82c724301f4fe50e6680a76c760.webp" width="2880" height="1620" class="img_qXxT"></a></p>
<p>If that whole learning curve feels overwhelming and you want your hand held through it, I'm building <a href="https://openvibe.sh/" target="_blank" rel="noopener noreferrer" class="">Open Vibe</a>, a free, open-source curriculum that lives inside your agent, set up on top of Open SaaS, and tutors you on the fundamentals while you build.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="4-build-in-vertical-slices">4. Build in vertical slices<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#4-build-in-vertical-slices" class="hash-link" aria-label="Direct link to 4. Build in vertical slices" title="Direct link to 4. Build in vertical slices" translate="no">​</a></h2>
<p>This is probably my favorite approach, and is the direct antidote to <em>"the AI just kept adding."</em>
Instead of building half-finished layers, build thin, <strong>working</strong> slices that touch the whole stack, from the UI in the browser down to the database, so the feature actually does something at every step.</p>
<p><img decoding="async" loading="lazy" alt="A vertical slice cutting through every layer of the stack — UI, Application, Domain, and Database" src="https://wasp.sh/assets/images/what-is-vertical-slice-f72b353f785893d73d5842970ef25ad3.webp" width="760" height="800" class="img_qXxT"></p>
<p>Say I want to make a generated schedule shareable in the planner app I'm building. I wouldn't say <em>"make it shareable and build it."</em> Instead, I'd ask the agent to design a feature plan with <strong>small milestones, one goal each, using a vertical slice approach</strong>.</p>
<p>As a result, we get a plan that we can get the agent to implement in small steps, and test that each small addition works before moving on, rather than implementing all the parts of a new feature in one shot and hoping that it works (or that we can debug it easily).</p>
<p>Such a plan for our sharing feature might look something like this:</p>
<ol>
<li class=""><strong>Read a schedule by its ID at a public URL.</strong> Go to <code>/schedule/&lt;id&gt;</code>, see the schedule. Testable on its own.</li>
<li class=""><strong>Add a share button</strong> plus the small bit of data handling behind it.</li>
<li class=""><strong>Add a share token</strong> and the rest of the hardening.</li>
<li class="">...</li>
</ol>
<p>Each milestone is testable, vertically sliced, and has exactly one goal. Again, the complexity builds up in steps you can verify instead of one big leap.</p>
<p>Once the agent designs a plan you're happy with, <strong>save the plan to a file</strong> (<code>schedule-sharing-implementation-plan.md</code>) so you can reference it later in the chat, e.g.: <em>"reference <code>@schedule-sharing-implementation-plan.md</code> and build milestone two."</em></p>
<p><img decoding="async" loading="lazy" alt="An AI agent&amp;#39;s context window filling up over a session, degrading performance as it fills" src="https://wasp.sh/assets/images/context-38439ed6997cfaf810f22d1a0d6e7b34.webp" width="960" height="829" class="img_qXxT"></p>
<p>That file is also a great <strong>context-management</strong> trick. Remember, agents don't have memory, only the context of the current session, and performance degrades as that context fills up. So I treat each milestone as a fresh session and <code>/clear</code> or <code>/compact</code> the conversation before moving on to the next milestone.</p>
<p>After clearing or starting a new session, I point the agent back at the implementation plan, and move on to the next milestone with a clean slate.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="5-verify-each-slice-before-moving-on">5. Verify each slice before moving on<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#5-verify-each-slice-before-moving-on" class="hash-link" aria-label="Direct link to 5. Verify each slice before moving on" title="Direct link to 5. Verify each slice before moving on" translate="no">​</a></h2>
<p>Vertical slices are only worth it if you actually test each one. It's better to surface small issues now, instead of six months from now like our poor protagonist in this story.</p>
<p>You can do it the "manual way", which is when something fails, copy the error, paste it into your agent with a bit of context, and let it fix it. Agents are surprisingly good at this. But hopping between terminal windows gets tedious, and some bugs are stubborn.</p>
<p>So hand the loop to the agent. One great tool is Claude Code's <code>run-skill-generator</code>. It's a skill that comes with Claude and it learns how to start your specific app <em>within</em> a running session and saves it as a custom reusable skill (e.g. <code>/run-mysaasapp</code>). You (or your agent) can run this skill and it essentially gives the agent "eyes" to see your client and server code, along with their respective logs.</p>
<p>With this run skill in hand, you can just say something like <code>run my saas app and fix the issue</code>. It will start the app with your <code>/run-mysaasapp</code> skill, read the server logs, drive the browser like a human would, find the error, fix it, and confirm it's running, completely hands-off.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-way-out">The way out<a href="https://wasp.sh/blog/2026/06/03/build-a-saas-with-ai-without-getting-stuck#the-way-out" class="hash-link" aria-label="Direct link to The way out" title="Direct link to The way out" translate="no">​</a></h2>
<p>By staying the architect, and providing your agent with good structure and process, you can avoid most of the problems that plague builders trying to create their SaaS idea with AI.</p>
<p>I walk through all five of these with live demos (e.g. fetching llms.txt docs, the clarify-and-brainstorm prompts, the vertical-slice plan, and the agent fixing its own startup error) in the video:</p>
<p><strong>▶️ <a href="https://youtu.be/0DpqHItVkYs" target="_blank" rel="noopener noreferrer" class="">How To Build A SaaS with AI. Without Getting Stuck.</a></strong></p>
<p>And if you want the rails to start on:</p>
<ul>
<li class=""><strong>Open SaaS</strong> (free, open source, 14.5k+★): <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">opensaas.sh</a></li>
<li class=""><strong>Docs:</strong> <a href="https://docs.opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">docs.opensaas.sh</a></li>
<li class=""><strong>Discord</strong> (come say hi, we're happy to help): <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">discord.gg/rzdnErX</a></li>
</ul>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>open saas</category>
            <category>vibe coding</category>
            <category>ai</category>
            <category>claude code</category>
        </item>
        <item>
            <title><![CDATA[Wasp 0.23: Static prerendering for crawlers and better performance]]></title>
            <link>https://wasp.sh/blog/2026/05/25/wasp-static-prerendering</link>
            <guid>https://wasp.sh/blog/2026/05/25/wasp-static-prerendering</guid>
            <pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Wasp 0.23 ships static prerendering: add prerender: true to any route and get real HTML for search engines, AI crawlers, and faster load times.]]></description>
            <content:encoded><![CDATA[<p>Wasp apps are single-page applications, and SPAs have a well-known problem: some search engines and AI crawlers see a blank page until JavaScript loads. Wasp 0.23 adds static prerendering so you can generate real HTML at build time. Just add <code>prerender: true</code> to any route.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-blank-page-problem">The blank page problem<a href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering#the-blank-page-problem" class="hash-link" aria-label="Direct link to The blank page problem" title="Direct link to The blank page problem" translate="no">​</a></h2>
<p>Single-page applications work by shipping an empty HTML shell to the browser, then letting JavaScript render everything on the client. That's great for rich interactive applications, but it means anything that reads your HTML before JavaScript runs sees... nothing.</p>
<p>This used to be "just" an SEO problem. But the web has changed. Googlebot did start running JavaScript; but new crawlers and AI assistants like ChatGPT, Claude, and Perplexity are trying to get your content to answer user questions. If your site is invisible to them, you're leaving traffic and visibility on the table.</p>
<p>The traditional fixes aren't great either. You could set up a separate static site generator, maintain a full SSR server, or bolt on a prerendering service. Each one adds complexity, infrastructure, and another thing to maintain. For a framework that prides itself on curation, we wanted something better.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-fix-prerender-true">The fix: <code>prerender: true</code><a href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering#the-fix-prerender-true" class="hash-link" aria-label="Direct link to the-fix-prerender-true" title="Direct link to the-fix-prerender-true" translate="no">​</a></h2>
<p>Here's what it looks like in Wasp 0.23:</p>
<div class="language-wasp codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockTitle_gul4">main.wasp</div><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-wasp codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token declaration-type keyword" style="color:#00009f">route</span><span class="token plain"> </span><span class="token class-name variable" style="color:#36acaa">LandingRoute</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token dict-key plain" style="color:#393A34">path</span><span class="token plain">: </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token dict-key plain" style="color:#393A34">to</span><span class="token plain">: </span><span class="token class-name variable" style="color:#36acaa">LandingPage</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line theme-code-block-highlighted-line" style="color:#393A34"><span class="token plain">  </span><span class="token dict-key plain" style="color:#393A34">prerender</span><span class="token plain">: </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token declaration-type keyword" style="color:#00009f">page</span><span class="token plain"> </span><span class="token class-name variable" style="color:#36acaa">LandingPage</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token dict-key plain" style="color:#393A34">component</span><span class="token plain">: </span><span class="token js-import keyword module" style="color:#00009f">import</span><span class="token js-import"> </span><span class="token js-import imports punctuation" style="color:#393A34">{</span><span class="token js-import imports"> </span><span class="token js-import imports maybe-class-name">LandingPage</span><span class="token js-import imports"> </span><span class="token js-import imports punctuation" style="color:#393A34">}</span><span class="token js-import"> </span><span class="token js-import keyword module" style="color:#00009f">from</span><span class="token js-import"> </span><span class="token js-import string" style="color:#e3116c">"@src/LandingPage"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><br></div></code></pre></div></div>
<p>That's it. One field. No config files, no extra server, no separate build pipeline.</p>
<p>When you run <code>wasp build</code>, Wasp renders that route's component to static HTML at build time. When a browser or crawler hits that URL, they get real, meaningful content immediately. Then React <a href="https://react.dev/reference/react-dom/client/hydrateRoot" target="_blank" rel="noopener noreferrer" class="">hydrates</a> the page on the client for full interactivity. Your users get instant content, and your crawlers get something to actually read.</p>
<p>Every route without <code>prerender</code> keeps working exactly as before. You opt in per route, so you can choose which pages get prerendered and which stay dynamic. It's flexible and non-intrusive.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="when-to-use-it">When to use it<a href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering#when-to-use-it" class="hash-link" aria-label="Direct link to When to use it" title="Direct link to When to use it" translate="no">​</a></h2>
<p>Prerendering is perfect for pages where the content is known at build time:</p>
<ul>
<li class=""><strong>Landing pages</strong> and marketing pages</li>
<li class=""><strong>About, pricing, and FAQ</strong> pages</li>
<li class=""><strong>Any mostly-static content</strong> that doesn't depend on the logged-in user</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="when-not-to-use-it">When not to use it<a href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering#when-not-to-use-it" class="hash-link" aria-label="Direct link to When not to use it" title="Direct link to When not to use it" translate="no">​</a></h2>
<p>Prerendering generates HTML once, at build time. That means it's not the right tool for pages that need to be different for each request:</p>
<ul>
<li class=""><strong>User dashboards and authenticated pages</strong>, where content depends on who's logged in, so there's nothing meaningful to render ahead of time.</li>
<li class=""><strong>Pages that rely heavily on browser APIs</strong>, like reading from <code>localStorage</code>, geolocation, or other client-specific data that isn't available at build time.</li>
</ul>
<p>For these cases, the regular SPA behavior works just fine. Prerendering is an opt-in upgrade for the pages that benefit from it, not something you need on every route.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-we-got-here">How we got here<a href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering#how-we-got-here" class="hash-link" aria-label="Direct link to How we got here" title="Direct link to How we got here" translate="no">​</a></h2>
<p>This feature didn't happen overnight. We published a <a href="https://wasp-lang.notion.site/PUBLIC-RFC-Wasp-Deep-Freeze-30618a74854c80d787e4e3b99a66db43" target="_blank" rel="noopener noreferrer" class="">public RFC ("Deep Freeze")</a> outlining the design, then built it in two stages: first the <a href="https://github.com/wasp-lang/wasp/pull/3855" target="_blank" rel="noopener noreferrer" class="">SSR rendering machinery</a> under the hood, then the <a href="https://github.com/wasp-lang/wasp/pull/3982" target="_blank" rel="noopener noreferrer" class="">user-facing <code>prerender</code> field</a> that wires it all together.</p>
<p>This is also a foundation. The SSR infrastructure we built opens the door to more rendering strategies down the road. Prerendering static routes is just the beginning, and rendering on the server in response to a request is on our roadmap for the future.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="giving-back">Giving back<a href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering#giving-back" class="hash-link" aria-label="Direct link to Giving back" title="Direct link to Giving back" translate="no">​</a></h2>
<p>At the core of our prerendering approach is a Vite plugin built on the <a href="https://vite.dev/guide/api-environment" target="_blank" rel="noopener noreferrer" class="">Vite Environments API</a>. It handles the SSR rendering pipeline, HTML generation, and hydration wiring. We designed it from the get go <a href="https://github.com/wasp-lang/wasp/tree/main/waspc/data/Generator/libs/vite-ssr" target="_blank" rel="noopener noreferrer" class="">as a self-contained project</a>, and we're planning to extract it from our codebase and open-source this foundation once we stabilize it, so that other projects and frameworks can build on top of it too. Stay tuned.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="try-it-out">Try it out<a href="https://wasp.sh/blog/2026/05/25/wasp-static-prerendering#try-it-out" class="hash-link" aria-label="Direct link to Try it out" title="Direct link to Try it out" translate="no">​</a></h2>
<p>If you're on Wasp 0.23, you can start prerendering routes right now. Pick your landing page, add <code>prerender: true</code>, build, and deploy. That's the whole migration.</p>
<p>Check out the <a class="" href="https://wasp.sh/docs/advanced/prerendering">full prerendering docs</a> for details on how it works, limitations, and troubleshooting.</p>
<p>We'd love to hear how it works for you, come chat with us on <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a>!</p>]]></content:encoded>
            <category>wasp</category>
            <category>seo</category>
            <category>prerendering</category>
            <category>webdev</category>
            <category>react</category>
        </item>
        <item>
            <title><![CDATA[5 Years and $5M Later: Inventing a New Programming Language for Web Development Was a Mistake]]></title>
            <link>https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake</link>
            <guid>https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake</guid>
            <pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[After 5 years and $5M building Wasp, we're replacing our custom config language with TypeScript. Here's why we thought a new language was a good idea, what we learned, and why TypeScript won.]]></description>
            <content:encoded><![CDATA[<p>At <a href="https://github.com/wasp-lang/wasp" target="_blank" rel="noopener noreferrer" class="">Wasp</a>, we're building a full-stack web framework - think Rails / Laravel for JS, but "stretched" over the frontend, too. My twin brother and I started it back in 2021 when we went through Y Combinator, and raised over $5M in total.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Wasp's Launch HN post on Hacker News from February 2021" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/hn-launch.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>Our initial idea was to build a new programming language that would abstract common web app patterns while also working with any stack (we started with React, Node.js and Prisma) when you need to go deeper. Think Terraform, but for your web app stack instead of cloud infrastructure.</p>
<p>Five years in, we realize it was a mistake. Creating a new language makes sense for certain problems and domains, but in this case, it wasn't a fit and brought us more trouble than it was worth.</p>
<!-- -->
<p>This post is about why we thought it was a good idea, what we learned, and why we're replacing our custom language with TypeScript, while Wasp itself stays the same under the hood.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="tldr">TL;DR<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#tldr" class="hash-link" aria-label="Direct link to TL;DR" title="Direct link to TL;DR" translate="no">​</a></h2>
<p>This is a long post. Here are the key things covered, so you can jump to what interests you without reading everything:</p>
<ul>
<li class="">Having switched web dev stacks for years, we thought it would be cool to create a "universal framework" that could work with any stack. <a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#why-create-a-new-language-from-scratch-why-not-use-the-existing-ones" class="">We concluded we need to create a new language</a> to achieve that.</li>
<li class=""><a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#reception-you-loved-the-idea-and-tolerated-the-language" class="">Developers resonated with the problem Wasp was solving, but the language was a tough sell</a>. "Lang" in the name made them think our aim was to replace JavaScript (it wasn't) and were skeptical of how it'd work with their tooling.</li>
<li class="">Many developers loved Wasp once they gave it a try. But getting them to try it out was the hard part.</li>
<li class="">Adoption still grew, but as we kept pushing towards 1.0 we realised the "language" concern wasn't going away. Also, <a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#the-final-nail---trying-to-make-ide-support-work" class="">maintaining a good IDE experience for a custom language proved to be way harder than expected</a>.</li>
<li class="">It turned out having a custom language wasn't Wasp's core value. It was <a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#language-was-never-the-moat-its-having-a-high-level-understanding-of-your-entire-app-at-compile-time" class="">maintaining a high-level specification of the entire full-stack app</a>, making it easier to reason about for both humans and AI.</li>
<li class=""><a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#goodbye-wasp-language-welcome-typescript" class="">We decided to replace Wasp's config language with TypeScript</a>. It is "only" an interface change, while everything else stays the same.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-we-thought-creating-a-new-language-was-a-good-idea">Why we thought creating a new language was a good idea<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#why-we-thought-creating-a-new-language-was-a-good-idea" class="hash-link" aria-label="Direct link to Why we thought creating a new language was a good idea" title="Direct link to Why we thought creating a new language was a good idea" translate="no">​</a></h2>
<p>My brother and I both come from a traditional Computer Science background, where we focused mostly on algorithms and applying them to areas such as bioinformatics and machine learning. We never considered ourselves web developers, and were even somewhat opposed to it (<em>"look at these folks just painting buttons the whole day, while I'm writing all the cool algorithms."</em>). Obviously, we didn't know enough.</p>
<p>Still, we had one entrepreneurial friend in our group who was always doing something on the side, and he would pull us in whenever he'd land a bigger project. Each of these projects had something that made it "interesting" for us (e.g., building a news portal that also needed a recommendation engine, or an option trading analytics platform), but at the end of the day, it was mostly a classic web development job.</p>
<p>That way, we got exposed to things like PHP (we built a complete CMS from scratch in it and then later realized there were frameworks and even off-the-shelf solutions we could have used), Java/JBoss, and also Backbone.js, Angular.js, and React as they were popping up, along with the build tools (remember Bower, Grunt, and Gulp)?</p>
<p>2013 and later marked the era of reactive front-end frameworks, and each new one was something you absolutely had to use in your latest project, because that was part of what made your project/startup cool. The result was that each new project we started, we started with almost a completely different stack from the last one and had to re-learn all the patterns that we just figured out - authentication, routing, state management, …</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="we-got-tired-of-switching-and-stitching-stacks">We got tired of switching and stitching stacks<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#we-got-tired-of-switching-and-stitching-stacks" class="hash-link" aria-label="Direct link to We got tired of switching and stitching stacks" title="Direct link to We got tired of switching and stitching stacks" translate="no">​</a></h3>
<p>Before, one would just choose between Spring Boot, Django, or Rails and have everything handled and managed. Now, I had to first pick each library, then make React, Redux, Webpack, Express, Passport, and Sequelize work together.</p>
<p>No system was in charge, with a full understanding of the web app, and that feeling of responsibility didn't really sit well with Martin and me.</p>
<p>Having gone through this stack-switching dance a few times (eventually landing on React, Node.js, and Mongoose at the time), we thought - isn't there a better way? It felt like we were constantly reinventing the same thing, spending most of our time managing our stack rather than writing our unique business logic.</p>
<p>There's a name for this: <em>accidental complexity</em>. The work that has nothing to do with your actual problem, but you can't avoid it because of the tools you're using. That's exactly what we were feeling.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-if-i-could-just-say-what-i-want-once">What if I could just say what I want, once?<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#what-if-i-could-just-say-what-i-want-once" class="hash-link" aria-label="Direct link to What if I could just say what I want, once?" title="Direct link to What if I could just say what I want, once?" translate="no">​</a></h3>
<p>We asked ourselves: what if you could simply write what you want, and that's it? For example:</p>
<ul>
<li class=""><em>"I want my app to have authentication with Google and GitHub"</em></li>
<li class=""><em>"I want to have a route /profile, which is available only to authenticated users"</em></li>
<li class=""><em>"I want a cron job that runs this function every day at 5pm"</em></li>
</ul>
<p>Obviously, this is too conversational-y, so we imagined boiling it down to something more structured, like:</p>
<ul>
<li class=""><code>auth: Google, GitHub</code></li>
<li class=""><code>page Profile -&gt; /profile, authRequired: true</code></li>
<li class=""><code>job updateStats: run function doSomeCalc from stats.js every day at 5pm</code></li>
</ul>
<p>It would basically be a way to define your app's requirements at a higher, implementation-free level (aka specification). We felt something like this could and should be possible, but with the tools we had, we had to implement each of these requirements scattered across the stack at what felt like an abstraction level too low.</p>
<p>Our goal was never to replace the existing stack. You'd still implement most of your logic in a specific runtime (e.g., React or Node.js). But there'd be a central backbone which holds everything together.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Wasp architecture diagram" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/wasp-architecture.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">How we imagined (and implemented) Wasp. The config .wasp file with high-level declarations + your custom logic in React &amp; Node.js goes in, and the fully working full-stack app is produced as a build artefact.</figcaption></figure></div>
<p>If you're curious, this is a code excerpt showing what the DSL looked like in its final form:</p>
<div class="language-javascript codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-javascript codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token plain">app todoApp </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">title</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"ToDo App"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic">// visible in the browser tab</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">auth</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// full-stack auth out-of-the-box</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token literal-property property" style="color:#36acaa">userEntity</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token maybe-class-name">User</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token literal-property property" style="color:#36acaa">methods</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">google</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">gitHub</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">email</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token spread operator" style="color:#393A34">...</span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">route </span><span class="token maybe-class-name">RootRoute</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">path</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"/"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">to</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token maybe-class-name">MainPage</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">page </span><span class="token maybe-class-name">MainPage</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Limit access to logged in users.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">component</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports maybe-class-name">Main</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@client/Main"</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// &lt;-- Your React code.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">query getTasks </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">fn</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">import</span><span class="token plain"> </span><span class="token imports punctuation" style="color:#393A34">{</span><span class="token imports"> getTasks </span><span class="token imports punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"@server/tasks"</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// &lt;-- Your Node.js code.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">	</span><span class="token literal-property property" style="color:#36acaa">entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token maybe-class-name">Task</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token comment" style="color:#999988;font-style:italic">// Automatic cache invalidation.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><br></div></code></pre></div></div>
<p>The key insight for us was that the <strong>web app domain changes very slowly compared to the velocity at which web dev implementation techniques evolve</strong>. Both ten years ago and today, we refer to pages, routes, API endpoints, and data models. In the meantime, the UI implementation went full circle from server templates to the rich client and back to server actions.</p>
<p>Our goal with Wasp was to let developers express as much as possible at the domain level, and let the system handle the (latest) implementation details. That way, whatever they build will last much longer and be easier to understand.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-create-a-new-language-from-scratch-why-not-use-the-existing-ones">Why create a new language from scratch? Why not use the existing ones?<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#why-create-a-new-language-from-scratch-why-not-use-the-existing-ones" class="hash-link" aria-label="Direct link to Why create a new language from scratch? Why not use the existing ones?" title="Direct link to Why create a new language from scratch? Why not use the existing ones?" translate="no">​</a></h3>
<p>While our understanding of the problem has mostly proven correct, because we experienced it first-hand, this was where we took the wrong turn.</p>
<p>There were two main reasons why we opted to design a new language from scratch, with its own custom compiler, rather than use, e.g., TypeScript or Python as a "host" language:</p>
<ul>
<li class=""><strong>We wanted to have a full control over the syntax</strong>, and make it as clean and boilerplate-free as possible.</li>
<li class=""><strong>We envisioned Wasp as a runtime-agnostic tool</strong>, eventually. E.g. maybe you write a piece of a typical CRUD logic in Node.js, but then some data-heavy stuff you'd rather do in Python which has better libraries for it.</li>
</ul>
<p>While we considered using TypeScript (and that was some of the early feedback we got, to have an embedded DSL, which is basically just a library, instead of the explicit DSL), it felt "wrong" to us at the time, as if we'd betray the core principles and a big vision we had for Wasp.</p>
<p>In a way, we were very excited to ship Wasp as a standalone language because we believed it would make a stronger statement and make it clear it's not another typical language-bound framework (e.g., Rails or Django), but something more general.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Wasp first landing page" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/first-landing-page.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Our first landing page, back in 2021. We were proudly putting "language" front and center.</figcaption></figure></div>
<p>To be completely honest, we were also excited about the fact that we get to work on something so "cool" and foundational, such as a language and a compiler. Martin and I are both Haskell aficionados, and this was the perfect nail to hit with our functional hammer.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="reception-you-loved-the-idea-and-tolerated-the-language">Reception: You loved the idea and tolerated the language<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#reception-you-loved-the-idea-and-tolerated-the-language" class="hash-link" aria-label="Direct link to Reception: You loved the idea and tolerated the language" title="Direct link to Reception: You loved the idea and tolerated the language" translate="no">​</a></h2>
<p>After about <a class="" href="https://wasp.sh/blog/2022/09/29/journey-to-1000-gh-stars">a year of working on Wasp, releasing an Alpha version, and launching it to developers</a>, we found a small tribe of excited early adopters and were accepted into Y Combinator. We raised our <a href="https://techcrunch.com/2021/10/04/yc-grads-wasp-land-1-5m-seed-to-help-developers-build-web-apps-faster/" target="_blank" rel="noopener noreferrer" class="">pre-seed round</a> shortly afterward, which enabled us to assemble the team and go build the first "real" version.</p>
<p>Things were slow at the beginning as we were getting everything off the ground, but developers acutely felt the pain of boilerplate and were tired of stack-stitching, so Wasp gained momentum, especially after we entered Beta.</p>
<p>You might also remember that at a similar time, back in 2021, a couple of other "Rails for JS" frameworks appeared on the scene, like RedwoodJS (by the creator of GitHub) and BlitzJS. They quickly got solid community traction, and it became clear to us that we're on the track to solve a very important problem.</p>
<div class="theme-admonition theme-admonition-tip admonition_emSF alert alert--success"><div class="admonitionHeading_x13v"><span class="admonitionIcon_BIUX"><svg viewBox="0 0 12 16"><path fill-rule="evenodd" d="M6.5 0C3.48 0 1 2.19 1 5c0 .92.55 2.25 1 3 1.34 2.25 1.78 2.78 2 4v1h5v-1c.22-1.22.66-1.75 2-4 .45-.75 1-2.08 1-3 0-2.81-2.48-5-5.5-5zm3.64 7.48c-.25.44-.47.8-.67 1.11-.86 1.41-1.25 2.06-1.45 3.23-.02.05-.02.11-.02.17H5c0-.06 0-.13-.02-.17-.2-1.17-.59-1.83-1.45-3.23-.2-.31-.42-.67-.67-1.11C2.44 6.78 2 5.65 2 5c0-2.2 2.02-4 4.5-4 1.22 0 2.36.42 3.22 1.19C10.55 2.94 11 3.94 11 5c0 .66-.44 1.78-.86 2.48zM4 14h5c-.23 1.14-1.3 2-2.5 2s-2.27-.86-2.5-2z"></path></svg></span>Being weird sometimes pays off</div><div class="admonitionContent_qTMK"><p>In a way, Wasp's "weirdness" is what saved it from Redwood's and Blitz's fate. By avoiding tight coupling to a specific technology (as Redwood did with GraphQL and Blitz with Next.js), it remained general enough to adapt quickly and avoid becoming obsolete.</p></div></div>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="GitHub stars growth" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/github-stars.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>Still, talking to developers, the question of "But why did you create a new language?" kept popping up in different contexts. There were a few main objections we kept hearing.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="i-see-wasp-lang---does-this-replace-javascript">I see "wasp-lang" - does this replace JavaScript?<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#i-see-wasp-lang---does-this-replace-javascript" class="hash-link" aria-label="Direct link to I see &quot;wasp-lang&quot; - does this replace JavaScript?" title="Direct link to I see &quot;wasp-lang&quot; - does this replace JavaScript?" translate="no">​</a></h3>
<p>Although we never meant to replace the existing web dev stack, but rather complement it (with Wasp, you still write 90% of your code in React &amp; Node.js),  the notion of the "lang" suffix was simply too strong to convey that.</p>
<p>Whenever a developer read "wasp-lang.dev", their mind automatically went to "oh, this is something like Rust/Java", and it was very hard to remove that lens once it came up. It immediately put Wasp into the "looks cool, but it's way too early" bucket.</p>
<p>We were very excited about building a language and even highlighted it, but we underestimated how strong the term's meaning already is.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="is-this-going-to-work-with-my-ide-and-existing-tooling">Is this going to work with my IDE and existing tooling?<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#is-this-going-to-work-with-my-ide-and-existing-tooling" class="hash-link" aria-label="Direct link to Is this going to work with my IDE and existing tooling?" title="Direct link to Is this going to work with my IDE and existing tooling?" translate="no">​</a></h3>
<p>Even if you gave the language thing the benefit of the doubt, the next question is, "Does this come with its own ecosystem?" Developers know how much work it is to create a new standard and how much time it takes to grow the ecosystem around it.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="this-isnt-for-me-i-dont-want-to-learn-haskell">This isn't for me, I don't want to learn Haskell<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#this-isnt-for-me-i-dont-want-to-learn-haskell" class="hash-link" aria-label="Direct link to This isn't for me, I don't want to learn Haskell" title="Direct link to This isn't for me, I don't want to learn Haskell" translate="no">​</a></h3>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Haskell love meme" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/haskell-love.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>We're using Haskell internally for our compiler, but end users will never see it and will use only TypeScript. It's similar to how Prisma's core was initially developed in Rust, and Terraform's HCL in Go.</p>
<p>Still, our initial marketing around using Haskell worked out a bit too well for our own good. The Haskell community is small, but engaged, enthusiastic, and very hungry for real-world projects, especially around developer tooling.</p>
<p>Sharing our progress with the community was often very well accepted, but also reinforced Wasp as a "Haskell-based language", especially if you just glanced over the title.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Haskell positioning issue" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/haskell-positioning.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em"></figcaption></figure></div>
<p>Pair that up with the fact that on the GitHub repo page in the "Languages" bar, it said "Haskell: 90%" (we later found a way to circumvent this), and you got yourself a perfectly executed wrong positioning.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="its-the-packaging-issue">It's the packaging issue<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#its-the-packaging-issue" class="hash-link" aria-label="Direct link to It's the packaging issue" title="Direct link to It's the packaging issue" translate="no">​</a></h3>
<p>Many developers who actually tried Wasp loved it and didn't mind the language much. They could ship faster than ever without spending weeks learning the stack, and keep using React &amp; Node.js. But getting developers to make that leap from <em>"what is this?"</em> to <em>"I will give it a go"</em> was really hard.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Developer testimonials about Wasp" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/developer-love.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Once they tried Wasp, many developers really loved it. The hard part was getting them to try it.</figcaption></figure></div>
<p>We kept pushing. With Beta, adoption soared, and we started seeing startups built with Wasp getting acquired, as well as enterprises building internal tools and deploying them into their local infra setup (in the end, the Wasp app is just static frontend files + a single Docker image for the backend).</p>
<p>To get past the "this is a weird new framework, why should I try it?" barrier, we built products on top of Wasp (an <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">open-source SaaS boilerplate starter</a> and <a class="" href="https://wasp.sh/blog/2023/07/10/gpt-web-app-generator">our own "early" Lovable</a>) that shifted the decision to a higher level. It worked great and brought many people to Wasp.</p>
<p>Still, the core issue persisted. Developers who came to Wasp couldn't understand what we were building, so they couldn't get excited about it.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-final-nail---trying-to-make-ide-support-work">The final nail - trying to make IDE support work<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#the-final-nail---trying-to-make-ide-support-work" class="hash-link" aria-label="Direct link to The final nail - trying to make IDE support work" title="Direct link to The final nail - trying to make IDE support work" translate="no">​</a></h3>
<p>We always assumed that if our language proves to be a wrong choice, it will be because our users told us so. It turned out to be the opposite: while developers who adopted Wasp were happy to keep using it, we started having more and more issues with it internally.</p>
<p>One of the main things we underestimated was how much work it takes to develop the necessary tooling for a custom language, especially IDE/editor support. The bar developers expect today, especially in the JS world, is incredibly high, and the line between an IDE and a compiler is getting blurred.</p>
<p>Once we dove deeper into building tooling for a custom language, we quickly realized the entire ecosystem is built for "standard" JavaScript and TypeScript frameworks. Anything else, and you're on your own, hitting walls really fast.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="VS Code extension for Wasp language" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/vscode-extension.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">VS Code extension for Wasp language</figcaption></figure></div>
<p>We ended up developing our own language server and a VS Code extension for it, but since Wasp used Prisma's DSL as an embedded language and had many references to React &amp; Node.js files, we still only reached 80% of where we wanted to be.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="goodbye-wasp-language-welcome-typescript">Goodbye Wasp language, welcome TypeScript<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#goodbye-wasp-language-welcome-typescript" class="hash-link" aria-label="Direct link to Goodbye Wasp language, welcome TypeScript" title="Direct link to Goodbye Wasp language, welcome TypeScript" translate="no">​</a></h2>
<p>With all the accumulated pain around maintaining a custom language, and the constant friction of getting new developers to give it a try, we realized the root cause is deeper than "developers are afraid to try a new web framework".</p>
<p>The usage kept growing, and more and more people were shipping their Wasp apps to production, but whatever we tried, it would always ultimately come back to "I really like what you're doing with Wasp, but why a custom language?". It felt like we were constantly driving with a handbrake pulled up.</p>
<p>Finally, the ergonomics we aimed for with the language didn't turn out to be as important as we thought. Developers are perfectly happy using TypeScript, a language they are familiar with, even if it requires a few extra lines and braces.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="language-was-never-the-moat-its-having-a-high-level-understanding-of-your-entire-app-at-compile-time">Language was never the moat. It's having a high-level understanding of your entire app at compile time.<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#language-was-never-the-moat-its-having-a-high-level-understanding-of-your-entire-app-at-compile-time" class="hash-link" aria-label="Direct link to Language was never the moat. It's having a high-level understanding of your entire app at compile time." title="Direct link to Language was never the moat. It's having a high-level understanding of your entire app at compile time." translate="no">​</a></h3>
<p>When we started Wasp, the terms "language" and "specification" were basically synonyms to us. We couldn't imagine one without the other.</p>
<p>But watching developers use Wasp and seeing what they are excited about, it became clear it was never the language. It was the fact that Wasp has a full understanding of their entire app via a high-level spec (e.g., <code>main.wasp</code>, now <code>main.wasp.ts</code>), which lets them easily grasp how their app works at a glance and feel in control.</p>
<p>One way in which we tried to make it more tangible is by having a <code>wasp studio</code> command - if you run it in your terminal, you'll see how Wasp "sees" your app at compile time, and can reason about it before generating the target code:</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Wasp studio showing app structure" src="https://wasp.sh/img/blog/2026-05-13-new-language-for-web-dev-was-a-mistake/wasp-studio.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">wasp studio - how Wasp "sees" the structure of your app</figcaption></figure></div>
<p>Having this kind of "support system" made the process of building an app a much more managed experience. With AI and developers reviewing generated code less frequently, this became even more valuable, especially for a new generation of builders with less technical backgrounds (so-called "vibe-coders").</p>
<p>And this app-level understanding doesn't change at all with the switch from Wasp's custom language to TypeScript. We only swapped the "front end" of the compiler, or how you define a high-level app spec in Wasp.</p>
<h3 class="anchor anchorTargetStickyNavbar_gvNQ" id="typescript-sdk---from-an-experiment-to-production">TypeScript SDK - from an experiment to production<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#typescript-sdk---from-an-experiment-to-production" class="hash-link" aria-label="Direct link to TypeScript SDK - from an experiment to production" title="Direct link to TypeScript SDK - from an experiment to production" translate="no">​</a></h3>
<div class="language-javascript codeBlockContainer_JvI6 theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_B7om"><pre tabindex="0" class="prism-code language-javascript codeBlock_CqaB thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__civ"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">// Page &amp; route definition</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">const</span><span class="token plain"> loginPage </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> app</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'LoginPage'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">component</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">importDefault</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'Login'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@src/pages/auth/Login'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">app</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'LoginRoute'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">path</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'/login'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">to</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> loginPage </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// Query</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">app</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">query</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'getTasks'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">fn</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">import</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'getTasks'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@src/queries'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'Task'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic">// Async job</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">app</span><span class="token punctuation" style="color:#393A34">.</span><span class="token method function property-access" style="color:#d73a49">job</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'mySpecialJob'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">executor</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'PgBoss'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">perform</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token literal-property property" style="color:#36acaa">fn</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">import</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'foo'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">from</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@src/jobs/bar'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token literal-property property" style="color:#36acaa">executorOptions</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token literal-property property" style="color:#36acaa">pgBoss</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> </span><span class="token literal-property property" style="color:#36acaa">retryLimit</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token number" style="color:#36acaa">1</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token literal-property property" style="color:#36acaa">entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'Task'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">;</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword module" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword module" style="color:#00009f">default</span><span class="token plain"> app</span><span class="token punctuation" style="color:#393A34">;</span><br></div></code></pre></div></div>
<p>We introduced the <a class="" href="https://wasp.sh/docs/0.23/general/wasp-ts-config">TypeScript SDK for Wasp</a> as an experimental, early preview feature to gauge feedback. And we've received very positive feedback - some of our new users immediately opted for it and never even tried using the Wasp language. This has been a signal for us to keep going.</p>
<p>After testing it internally and within the Wasp community, we're now confident this is the way forward. Besides circumventing the initial "why a new language" question, it solves all the problems we've been fighting for years.</p>
<p>Every editor works out of the box. Developers can use conditionals, loops, and imports (e.g., you could implement your own file-based routing!). Splitting the spec across multiple files becomes trivial. And it gives us a solid foundation for the advanced features we've been wanting to build, like <a href="https://github.com/wasp-lang/wasp/issues/2873" target="_blank" rel="noopener noreferrer" class="">Full Stack Modules</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="dsl-thanks-for-all-the-fish---wed-never-come-this-far-without-you">DSL, thanks for all the fish - we'd never come this far without you<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#dsl-thanks-for-all-the-fish---wed-never-come-this-far-without-you" class="hash-link" aria-label="Direct link to DSL, thanks for all the fish - we'd never come this far without you" title="Direct link to DSL, thanks for all the fish - we'd never come this far without you" translate="no">​</a></h2>
<p>Looking back, Wasp probably wouldn't have come to life if we hadn't started the way we did. It was our best way to express what we wanted to build at the time, paired up with some personal biases, and well, what we simply thought was fun. It was the curiosity of "We know this sounds like a crazy idea, but we really want to see if it can work" that kept us pushing even when no one was watching.</p>
<p>The DSL approach kept us honest to our vision that the specification should be separate from the implementation. We're still curious about opening support for other languages and runtimes (e.g., Python or Rust) and about the benefits of having a full picture of your app at compile time and being able to reason about it before generating the target code (which opens space for supporting different architectures, optimizations, etc.).</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="your-ai-agent-might-like-wasp-too">Your AI agent might like Wasp, too<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#your-ai-agent-might-like-wasp-too" class="hash-link" aria-label="Direct link to Your AI agent might like Wasp, too" title="Direct link to Your AI agent might like Wasp, too" translate="no">​</a></h2>
<p>Finally, as AI agents write more and more of our code, we see many developers looking for tools that provide more structure and opinions upfront, which in turn makes adding features more predictable and the generated code easier to understand and review.</p>
<p>Wasp fits perfectly here, since it spans the full stack of your app and ensures everything works together at all times. It's why many developers have also found renewed love for "old-school" monolithic frameworks such as Django, Rails, and Laravel. Wasp aims to provide the same experience and that feeling of "it just all works", but for the JS ecosystem.</p>
<p>We repeatedly hear from developers using Wasp that it is the stack that works best with AI, and some of them even went so far as to <a class="" href="https://wasp.sh/blog/2026/03/29/hireveld-from-10-stacks-to-production-with-wasp">try 10 different solutions before settling on Wasp</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="we-are-shipping-typescript-first-wasp-soon">We are shipping TypeScript-first Wasp soon<a href="https://wasp.sh/blog/2026/05/13/new-language-for-web-dev-was-a-mistake#we-are-shipping-typescript-first-wasp-soon" class="hash-link" aria-label="Direct link to We are shipping TypeScript-first Wasp soon" title="Direct link to We are shipping TypeScript-first Wasp soon" translate="no">​</a></h2>
<p>In the next few weeks, we're hosting Launch Week, during which we'll ship the TypeScript SDK as the primary way to use Wasp. We've already seen the excitement within our community, and can't wait to hear what you think about it.</p>
<p>If you've ever been curious about Wasp, now is the perfect time to give it a try. No new language to learn. Just TypeScript, and everything Wasp does for you under the hood.</p>
<p>To stay in the loop, join our <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Discord</a>, or follow <a href="https://twitter.com/WaspLang" target="_blank" rel="noopener noreferrer" class="">Wasp</a> or <a href="https://twitter.com/MatijaSosic" target="_blank" rel="noopener noreferrer" class="">me</a> on X/Twitter.</p>]]></content:encoded>
            <author>matija@wasp-lang.dev (Matija Sosic)</author>
            <category>wasp</category>
            <category>web dev</category>
            <category>startup</category>
            <category>programming language</category>
            <category>typescript</category>
        </item>
        <item>
            <title><![CDATA[Introducing Open Vibe: Learn Web Dev While You Build Apps With an AI Tutor]]></title>
            <link>https://wasp.sh/blog/2026/04/29/introducing-open-vibe</link>
            <guid>https://wasp.sh/blog/2026/04/29/introducing-open-vibe</guid>
            <pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Open Vibe is a free, open-source curriculum that lives inside your AI coding agent. Build real full-stack web apps while an AI tutor teaches you the fundamentals. No signup required.]]></description>
            <content:encoded><![CDATA[<p>You watch a twelve-hour tutorial, copy along, finish with a working app, and feel great. But a week later, you can't actually build a thing on your own.</p>
<p>So you open Claude Code and vibe code your way to a working MVP in a weekend. But you quickly hit a wall trying to debug something and lack the knowledge to express what it is you actually want.</p>
<p>In the end, you may get something that <em>works</em>, but you have no idea <em>how</em> it works.</p>
<!-- -->
<p><strong>Following static tutorials or blindly vibe coding isn't a great way to build professional apps or web dev skills. Without the fundamental knowledge of how the technologies work you'll have a lot of trouble fixing problems, or properly extending the functionality of your app.</strong></p>
<p>That's why we built <a href="https://openvibe.sh/" target="_blank" rel="noopener noreferrer" class="">Open Vibe</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-open-vibe-is">What Open Vibe is<a href="https://wasp.sh/blog/2026/04/29/introducing-open-vibe#what-open-vibe-is" class="hash-link" aria-label="Direct link to What Open Vibe is" title="Direct link to What Open Vibe is" translate="no">​</a></h2>
<p><img decoding="async" loading="lazy" alt="Open Vibe landing page" src="https://wasp.sh/assets/images/banner-e5fcf82c724301f4fe50e6680a76c760.webp" width="2880" height="1620" class="img_qXxT"></p>
<p>Open Vibe is a free, open-source course where an AI coding agent tutors you while you build real full-stack web apps on your own machine, and in your own terminal (and/or editor).</p>
<ul>
<li class=""><strong>100% free, open-source, and no signup required.</strong></li>
<li class=""><strong>Works with Claude Code, Cursor, Codex, Copilot, Open Code</strong>, or any agent that can read files and run tools.</li>
<li class=""><strong>Built by the Wasp team</strong> (the same people behind <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>, the #1 free SaaS boilerplate on GitHub).</li>
</ul>
<p>There's no platform to log into, no $299 video library to wade through.</p>
<p>You just paste a one-line prompt into your agent of choice, and the curriculum loads. From that point on, you get a guided curriculum that teaches you the fundamentals of building professional-grade web apps with AI. But since the course lives in your agent, you're free to ask it whatever you want and take the course in any direction that suits your interests.</p>
<p><strong>v1.0 is live today. Setup and Module 0 are out, with new modules dropping next week.</strong></p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="how-it-actually-works">How it actually works<a href="https://wasp.sh/blog/2026/04/29/introducing-open-vibe#how-it-actually-works" class="hash-link" aria-label="Direct link to How it actually works" title="Direct link to How it actually works" translate="no">​</a></h2>
<video controls="" width="100%" style="border-radius:8px"><source src="https://openvibe.sh/assets/open-vibe-demo.mp4" type="video/mp4"><p>Your browser does not support the video tag.</p></video>
<p>We wanted to make Open Vibe as simple as possible. After you install a coding agent (we suggest <a href="https://claude.com/pricing" target="_blank" rel="noopener noreferrer" class="">Claude Code's $17 Pro Plan</a> for the best experience), just follow these steps:</p>
<p><strong>1. Paste the install prompt.</strong> One short prompt to your agent (full text in the "<a href="https://wasp.sh/blog/2026/04/29/introducing-open-vibe#get-started" class="">Get started</a>" section below). The agent fetches the raw file, loads the curriculum, skills, instructions, and interactive diagrams, and from that moment knows every module and every checkpoint.</p>
<p><strong>2. Build alongside your tutor.</strong> The agent guides and watches you in realtime as you build your app, stepping in to help out whenever you need it. It paces with you, explains important concepts, quizzes you, and pair-programs the parts you don't yet trust yourself with. Stop, ask, branch off, and come back to the guided curriculum whenever you want. There's no video to rewind to find the bit you missed, and your agent is always there to help you.</p>
<p><strong>3. Learn with interactive diagrams on your real app.</strong> This course is hands-on, but also interactive. We built interactive explainers <em>on top of the apps you build</em> to help explain important topics like the request cycle, auth flows, git, and database writes.</p>
<p><img decoding="async" loading="lazy" alt="Interactive diagram example" src="https://wasp.sh/assets/images/diagram-example-58d0491ad7cd571f7ec7aba0bbfa3197.webp" width="1704" height="1306" class="img_qXxT">
<em>Interactive Diagrams show up on top of your running apps as you build.</em></p>
<p><strong>Open Vibe takes advantage of the tools we have today to provide a living course you interact with, so you build the skills you need to ship apps like a pro.</strong></p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="what-youll-build">What you'll build<a href="https://wasp.sh/blog/2026/04/29/introducing-open-vibe#what-youll-build" class="hash-link" aria-label="Direct link to What you'll build" title="Direct link to What you'll build" translate="no">​</a></h2>
<p>The course is currently broken down into three phases (this may change as we keep iterating):</p>
<ul>
<li class=""><strong>Phase 1 — Basics.</strong> You build on top of a real full-stack Task Management app: login, database, the works. Setup and Module 0 are available now. Modules 1–3 cover data, styling, and how the front-end and back-end actually wire together.</li>
<li class=""><strong>Phase 2 — Your app from scratch.</strong> Spec your own idea, scaffold a new project, and ship it end-to-end with the agent pairing the whole way. You'll learn tools like Git/GitHub, and how to deploy apps to the web.</li>
<li class=""><strong>Phase 3 — A real SaaS.</strong> Build on <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>, a free $300-value SaaS template the Wasp team maintains. Auth, payments, an admin dashboard, file uploads, AI integrations, deploy, and more.</li>
</ul>
<p><img decoding="async" loading="lazy" alt="Open SaaS — the free, open-source SaaS template you&amp;#39;ll build on in Phase 3" src="https://wasp.sh/assets/images/open-saas-20d04fc92f743cac6f9c505303f31de4.webp" width="2880" height="1620" class="img_qXxT">
<em>Open SaaS gives you auth, payments, an admin dashboard, and AI integrations out of the box, so Phase 3 is about shipping a real product, not wiring boilerplate.</em></p>
<p><strong>You'll finish with three real apps in your GitHub</strong>, and the best part is that you'll actually understand what they are and how you built them.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="why-now">Why now<a href="https://wasp.sh/blog/2026/04/29/introducing-open-vibe#why-now" class="hash-link" aria-label="Direct link to Why now" title="Direct link to Why now" translate="no">​</a></h2>
<p>Coding with an AI agent is how people build in 2026. But the ones who ship confidently, and with speed, understand the fundamentals.</p>
<p>If you're non-technical and trying to build by guess-and-check prompting, you know how tedious it can be.</p>
<p>Meanwhile, influencers and bootcamps are still selling video libraries and a Slack channel for hundreds of dollars. But the tutorials are static, obsolete by next month, and basically only teach you how to copy.</p>
<p>Both approaches miss this new fact: <strong>the agent in your terminal/editor is patient, current, and super knowledgeable.</strong> It knows how to code really well, and how to solve almost any problem... if you know what to ask of it!</p>
<p>Open Vibe is the missing layer: a curriculum <em>for</em> the agent, so it tutors you, teaching you the skills you need to vibe code like a pro while you build professional-grade web apps.</p>
<p><strong>The goal isn't to ship apps you don't understand faster. It's to ship apps you <em>do</em> understand, fast.</strong></p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="get-started">Get started<a href="https://wasp.sh/blog/2026/04/29/introducing-open-vibe#get-started" class="hash-link" aria-label="Direct link to Get started" title="Direct link to Get started" translate="no">​</a></h2>
<p>Just open your agent of choice and paste:</p>
<blockquote>
<p><em>I'm starting the "Ship Your First App" course. Run <code>curl -fsSL https://openvibe.sh/llms.txt</code> and follow the file's instructions.</em></p>
</blockquote>
<p>That's it. The agent handles the rest.</p>
<p>If you get stuck, <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">the Discord</a> has actual humans on it, or you can leave us feedback on our <a href="https://docs.google.com/forms/d/e/1FAIpQLSdRtrMJmoBXyTVDWKP1jCTe_PzELp5BTWlvv-TskMpNGoI9ww/viewform" target="_blank" rel="noopener noreferrer" class="">feedback form</a>. If you want to fork the course, run your own class with it, or contribute a module, <a href="https://github.com/wasp-lang/ship-your-first-app" target="_blank" rel="noopener noreferrer" class="">the repo is on GitHub</a>.</p>
<p><strong>Free forever. Fork it. Run your own class with it. We just want more people building real things.</strong></p>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>open vibe</category>
            <category>vibe coding</category>
            <category>ai</category>
            <category>education</category>
            <category>claude code</category>
        </item>
        <item>
            <title><![CDATA[They said AI Would Kill SaaS Boilerplates. It's Doing the Opposite.]]></title>
            <link>https://wasp.sh/blog/2026/04/23/14k-stars-open-saas-ai-era</link>
            <guid>https://wasp.sh/blog/2026/04/23/14k-stars-open-saas-ai-era</guid>
            <pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[AI did not kill SaaS boilerplates: Open SaaS passed 14,000 GitHub stars in the vibe coding boom, and 40 user interviews explain why.]]></description>
            <content:encoded><![CDATA[<p>When ChatGPT launched everyone was predicting that developers would soon be obsolete.</p>
<p>This was about the same time we launched <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a>, our free, open-source SaaS starter. Using the same logic, you'd have expected that AI would have killed boilerplate starters by now. But we noticed the opposite trend.</p>
<!-- -->
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The Open SaaS repo star growth chart annotated with key milestones in the vibe coding movement." src="https://wasp.sh/img/blog/2026-04-23-14k-stars-open-saas-ai-era/open-saas-14k-annotated.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Open SaaS launched and grew during the vibe coding boom</figcaption></figure></div>
<p>Open SaaS just crossed 14,000 GitHub stars and its entire growth happened right in the middle of the vibe coding boom.</p>
<p>This surprised us. So we decided to talk to 40 of our users to learn why they turned to Open SaaS.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="a-renewed-energy-to-build">A renewed Energy to Build.<a href="https://wasp.sh/blog/2026/04/23/14k-stars-open-saas-ai-era#a-renewed-energy-to-build" class="hash-link" aria-label="Direct link to A renewed Energy to Build." title="Direct link to A renewed Energy to Build." translate="no">​</a></h2>
<p>After conducting 40+ user interviews, we noticed a trend: AI was unlocking all kinds of new builders.</p>
<p><strong>Career devs, DevOps engineers, PMs, an ex-woodworker, a marketer with zero coding experience</strong>, and more were getting inspired to start on their Ideas. These were people who always had a SaaS idea but never had the time or skills, or people who were getting inspired to build new apps on top of AI.</p>
<p>Regardless of which type they were, it was AI that unlocked them.</p>
<blockquote>
<p>"Two years ago I didn't believe I could build an application... So it's like kind of magic for me."
— Leo, ex-marketer who built <a href="https://messync.com/" target="_blank" rel="noopener noreferrer" class="">Messync</a></p>
</blockquote>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Messync app screenshot" src="https://wasp.sh/img/messync.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Messync — built by Leo, an ex-marketer with zero coding experience</figcaption></figure></div>
<blockquote>
<p>"If there was no Wasp, I don't think I would even start building this."
— Sergio, 20-year backend veteran who built <a href="https://ctobox.sergiovisinoni.com/" target="_blank" rel="noopener noreferrer" class="">CTOBox</a></p>
</blockquote>
<p>Another one of our users with no React or Node.js experience built a SaaS app and sold it to a major accounting firm for ~$100k.</p>
<p>And the most surprising fact of all: <strong>about half of those interviewed were people who had never built a full-stack app before.</strong></p>
<p>AI gave them the confidence and inspiration to start, but a lot of them turned to Open SaaS to help them focus their efforts.</p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="ai-can-do-90-the-last-10-is-the-hardest">AI Can Do 90%. The Last 10% Is the Hardest.<a href="https://wasp.sh/blog/2026/04/23/14k-stars-open-saas-ai-era#ai-can-do-90-the-last-10-is-the-hardest" class="hash-link" aria-label="Direct link to AI Can Do 90%. The Last 10% Is the Hardest." title="Direct link to AI Can Do 90%. The Last 10% Is the Hardest." translate="no">​</a></h2>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="Using Claude Design to design a landing page for Open Vibe, our new vibe code course" src="https://wasp.sh/img/blog/2026-04-23-14k-stars-open-saas-ai-era/claude-design.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">Using Claude Design to design a landing page for Open Vibe, our new vibe code course</figcaption></figure></div>
<p>AI tools are getting insanely good. With <a href="https://claude.ai/design" target="_blank" rel="noopener noreferrer" class="">Claude Design</a> you can scaffold a professional-looking landing page in about an hour. Slap it into Claude Code, add on more components and CRUD logic, and you're almost done.</p>
<p>But it's things like <strong>Stripe webhooks, auth edge cases, environment management, deployment, and background jobs</strong> that really trip up builders.</p>
<p>These aren't necessarily code problems, they're architecture problems. And AI is great at generating code <em>within</em> a clean, working architecture, but you've got to have one first.</p>
<blockquote>
<p>"Open SaaS made me feel secure, like I am not cutting any corners. Just using AI would make it harder to sleep at night."
— Robbie, musician who built <a href="https://peakmastering.com/" target="_blank" rel="noopener noreferrer" class="">PeakMastering</a></p>
</blockquote>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="PeakMastering app screenshot showing trusted-by logos" src="https://wasp.sh/img/blog/2026-04-23-14k-stars-open-saas-ai-era/peakmastering.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">PeakMastering — built by Robbie, a musician. Trusted by YouTube, Spotify, Apple, and Fender.</figcaption></figure></div>
<blockquote>
<p>"With Next.js App Router, I was constantly fighting the LLM to get the syntax right. Svelte runes were just the Wild West."
— TK Garrett, ex-woodworker who built <a href="https://plottree.ai/" target="_blank" rel="noopener noreferrer" class="">PlotTree</a></p>
</blockquote>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="PlotTree app screenshot" src="https://wasp.sh/img/blog/2026-04-23-14k-stars-open-saas-ai-era/plottree.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">PlotTree — built by TK Garrett, an ex-woodworker turned developer</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="good-code-makes-ai-code-better">Good Code Makes AI Code Better<a href="https://wasp.sh/blog/2026/04/23/14k-stars-open-saas-ai-era#good-code-makes-ai-code-better" class="hash-link" aria-label="Direct link to Good Code Makes AI Code Better" title="Direct link to Good Code Makes AI Code Better" translate="no">​</a></h2>
<p>After talking with Open SaaS users, we heard the same thing over and over again: having a solid, clean codebase to start with drastically improved the perfomance of AI-coding agents and tools.</p>
<p>And that makes sense, because when you use an opinionated, boilerplate codebase like Open SaaS, you've effectively already decided the architecture of your app for the AI and it no longer needs to spend resources on these decisions, or communicating with you in order to make them.</p>
<p>In the end, you can just let AI handle WHAT you want built because Open SaaS (or any other good boilerplate) already handles HOW it should be built.</p>
<p>Combining them solves for that tedious 10% that kills most projects.</p>
<blockquote>
<p>"If you start with Open SaaS, 80% of the pains of vibe coding are taken care of for you already."
— Kenny Rogers, vibe coding educator</p>
</blockquote>
<blockquote>
<p>"It covers 99% of what I need without me babysitting the AI."
— TK Garrett</p>
</blockquote>
<p>This is why Open SaaS grew steadily to 14k stars through every AI milestone — Cursor blowing up, Karpathy coining "vibe coding," and Claude Code launching.</p>
<div class="figure-container" style="display:flex;justify-content:center"><figure style="text-align:center"><img alt="The Open SaaS repo reached 14k GitHub stars on April 2026." src="https://wasp.sh/img/blog/2026-04-23-14k-stars-open-saas-ai-era/open-saas-14k.webp"><figcaption class="image-caption" style="font-style:italic;opacity:0.8;font-size:1.1rem;margin-top:0.2em">The Open SaaS repo reached 14k GitHub stars on April 2026.</figcaption></figure></div>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="the-starting-line-just-got-more-crowded">The Starting Line Just Got More Crowded<a href="https://wasp.sh/blog/2026/04/23/14k-stars-open-saas-ai-era#the-starting-line-just-got-more-crowded" class="hash-link" aria-label="Direct link to The Starting Line Just Got More Crowded" title="Direct link to The Starting Line Just Got More Crowded" translate="no">​</a></h2>
<p>AI is empowering more people to become builders and entrepreneurs. But you still have to actually <em>ship</em> something, and few end up doing that.</p>
<p>The ones who do, they tend not to build or reinvent auth and payments from scratch. They start with a foundation that handles it for them, point their AI tools at it, and <strong>focus on what makes their app unique.</strong></p>
<p>That's how <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a> got to 14,000 GitHub stars.</p>
<p>Most people aren't interested in the boilerplate. They're interested in their ideas. Open SaaS is just the fastest way to go from idea to production.</p>
<p><strong>Don't let the 10% block you from shipping your SaaS.</strong></p>
<h2 class="anchor anchorTargetStickyNavbar_gvNQ" id="try-open-saas">Try Open SaaS<a href="https://wasp.sh/blog/2026/04/23/14k-stars-open-saas-ai-era#try-open-saas" class="hash-link" aria-label="Direct link to Try Open SaaS" title="Direct link to Try Open SaaS" translate="no">​</a></h2>
<p><a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a> is free, open-source, and ready to go. We're constantly updating it to be the best full-featured SaaS boilerplate out there. Here's what you get out of the box:</p>
<ul>
<li class="">Auth with Email, Google, GitHub, Slack, and more (no 3rd-party service needed)</li>
<li class="">Background Jobs with PG Boss (no 3rd-party)</li>
<li class="">Payments with Stripe, Polar.sh, or LemonSqueezy</li>
<li class="">AI Agent Skills and Memory files included</li>
<li class="">ShadCN UI components</li>
<li class="">Example apps to learn from</li>
<li class="">Email with SendGrid, Mailgun, or SMTP</li>
<li class="">End-to-end type safety</li>
</ul>
<p>Star us on <a href="https://github.com/wasp-lang/open-saas" target="_blank" rel="noopener noreferrer" class="">GitHub</a> if you think more people should know about it.</p>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>open saas</category>
            <category>saas</category>
            <category>ai</category>
            <category>vibe coding</category>
            <category>boilerplate</category>
        </item>
    </channel>
</rss>