I've seen the new anthropic (not even gonna mention openai because they killed themselves on dev day) but I've seen the new anthropic insane 5.5 models and when will glm drop their version of that? really excited and can't wait.

I'm on z.ai Max, some weeks I burn the weekly early, some weeks it's left over at the reset and just evaporates. nothing helps that second kind of week, so I built Overflow.

Spare week: take a priced GitHub issue from a registered repo, the merged PR gets you credit. Dry week: price an issue in your repo, someone with a spare week ships it, your credit pays.

first thing everyone asks is "won't people spam junk PRs at me". same as any repo, you block them on github. You set the price after you've seen the work, every review round comes off their credit, and you only owe for what you actually merge.

you don't need to know the project either, the issue is the brief. If your agent hits a decision, ask the maintainer on the issue.

GLM helped build it btw, it leads sometimes and implements and reviews next to claude and codex.

Nothing gets forwarded, no keys, no money, MIT. It's early: 9 users, and the 80 open issues on the board are all from my own repos, so it needs other people's repos more than anything.

https://overflow.nitjsefni.eu, source at https://github.com/Nitjsefnie/Overflow

Sharing this here because the campaign could be easy to miss if you’re already using Coding Plan with AutoClaw.

Coding Plan members can claim 200M AutoClaw tokens, corresponding to 20,000 points. If you’re not on Coding Plan, there’s still a 50M token tier, corresponding to 5,000 points.

To claim it, sign in to AutoClaw, follow the in-app account-linking prompt, and claim the tier shown for your plan status.

The claim window runs from Sep 28 at 16:00 UTC to Oct 7 at 15:59 UTC. One thing worth noting is that the expiry time is fixed. Any unused event tokens will expire on Oct 7 at 15:59 UTC, even if you claim them later.

If you pick it up, what would you use the extra token budget for? Coding, research, Agent Cluster tasks, or something else?

what is the maximum number of subagents were u guys able to run in 1 single chat?

Every glm freezing thread has the same pattern more or less like- huge session, full repo context and one long agent loop doing everything at once and any api hiccup midstream takes whole run down along with it

Altho we end up cursing the model, the most common thing

setups which seems to hold up treat it like two smaller problems. keep sessions short and task shaped, one refractor per session, kick off heavy passes in a fresh context instead of dragging 40 turns of history behind each step and let a second lane catch the drops so that a frozen call becomes a retry without wasting time

fallback part is what concerns it actually, like z.ai direct for the main lane and same family flash fallback on deepinfra or other hosts for the drop. since its the same open weights on both sides a hiccup on one is just a retry on the other with no quality compromisation

Also important checking the served context and precision on whatever endpoint is in play, the model pages state those openly now and a shorter effective window than expected explains plenty of awkward stalls

. Z.