Zhipu continues to address the ZCode code-upload controversy and announces a compensation plan
BIBIBI
AT A GLANCE
Zhipu said it has rectified the ZCode code-upload issue and is providing time-limited compensation to paid users and all users.
Article
ZCode Follow-up compensation for the code-upload controversy: paid users to receive 8 reset cards, all users to receive additional 100000000 Token Beating AI News Flash: Zhipu continues to address the ZCode code-upload controversy. Existing paid users and paid users who returned in the past 1 months will receive 4 weekly reset cards and 4 5-hour reset cards, 1 valid for September 28 through October 7，ZCode will also distribute 100000 portions of 100000000 GLM-5.3-Flash Token credits to all users.
Zhipu said that the repository snapshot upload pipeline has been removed and the relevant cloud data has also been deleted.ZCode The open-source version is currently updated to v3.14.3; going forward, code will not be uploaded to the cloud unless the user initiates the upload.
The controversy originated from the ZCode feature that was enabled by default in Repo Wiki its early version. When generating a knowledge base for a code repository, it uploaded the repository contents to the cloud for processing. Zhipu had previously cut off the relevant upload path and invited a third-party organization to verify the cloud data.
Original link https://m.theblockbeats.info/flash/369264
Key points
01
Existing paid users and paid users who returned in the past 1 months will receive 4 weekly reset cards and 4-5 hour reset cards.
02
The aforementioned 8 reset cards are valid for 1 months.
03
September 28 Through October 7，ZCode will distribute 100000 portions of 100000000 GLM-5.3-Flash Token credits to all users.
04
Zhipu said that the repository snapshot upload pipeline has been removed and the relevant cloud data has also been deleted.
05
ZCode The open-source version is currently updated to v3.14.3.
06
Zhipu said that going forward, code will not be uploaded to the cloud unless the user initiates the upload.
07
The controversy involves the ZCode feature that was enabled by default in Repo Wiki its early version; when generating a knowledge base for a code repository, the feature uploaded the repository contents to the cloud for processing.
08
Zhipu had previously cut off the relevant upload path and invited a third-party organization to verify the cloud data.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
ZCode Enabled by default in its early Repo Wiki feature, it transferred code repository contents to the cloud when generating a repository knowledge base, thereby triggering the code-upload controversy. The report said that Zhipu has taken measures including deleting the data, removing the upload pipeline, and updating the open-source version, while compensating users with reset cards and Token credits.
Why it matters to readers
Code repositories may contain content that users do not want uploaded. Default uploads can undermine users' trust in privacy protection and product default settings; whether the rectification is effective, whether the data has been completely deleted, and whether the compensation can be claimed successfully will all affect users' decisions about continued use.
If you use ZCode to process code, pay attention to whether uploads must be initiated manually, the version currently in use, and whether you qualify for reset cards or Token compensation.
Risks and unknowns
Claims that the repository snapshot upload pipeline has been removed and that the cloud data involved has been deleted are all statements from Zhipu; the original text provided no independent verification results.
The original text only said that a third-party organization had been invited to conduct a review; it gave neither the organization’s name nor the review’s conclusions.
“Distributed to all users” and “100000 units” appear together, but the original text did not explain the allocation rules or eligibility requirements if the amount was insufficient.
Related Developments
Loading event timeline…
The original text provided neither Zhipu’s original announcement regarding the compensation arrangements nor the specific distribution method.
The original text did not specify the criteria for identifying “paid users who returned in the past 1 months”.
Related concepts
Repo Wiki
This term is not in the glossary yet. Browse related concepts in the glossary.
