vercel / vercel/next.js

agents-md provides non-working command in AGENTS.md instructions

Open
#89,772 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
142k
Forks
32.4k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

Link to the code that reproduces this issue

https://github.com/emonty/next.js

To Reproduce

Run npx @next/codemod agents-md --output AGENTS.md
Inspect the instruction added to AGENTS.md. Execute that command in a clean checkout as-if you are an agent in a sandbox:
npx @next/codemod agents-md --output AGENTS.md

Current vs. Expected behavior

I expect the agent being given the instruction to be able to re-run the instruction successfully.

Provide environment information
Operating System:
  Platform: linux
  Arch: x64
  Version: #12-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan  9 20:46:52 UTC 2026
  Available memory (MB): 31021
  Available CPU cores: 22
Binaries:
  Node: 24.12.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.1.6 // Latest available version is detected (16.1.6).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: standalone
Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running npx @next/codemod agents-md --output AGENTS.md in a clean checkout and inspect the instruction written to AGENTS.md. Re-run the generated command as described in the reproduction steps, then verify that the instruction completes successfully without producing the same non-working command.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nextjs
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.