refactor: rename agent-zero to code-zero

[RedStar071]

Summary

Rename the project brand from Agent Zero to Code Zero across all packages, apps, documentation, configuration, and infrastructure. This includes updating package scopes from @agent-zero/* to @code-zero/*, environment variables from AGENT_ZERO_* to CODE_ZERO_*, and all references in documentation, workflows, and configuration files.

Why

Unify the project identity as Code Zero throughout the codebase, tooling, and public-facing documentation. The rebranding improves clarity and consistency across the entire monorepo.

Verification

• aube run check:repo
• aube run lint:ci
• aube run typecheck
• aube test
• aube run build

Safety and compatibility

• I added or updated deterministic tests for changed behavior.
• I preserved observe mode as read-only, or explained the policy change above.
• Runtime commands and target-repository writes remain inside the runner boundary.
• I did not expose secrets, tokens, personal data, or untrusted output in logs.
• I updated documentation and Agent Skills when workflows or boundaries changed.

Agent context

• Agent/tools used: None
• What the agent did, and what you changed or verified yourself: Generated commit message and PR body from diff analysis and repository conventions.

Reviewer notes

This is a comprehensive rebranding affecting:

• Package scopes and all imports across the workspace
• Environment variables in all .env files
• Agent Skills renaming
• Documentation and reference files
• GitHub workflows and issue templates
• Website branding assets and content
• Configuration files and examples
• Internal references in code comments and strings

No behavior changes — purely a rebranding effort. All package boundaries and architecture remain unchanged.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
agent-zero-dashboard	Ready	Preview	Sep 2, 2026 8:18am UTC
agent-zero-docs	Ready	Preview	Sep 2, 2026 8:18am UTC
agent-zero-marketing	Ready	Preview	Sep 2, 2026 8:18am UTC

[greptile-apps]

Too many files changed for review (251 files, 100 file limit).

Bypass the limit by tagging @greptile-apps to review.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad rebrand that also changes package, configuration, environment-variable, credential-store, and operational contracts, so existing consumers and deployments require an intentional migration. Authentication package files are directly modified, making human review necessary even though much of the diff is mechanical.

Not approved because:

• Credit balance exhausted. Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​code-zero/​auth@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​build-env@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​i18n@​0.3.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​mail@​0.3.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​shared@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​config@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​models@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​runner@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​agent@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​source-control@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​database@​0.4.0	N/A	N/A	N/A	N/A	N/A
	@​code-zero/​api@​0.3.0	N/A	N/A	N/A	N/A	N/A

View full report