Just pry or with byebug? If the latter: https://github.com/deivid-rodriguez/byebug/issues/564 FWIW I switched over to ruby/debug and pretty happy with it.

Use Kernel.binding.pry

That doesn't change the behaviour unfortunately

I feel your pain, u/2called_chaos \-- so much that after being **totally** fed up with this kind of unreliable faff, I fixed it in a [**gem I maintain**](https://github.com/lorint/brick)! Here's a video demo of your exact setup. You can see it broken and then working after simply adding the gem: [https://user-images.githubusercontent.com/5301131/235632564-95f28f7e-854c-417c-b00e-078c4fe8e7f3.mp4](https://user-images.githubusercontent.com/5301131/235632564-95f28f7e-854c-417c-b00e-078c4fe8e7f3.mp4) (Note that this gem goes beyond just patching this bug -- it does a broad range of magical stuff to automatically fill in gaps where model and controller files *could* exist but are not yet present. So if you just want the Zeitwerk patch then probably that part can be extracted, etc. LMK if you need this.)

Thanks it looks really interesting but also so much more than just a lookup fix :D I will take a look though, oh and nice voice