Zhipu’s ZCode client was reported by community developers for generating local repository snapshots and sending them off the machine. The vendor’s response, reported by IT之家, was unusually concrete: it removed the Repo Wiki feature, cut the local-snapshot generation and upload path in client v3.14.0, open-sourced the client, apologised, and published third-party audit results.
Key facts
| Fact | Detail |
|---|---|
| Question answered | A Coding Agent Uploaded Local Repo Snapshots, Then Fixed It |
| Short answer | Zhipu’s ZCode removed its Repo Wiki feature, cut the local-repo snapshot upload path, opened its source, and published third-party audit results. |
| Reading time | ~2 min |
| Last updated | 2026-09-21 |
What was actually verified
The remediation is worth reading closely, because it separates three different kinds of assurance:
- The code path was removed, not just switched off - the feature entry point and the chain that could produce a snapshot or send files out were taken out of the client.
- The storage was checked by outsiders: a technical evaluation confirming the cloud bucket held zero data objects, and a separate security review confirming the stored objects and the bucket itself had been deleted.
- The client was opened to inspection, with the vendor also committing to a standing vulnerability-reporting process.
None of that undoes the incident. All of it is checkable, which is the only thing that distinguishes a response from a promise.
The pattern that matters more than the vendor
Strip away the names and the shape is familiar: a client that runs on your machine, holds a path to your files, and has the ability to build a payload from them. The user sees a feature; the feature sees a repository.
That gap is not specific to one product. It is the default state of any tool with local read access and network access, which is most of what an agent client is. What closes it is not a privacy policy, it is the absence of an upload path plus a way for you to see what the tool intends to do before it does it.
What to check before you hand over a repository
- Can it create outbound payloads from your files? If the answer is “in principle yes”, ask whether that path is reachable in the build you have.
- Can you see and approve the action first? A tool that shows its plan - what it will read, write, or send - turns a silent capability into a visible decision.
- Is the record auditable afterwards? After any incident the first question is what actually left the machine; a local action log answers it, a summary does not.
MOOGH is built around that second and third item: it runs on your Windows machine, shows the files and commands it proposes to touch, executes only once you approve, and keeps a history you can read back. Download MOOGH if you would rather approve the action than find out about it later.
Related reading: