All of the harnesses I've used are terrible at cleaning up after themselves. They leave all kind of clutter behind, to the point where on my dev VM, I now have an LLM run once a day to just look through the disk and delete everything that looks like it's leftover garbage.

It's like fighting fire by employing an arsonist.

Running an LLM to delete files seems like overkill to me. Couldn't a cron job do the same thing? Or is the clutter just put into random places, which, if true, seems like bad software, which then leads me to consider the output of LLMs in general, which then leads me to wonder why are we doing this?

But, I'm just wondering.

Installed "clor.com" and it got into a loop of downloading its docker image from ghcr them throwing it away immediately because it was supposedly out of date (iirc). 65mbps continuous transfers for a week until I looked at my network traffic and saw 500gb of rx per day.

I just erased 20GB of Cursor’s cruft.

Is that cruft or past conversation history / subagent history and observability logs?

Over eager use of /tmp is the worst. That’s RAM, my boy! Precious gold.

Harness problem, or model problem?

> I now have an LLM run once a day to just look through the disk and delete everything that looks like it's leftover garbage

...are you sure it wouldn't consider your personal files garbage?