I stopped treating AI cost and doomscrolling as separate problems (solo Mac dev notes)

For months I thought I had two unrelated issues: 1) my AI coding costs were all over the place 2) I kept losing hours to feed-driven context switching Turns out it was the same bug. When I got distracted, my prompts got sloppy. Sloppy prompts meant retries. Retries meant token burn. What changed I started tracking spend per session and focus quality together. If a session was expensive, I checked where my attention broke. If I had a doomscrolling day, I expected higher AI spend. If I stayed in one deep block, cost per shipped task dropped. That one framing shift changed everything.