My last piece, " · *
Catch the 5-Hour Cap Before You Hit It: token-budget-advisor and Status-Line Integration
- ▸ The problem: you can't tell until you hit the cap
- ▸ Design of token-budget-advisor.sh
- ↳ Dual source: ccusage as primary, cost-log.jsonl as secondary
- ↳ cost-log.jsonl: unless you take "only the latest line," the numbers come out 2–3x too high
- ↳ Thresholds and decision logic
- ↳ Output format of --short mode
- ▸ Status-line integration and dashboard.sh
- ↳ Wiring it into the Cost section of dashboard.sh
- ↳ Auto-updating every 4 hours with launchd
- ↳ Using it as a gate for unattended jobs
- ▸ Pitfalls I hit
- ▸ Summary
SOCIAL SHARE CARD GENERATOR