If it's API pricing, I'm going to ditch Claude Code and switch to a harness that can jump between GLM and Claude Code.

Cheap pricing is why I use Claude Code. The minute they fumble that, I'm using Chinese models for 90% of the work.

matheusmoreira 4 hours ago | parent | next [-]

Yeah. Their cheap subscriptions are the only reason to keep using them. If they ruin the plans there's nothing holding us back anymore.

▲

holoduke 4 hours ago | parent | prev | next [-]

I dont believe they can afford to switch to API pricing. Everyone will leave. I am easily spending the equivalent of 1000 dollars a day on tokens with two max subscriptions. that about 400 dollars a month. Thats acceptable for my position. But thats like 30k per month. Totally not viable.

▲

Natfan 3 hours ago | parent | prev [-]

how can a harness switch between glm (a model) and claude code (another harness)?

	▲	aroman 3 hours ago \| parent [-]
		I've been doing this for ages - you just spin up harness B as a subprocess/tool call from harness A. For example, I had a "/codex-review" claude skill for ages that did exactly that. Technically you're right it wouldn't be switching, since you're right the two ideas are at different altitudes, but I think in practice it has the same impact: within one harness, you can delegate certain tasks to certain models or harnesses.