Verifiable AST patches for the latest Claude Code native CLI

Get started · Patch catalog · Configuration · Desktop and remote targets · Documentation

cc-enhanced extracts the JavaScript embedded in an official Claude Code native executable, rebundles split modules into one patch surface when needed, applies a selected set of independently verifiable patches, and repacks the result without changing the native file's fixed layout. The primary cli-full profile improves Read and Edit ergonomics, modernizes prompt and tool routing, unlocks runtime and UI controls, and keeps the patched installation recoverable through atomic promotion and rollback.

The complete behavior and source link for every tag lives in the 44-patch catalog.

mise install
bun install --frozen-lockfile

mise run native:update

claude --version
mise run status

native:update fetches the current official release, builds and verifies a separate candidate, and promotes it only after all selected patch gates pass. Rollback is an atomic symlink exchange:

mise run native:rollback

See Getting started for requirements, patch selection, runtime tooling, traffic settings, and verification levels.

flowchart LR
    upstream["Official native executable"] --> extract["Extract or rebundle embedded JavaScript"]
    extract --> prompts["Prompt string transforms"]
    prompts --> ast["One shared AST pass<br/>discover → mutate → finalize"]
    ast --> verify{"Every selected verifier passes?"}
    verify -- no --> abort["Abort without writing"]
    verify -- yes --> signature["Inject patch signature"]
    signature --> repack["Repack at the original byte length and layout"]
    repack --> promote["Atomic promotion"]
    promote -. rollback .-> promote

Structural patches share one parsed AST and run in registration order. Each patch owns its verifier, failed tags are reported together, and no artifact is written when any required verification fails. Native lifecycle operations are serialized by a process-tree lease because bundle parsing, repacking, prompt export, and full verification are memory-heavy.

Offline construction, matching-host execution, stock-client rendering, and live control-plane operation are separate proof levels. A passing earlier level never promotes a reserved profile or establishes later compatibility. The target workflow guide explains the commands, client UI risks, Remote Control path, self-hosted path, and upkeep model.

bun run docs:check
bun run typecheck
bun run lint
bun run test
mise run verify:patches

bun run test deliberately executes one test file at a time to bound memory. Fixture tests validate contracts and edge cases; only mise run verify:patches against a real native bundle proves that the current upstream release still matches and verifies. See the CLI reference for prompt exports, matrix checks, and release-diff tooling.

• Generated candidates and evidence belong under ignored repository-local cache paths or another explicit private location.
• CI installs dependencies, checks documentation, typechecks, lints, and runs the serial test suite; it does not upload release assets or patched builds.
• Desktop-managed artifacts are not mutated by the offline candidate builder.
• Remote Control and self-hosted live actions remain explicit, receipt-bound operations with their own trust and consent gates.

This project is not affiliated with, endorsed by, or connected to Anthropic, PBC or any of its affiliates. "Claude" and "Claude Code" are trademarks of Anthropic, PBC. This tool modifies a locally obtained Claude Code executable, which may not be permitted under applicable terms. Users are responsible for their own compliance and use it at their own risk.

MIT