Zhipu Open-Sources ZCode After Data Dispute

Read original on TechNode

#data-privacy#no-retention#developer-toolszcodezhipuzcodegithubmaas

Zhipu’s response offers a case study in AI coding-tool transparency and data retention.

30-Second TL;DR

What Changed

ZCode’s code is now available on GitHub.

Why It Matters

The incident highlights how data-governance failures can affect trust in AI coding tools and model APIs. No-retention controls could make the platform more viable for enterprise workloads, subject to implementation and verification.

What To Do Next

Ask Zhipu for written retention guarantees and test the planned no-retention setting with non-sensitive code before production use.

Who should care:Enterprise & Security Teams

Key Points

•ZCode’s code is now available on GitHub.
•Zhipu completed a remediation process after a data-handling dispute.
•Its MaaS platform plans to offer no-retention controls.

Deep Insight

Background and context from public sources — not the original article. 12 sources cited.

Enhanced Key Takeaways

•The data dispute was triggered on September 18, 2026, when blogger ferstar revealed ZCode was secretly bundling and transmitting entire local workspaces and Git histories to an Alibaba Cloud OSS bucket ('zcode-prod').
•Zhipu attributed the unauthorized uploads to its 'Repo Wiki' feature, which attempted cloud-based codebase indexing without explicit user consent or opt-out toggles.
•Enterprise clients, including Taiyuan Chengming Technology, formally demanded proof of data destruction over fears of exposed proprietary code, cloud access keys, and credentials.
•Third-party cybersecurity audits by CAICT and NSFOCUS confirmed that Zhipu's 'zcode-prod' bucket objects were completely wiped and verified the patch integrity.
•The remediation culminated in the release of ZCode v3.14.0, which permanently excised the Repo Wiki feature and disabled local background snapshot mechanisms.

Competitor Analysis

Client Transparency

Zhipu ZCode: Open-source client (as of Sept 2026)
Cursor: Closed-source commercial IDE
Anthropic Claude Code: CLI-based tooling / Closed-source harness

Data Retention Controls

Zhipu ZCode: Zero-retention MaaS options + client verification
Cursor: Privacy Mode (SOC 2, no prompt retention)
Anthropic Claude Code: Strict API zero-retention policies available

Codebase Indexing

Zhipu ZCode: Localized only (Repo Wiki cloud pipeline stripped in v3.14.0)
Cursor: Cloud vector indexing (with opt-out)
Anthropic Claude Code: Context window injection / terminal indexing

Auditing & Trust

Zhipu ZCode: CAICT & NSFOCUS security audits completed
Cursor: Third-party SOC 2 Type II compliance
Anthropic Claude Code: Third-party red-teaming & enterprise compliance

Feature / Aspect	Zhipu ZCode	Cursor	Anthropic Claude Code
Client Transparency	Open-source client (as of Sept 2026)	Closed-source commercial IDE	CLI-based tooling / Closed-source harness
Data Retention Controls	Zero-retention MaaS options + client verification	Privacy Mode (SOC 2, no prompt retention)	Strict API zero-retention policies available
Codebase Indexing	Localized only (Repo Wiki cloud pipeline stripped in v3.14.0)	Cloud vector indexing (with opt-out)	Context window injection / terminal indexing
Auditing & Trust	CAICT & NSFOCUS security audits completed	Third-party SOC 2 Type II compliance	Third-party red-teaming & enterprise compliance

Technical Deep Dive

Exfiltration Mechanism: ZCode created encrypted archive payloads (e.g., snapshots up to ~313 MB) encapsulating full project directories and Git commit trees.
Storage Infrastructure: Archives were transmitted to an Alibaba Cloud Object Storage Service (OSS) bucket named zcode-prod, with decryption private keys retained exclusively on Zhipu's backend servers.
Faulty Architecture Component: The indexing mechanism designed for the 'Repo Wiki' feature initiated autonomous cloud-side transfers by default at startup rather than processing indexing locally.
Remediation Build (v3.14.0): Fully disassembled the background snapshot packaging routine, eradicated the Repo Wiki module, and eliminated hardcoded OSS network telemetry pipelines.

Future ImplicationsAI analysis grounded in cited sources

Open-source client architecture will become the mandatory baseline for enterprise AI coding assistants.

Heightened corporate vigilance over IP leakage will force competing AI IDE vendors to offer fully auditable, open-source desktop clients to satisfy enterprise infosec demands.

Zhipu faces prolonged compliance verification cycles from state-backed and enterprise clients.

Despite CAICT and NSFOCUS certifications, enterprise customers like Taiyuan Chengming Technology will impose stricter local isolation requirements before re-approving ZCode deployments.

Timeline

2026-09

Blogger ferstar discovers secret workspace uploads to OSS bucket in ZCode

2026-09

Corporate clients demand verification of credential security and data deletion

2026-09

Zhipu issues ZCode v3.14.0 patch, stripping Repo Wiki and file exfiltration paths

2026-09

CAICT and NSFOCUS audit and certify complete data wiping of zcode-prod

2026-09

Zhipu publicly open-sources ZCode client on GitHub and commits to zero-retention MaaS

2026-09
Blogger ferstar discovers secret workspace uploads to OSS bucket in ZCode
2026-09
Corporate clients demand verification of credential security and data deletion
2026-09
Zhipu issues ZCode v3.14.0 patch, stripping Repo Wiki and file exfiltration paths
2026-09
CAICT and NSFOCUS audit and certify complete data wiping of zcode-prod
2026-09
Zhipu publicly open-sources ZCode client on GitHub and commits to zero-retention MaaS