Project releases

Agentic-Flow 2.1.4 points the repair command at the right package

The npm patch corrects npx examples to select the agentic-flow package before running its differently named repair executable.

GitHub activity: · Published:

Select the package, then the binary

Package name and executable name differ. Select the package, then follow its declared binary mapping.

Explanatory diagram · not live telemetry
Explanatory connectionsnpx selects agentic-flow, follows its declared agentic-flow-repair executable mapping and passes the repository argument. This explains resolution, not repair execution.Explanatory connectionsnpx selects agentic-flow, follows its declared agentic-flow-repair executable mapping and passes the repository argument. This explains resolution, not repair execution.

Explicit package selector

npx --package=agentic-flow

Package: agentic-flow

Declared bin mapping

Binary: agentic-flow-repair

Executable inside that package

Repository argument

./my-repo and documented flags

What changed

Agentic-Flow’s executable is named agentic-flow-repair, but it comes inside the agentic-flow package. Without a local executable, a bare npx executable name can make npm look for a package of the same name. The corrected README explicitly selects agentic-flow before naming the repair binary.

Agentic-Flow 2.1.4 publishes those corrected examples after the October 9 source fix. It adds no repair engine, runtime API change or dependency update. A syntax regression guard backs the correction. Explicit package selection does not pin a version, guarantee integrity or protect a compromised local executable path; the evidence does not establish an exploited vulnerability.

Get started

Use Node >=20 and a disposable checkout. These are source examples, not commands we ran or recommend running on an important repository.

Documentation-verified only. We did not install this release, execute these commands or reproduce the maintainers’ tests.

npx --package=agentic-flow -- agentic-flow-repair ./my-repo --mock
npx --package=agentic-flow -- agentic-flow-repair ./my-repo --generations 3

This documentation-only patch adds no MCP endpoint, server or skills setup; no repair demo was verified.

Use it today

Update copied notes and scripts to use explicit package selection. Begin with a disposable checkout and the documented mock example. This documentation patch is not permission to run repair against an important repository.

Experimental commentary — acceptance test

Acceptance: inspect onboarding in an empty environment without a preinstalled executable and confirm the selected package declares the repair bin mapping. A cached binary can hide the ambiguity. Runtime repair behavior was not exercised here.

Limits and verification

  • The manifest/registry requires Node >=20 even though older README text says 18+. Prefer the package requirement.
  • The README examples are intentionally unpinned; no article command was executed.
  • No GitHub release entry was found for 2.1.4. Npm publication and the merged release PR establish the release.
  • No malicious package, compromise or new autonomous capability is alleged.

Read the original on Repair documentation PR #237

PR #237

Agentic-Flow repository

Back to the newsroom