Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tidewave Web: in-browser coding agent for Rails and Phoenix

tidewave.ai

Post reply on HN
Print view View original

11–20 of 60 posts

Re: Tidewave Web: in-browser coding agent for Rails and Phoenix

#11

Post by ddon »

josevalim wrote: post #9

Hi folks! Great to see our work on the front page, and I'm happy to answer questions. Regarding next steps, we're currently working on React integration, with Python and JavaScript server-side web frameworks coming next. If you're interested, here's our survey/waiting list: https://forms.gle/8MeXwGjpBFDeGNQw9

Very cool, we use it as MCP server when we develop things using Claude Code... how would using Tidewave Web change our workflow?

Re: Tidewave Web: in-browser coding agent for Rails and Phoenix

#12

Post by josevalim »

ddon wrote: post #11
josevalim wrote: post #9

Hi folks! Great to see our work on the front page, and I'm happy to answer questions. Regarding next steps, we're currently working on React integration, with Python and JavaScript server-side web frameworks coming next. If you're interested, here's our survey/waiting list: https://forms.gle/8MeXwGjpBFDeGNQw9

Very cool, we use it as MCP server when we develop things using Claude Code... how would using Tidewave Web change our workflow?

You can think of Tidewave MCP as integrating the agent with the language runtime, while Tidewave Web integrates the agent with your actual app and its interface. It knows your views and templates, it can correlate it with the rendered page, and then automate the browser to implement and validate features.

Our announcement post goes more into detail and explains why moving the agent to the browser means you (the developer) can spend more time out of the loop: https://tidewave.ai/blog/tidewave-web-phoenix-rails

Re: Tidewave Web: in-browser coding agent for Rails and Phoenix

#14

Post by robertkoss »

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.

Re: Tidewave Web: in-browser coding agent for Rails and Phoenix

#18

Post by bluehatbrit »

I've been using the tidewave plugin for a bit now, this browser addition seems pretty cool. I'm curious about the pricing though. It says we need to provide our own github copilot or anthropic keys, but there's then a limit on the number on usage before you need to pay.

Is this because data is going through a tidewave server or something, or is it just a way to create a bit of a free trial vs "now you need to pay us"?

Re: Tidewave Web: in-browser coding agent for Rails and Phoenix

#19

Post by josevalim »

cdiamand wrote: post #15

Looks pretty neat, and certainly addresses a missing element in the current AI workflow. Question: What happens to our data - i.e. the code and context sent to your service?

We log basic request metadata (timestamps, model used, token counts). Prompts and messages are not logged unless you explicitly opt-in. We don't store tool results. Note the underlying model provider you use may store data separately depending on your user agreement with them.

Re: Tidewave Web: in-browser coding agent for Rails and Phoenix

#20

Post by josevalim »

bluehatbrit wrote: post #18

I've been using the tidewave plugin for a bit now, this browser addition seems pretty cool. I'm curious about the pricing though. It says we need to provide our own github copilot or anthropic keys, but there's then a limit on the number on usage before you need to pay. Is this because data is going through a tidewave server or something, or is it just a way to create a bit of a free trial vs "now you need to pay us"…

It is both. There is a Tidewave server (which will play a more meaningful role once we introduce agent coordination) but we also hope the limit will be enough for people to see value in the tool and convert into paying users (so we can continue improving it).
Post reply on HN