PR #89774: fix(codemod): ensure agent instruction is executable

• Repository: vercel/next.js
• Author: emonty
• State: open | merged: False
• Link: https://github.com/vercel/next.js/pull/89774

Description (problem / solution / changelog)

In the current form, the agents-md command writes an instruction that doesn't actually execute, since the command is only on @canary.

What?

In the current form, the agents-md command writes an instruction that doesn't actually execute. There are two issues. One is that it writes the instruction without @canary and it only exists in canary right now. The second is that, without embedding a version in the instruction, it does version inference logic and in the case of a version range, the command fails.

Why?

I work with agents running in their own sandboxes, not on my laptop where I have done out of band setup work. So the agent needs to be able to clone the repo and do necessary steps from AGENTS.md for things to work.

How?

Fixes #89772 Fixes #89773

Capture the invocation details when it is run and write the instructions to AGENTS.md so that the original command will be re-run.

For the version issue, look for a version in package-lock.json which should always have the correct and precise version.

Changed files

• packages/next-codemod/bin/agents-md.ts (modified, +8/-0)
• packages/next-codemod/lib/__tests__/agents-md-unit.test.js (added, +270/-0)
• packages/next-codemod/lib/agents-md.ts (modified, +46/-2)

PR #90067: fix(codemod): handle semver ranges in agents-md version detection

• Repository: vercel/next.js
• Author: sleitor
• State: open | merged: False
• Link: https://github.com/vercel/next.js/pull/90067

Description (problem / solution / changelog)

What?

Fix agents-md codemod failing when Next.js version is specified as a semver range in package.json (e.g. ^16, ~16.1.0) and the package is not yet installed.

Why?

getNextjsVersion() only detects the installed version via require.resolve('next/package.json'). When Next.js isn't installed yet (common when running the codemod for the first time, or when an AI agent re-runs the generated command in a fresh sandbox), the function returns null and the codemod fails with:

Could not find documentation for Next.js v16. This version may not exist on GitHub yet.

How?

Added a fallback in getNextjsVersion() that reads the version range from package.json dependencies and extracts a concrete version using a new exported extractVersionFromRange() helper:

• ^16.1.3 → 16.1.3
• ~16.1.0 → 16.1.0
• ^16 → 16.0.0
• >=15.0.0 → 15.0.0
• ^16.2.0-canary.16 → 16.2.0-canary.16

The fallback is only used when require.resolve fails and monorepo detection finds nothing.

Checklist

• Related issues linked using fixes #number
• Tests added
• Errors have a helpful link attached — N/A (no new error messages)

Fixes #89773 Fixes #89772

Changed files

• packages/next-codemod/lib/__tests__/agents-md.test.js (added, +128/-0)
• packages/next-codemod/lib/agents-md.ts (modified, +64/-12)

PR #90145: docs: fix pnpm new-test example to forward args

• Repository: vercel/next.js
• Author: lllomh
• State: open | merged: False
• Link: https://github.com/vercel/next.js/pull/90145

Description (problem / solution / changelog)

Summary: Fixes an incorrect example in AGENTS.md that showed pnpm new-test --args .... The correct usage is to forward arguments to the script with --, e.g. pnpm new-test -- --args ....

Changes:

Update the example and add a short note explaining that -- forwards args to the script. Related:

Closes #89772 Verification:

Documentation-only change; verify the example in AGENTS.md shows pnpm new-test -- --args ....

Changed files

• AGENTS.md (modified, +4/-4)