zai-org / zai-org/feedback

[Technical Report] GLM Coding Pro quota consumption anomaly - empirical analysis shows 5.6x faster burn rate than expected

Open
#240 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Suggestion from a user: peanut_the_fox_terrier (Discord)

My hypothesis is the medium thinking level might not saves tokens in a multi-round implementer-reviewer workflow, in which lower thinking effort could lead to more rounds of reviews. On the other hand, lower thinking level in a single-pass workflow could, or very likely, to save tokens as Agnes suggested.

Unfortunately, it will be a little tricky to reproduce this data locally, since the experiment was done on my personal project, which is not ready to be open-sourced yet.

If someone from your team is interested to reproduce it, the workflow I used is https://github.com/BoTime/custom_toolkit/tree/main/plugins/autopilot/skills/autopilot.

After the plugin is installed:
/autopilot

Full Report Thread:
https://discord.com/channels/1346756824233148527/1534315858921259088

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked custom_toolkit autopilot workflow and the full Discord report thread; the issue provides no repository file or test to inspect. Install the plugin and use /autopilot with a comparable feature description, then compare quota usage across single-pass and multi-round implementer-reviewer workflows. Done means producing reproducible evidence that explains or confirms the reported 5.6x burn rate.

Written by the indexing model from the issue text.

Assessment

Domain
ai, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.