mintlify broken-links reports auto-generated /llms.txt and /llms-full.txt as broken

[vesai]

mintlify broken-links reports /llms.txt and /llms-full.txt as broken, but
Mintlify itself auto-generates and serves these at the site root.

To reproduce: add llms.txt to any page, run mintlify broken-links:

found 2 broken links in 1 files

developers/test.mdx
 ⎿  /llms.txt
 ⎿  /llms-full.txt

Both URLs return 200 on the deployed site, so this is a false positive that fails CI.

Request: either treat these two paths as known-valid, or add an ignore/allowlist option so paths outside the MDX routing tree can be whitelisted.

Current version:
npm package: mintlify@4.2.525

npx mintlify version

cli version 4.0.1128
client version 0.0.2795

[cookesan]

This looks like a valid false positive.

The docs say Mintlify automatically hosts both /llms.txt and /llms-full.txt at the site root, and also under /.well-known/. But the documented mint broken-links command only describes checking internal links against documentation files/routes; its flags are --check-anchors, --check-external, and --check-snippets. I do not see a documented allowlist/ignore flag for generated root routes.

Until the CLI special-cases these generated files or adds an allowlist, the least invasive CI workaround is to avoid root-relative internal links to those generated files in MDX. For example, link to the deployed absolute URL instead if you are not running --check-external. Creating custom llms.txt files in the repo may also make the paths concrete, but that changes the behavior by overriding the generated files, so I would not treat that as the normal fix.