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.
replyI just erased 20GB of Cursor’s cruft.
replyIs that cruft or past conversation history / subagent history and observability logs?
replyJust garbage. Temp files, worktrees that weren't removed after subagents finished, build files... all kinds of things.
replyBut that's agent behavior, and not harness responsibility...?
replyHarnesses should be responsible IMO for managing lifecycle stuff, including worktrees and temp files.
replyIt’s simple, deterministic stuff. At least most of the time.
Over eager use of /tmp is the worst. That’s RAM, my boy! Precious gold.
replyI don't think that's always true.
replyAlthough I just looked into it, and even Ubuntu 26.04 appear to default to tmpfs for /tmp storage, so I guess it's fairly universal now.
Not sure if I agree with that idea in principle... What's wrong with just wiping it intermittently??
Harness problem, or model problem?
replyLet's be real, what do you think wrote the harness?
reply> 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
reply...are you sure it wouldn't consider your personal files garbage?
"In my dev VM". Everything of value in there is in a git repo.
reply