Serve /evaluate/prompt.md and /agent-setup/prompt.md as text/plain: ChatGPT's web reader refuses text/markdown
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Locate the hosting or header configuration that serves /evaluate/prompt.md and /agent-setup/prompt.md; the issue cites the existing llms.txt and domain-bundle behavior and the analogous Netlify rule in nextcommerce-site#176. Update both paths to return text/plain; charset=UTF-8, then run the stated curl -sI check and confirm the paths and references remain unchanged.
Written by the indexing model from the issue text.
Description
Gap: both agent prompt files are served with Content-Type: text/markdown. ChatGPT's web reader refuses to open that type. Observed twice on 2026-09-16 against nextcommerce.com/agent-eval/prompt.md (same content type, same behaviour): "the web reader here is rejecting that endpoint because it serves text/markdown directly". The URL was confirmed 200 to ChatGPT-User, OAI-SearchBot and GPTBot user agents, so it is the type, not access.
Codex CLI, Claude Code and Cursor fetch these fine (plain HTTP clients), which is why the persona × agent probes never hit it. ChatGPT web is the surface a prospect on the marketing site reaches through the hero strip, and the www consultation file hands the developer persona to /evaluate/prompt.md, so a ChatGPT user gets one hop and then a wall.
Fix: serve /evaluate/prompt.md and /agent-setup/prompt.md as text/plain; charset=UTF-8, as llms.txt and the domain bundles already are. Paths unchanged; they are referenced from llms.txt and from the www file. nextcommerce-site did the same in NextCommerceCo/nextcommerce-site#176 with a Netlify header rule.
Verify: curl -sI https://developers.nextcommerce.com/evaluate/prompt.md | grep -i content-type.
- Dominant language
- MDX
- Stars
- 2
- Forks
- 0
- Avg merge
- 6h 4m
- Merged PRs (30d)
- 13
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NextCommerceCo/developer-docs
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
All issues in NextCommerceCo/developer-docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100