Mintlify's silent asset-path change breaks reverse proxy docs deployments; AI agent diagnoses fix
tmuxvim · x · 2026-10-21
tmuxvim called out Mintlify over an apparent breaking change to reverse proxy deployments. The attached screenshot shows an AI coding agent's full diagnosis: Mintlify's new build now loads CSS/JS/fonts from root-level /mintlify/assets/... instead of /mintlify-assets/..., so proxies set up per Mintlify's own docs (forwarding only /developer/docs/) return 404s and pages render as bare HTML — even Mintlify's own example proxy domain is broken, with no changelog note.
- Fix: add a /mintlify/:path rewrite in next.config.js and extend isDeveloperDocsPath to cover /mintlify/; note the pitfall in a docs memory file for next time.
- Mintlify officially replied that they released no changes and are investigating.
Related event: Mintlify reverse proxy deployments break, team investigating(2 posts)→
More from coding & agent
- Index Network open-sources Social Discovery Protocol: agents negotiate fit on your behalf — carsonfarmer · 2026-10-23
- Installed a formal-verification skill: it silently installed Java, MacBook runs 10 degrees hotter — zealcaiden · 2026-10-23
- OpenAI's Decisions API hits GA: near real-time routing up to 10x faster than GPT-6 Luna — OpenAIDevs · 2026-10-23
- Ruff author warns: upgrade Node/Bun now — --use-system-ca still accepts the eMudhra cert — charliermarsh · 2026-10-23
- Proof of Agent: paste one prompt and your AI mines, grades, and self-governs — adamamcbride · 2026-10-23
- DeepLearning.AI weekly: GPT-6.1 hits 97.9% byte parity on COBOL migration — DeepLearningAI · 2026-10-23