21–30 of 60 posts
I would love to have a React Copilot that has access to the console, network logs, the actual html elements, computed styling etc. + my code. This would be such a game-changer. I am also convinced that monorepos will become the de facto standard, since it is way easier for LLMs to navigate / implement features across the whole stack.
Hey Jose, How does this differ from Phoenix.new?
Phoenix.new is about remote agents, while Tidewave integrates with your app running on your machine!
Earlier quoted context omitted.
Phoenix.new is about remote agents, while Tidewave integrates with your app running on your machine!
Why does it forward to https://tidewave.ai/ when I type http://localhost:4000/tidewave ?
Hey Jose, How does this differ from Phoenix.new?
Phoenix.new is about remote agents, while Tidewave integrates with your app running on your machine!
I would love to have a React Copilot that has access to the console, network logs, the actual html elements, computed styling etc. + my code. This would be such a game-changer. I am also convinced that monorepos will become the de facto standard, since it is way easier for LLMs to navigate / implement features across the whole stack.
We are working on React integration, first within Rails and Phoenix, but then also standalone. How are you serving/running your React apps in development?
> "This Rails MCP Server implements the MCP specification to give AI models access to Rails projects for code analysis, exploration, and assistance."
And again I don't get the value. I can see some slight benefits to having a tight browser integration but I don't think that's worth leaving the IDE / CLI tools and the workflows they bring. You can also use Playwright MCP or just screenshot easily for more context. Claude Code can now run your server in the background and view logs as well. In a perfect world where LLM's can one shot whole features, maybe. But I can't let Claude Code go 10 minutes without it introducing a bad pattern and having to stop it. Reducing that visibility even further with this does not seem like a good combo.
I'm not wanting to tear down others projects either, just giving my perspective. I should try it to see how it does in the wild but the Copilot license or Anthropic API key requirement also deters me as well as having to have a project specific dependency.
As someone who builds AI products and having used agentic coding tools since they came out (often with Rails projects), I don't get this. There was a similar project called Rails MCP Server which said: > "This Rails MCP Server implements the MCP specification to give AI models access to Rails projects for code analysis, exploration, and assistance." And again I don't get the value. I can see some slight benefits to h…
First, Playwright MCP is really not enough. For example, imagine you are building a project management software and you are working on a feature for transferring tasks between projects. Testing this feature requires at least a user who is admin and at least two projects. When it is time for Playwright to test this feature, you need to automate the account creation, then it has to set up two projects, add the task, etc, and it often gets stuck.
When you are using Tidewave, you naturally do this setup as part of your development, which Tidewave has direct access to during tests. So it just interacts with the same page. Furthermore, if you see any bugs or places you could improve, you can't really tell Playwright or regular coding agent to fix them, you have to translate what you want. With Tidewave you just point and click and it works across browsers. I talk more about this in the announcement post: https://tidewave.ai/blog/tidewave-web-phoenix-rails
Other than that, I am really curious about the handoff between Tidewave and the editor that you mentioned. At some point, you will need the editor indeed, but how to best do this transaction? Should you be able to review and do tiny tweaks within Tidewave first? Regardless, moving the agent to the browser for web applications bring enough benefits to justify going one lever higher. :)