CrashLens v1.1.7 — Grouped Reports, Cleaner Output, and Critical Fixes
🚀 CrashLens v1.1.7 is here with a powerful revamp to the --detailed reporting system and key bug fixes! Say goodbye to scattered trace files and hello to clean, grouped issue summaries ready for automation, collaboration, and real-time action.
✨ What's New
🗂️ Grouped Category Reports (NEW!)
The --detailed flag now generates one JSON file per detector type, each containing:
- ✅ A clear summary of affected traces and estimated waste
- 🔎 All relevant issues grouped by category (e.g.,
retry_loop.json) - 💡 Targeted fix suggestions
- 📊 Embedded metadata for scripting/automation
detailed_output/
├── fallback_failure.json
├── retry_loop.json
├── fallback_storm.json
└── overkill_model.json🐛 Bug Fixes
-
Fixed:
TypeError: unsupported operand type(s) for +: 'int' and 'NoneType'- 🔍 Cause: Missing/null cost values in logs
- ✅ Fix: All formatters now safely handle
Nonecosts
🧹 Cleanup & Improvements
- 🧽 Removed the
--include-emptyflag to simplify CLI usage - 📘 Updated README with full CLI reference and pro tips
- 🧪 Improved
--demoguidance and usage examples
📋 Updated CLI Cheatsheet
# 🔍 Scan log file
crashlens scan logs.jsonl
# 🎯 Grouped report by waste type
crashlens scan --detailed
# 💰 Cost summaries
crashlens scan --summary
crashlens scan --summary-only
# 🎨 Output formats
crashlens scan --format json
crashlens scan --format markdown
crashlens scan --format human
# 🧾 Input sources
crashlens scan --stdin
crashlens scan --paste
crashlens scan --demo🔮 Coming Soon
- Visual dashboards for grouped output
- More detectors (e.g., long prompt spam, unused response tokens)
- SDK + GitHub Action support
🧠 Tip
Use the grouped JSONs to create your own dashboards, auto-alerts, or cost heatmaps. One file per category = easy integrations!
📦 Install / Upgrade
pip install --upgrade crashlens
# or
pip install crashlens==1.1.7💬 Feedback
Let us know how the new --detailed feels! We built it to make your GPT cost debugging actionable, team-friendly, and automatable.