Tidewave for Next.js

Hi everyone. Today I would like to announce Tidewave for Nex.js. So Tidewave is the coding agent for fully stack web app development. So Tidewave in many ways is going to offer a similar experience to both or visero but with two important differences. The first one is that it works with your existing cloud code and open AI codeex subscriptions. But more importantly, Tidewave runs on your machine. So it can use your existing Git repositories. You don't have to push your code elsewhere and it can work with all of your existing tools. Let's check it out. So after you install Tidewave and connect it to your application, you're going to have a screen like this where you have the agent chat and you have your web application running side by side. And what I have here is that I have a brand new Nex.js application. Okay. And I asked cloud code. You can see I'm using cloud code to build a Trello clone and it was able to do that. Right? It's quite straightforward. So, you know, we can rename the tasks. We can move them around. But there are a couple things in tide wave that makes it special, right? So the first one is that because we're running in the browser as the agent is building the feature we can see that it's running tests in the browser to make sure that everything works as expected and if anything goes wrong it goes ahead and automatically fixes it. The second thing is that Tidewave offers what we call the deep web framework integration. So we try to understand everything that your framework is doing. We expose the logs. We expose open telemetry events to the agent. So you can see here that it's reading the logs whenever it wants to check if something went wrong. It can restart the app whenever it makes relevant changes to the files and so on. So another example that I want to show you is for example the the get docs. So whenever the agent needs to read documentation or you want to access documentation, we have a tool for doing exactly that. And the nice part is that it's not going to a separate service to get this information. No, the source code is already available on your machine. So when we ask it to get the documentation, it get the documentation for the exact version in your project that is in disk. And finally, another neat feature I want to show you is the inspector. So we can use the tide wave inspector and at first it looks like the browser inspector but it has one important difference which is that when we mouse over the element we not only know the HTML element but we know the exact react component it comes from. So when you select something and you want to ask the agent to do a change, we pass the HTML information but exactly where that thing came from disk, right? What exactly where it is in the file system. So whenever you ask the agent to do changes, it can do them uh more precisely and faster. Well, this is it for now. I hope you give it a try and see you next time.