Existing setup. I'm already used to Claude Code I guess. I actually spent time and tokens customizing and fixing it. Have a patcher utility that modifies the bi

Existing setup. I'm already used to Claude Code I guess. I actually spent time and tokens customizing and fixing it. Have a patcher utility that modifies the binary in order to disable telemetry and remove performance reducing language in the system prompts. Every update I spend some Claude tokens dissecting the newest executable and integrating it with my patcher. The monthly subscription is also a major hurdle for me. The "high end frontier models for low prices" aspect is a major reason. I think I'm getting a lot of value from my subscription, given that the API prices are like a hundred times higher. However, there's also a psychological factor here. These subscriptions are like the gachas of the software world. I got "addicted" to them. I developed workflows around achieving 100% weekly usage. Sometimes Anthropic randomly resets weekly usage and I scramble to get the most out of it. I'll point Claude at things and then just have it run hundreds of code review agents. I ran out of projects to do this on and started doing it to my favorite open source projects instead, looking for things to contribute. I think with usage-based pricing I wouldn't use LLMs quite so freely. It'd probably cure my "addiction" too, but the problem is I'm not sure whether that's a good thing, since this "addiction" has been a somewhat positive force in my life. It's driven me to start new projects and also make major progress on existing ones. It brought me out of a slump. I'm a little afraid of moving away from Claude and not being as driven as I was before.