What gets accumulated by JLFG dev tools
- DayTrading Swarm session caches — every paper-trading session writes ~50–500 MB of agent state, decision logs, and reconstructed market data to a session directory. Researchers running daily backtests accumulate 5–50 GB of these per quarter.
- LeadGen Engine bulk exports — bulk enrichment jobs write CSV/JSON outputs to a temp directory. Files persist by default for 30 days; for high-volume API users this is 5–20 GB.
- ProducerLens dev scratch — developers prototyping against the ProducerLens API often dump query results, JSONB warehouse extracts, and exploratory analysis to a scratch directory.
- JLFG SDK caches — the unified JLFG SDK (planned) caches API responses by default to reduce per-call costs during development.
Where these live
- Swarm sessions: `~/.swarm/sessions/
/` - LeadGen exports: `~/.leadgen/exports/`
- ProducerLens scratch: `~/Projects/
/.pl-scratch/` - SDK caches: `~/.cache/jlfg-sdk/`
None of these are visible to generic cleaners because they're application-specific paths buried in the home directory. JLFG Developer Mode adds them to the scan with appropriate retention policies (older than 30 days = candidate for cleanup).
How JLFG Developer Mode is different from generic profiles
The AI Developer profile in DreamCleanr handles Hugging Face, Docker, conda, etc. — the universal categories. JLFG Developer Mode adds the JLFG-specific paths AND understands the lifecycle of each artifact type:
- Swarm sessions older than 30 days that don't have a 'pinned' marker are candidates for cleanup
- LeadGen exports that have already been ingested into the customer's downstream system are safe to remove
- ProducerLens scratch tagged 'experimental' is reclaimable; tagged 'preserve' is not
How to enable it
JLFG Developer Mode is available in DreamCleanr Pro:
- Open DreamCleanr → Preferences → Scan Profiles
- Click 'Add Profile' → select 'JLFG Developer Mode'
- Run a scan — JLFG-specific findings appear in their own category
The profile is bundled free with any annual JLFG subscription. If you have an annual ProducerLens, Lending by JLFG, LeadGen, or Swarm subscription, your DreamCleanr Pro license is included at zero additional cost.
What it doesn't touch
- Active sessions (Swarm sessions running in the last 7 days)
- Production exports (anything in ~/.leadgen/production/)
- Anything tagged with a 'preserve' marker
- Anything inside a git working tree with uncommitted changes
The defaults err conservative. Power users can configure looser retention if they're confident in their workflow.
Frequently asked questions
- Do I need DreamCleanr to use JLFG developer tools?
- No. DreamCleanr is a developer-experience product, not a dependency. JLFG tools work fine without it — DreamCleanr just makes it easier to manage the disk-space side of using them heavily.
- How much space does JLFG Developer Mode typically reclaim?
- For an active JLFG developer (daily Swarm sessions + regular LeadGen API use), 10–40 GB per quarter. The number scales roughly with how heavily you use the tools.
- Is JLFG Developer Mode included with DreamCleanr Pro?
- Yes — it's a built-in profile in Pro. Free with any annual JLFG product subscription, or available standalone with the $29 one-time DreamCleanr Pro purchase.
- Can I customize what JLFG Developer Mode considers stale?
- Yes. The retention thresholds (default 30 days for sessions, 30 days for exports) are configurable per-category in Pro.
- Will JLFG Developer Mode delete production data?
- No. Production paths (~/.leadgen/production/, anything tagged 'preserve', anything inside a git working tree with uncommitted changes) are deliberately excluded. The defaults err conservative.