Fern
Several docs-platform and AI-agent improvements shipped across April and May 2026.
Search scoped to product or version landed with a new settings.search object in docs.yml.1 Two modes are available: prioritize-current-product boosts results from the active product without hiding others, while default-filter-by-current-product auto-applies a facet filter so only that product's results appear by default.
AI agents now receive full API examples in Markdown output.2 Interactive components like <EndpointRequestSnippet> and <RunnableEndpoint> render as fenced code blocks in .md URLs, llms.txt, and llms-full.txt, closing the gap between the rendered page and machine-readable representations.
A live link checker joined the CLI.3 fern docs link check scrapes every published page and reports broken and blocked URLs with the source pages where they appear — catching live 404s that local YAML validation misses.
Multi-source docs and custom robots.txt arrived together.4 Teams can now publish independently to sub-paths of a shared custom domain, and authors can serve their own robots.txt to control AI crawler access per section.
API catalog discovery via the standards-based /.well-known/api-catalog endpoint lets MCP clients and catalog crawlers find APIs automatically from the navigation tree.5
The <Prompt> component added support for arbitrary URL actions, extending beyond Cursor, Claude, and ChatGPT to any AI tool.6 Global themes, per-page agent directives, custom llms.txt files, and a standalone search widget rounded out the AI-integration work. Preview-deployment cleanup workflows for both GitHub Actions and GitLab CI also shipped, removing stale previews automatically on merge.