You're gonna have a had time getting straight answer to that out of the internet. There are now 4 different flavours of the Max plan floating around (Legacy V1, Legacy V2, New plans, and the current credit ones). And on top of that they have peak times. So ~8 scenarios, 24 in total across all feedback for their coding plans.
So when someone tells you they're having a good time on a GLM coding plan it's damn near unusable as a datapoint unless both parties are very clear about what precisely is being discussed
[It's been good for me though...V1 Max off peak...which is basically the best of the 24]
I haven't tried it in a few months, but it went from amazing to unusable really fast.
Currently 20% of my 5 hour limit and 4% of my weekly limit.
Total: 58.46M
GLM-5.3 Cached: 56.91M
GLM-5.3 Uncached: 1.23M
GLM-5.3 Output: 315.18K
Cache hit rate: 97.9%
Full 5-hour Full weekly
Total 292.3M 1.461B
Cached 284.6M 1.423B
Uncached 6.15M 30.75M
Output 1.576M 7.88M
Their own estimates are quite different, probably due to their conservative caching estimates vs what I normally get on longer form work: https://docs.z.ai/devpack/overview#estimated-token-allowance
export ZAI_ANTHROPIC_BASE_URL="https://api.z.ai/api/anthropic"
export ZAI_ANTHROPIC_AUTH_TOKEN="$ZAI_API_KEY"
claude-zai() {
{ local -; set -x; } 2>/dev/null
ANTHROPIC_BASE_URL="$ZAI_ANTHROPIC_BASE_URL" ANTHROPIC_AUTH_TOKEN="$ZAI_ANTHROPIC_AUTH_TOKEN" claude "$@"
}
$ claude-zai
Got reminded now of glm-5v-turbo - that 'v' was for vision - will try assign it role [vision] now in omp. See what happens. :-) Often times it's handy when describing gui problems if the harness/model 'can see'.
I am talking about ZCode, the program, being unable to delegate to other harnesses, like using Claude Code (or even OpenCode) within their UI, so that an Anthropic subscription can be used, because Anthropic don't let you use 3rd party harnesses directly.
It's basically what Paseo: https://paseo.sh/ and Kepler https://www.gitkraken.com/kepler and Zed https://zed.dev/ support doing.
ZCode doesn't seem to work at that level, it instead feels comparable to OpenCode or Codex or Claude Code directly, while also being desktop oriented - you just make API calls directly within it.
It's okay if it's not a goal of theirs, it's just that their UI is really really nice and that would be a cool direction for them to also go in some day.
Paseo had a really nice UI/UX, except sometimes sub-agents within OpenCode sessions would hang. Still, quite pleasant if you want something like the Codex or Claude Code desktop apps, but across various providers.
Kepler integrates with issue trackers like GitHub, you can just create a worktree from a ticket and let it churn, seemed like the second most polished option I tried, but there are obvious gaps - like moving cards manually, some missing UI options etc., which I'd chalk up to either the software just being that new or maybe being a little bit vibe-codey. Either way, one of the more promising options if you want something like Kanban board for agents.
Zed is mostly just a (really nice) text editor with some AI integrations, though it seems like they're also building a more agentic product as well - https://delta.dev/ haven't used that one much and am not in circumstances where I'd collaborate with people that closely, but there was a pretty cool podcast episode with the creators recently and it seems like it works pretty nicely for them! As an editor though, it succeeded where Fleet failed and has mostly replaced Visual Studio Code for me. Nothing against VSC, Zed just does most of the stuff I actually need out of the box.
Some of those tools interacting with Claude Code instead of trying to replace it is more or less the way to get Anthropic's models in other tools while still on a subscription (at least for now). How it works under the hood, go figure, there's ACP https://agentcommunicationprotocol.dev/introduction/welcome but also any number of hacky approaches.
To be fair, you can use Anthropic's models in many other harnesses directly, it's just that it then counts against API billing instead of your subscription, which ends up being way more expensive for individuals, but is kinda what you're supposed to do as a company.
But Neuralwatt significantly raised their rates since then.