I’ll definitely give it a try too!! Do you use github copilot or Claude Api?
fbutano
preciz
I just subscribed to the paid Tidewave pro plan.
I mainly use aider but there is an accessibility gap there when it comes to changing UI.
When I tried Tidewave out it filled in that gap for me so I completed some tasks that have been open for a while now.
I already pay for GitHub Copilot monthly so the fact that I can use that with Tidewave made it just the right tool for me and the additional cost is actually going to be probably less money then using Claude Code CLI with our Claude API key which I haven’t even started since I started using Tidewave.
So far very good.
3
JoeZMar
I had copilot already and it’s working great with gpt-5 mini. I am really curious about how Claude compares though and have considered dropping $5 to test it out.
0
fbutano
I already have a Claude Code Pro plan and I’m really happy with it for adding new features to my Phoniex apps. Now I’m really curios about Tidewave but paying for using Claude API too is a little uncomfortable…
1
vanderhoop
@josevalim I’m digging tidewave web so far, and I’m curious about a public changelog, as this is likely(?) different from the standard tidewave_phoenix changelog, and there’s nothing mentioned on the https://tidewave.ai/ site. I think this would be a positive thing to add, so that anyone evaluating tidewave web can see the progress transparently.
Additionally, what’s the best way to request and discuss features specifically for the tidewave web side of things?
0
josevalim
Creator of Elixir
If you have copilot you can enable Claude in your copilot settings. 
We will publish updates on the website blog: News - Tidewave . First changelog will be next week.
We will also open up a public roadmap. But the best way to request a feature is to discuss it here or in our discord. We are constantly evaluating user feedback and prioritizing accordingly.
2
Electron
Maybe the Github docs should specify the minimum Elixir version (1.18 i think). Was running on 1.15 and file read was not working.
Otherwise browser integration seems incredible.
Cheers
0
vanderhoop
Feature Request: more granular agent permissions
At the moment, tidewave web either requires manually approving all actions taken by the agent, or bypassing checks altogether via the Setting’s Auto-run mode toggle. I imagine more granular permissions are already on the roadmap, but I wanted to mention the need explicitly so that folks can choose to upvote it to influence its priority, as approving is tedious for innocuous commands, and the ‘Auto-run mode’ is a no-can-do for many folks who are just evaluating the tool or have yet to containerize its execution.
5
josevalim
Creator of Elixir
dimitarvp
Finally also watched the video linked a few weeks ago and, together with this post, I have to say: very well done!
I second @vanderhoop’s concern here: I’d like to try it but I want finer-grained permissions because I am not looking forward to containerizing my dev env (haven’t done it in a while and I am sure it’s not going to go quick or easy).
0