agnostic-ai v0.64.0: npm installs without postinstall downloads

What to do #

1. If you used AGNOSTIC_AI_VERSION with npm, pin the package instead, for example withnpm install -g agnostic-ai@0.64.0 .

2. If npm reports a missing optional platform package, run npm install -g agnostic-ai --force --include=optional . Nothing else needs action.

Shipped in agnostic-ai v0.64.0 #

Changed

• npm install agnostic-ai no longer downloads anything: the binary ships in a platform package (@chemaclass/agnostic-ai-darwin-arm64 and five siblings) that npm picks byos andcpu , so the install works under--ignore-scripts , offline, and behind a proxy.AGNOSTIC_AI_VERSION stops applying to npm, where the package version is the pin, sonpm install -g agnostic-ai@0.62.0 replaces it; both install scripts still honour it, andAGNOSTIC_AI_BINARY still points the wrapper at a binary of your own. A global copy missing its platform package is now toldnpm install -g agnostic-ai --force --include=optional , which reaches the global tree and overrides anomit=optional in your npm config (#942).
• The release publishes the six platform packages before the parent that pins them, and the distribution guard checks the version and the dist-tag on all seven, so a partial publish fails the release instead of breaking installs on one platform. Every publish carries a --tag derived from the version (-beta.1 tobeta ,-rc.2 torc , anything unrecognised tonext ), so cutting a prerelease no longer hands it npm'slatest (#942).
• The Homebrew cask is no longer pushed from this repository, and no longer needs a secret in it. Chemaclass/homebrew-tap updates its own cask every half hour with theGITHUB_TOKEN its workflow already has, checking all four archives resolve before it commits. The release still supportsHOMEBREW_TAP_APP_ID /HOMEBREW_TAP_APP_PRIVATE_KEY andHOMEBREW_TAP_TOKEN , and writes a byte-identical file, so the two routes never fight (#920, #943).
• Target audits reuse one issue index, load vendor references by target, and fit available worker slots; fix instructions load only when needed.

Added

• agnostic-ai lint warns (LINT009) on an allowedBash(...) rule with a* before the end of the command, such asBash(git * main) , which also approves options inserted at that spot on Claude Code and every target that translates the rule. Deny and ask rules are not flagged, since widening them only blocks or prompts more.
• Gemini emits and imports default-model settings, and Qoder emits HTTP and prompt hooks (#998, #1005).
• This repository now dogfoods the three spec kinds it never used: an ignore spec keeps build output, lockfiles, and local secrets out of ten targets' exclusion files, beside areview spec Cursor Bugbot and Goose read and anenvironment spec for Cursor, Amp, and OpenHands (#980).

Fixed

• Claude rejects disabled project MCP servers and preserves manual rejection entries when re-enabled (#997).
• Import preserves Cline and Continue rule conditions, both Cline rule roots, and compatible Junie, Warp, and OpenCode skills (#999, #1000, #1001, #1002).
• Factory keeps scoped skills in their project areas, and Trae rejects invalid native agent names (#1004, #1006).

Site

• The targets index records Cursor's default-on compatibility hooks and required type: stdio field (#1007).
• The landing says the same things in fewer words. The mission lede loses a restated line, each principle drops a repeated clause, the targets lead names the four omitted spec kinds, and the hero fan drops its accent dot.
• The site builds on Zola 0.23.6 instead of 0.22.0: templates moved to Tera 2 components, shortcodes became components, and the three site tests that silently skipped on a mismatched local Zola now run for anyone on a current release (#970).
• The ten spec kinds stop being a bare list. The playground's kind picker now says in one line what the selected kind is and links to the section of the spec format that defines it, the landing names the four kinds its capability matrix leaves out with a link each, and the README explains review ,environment , andignore instead of only listing them (#980).
• The landing ships its generated-file tablist inert until landing.js wires it, so readers without JavaScript see one real file (#977).landing.toml also drops the unrenderedgo andbinary installers while keeping the hero default and entries withrecommend_for ; a test now rejects unreachable installers (#991).

Upstream CLI and model news #

No verified upstream change met the bar for this briefing.