Nice. I’ve been watching things crop up over the last hour or so and didn’t want to spoil anything by revealing the surpise. But I also don’t use Twitter, so I didn’t see the announcement.

I’ve got to figure out how to get all this stuff working in NeoVim (it’s not in the list of supported editors… yet).

Between this and the launch of Qwen3 yesterday (which seems to work well on powerful CPUs, may not need a huge GPU to use it), I’m pretty excited to see if I can get my hands on some sort of “agentic” coding experience that doesn’t send all my code to some Big Data oligarchs (without having to drop $$$ on a GPU farm).

Great questions!

That particular example had the MCP tell the precise LiveView active on the page, which is not as straight-forward to get from a browser MCP (doable but then you had to write your own JS traversal scripts). This reveals the two important parts about Tidewave: it runs inside your application, so it has access to everything your application does, and it is fine-tuned for your specific web framework.

For example, one of the tools Tidewave offers is access to the database. Surely you can do this with another MCP, but your app already has access to the database, with all of the credentials and configs you would need, and that saves you work. Plus the tool has the ability to query your database using SQL or using your language’s query builder. And this applies to everything: access to background queue? Check, Access to the APIs you talk to? Check. Most of it is powered by the project_eval tool, where we evaluate code within your running application instance.

Another tool that we offer is to get the package documentation. Many people are asking for llms.txt (which I agree are useful) but, when working on a project, all of the packages and their documentations are already available on your machine, with the exact version your application uses. This also applies to getting the location where packages are installed or the file+line of where modules and functions are defined. Those are all things that could be done separately but, because Tidewave is literally running within your web app, we can ask the language runtime/compiler, which will just do a better/faster job.

I got tidewave working with Claude in Emacs today.

I needed this PR Fix endpoint parsing function by peaceful-james · Pull Request #26 · lizqwerscott/mcp.el · GitHub
and this package GitHub - karthink/gptel: A simple LLM client for Emacs

but it is certainly working.

It is relatively straightforward if you just follow the READMEs in both of those repos.

Damn, is this the future of development, just let a LLM chug in background until something works?

full self-driving cars have been a promise for almost 15 years… i guess some stuff just stalls
but I guess I’m not a good measure for those stuff, I still drive a manual transmission car.