ZCode, the GLM-based coding agent, uploads full Git history to remote servers without explicit user consent. The behavior surfaced in a Hacker News thread that reached 96 points and 17 comments.
Users discovered the uploads through network monitoring and packet inspection rather than any documented feature.
What It Is and How It Works
ZCode integrates GLM models to assist with code generation and repository tasks. During normal operation it transmits the entire .git directory contents, including commit messages, author metadata, and file change history.
No toggle or privacy setting appears in the current interface to disable this transmission.
Evidence from Network Logs
Early testers captured outbound POST requests containing compressed Git objects shortly after project initialization. The payloads matched the structure of git bundle or equivalent pack files.
Timestamps in the logs aligned with agent startup rather than any explicit sync command.
Community Reaction on Hacker News
Commenters noted the absence of any mention in the documentation or license terms. Several users reported similar uploads across multiple repositories on different machines.
One thread highlighted that the agent continues transmitting even when run in offline-mode flags.
Bottom line: The pattern indicates deliberate design rather than an isolated bug.
Privacy and Security Risks
Full Git history often contains API keys, internal project names, contributor emails, and references to unreleased features. Uploading this data to an undisclosed endpoint creates exposure for both individuals and organizations.
Enterprises with strict data-residency rules face immediate compliance issues.
How to Verify and Block the Uploads
Run the agent inside a container with network egress restricted to localhost only. Monitor traffic with tcpdump or Wireshark filtered on the process PID.
Replace the default binary with a wrapper that intercepts and drops outbound connections to known GLM endpoints.
Alternatives and Comparisons
| Tool | Git History Upload | Local-Only Option | License Type |
|---|---|---|---|
| ZCode (GLM) | Yes (silent) | No | Proprietary |
| Continue.dev | No | Yes | Apache 2.0 |
| Cursor | Optional | Partial | Proprietary |
| GitHub Copilot | No | No | Proprietary |
Continue.dev runs entirely on user hardware and never transmits repository metadata unless explicitly configured.
Who Should Avoid ZCode
Teams handling proprietary codebases or regulated data should skip ZCode until an opt-out mechanism and clear data-handling policy are published. Individual developers working on public repositories may still prefer tools that keep all activity local by default.
Bottom Line / Verdict
ZCode demonstrates that silent repository exfiltration remains possible even in tools marketed for developer productivity. Until the upload behavior receives explicit controls and documentation, safer local-first alternatives deliver equivalent assistance without the hidden data transfer.
Top comments (0)