Post

Andrew 🇵🇸
@src.rip

For my fellow Phoenix Phreaks, a poll: How many of you knew that: A. Tidewave Web is deprecated now in favor of a Desktop client B. There is a new thing called ACP that lets you connect other agents (codex, claude code) directly to Tidewave Desktop and get extra features

0 reposts1 like

Andrew 🇵🇸
@src.rip

extra features meaning, as compared to the MCP. Apparently the ACP protocol lets you leverage the full tidewave desktop feature sets from other agents, whereas the MCP only talks to the *phoenix server* and has a few tool calls you can then do from that

Mario Vellandi
@vellandi.net

shit, cool, now I do. There's just so much going on, plus these damn mega co's are competing on various weekly announcements it's hard keeping up with the actual meaningful

Steffen Deusch
@steffend.me

Why? In the past, we implemented features the agent needs like reading and writing files for each framework. So the Phoenix MCP had a separate endpoint for file system access, the Ruby one, the Next.js one, etc.

Steffen Deusch
@steffend.me

Since that’s not really scalable and because we also wanted to support external agents over ACP like Claude Code, we decided to move all that to one Rust codebase. Otherwise we would not have been able to implement ACP as doing that separately for each framework would be a lot of unnecessary work.

Steffen Deusch
@steffend.me

So Tidewave Web talks to both the App/CLI and the MCP running in your web framework. We deprecated the old /tidewave entrypoint because maintaining it would have required to keep duplicate endpoints around and having different features depending on how you open Tidewave Web.