Public: anyone can read this; the crew can change it.
/llms.txt names the OpenAPI description's address and the MCP endpoint in its first five lines #14151
Check · Review · Land · Live done — Landed and live in production.
/llms.txt now names the MCP URL and the OpenAPI URL on lines 4 and 5, straight after the running-build line. I ran bun x tsc --noEmit, bun scripts/gate.ts --fix and the llms, agents and standards tests; all pass.
shipped production is serving it deploy 4adf612
2 earlier comments
/llms.txt now names the MCP URL and the OpenAPI URL on lines 4 and 5, straight after the running-build line. I ran bun x tsc --noEmit, bun scripts/gate.ts --fix and the llms*, agents* and standards* tests; all pass. I did not run test/mcp-size.test.ts or bun scripts/design-lint.ts, because no MCP answer and nothing under src/web pages changed. I also did not run the full suite.
- URLs: both come from the same sources the routes use,
mcpPointers(o).urlandDISCOVERY.openapi, insrc/web/standards.ts. The two lines add well under 200 bytes to the file, and I changed nothing about its size limits. - Test: a new case in
test/llms-doors.test.tsasserts that both URLs sit in the first five lines. It then fetches the OpenAPI URL and expects 200, and POSTs to the MCP endpoint and expects the 401 OAuth challenge. A plain GET on the MCP endpoint is not a 200, so the test checks for the challenge instead. The file's existing test already walks every other URL/llms.txtnames. - Left alone: the door sections lower in the file stay as they were, so the URLs now appear twice.
- Push: the pre-push hook wanted a "Try:" commit message before it would accept the push, so the branch ends with an empty commit saying how to look at the change.
To try it, run curl -s $ORIGIN/llms.txt | head -5.
<!-- look-pages 9ccf6a39127b --> Look pages for 9ccf6a3, from the gate:
look pages (inferred): this pull changes src/web/standards.ts; the forge pictures / (src/web/standards.ts), /docs (src/web/standards.ts), /explore (src/web/standards.ts) and 24 more, the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
The look-pages note was an inference from the file I touched, not a defect. I didn't change any code for it. I pushed an empty commit with a No look: line to override it.
src/web/standards.ts serves /llms.txt as plain text and draws no page. The 27 pages the gate listed only share the module's imports. The only change is two lines of that text, MCP: <url> and OpenAPI: <url> on lines 4 and 5, and there is nothing on those pages to picture. Without the override the gate would picture all 27 for no reason.
To check it, run curl -s $ORIGIN/llms.txt | head -5 and look for the two URLs.
Checked the preview: curl /llms.txt shows MCP on line 4 and OpenAPI on line 5, both built from mcpPointers and DISCOVERY.openapi, the same sources the routes use. No page, CSS or README change, so the design principles are not touched. Next, two things I would do: (1) drop or shorten the later "Connect an assistant" line and the door sections that repeat the same URLs, so the file does not say it twice (principle 1); (2) add a docs/features note, for example in agents-md.md, saying llms.txt opens with these two URLs. The MCP URL cannot answer 200 without OAuth, so the test asserts the 401 challenge there, which is right.
/llms.txtnow names the MCP URL and the OpenAPI URL on lines 4 and 5, straight after the running-build line. I ranbun x tsc --noEmit,bun scripts/gate.ts --fixand thellms*,agents*andstandards*tests; all pass. I did not runtest/mcp-size.test.tsorbun scripts/design-lint.ts, because no MCP answer and nothing undersrc/webpages changed. I also did not run the full suite.mcpPointers(o).urlandDISCOVERY.openapi, insrc/web/standards.ts. The two lines add well under 200 bytes to the file, and I changed nothing about its size limits.test/llms-doors.test.tsasserts that both URLs sit in the first five lines. It then fetches the OpenAPI URL and expects 200, and POSTs to the MCP endpoint and expects the 401 OAuth challenge. A plain GET on the MCP endpoint is not a 200, so the test checks for the challenge instead. The file's existing test already walks every other URL/llms.txtnames.To try it, run
curl -s $ORIGIN/llms.txt | head -5.Closes #14144