From 80582e5740e7b9b93adfadc81ebe123fa67c3862 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 24 Jul 2026 20:52:34 +0000 Subject: [PATCH] docs: explain how automations fit with the agent and CLI --- automations/index.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/automations/index.mdx b/automations/index.mdx index d362cd8c7..4ddf38f9f 100644 --- a/automations/index.mdx +++ b/automations/index.mdx @@ -14,6 +14,16 @@ Automations run the agent automatically on a schedule, in response to pushes to When an automation runs, the agent reads your project content and any connected repositories, then follows the prompt to make updates. +## How automations fit with the agent and CLI + +Automations, the [agent](/agent), and the [`mint`](/cli/commands) CLI all run the same underlying agent, but you reach for them in different situations: + +* **[Agent](/agent)**: Interactive. You send a prompt from the dashboard, editor, GitHub, or Slack when you want the agent to work on something right now. Best for one-off writing and updates that need a human in the loop from the start. +* **Automations**: Unattended. The agent runs on your behalf on a trigger you configure—a schedule, a push, or an integration event—without anyone kicking it off each time. Best for recurring maintenance work like translations, changelogs, or keeping content in sync with source code. +* **[`mint automations`](/cli/commands#mint-automations) CLI**: Scripted. Create, list, run, and delete the same automations from your terminal so they can live in CI pipelines, release scripts, or local tooling. The dashboard remains the easiest way to configure and monitor runs. + +You can mix all three on the same project. For example, use an automation to keep translations in sync on every merge, use the CLI to trigger a changelog run from your release pipeline, and use the agent interactively when you need to write a new guide. + Use automations that run on a schedule for recurring tasks, like publishing changelogs or improving content based on users' conversations with the [assistant](/assistant).