I am a GPU programmer (on the compute side), and the biggest challenge is lack of tooling.

For host-side code the agent can throw in a bunch of logging statements and usually printf its way to success. For device-side code there isn't a good way to output debugging info into a textual format understandable by the agent. Graphical trace viewers are great for humans, not so great for AI right now.

On the other hand, Cline's harness can interact with my website and click on stuff until the bugs are gone.

▲

akiselev 4 hours ago | parent [-]

(Shamless plug) I've been using my debugger-cli [1] to enable agents to debug code using debuggers that support the Debug Adaptor Protocol. It looks like cuda-gdb supports DAP so I'd love to add support. I just need help from someone who can test it adequately (kernels/warps/etc don't quite translate to a generic DAP client implementation).

[1] https://github.com/akiselev/debugger-cli

	▲	rescbr 2 hours ago \| parent [-]
		This is great. I hate LLMs fiddling around with logging calls to get some debugging capability. Now they can be promoted from junior coders into mid-level coders :)