From c5944348ba57db1e969a6eb7d273c32822f07c67 Mon Sep 17 00:00:00 2001 From: "devin.logan" Date: Mon, 31 Aug 2026 12:52:40 +0000 Subject: [PATCH 1/4] docs: document Fern Agent automations Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- fern/products/docs/pages/ai/fern-agent.mdx | 38 +++++++++++++++++++ fern/products/docs/pages/ai/overview.mdx | 2 +- .../docs/pages/changelog/2026-08-31.mdx | 9 +++++ 3 files changed, 48 insertions(+), 1 deletion(-) create mode 100644 fern/products/docs/pages/changelog/2026-08-31.mdx diff --git a/fern/products/docs/pages/ai/fern-agent.mdx b/fern/products/docs/pages/ai/fern-agent.mdx index 83a72e6207..7b43d66157 100644 --- a/fern/products/docs/pages/ai/fern-agent.mdx +++ b/fern/products/docs/pages/ai/fern-agent.mdx @@ -195,6 +195,44 @@ Fern Agent is an expansion of Fern Writer. Fern Writer opened documentation pull What Fern Agent adds is context on your organization and more places to work from. Alongside editing, it answers questions about your traffic, reader questions, deployments, and site configuration, and the same capabilities are now available in the Fern Dashboard and in your coding agent over MCP rather than in Slack alone. +## Automations + +An automation is a prompt Fern Agent works on a schedule, with nobody present. Create one on the **Automations** page of the [Fern Dashboard](https://dashboard.buildwithfern.com/), or describe the recurring work in the chat panel or Slack and Fern Agent sets it up. + +Each run starts a fresh conversation from the prompt, works it in a single turn, and closes with a report on what it did, what it found, and what it skipped. The prompt decides whether a run changes anything: runs report back unless the prompt asks for a change, as in "make the change and open a pull request". + + + +Open **Automations**, select **New automation**, and describe what each run should look at and produce. Every run has your organization's docs, analytics, reader feedback, Ask Fern conversations, and search queries available to it. To start from an example, pick one from **Start from an example** and edit it. + +```text Fix what readers complained about +Review the feedback readers left on our docs pages and fix the pages they +said were missing information, wrong, or unclear. Make the changes and open +a pull request. Ignore feedback about the product rather than the docs. +``` + +```text Report on how the docs are doing +Report on how our docs are doing: the pages readers spend the most time on, +where they drop off, the searches that return nothing, and what changed +since last week. Do not change any docs. +``` + + + +Select **Authorize** and complete the browser prompt. A run acts with the Fern permissions of whoever created the automation, read again each time a run uses them, so an unattended run needs that person's authorization first. One authorization covers all your automations. + + + +Choose daily or a day of the week, a time of day, and the timezone that time is read in, then turn the automation on. A schedule fires at most once every 20 hours. + + + +Select **Run now** instead of waiting for the schedule, since running by hand leaves the next scheduled run where it was. Runs take a few minutes, and **Past runs** lists each one with a link to its conversation, where the report and any pull request are. + + + +Everyone in your organization sees every automation, and only its creator can change, delete, or run one. Turning an automation off keeps its prompt and history, while deleting it discards both — pull requests its runs opened are unaffected. An organization can keep up to 10 automations, and run history covers the last 30 days. + ## Privacy and data handling Fern Agent acts with your own Fern permissions on every surface, so it reads and edits only the sites, analytics, and organization data your account can already see. Requests are scoped to a single session: the prompt, any Slack message or thread you tag it in, and attached files are stored to complete the task and aren't retained afterward. diff --git a/fern/products/docs/pages/ai/overview.mdx b/fern/products/docs/pages/ai/overview.mdx index 51be0a3225..3dad9c5623 100644 --- a/fern/products/docs/pages/ai/overview.mdx +++ b/fern/products/docs/pages/ai/overview.mdx @@ -32,7 +32,7 @@ Your users can ask a question instead of searching for one. Ask Fern answers wit ## Build your docs with AI -You can hand your docs to an agent. [Fern Agent](/learn/docs/ai-features/fern-agent) writes them from inside Fern, opening a pull request with the change you describe. The coding agent you already use writes them too, once Fern's skill and MCP server teach it how Fern Docs sites are built. Fern also generates realistic API examples from your spec. +You can hand your docs to an agent. [Fern Agent](/learn/docs/ai-features/fern-agent) writes them from inside Fern, opening a pull request with the change you describe, either on request or on a [schedule you set](/learn/docs/ai-features/fern-agent#automations). The coding agent you already use writes them too, once Fern's skill and MCP server teach it how Fern Docs sites are built. Fern also generates realistic API examples from your spec. diff --git a/fern/products/docs/pages/changelog/2026-08-31.mdx b/fern/products/docs/pages/changelog/2026-08-31.mdx new file mode 100644 index 0000000000..f31f2e2c7a --- /dev/null +++ b/fern/products/docs/pages/changelog/2026-08-31.mdx @@ -0,0 +1,9 @@ +## Fern Agent automations + +ai + +You can now put Fern Agent on a schedule. An automation is a prompt Fern Agent works daily or weekly with nobody present: it reviews your reader feedback, unanswered Ask Fern questions, search queries, or analytics, reports back what it found, and opens a pull request when the prompt asks it to change the docs. + +Create one on the **Automations** page in the [Fern Dashboard](https://dashboard.buildwithfern.com/), or describe the recurring work you want in the Fern Agent chat panel or in Slack. **Run now** shows what a run comes back with before the first scheduled one. + + From 3d2214ae62bf0cd028b713ed15c1bc12b1696a20 Mon Sep 17 00:00:00 2001 From: "devin.logan" Date: Mon, 31 Aug 2026 12:57:39 +0000 Subject: [PATCH 2/4] docs: wrap automation prompt examples to fit the code block Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- fern/products/docs/pages/ai/fern-agent.mdx | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/fern/products/docs/pages/ai/fern-agent.mdx b/fern/products/docs/pages/ai/fern-agent.mdx index 7b43d66157..3e7107425c 100644 --- a/fern/products/docs/pages/ai/fern-agent.mdx +++ b/fern/products/docs/pages/ai/fern-agent.mdx @@ -206,15 +206,17 @@ Each run starts a fresh conversation from the prompt, works it in a single turn, Open **Automations**, select **New automation**, and describe what each run should look at and produce. Every run has your organization's docs, analytics, reader feedback, Ask Fern conversations, and search queries available to it. To start from an example, pick one from **Start from an example** and edit it. ```text Fix what readers complained about -Review the feedback readers left on our docs pages and fix the pages they -said were missing information, wrong, or unclear. Make the changes and open -a pull request. Ignore feedback about the product rather than the docs. +Review the feedback readers left on our docs pages and fix +the pages they said were missing information, wrong, or +unclear. Make the changes and open a pull request. Ignore +feedback about the product rather than the docs. ``` ```text Report on how the docs are doing -Report on how our docs are doing: the pages readers spend the most time on, -where they drop off, the searches that return nothing, and what changed -since last week. Do not change any docs. +Report on how our docs are doing: the pages readers spend +the most time on, where they drop off, the searches that +return nothing, and what changed since last week. Do not +change any docs. ``` From f115a427d29e5635dd02c1a250aa3960095f9b41 Mon Sep 17 00:00:00 2001 From: "devin.logan" Date: Mon, 31 Aug 2026 13:33:12 +0000 Subject: [PATCH 3/4] docs: document the automation prompt limit and Slack run reports Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- fern/products/docs/pages/ai/fern-agent.mdx | 6 +++++- fern/products/docs/pages/changelog/2026-08-31.mdx | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/fern/products/docs/pages/ai/fern-agent.mdx b/fern/products/docs/pages/ai/fern-agent.mdx index 3e7107425c..70a5139ee4 100644 --- a/fern/products/docs/pages/ai/fern-agent.mdx +++ b/fern/products/docs/pages/ai/fern-agent.mdx @@ -203,7 +203,7 @@ Each run starts a fresh conversation from the prompt, works it in a single turn, -Open **Automations**, select **New automation**, and describe what each run should look at and produce. Every run has your organization's docs, analytics, reader feedback, Ask Fern conversations, and search queries available to it. To start from an example, pick one from **Start from an example** and edit it. +Open **Automations**, select **New automation**, and describe what each run should look at and produce. Every run has your organization's docs, analytics, reader feedback, Ask Fern conversations, and search queries available to it. To start from an example, pick one from **Start from an example** and edit it. A prompt holds up to 2,000 characters. ```text Fix what readers complained about Review the feedback readers left on our docs pages and fix @@ -231,6 +231,10 @@ Choose daily or a day of the week, a time of day, and the timezone that time is Select **Run now** instead of waiting for the schedule, since running by hand leaves the next scheduled run where it was. Runs take a few minutes, and **Past runs** lists each one with a link to its conversation, where the report and any pull request are. + + +With Fern Agent [connected to Slack](#setup), every finished run is reported in Slack: the automation's name, whether the run finished or failed, and a link to its conversation. The report is a direct message to whoever created the automation, which requires their Slack account to be linked to `@Fern`. Set **Slack notifications** on the automation to name a channel that receives the report instead when it isn't. + Everyone in your organization sees every automation, and only its creator can change, delete, or run one. Turning an automation off keeps its prompt and history, while deleting it discards both — pull requests its runs opened are unaffected. An organization can keep up to 10 automations, and run history covers the last 30 days. diff --git a/fern/products/docs/pages/changelog/2026-08-31.mdx b/fern/products/docs/pages/changelog/2026-08-31.mdx index f31f2e2c7a..e39f8174ab 100644 --- a/fern/products/docs/pages/changelog/2026-08-31.mdx +++ b/fern/products/docs/pages/changelog/2026-08-31.mdx @@ -4,6 +4,6 @@ You can now put Fern Agent on a schedule. An automation is a prompt Fern Agent works daily or weekly with nobody present: it reviews your reader feedback, unanswered Ask Fern questions, search queries, or analytics, reports back what it found, and opens a pull request when the prompt asks it to change the docs. -Create one on the **Automations** page in the [Fern Dashboard](https://dashboard.buildwithfern.com/), or describe the recurring work you want in the Fern Agent chat panel or in Slack. **Run now** shows what a run comes back with before the first scheduled one. +Create one on the **Automations** page in the [Fern Dashboard](https://dashboard.buildwithfern.com/), or describe the recurring work you want in the Fern Agent chat panel or in Slack. **Run now** shows what a run comes back with before the first scheduled one, and Fern reports every finished run in Slack to whoever scheduled it. From 7da026ec18c01932d934adac4959eda10263e020 Mon Sep 17 00:00:00 2001 From: Devin Logan Date: Mon, 31 Aug 2026 10:07:07 -0400 Subject: [PATCH 4/4] update --- fern/products/docs/pages/ai/fern-agent.mdx | 38 +++++++++---------- .../docs/pages/changelog/2026-08-31.mdx | 4 +- 2 files changed, 20 insertions(+), 22 deletions(-) diff --git a/fern/products/docs/pages/ai/fern-agent.mdx b/fern/products/docs/pages/ai/fern-agent.mdx index 70a5139ee4..ca61149798 100644 --- a/fern/products/docs/pages/ai/fern-agent.mdx +++ b/fern/products/docs/pages/ai/fern-agent.mdx @@ -197,31 +197,17 @@ What Fern Agent adds is context on your organization and more places to work fro ## Automations -An automation is a prompt Fern Agent works on a schedule, with nobody present. Create one on the **Automations** page of the [Fern Dashboard](https://dashboard.buildwithfern.com/), or describe the recurring work in the chat panel or Slack and Fern Agent sets it up. +Create an automation on the **Automations** page of the [Fern Dashboard](https://dashboard.buildwithfern.com/), or describe the recurring work in the chat panel or Slack and Fern Agent sets it up. Each run starts a fresh conversation from the prompt, works it in a single turn, and reports back on what it did, found, or skipped. An automation only changes the docs when the prompt explicitly requests it. -Each run starts a fresh conversation from the prompt, works it in a single turn, and closes with a report on what it did, what it found, and what it skipped. The prompt decides whether a run changes anything: runs report back unless the prompt asks for a change, as in "make the change and open a pull request". +### Setup -Open **Automations**, select **New automation**, and describe what each run should look at and produce. Every run has your organization's docs, analytics, reader feedback, Ask Fern conversations, and search queries available to it. To start from an example, pick one from **Start from an example** and edit it. A prompt holds up to 2,000 characters. - -```text Fix what readers complained about -Review the feedback readers left on our docs pages and fix -the pages they said were missing information, wrong, or -unclear. Make the changes and open a pull request. Ignore -feedback about the product rather than the docs. -``` - -```text Report on how the docs are doing -Report on how our docs are doing: the pages readers spend -the most time on, where they drop off, the searches that -return nothing, and what changed since last week. Do not -change any docs. -``` +Open **Automations**, select **New automation**, and describe what each run should look at and produce. Every run has your organization's docs, analytics, reader feedback, Ask Fern conversations, and search queries available to it. A prompt holds up to 2,000 characters. -Select **Authorize** and complete the browser prompt. A run acts with the Fern permissions of whoever created the automation, read again each time a run uses them, so an unattended run needs that person's authorization first. One authorization covers all your automations. +Select **Authorize** and complete the browser prompt. A run acts with the Fern permissions of whoever created the automation, so an unattended run needs that person's authorization first. One authorization covers all your automations. @@ -233,12 +219,26 @@ Select **Run now** instead of waiting for the schedule, since running by hand le -With Fern Agent [connected to Slack](#setup), every finished run is reported in Slack: the automation's name, whether the run finished or failed, and a link to its conversation. The report is a direct message to whoever created the automation, which requires their Slack account to be linked to `@Fern`. Set **Slack notifications** on the automation to name a channel that receives the report instead when it isn't. +With Fern Agent [connected to Slack](#setup), every finished run is reported in Slack: the automation's name, whether the run finished or failed, and a link to its conversation. The report is a direct message to whoever created the automation, which requires their Slack account to be linked to `@Fern`. + +Set **Slack notifications** on the automation to name a channel that receives the report instead when it isn't. Everyone in your organization sees every automation, and only its creator can change, delete, or run one. Turning an automation off keeps its prompt and history, while deleting it discards both — pull requests its runs opened are unaffected. An organization can keep up to 10 automations, and run history covers the last 30 days. +### Examples + + +Review the feedback readers left on our docs pages and fix the pages they said were missing information, wrong, or unclear. Make the changes and open a pull request. Ignore feedback about the product rather than the docs. + + +
+ + +Report on how our docs are doing: the pages readers spend the most time on, where they drop off, the searches that return nothing, and what changed since last week. + + ## Privacy and data handling Fern Agent acts with your own Fern permissions on every surface, so it reads and edits only the sites, analytics, and organization data your account can already see. Requests are scoped to a single session: the prompt, any Slack message or thread you tag it in, and attached files are stored to complete the task and aren't retained afterward. diff --git a/fern/products/docs/pages/changelog/2026-08-31.mdx b/fern/products/docs/pages/changelog/2026-08-31.mdx index e39f8174ab..a977529681 100644 --- a/fern/products/docs/pages/changelog/2026-08-31.mdx +++ b/fern/products/docs/pages/changelog/2026-08-31.mdx @@ -2,8 +2,6 @@ ai -You can now put Fern Agent on a schedule. An automation is a prompt Fern Agent works daily or weekly with nobody present: it reviews your reader feedback, unanswered Ask Fern questions, search queries, or analytics, reports back what it found, and opens a pull request when the prompt asks it to change the docs. - -Create one on the **Automations** page in the [Fern Dashboard](https://dashboard.buildwithfern.com/), or describe the recurring work you want in the Fern Agent chat panel or in Slack. **Run now** shows what a run comes back with before the first scheduled one, and Fern reports every finished run in Slack to whoever scheduled it. +You can now put Fern Agent on a schedule. Create an automation on the **Automations** page in the [Fern Dashboard](https://dashboard.buildwithfern.com/). You can also describe the recurring work in the chat panel or in Slack and Fern Agent will set up an automation. Each run reviews your reader feedback, unanswered Ask Fern questions, search queries, or analytics, reports back what it found, and opens a pull request when the prompt asks for a change.