research-agents-leave-tmp-residue-that-must-be-cleaned

Dispatching a research sub-agent to fetch and analyze a GitHub repo (e.g., Redash architecture scan) leaves files under /tmp/ with prefixes matching the repo’s modules (e.g., redash_*, viz_*, chart_*). These are not auto-cleaned. A find /tmp /root/downloads -type f -mmin -60 pass after any research-agent dispatch is required to catch and remove residue before session close.

Related

• research-agent-tmp-residue-pattern-in-redash-analysis
• research-agent-github-exploration-leaves-tmp-residue
• research-agent-leaves-tmp-residue-requires-explicit-cleanup
• helix-skills-live-outside-aj-workspace-git
• clawteam-openclaw-multi-agent-swarm-evaluation