github agent-sh/agnix v0.51.0

latest release: v0.52.0
5 hours ago

Added

  • PyPI distribution. pip install agnix and uvx agnix . now work. The
    wheels in pypi/ bundle the release binary for each supported target
    (manylinux and musllinux x86_64, manylinux aarch64, macOS Apple silicon,
    Windows x86_64), so there is no Rust toolchain to install and nothing is
    downloaded after install. python -m agnix and a small Python API
    (agnix.run, agnix.lint, agnix.version) mirror the Node wrapper.
    pypi/build_wheels.py repacks the archives the release already built and
    verified against their .sha256 sidecars, deriving each manylinux tag from
    the binary's own glibc symbol references rather than a hardcoded floor.
  • JetBrains plugin: WSL execution mode
    (#1346). IntelliJ on Windows
    can now run agnix-lsp from inside a WSL distribution for projects that live
    in WSL, without Remote Development. The plugin launches an argument-safe
    wsl.exe --distribution <name> --exec <path> command, maps document and
    workspace URIs at the LSP boundary, validates configuration, and skips the
    host-local binary installer. Native launches remain unchanged.

Changed

  • Tool and spec baselines refreshed (closes
    #1426,
    #1427,
    #1428,
    #1429). Advanced Claude Code
    from v2.1.245 to v2.1.246, Cursor from 3.17.19 to 3.17.21, and amp from
    friendly-urls-for-sharing-orbs to setup-without-a-commit, and re-baselined
    the eight drifted spec sources (Claude Code hooks/skills/plugins-reference;
    Cursor rules/hooks/subagents/mcp and the environment schema). Reviewing all
    eight against the rules they back found no contract change that agnix asserts
    incorrectly: Claude Code's 31 known hook events still cover every event the
    hooks reference documents, the skill frontmatter allowlist still covers all 20
    documented fields, the plugin path-bearing keys remain a superset of the
    documented table, Cursor's hook events (including the still-supported
    beforeShellExecution / beforeMCPExecution) and per-script options are
    unchanged, subagent frontmatter and model-parameter syntax still validate, the
    environment schema's property set still matches ALLOWED_ROOT_FIELDS, and
    neither MCP nor hook entries reject unknown fields, so newly documented keys
    cannot produce false positives. Coverage gaps the review surfaced (upstream's
    new wildcard-permission warning, unvalidated keybindings.json, Cursor's
    now-required MCP type and STDIO-only envFile) are recorded in
    RESEARCH-TRACKING. amp's release stores pre-clone and pre-setup scripts in
    server-side project settings rather than any validated file. Cline
    (v4.1.16) and Codex (rust-v0.150.0) published after those issues were
    opened and are deliberately left at their previous baselines so the watcher
    files their own triage issues.
  • Tool release baselines. Advanced Claude Code from v2.1.243 to
    v2.1.245 and OpenCode from v1.18.22 to v1.18.23 after reviewing their
    live release notes. Claude Code's change is a Linux glibc 2.44 startup-crash
    fix; OpenCode's changes fix Cloudflare AI Gateway routing, Anthropic model
    slugs, parent-session headers, and immutable-OIDC GitHub auth. None changes
    an agnix-validated configuration contract. Advanced Gemini CLI from v0.56.0
    to v0.57.0; its changes affect OAuth redirects, IDE and Git worktree state,
    runtime retry and cancellation behavior, agent enablement, and command help,
    without changing an agnix-validated configuration contract.

Fixed

  • Stale rule count in the npm long description. npm/README.md advertised
    405 rules against a canonical 451, and no automation covered it, so the number
    had drifted for several releases and was copied into the new PyPI README.
    Corrected, and both wrapper READMEs are now in sync-rule-bookkeeping.js's
    COUNT_FILES so CI fails on the next drift.

Don't miss a new agnix release

NewReleases is sending notifications on new releases.