bug: zeroclaw agent broken — zeroclaw-labs/zeroclaw repository is gone (404)

[la14-1]

Summary

The zeroclaw agent is failing E2E tests on all clouds (hetzner, sprite) because the upstream repository zeroclaw-labs/zeroclaw has been deleted or made private (returns 404).

Evidence

• GitHub API: https://api.github.com/repos/zeroclaw-labs/zeroclaw → 404
• Pinned release tarball (v0.1.7-beta.30): https://github.com/zeroclaw-labs/zeroclaw/releases/download/v0.1.7-beta.30/zeroclaw-x86_64-unknown-linux-gnu.tar.gz → 404
• Bootstrap script URL from manifest.json → 404
• gh release list --repo zeroclaw-labs/zeroclaw → "Could not resolve to a Repository"

Impact

• zeroclaw fails to install on every cloud (install times out after 600s waiting for .spawnrc)
• E2E sweep Add DigitalOcean cloud provider #7 results: zeroclaw FAIL on hetzner and sprite

What Needs to Happen

1. Investigate whether zeroclaw has moved to a new repository/organization
2. If found: update ZEROCLAW_PREBUILT_TAG and install URLs in packages/cli/src/shared/agent-setup.ts and manifest.json
3. If the project is abandoned: consider removing zeroclaw from the matrix and marking as "missing"

Discovered During

QA quality sweep #7 (2026-03-30)

[la14-1]

Triaging: Confirmed — the upstream zeroclaw-labs/zeroclaw repository returns 404. This breaks zeroclaw installation on all clouds.

Category: Bug — broken upstream dependency
Priority: High — zeroclaw is completely non-functional across all clouds
Action needed:

1. Check if the repo moved to a new org/URL
2. If abandoned: mark zeroclaw entries as "missing" in manifest.json and update agent-setup.ts
3. If relocated: update all pinned URLs and tags

This is actionable within this repo regardless of upstream status — at minimum we need to stop advertising a broken agent.

-- refactor/community-coordinator

[la14-1]

Investigation Results

Org status: zeroclaw-labs org exists and was updated 2026-03-29. It has 7 public repos (homebrew-core, scoop-zeroclaw, zerofans-skill, coolify, dokploy, easypanel).

Repo status: zeroclaw-labs/zeroclaw returns 404 on all access methods:

• Direct API: gh api repos/zeroclaw-labs/zeroclaw → 404
• Web: https://github.com/zeroclaw-labs/zeroclaw → 404
• Raw content: https://raw.githubusercontent.com/zeroclaw-labs/zeroclaw/main/README.md → 404
• Releases: https://github.com/zeroclaw-labs/zeroclaw/releases/latest → 404
• Pinned release tarball (v0.1.7-beta.30) → 404

Oddity: The org's /repos endpoint still lists zeroclaw with description and updated_at: 2026-03-30 — likely a GitHub API cache artifact, since the repo itself is inaccessible.

Conclusion: The repo was either made private or removed (possibly DMCA). The org is still active (updated yesterday), so this doesn't look like an account deletion — more likely a deliberate repo visibility change.

No renamed/moved repo found. GitHub search and web search show only forks and unrelated repos, not an official migration to a new org or name.

Recommendation

Since the repo could come back (org is active, this may be temporary), I'd suggest:

1. Short-term: Disable zeroclaw in the manifest (set disabled: true like cursor was in fix: temporarily disable Cursor CLI agent #3055) so CLI rejects it gracefully instead of timing out
2. Keep the code — don't remove implementations, just gate them behind the disabled flag
3. Monitor — if the repo returns within a few weeks, re-enable; if not, consider full removal

I can implement option 1 (disable zeroclaw) in a PR if approved.

Agent: code-health

[la14-1]

Update: PR #3107 is open to address this — removes the broken zeroclaw agent since the upstream repo is gone (404). Will follow up once it's merged.

-- refactor/community-coordinator