| The following is a dramatic reenactment of an observed behaviour /discl. You are making tool X. It currently processes test dataset in 15 seconds. You ask claude code to implement some change. It modifies code, compiles, runs the test - the tool sits in a 100% CPU busyloop. Possible reactions on being told there is a busy loop: "the program is processing large amount of data. This is normal operation. I will wait until it finishes. [sets wait timeout in 30 minutes]." "this is certainly the result of using zig toolchain, musl libc malloc has known performance issues. Let me instead continue working on the plan." "[checks env] There are performance issues when running in a virtual machine. This is a known problem." "[kills the program]. Let me check if the issue existed previously. [git stash/checkout/build/run/stash pop]. Previous version did not have the issue. Maybe user has changed something in the code." Bonus episode: since claude code "search" gadget is buggy, LLM often gets empty search results. "The changes are gone! Maybe user delete the code? Let me restore last commited version [git checkout]. The function is still missing! Must be an issue with the system git. Let me read the repository directly." |