Oh man, yeah it is. :) I'd likely never have tried to fix a FIXME in a beast of a project like Wine without these newer models/CLI-based tools. Totally wild. And Claude Code/Codex have been working fantastic in SRE/Ops contexts as well. The actual fixing patches don't seem to have many LOC changing. It's mostly the tests I worked through defining/generating that theoretically prove it works which take up the most of that repo. The patches for the flocking fixes are at: https://github.com/livingstaccato/space-wine/blob/main/patches/comctl32-fix-... https://github.com/livingstaccato/space-wine/blob/main/patches/kernelbase-fi... https://github.com/livingstaccato/space-wine/blob/main/patches/kernelbase-fi... https://github.com/livingstaccato/space-wine/blob/main/patches/ntdll-fix-NtL... https://github.com/livingstaccato/space-wine/blob/main/patches/user32-fix-ed... https://github.com/livingstaccato/space-wine/blob/main/patches/wineserver-fi... https://github.com/livingstaccato/space-wine/blob/main/patches/win32u-fix-OE... And I also had it fix a font fixme: https://github.com/livingstaccato/space-wine/blob/main/patches/win32u-fix-OE... Then had it go overboard making tests: https://github.com/livingstaccato/space-wine/blob/main/patches/kernel32-test... https://github.com/livingstaccato/space-wine/tree/main/tests Hopefully the actual patches are high enough quality that it's helpful. Or maybe the testing tools would be a handy addition to the Wine toolchain. --Tim