Changelog

You can now pass lang=php to /llms.txt and to per-page .md and .mdx URLs to return only PHP SDK code examples. php joins node, python, java, ruby, go, csharp, and swift as accepted values for the lang query parameter.

/llms.txt?lang=php
/plants/create-plant.md?lang=php

You can now omit changelog sections from llms.txt by adding the excludeChangelog=true query parameter. This keeps the index small for sites with long release histories. It combines with the existing lang and excludeSpec parameters, for example /llms.txt?lang=python&excludeSpec=true&excludeChangelog=true.

Requests for a nonexistent .md URL now return up to five “Similar pages” suggestions instead of three, so agents on large sites are more likely to find the page they were looking for.

Multi-product sites can now have a single changelog shared by every product. Add a top-level changelog key in docs.yml next to products and the changelog is served at /changelog, without a product slug prefix and without appearing in the product switcher. This replaces the workaround of a dedicated “Changelog” product hidden with CSS.

products:
  - display-name: Ferns
    path: ./products/ferns.yml
  - display-name: Cacti
    path: ./products/cacti.yml
changelog:

You can now point an api navigation item straight at your OpenAPI, AsyncAPI, or GraphQL specification files with a specs list, without creating a generators.yml. Each entry takes a type and a path (relative to the configuration file), plus optional overrides, overlays, and namespace. Existing api-name setups are unchanged.

navigation:
  - api: API Reference
    specs:
      - type: openapi
        path: ./openapi.yml

You can now replace the default Ask Fern disclaimer (“Responses are generated using AI and may contain mistakes.”) with your own wording. Set ai-search.disclaimer in docs.yml and the text appears beneath answers in the chat panel, standalone modal, mobile drawer, and search widget, so the disclaimer can match your legal or privacy requirements.

ai-search:
  disclaimer: Answers are generated by a third-party AI model and may be inaccurate.

You can now add auth instructions that appear only in the API Explorer, such as where to generate a token, without changing the Authorization description in your API Reference. Set x-fern-playground-description on a security scheme in your OpenAPI spec, or playground-docs on an auth scheme in a Fern Definition. The text renders as an info callout beneath the matching auth input and supports links, inline code, and paragraphs.

You can now attach your own key-value metadata to a page with the search-metadata frontmatter object. Fern copies the block onto every Algolia record for that page and declares each key for faceting, so a custom search integration can group and filter results by your own taxonomy.

A self-hosted container can now resolve environment variables in the pages it serves, on each request. A ${VAR} whose name is listed in FERN_RUNTIME_ENV_VARS is deferred past generation instead of being substituted with its build-time value, so one image serves deployments that differ only in those values.

You can now put Fern Agent on a schedule. Create an automation on the Automations page in the Fern Dashboard. You can also describe the recurring work in the chat panel or Slack, and Fern Agent will set up an automation for you. Automations can review your reader feedback, unanswered Ask Fern questions, search queries, or analytics, report back what it found, and open a pull request when the prompt asks for a change.

GraphQL API References now include a page for every named type in your schema, collected under a Types section at the API Reference root and grouped by kind: Objects, Inputs, Enums, Scalars, Interfaces, and Unions. Interface pages list the interface’s fields and the types that implement it.

You can now configure a Card’s image title, link, source, position, and badge directly in Fern Editor. Repo-relative image paths resolve in the Editor, and the preview matches the published Card component.

You can now generate a single GraphQL API Reference from a schema split across several SDL files, including Apollo Federation subgraphs. List each file as its own spec in generators.yml with the same name, and Fern compiles them into one schema.

You can now present a changelog as a blog, with dated entries rendered as cards in a grid or list, tag filters, search, and author bylines on each post. Use this layout when a changelog functions more like a series of announcement posts than a list of releases. Set layout: blog and blog-layout in the changelog overview frontmatter.

You can now keep redirects in a separate YAML file and reference it from docs.yml. You can also split redirects across multiple files.

redirects: ./redirects.yml

Fern Agent edits your documentation and analyzes your organization’s Fern data. Talk to it in the Fern Dashboard chat panel, or integrate it with your Slack or your coding agent (via MCP) in one click.

Fern now hosts a private MCP server for the agent you build your docs with, with full context on Fern’s documentation and configuration — docs.yml syntax, components, CLI commands, and API definitions. It’s scoped to a single organization and returns only what your Fern account can already see: your sites and their configuration, deployment and preview-URL status, traffic and 404 analytics, search queries, Ask Fern conversations, and page feedback. Run fern mcp install to connect Claude Code, Cursor, or Codex to it.

You can now iterate on library docs locally from git inputs, not just path inputs. fern docs md generate --local reads the library source from the repository at the configured ref and parses it on your machine, so you can preview generated pages without publishing or logging in to Fern.

The @fern-api/search-widget package now ships an AskAiChat component: a sidebar panel that answers questions from your documentation inside any React application, like a dashboard or marketing site. The panel becomes a bottom drawer on small screens, and the theme and accentColor props match it to your product.

You can build scroll-synced code walkthroughs with the new <ScrollWalkthrough> component. Prose steps flow down the page while a code panel stays pinned beside them, following the reader’s scroll position. Use this component for quickstarts and integration guides where successive steps add to the same few files.

npm install @plantstore/sdk