[jonator]

I can attest to everything. Using Tidewave MCP to give your agent access to the runtime via REPL is a superpower, especially with Elixir being functional. It's able to proactively debug and get runtime feedback on your modular code as it's being written. It can also access the DB via your ORM Ecto modules. It's a perfect fit and incredibly productive workflow.

[ogig]

Some MCP's do give the models superpowers. Adding playwright MCP changed my CC from mediocre frontend skills, to really really good. Also, it gives CC a way to check what it's done, and many times correct obvious errors before coming back at you. Big leap.

[ch4s3]

Which models are you using? I’ve had mixed luck with GPT 5.2.

[barkerja]

Opus 4.5 with Elixir has been remarkably good for me. I've been writing Elixir in production since ~2018 and it continues to amaze me at the quality of code it produces.

I've been tweaking my skills to avoid nested cases, better use of with/do to control flow, good contexts, etc.

[ch4s3]

I'll have to check it out. I've found GPT to be adequate at producing running code that I can improve either by hand, or very specific prompting.

What does your workflow look like?

[barkerja]

I don't have a fancy workflow per se, but I have started leaning into git workspaces more which has really been a boon with Elixir (especially in large projects where compile times can be in the many tens of seconds).

[jonator]

I've been using Opus 4.5 via Claude Code

[manmal]

Is an MCP really required for this?

[dnautics]

sure, you could in principle write a script that calls into the running vm, executes code, and just make this a text-based command attached to a script + skill.

6 of one one-half dozen of the other.

At the point where you have a phoenix project in dev, you're already exposing an http endpoint, so the infra to not have to do a full on "attach to the VM and do RPCs" is nice, and you just pull tidewave in as a single dependency, instead of downloading a bunch of scripts, etc.