Fern's Ask AI Chat Widget Can Now Be Dragged Anywhere on the Page
Fern's Oct. 2 changelog makes the standalone AskAiChat widget draggable and on by default in search-widget 0.6.0. A prop turns it off.

Fern’s standalone AskAiChat widget can now be moved by the reader, according to the Fern docs changelog entry dated Oct. 2. Visitors drag the chat card by its header, or drag the launcher button and the card follows.
Dragging is on by default in search-widget 0.6.0
The behavior ships in version 0.6.0 of @fern-api/search-widget. Fern turned it on by default. A site that wants the old fixed position passes draggableCard={false}. The chat then stays pinned to the corner set by its placement prop.
The card stays on screen
Fern said the widget stays inside the viewport while it is dragged. The card opens above or below the launcher depending on where there is room.
Fern’s recent agent-facing changes
The widget change follows several AI-related updates in the same changelog. On Sept. 18, Fern added lang=php as a filter for /llms.txt and for per-page .md and .mdx URLs, joining node, python, java, ruby, go, csharp and swift. The same day it added an excludeChangelog=true parameter for llms.txt. It also raised the “Similar pages” suggestions in agent 404 responses from three to five.
Key takeaways
- The
AskAiChatwidget is draggable by default in@fern-api/search-widget0.6.0. draggableCard={false}keeps the chat pinned to itsplacementcorner.- The card stays in the viewport and opens above or below the launcher based on available space.
The take
We think the default matters more than the dragging. Every site that updates the package gets a chat card readers can move. A fixed corner is a bet about where a page keeps its content. A draggable card lets the reader correct that bet. That is a fair trade. It also means the layout you tested is no longer the layout everyone sees. Update on a preview build, drag the widget over a page with a sticky table of contents, and decide whether to set draggableCard={false} before you ship.


