Claude Code burning 30k context tokens on messy stack traces is driving me crazy how are power-users dealing with terminal error loops?

Wait 5 sec.

watching claude code burn half my context window just looping over raw stderr and giant stack traces is getting painful been messing around with a tiny local cli script im calling dot for now that sits between the terminal and the agent. basically catches the crash, strips out the build noise locally, and just passes the actual error line to claude instead of dumping the whole trace for people running heavy sessions on max or pro, how are you guys handling this? do you strip down the default system prompt and build your own local wrappers around it, or just eat the token hit? also curious how you stop it from trying a bunch of random fixes when the issue is literally just a broken env var btw i want to stress test this on a bigger repo before i drop money on a max sub. if anyone on max has a spare guest pass sitting in their settings, lmk in dms. youll get the referral credit when i upgrade anyway   submitted by   /u/ApprehensiveRise2336 [link]   [comments]