Just garbage. Temp files, worktrees that weren't removed after subagents finished, build files... all kinds of things.

thdr a day ago | parent [-]

But that's agent behavior, and not harness responsibility...?

Harnesses should be responsible IMO for managing lifecycle stuff, including worktrees and temp files.

It’s simple, deterministic stuff. At least most of the time.

	▲	TeMPOraL 4 hours ago \| parent [-]
		Hence my question. I assume auto-updates are handled by deterministic code that's far away from anything agents can touch (self-modifying harnesses like Autolith notwithstanding). With the same behavior showing up in multiple high-profile harnesses (Codex, Claude Code), it feels likely there must be some actual reason for doing it this way.