clawgod

Highlights

This release fixes three Windows install paths that users hit on v1.0.8 and earlier.

Markers-missing extraction failure on Windows PE

Could not locate cli.js payload in binary (markers missing) — Anthropic's Windows PE builds don't embed the file:///$bunfs/root/src/entrypoints/cli.js path string we anchored on, even though Mach-O and ELF builds do. The extractor now adds a fallback: if the path anchor misses, walk back from the application-level cli_after_main_complete marker to find the IIFE start, requiring a >=1MB gap so we don't latch onto a sub-module wrapper. Verified against the v2.1.113 win32-x64 tarball pulled directly from npm.

Existing npm-global / bun-global installs are now picked up

Users who had previously run npm install -g @anthropic-ai/claude-code (or bun add -g) had a perfectly good binary on disk, but the installer only checked ~/.local/share/claude/versions/ and the prior claude.orig.exe backup. We now also scan:

• <npm root -g>/@anthropic-ai/claude-code/bin/claude.exe (the wrapper postinstall always names the binary .exe regardless of OS — that's upstream's choice)
• <npm root -g>/@anthropic-ai/claude-code-<platform>/<binary> (the per-platform package's own binary, in case --omit=optional skipped the wrapper postinstall)
• ~/.bun/install/global/node_modules/... for both layouts

Each candidate's package.json version is read into .source-version so the drift detector compares cleanly on the next launch.

Registry fetch no longer needs npm or tar on PATH

When no local binary is found, the previous fallback shelled out to npm pack + tar then silenced both with 2>$null. On Windows this produced a flat Failed to download with no diagnostic — common causes were a missing tar.exe on older Win10 builds, or & npm PowerShell shim quirks. The fallback is now an inline Node script that hits registry.npmjs.org directly via https.get, gunzips with Node's built-in zlib, and parses the POSIX tar header in ~30 lines of code. Errors (HTTP status, network failures, parse errors) propagate intact, so a failure tells you what actually broke.

README

Added Latest / Released / Downloads shields.io badges to the top of README.md, README_ZH.md, README_JP.md.

Verified

• macOS arm64: install with versions/ populated → patches cleanly (24/0 failed). Hidden versions/ → npm-global detection finds bun-global install. Hidden everything → Node-based registry fetch pulls v2.1.114, extracts, patches.
• Windows v2.1.113 PE binary: extractor fallback locates cli.js where primary anchor fails, full extraction succeeds, patcher runs 24/0 failed.

Install

macOS / Linux:

curl -fsSL https://github.com/0Chencc/clawgod/releases/latest/download/install.sh | bash

Windows (PowerShell):

irm https://github.com/0Chencc/clawgod/releases/latest/download/install.ps1 | iex

Closes: #50

Full changelog: https://github.com/0Chencc/clawgod/compare/v1.0.8...v1.0.9