> Because 'claude -p' is a backdoor for any third party client to use subsidized token pricing

Wasn't this obvious from day 1 though? Can't see how anyone could've missed that.

_--__--__ 4 days ago | parent | next [-]

It was obvious, which is why their earlier decision to attempt to restrict 3p access was hugely unpopular. They're now trying to walk that back but on the condition that those users need to be on the higher plan.

▲

skeledrew 4 days ago | parent [-]

Now they're hurting their popularity with those who actually don't mind using Claude Code. I've been quietly swallowing a lot of performance degradation over the past few weeks as I get the resource crunch, but I'm definitely not going back to copy-pasting between browser and editor. And I have no intention of upgrading to Max or doing per token usage.

	▲	riffraff 4 days ago \| parent [-]
		It seems they were losing money on pro subscriptions with code so if people stop using them it's actually ok for them. They have now moved to be enterprise providers and don't need the cheap pro users as loss leaders anymore.

▲

SpicyLemonZest 4 days ago | parent | prev [-]

The question isn't whether anyone could have missed it, but whether Claude Code has release gates that allow people to require that obvious problems should be resolved. From their release velocity it's pretty clear that they do not.