@gentbajko/slopify 3.16.0 → 3.18.0

package/dist/tutorials/Project-Page.md

@@ -39,6 +39,11 @@ The status beside the title reads one of:
 | **Done with problems** | The main output was made (the video, or the narration when there is no video, or the article when there is neither), but another step failed. Each failed step shows its error and its fix. |
 | **Failed** | A step failed and the main output was not made. |
 | **Canceled** | You canceled the run. Finished outputs are kept. |
+| **Waiting for your review** | A review checkpoint is holding the run for you to approve. |
+| **Waiting for the agent** | An [External agent](Agents-MCP#the-external-agent-reviewer) is reviewing what was made. It goes on by itself once the agent answers, or after 2 hours. |
+| **Prepared** | Made ahead by its schedule; only the video is left, for its day. See [Schedules](Schedules#prepare-a-video-ahead). |
+| **Stopped** | The run stopped before it finished (for example after a restart). Press **Continue the run**. |
+| **Kept as is** | What is left was set aside with **Keep as is** and won't run. Editing the project brings it back. |
 
 ## The next action button
 
@@ -49,7 +54,8 @@ The right rail always shows at most one button, named for what it will do. It is
 | The bundled sample project | Sample project | **Make my own copy** (the sample is read-only; your copy can be edited and made again) |
 | Paused | Paused | **Continue the run** |
 | A step failed and will not retry by itself | Failed | The step's fix-it button (for example **Copy sign-in command** with **Check again**, **Soften and retry**, **Edit the prompt**, **Switch model**), or **Try the article again**, **Try images again** and so on. See [Recovery and Retries](Recovery-and-Retries#fix-it-buttons). |
-| A checkpoint is holding the run | Waiting for you | **Approve and record the narration**, **Approve and make the images**, **Approve and render the video**, or **Approve the ...** when nothing waits on it |
+| A checkpoint is holding the run | Waiting for your review | **Approve and record the narration**, **Approve and make the images**, **Approve and render the video**, or **Approve the ...** when nothing waits on it |
+| An External agent is reviewing what was made | Waiting for the agent | No button. "An agent is reviewing what was made." The run carries on once the agent answers, and a review nobody answers passes by itself after 2 hours. |
 | A CLI plan limit is used up | Waiting for limits | No button. The line says, for example, "Waiting for Codex limits (resets at 14:00)." and that the run carries on by itself. |
 | A step is waiting to retry | Waiting to try again | No button. The line says the time it tries again. |
 | Running | Running | **Pause** |
@@ -84,7 +90,7 @@ A step that is waiting to retry or waiting for a CLI limit also stays held while
 2. Choose **Cancel the run…**.
 3. Confirm with **Cancel run**, or press **Keep running** to leave it alone.
 
-Canceling stops every running stage; finished outputs are kept. You can continue a canceled run later with **Continue the run**. A project has to be canceled (not running) before you can delete it from Projects.
+Canceling stops every running stage; finished outputs are kept. You can continue a canceled run later with **Continue the run**. If you took a step up again after canceling (**Try ... again**), Continue carries on only that work; see [Recovery and Retries](Recovery-and-Retries#cancel-then-continue). A project has to be canceled (not running) before you can delete it from Projects.
 
 ## The sections
 

package/dist/tutorials/Publishing-to-YouTube.md

@@ -122,6 +122,7 @@ Slopify does not check YouTube, so it can't know when you've published. After yo
 - Set the playlists once in Settings (per channel if your channels upload to different playlists), and tick the few a single video joins in its Prepare upload.
 - Upload the long video first, then paste its link as the shorts' **Full video link** so each short's description points to it.
 - If the AI use answer surprises you, read its reason: it names the voice, footage or prompt that made it Yes.
+- A connected [agent](Agents-MCP) can take a video as far as **Ready to upload** and mark it uploaded, but never uploads it or sends it to the extension: that stays yours.
 
 ## Related pages
 

package/dist/tutorials/Recovery-and-Retries.md

@@ -109,15 +109,28 @@ A failed step stops only the steps that need its output. The video never reads t
 ## After a crash or restart
 
 - A stage that was **running** when Slopify stopped is marked failed with the reason "interrupted". Nothing re-runs by itself: press **Try ... again**. If the project was paused at the time, the stage simply goes back to waiting.
-- A project that has unfinished work nothing will start on its own shows **Stopped** and **Continue the run**. Continuing makes only what is missing.
+- A project that has unfinished work nothing will start on its own reads **Stopped** on its header, in Projects and on Home, where it is listed under **Needs you** with **Continue the run** (and **Keep as is** to leave the rest unmade). The project page says "The run stopped before it finished." with the same button. Continuing makes only what is missing; everything made so far is kept. An [agent](Agents-MCP) running the attend routine may continue it for you.
 - Steps waiting to retry, or waiting for CLI limits, carry on by themselves after the restart.
 - A queued batch project waits its turn as before.
 
+## Cancel, then continue
+
+**Cancel** stops every step that has not finished; what was made is kept. Later:
+
+- **Continue the run** on the canceled project makes everything that is missing.
+- If you took one step up again after the cancel (with **Try ... again**), **Continue the run** carries on only that work. The steps you canceled stay canceled until you take them up too.
+
+A canceled run's reviews waiting for an agent stop, and never pass on their own. See [Reviews and Checkpoints](Reviews-and-Checkpoints#the-external-agent-reviewer).
+
 ## Checkpoints and paused runs
 
-A checkpoint holds the run before a step so you can check what came before it. While held, the project shows **Waiting for you** and an **Approve ...** button; nothing after it runs until you approve. Checkpoints are stored with the project, so a restart does not lose them; when you save a new revision, a checkpoint whose reviewed inputs changed asks for your review again (the Checkpoints view says "Inputs changed. Review the current revision before approving."). See [Reviews and Checkpoints](Reviews-and-Checkpoints).
+A checkpoint holds the run before a step so you can check what came before it. While held, the project shows **Waiting for your review** and an **Approve ...** button; nothing after it runs until you approve. Checkpoints are stored with the project, so a restart does not lose them; when you save a new revision, a checkpoint whose reviewed inputs changed asks for your review again (the Checkpoints view says "Inputs changed. Review the current revision before approving."). See [Reviews and Checkpoints](Reviews-and-Checkpoints).
+
+A paused project keeps everything. **Continue the run** picks up where it stopped. See [Project Page](Project-Page#pause-continue-and-cancel-a-run). A connected [agent](Agents-MCP) may continue any paused run once nothing else on it needs fixing; cancel instead of pausing if you want a run to stay put.
+
+## A failed step beside a wait
 
-A paused project keeps everything. **Continue the run** picks up where it stopped. See [Project Page](Project-Page#pause-continue-and-cancel-a-run).
+When a step fails while another step of the run is waiting (for an agent's review, your checkpoint, or a prepared run's day), the run is not over: the project still reads by what it waits for (**Waiting for the agent** or **Waiting for your review**), and the failed step shows on the page with its fix. Home lists it as a failed item too, and a "Step failed" notification goes out right away (see [Notifications](Notifications#step-failed)). The project reads **Failed** only once nothing else can go on.
 
 ## Updating while work runs
 
@@ -139,3 +152,4 @@ When an update or install cannot finish, Slopify puts the previous version back.
 - [Providers and Keys](Providers-and-Keys)
 - [AI CLIs](AI-CLIs)
 - [Reviews and Checkpoints](Reviews-and-Checkpoints)
+- [Agents (MCP)](Agents-MCP)

package/dist/tutorials/Reviews-and-Checkpoints.md

@@ -52,13 +52,15 @@ The checkpoint then says "Checkpoint approved. Work will run when its dependenci
 
 | Message | Meaning |
 | --- | --- |
-| "Images is held for your review. Its dependent work waits for this approval; independent work can continue." | Waiting for you. |
+| "Images is held for your review. Its dependent work waits for this approval; independent work can continue." | Waiting for you. The project reads **Waiting for your review**. |
 | "Inputs changed. Review the current revision before approving." | You edited something the held step uses. Check the new version before approving. |
 | "Authorized for this revision. Work can run when dependencies are ready and the project is resumed." | Approved; it runs when it can. |
 | "Checkpoint satisfied. Its reviewed work is complete." | Done. |
 
 If the project is paused, the panel says "The project is paused. Continue the run before approving held work." Pausing always applies on top of checkpoints.
 
+A checkpoint is approved once. If it was already approved (by you in another tab, or by an [agent](Agents-MCP)), approving again changes nothing and says so.
+
 ### Change checkpoints after the run started
 
 On the project page → **Checkpoints** → **Checkpoint choices**:
@@ -70,11 +72,12 @@ Only generated steps can have one. If the project was edited elsewhere in the me
 
 ## Automatic reviews
 
-A reviewer model checks each finished item and saves its verdict and reasons on the project page. Each review is a text-model call, counted in usage and in the estimate.
+A reviewer checks each finished item and saves its verdict and reasons on the project page. The reviewer is a model Slopify asks (each review is a text-model call, counted in usage and in the estimate), or an agent you connected (free; see [The External agent reviewer](#the-external-agent-reviewer)).
 
 | Option | What it does | Default / range |
 | --- | --- | --- |
-| **Reviewer** | Who runs the review model. Picture reviews (images, the thumbnail and shorts) need Claude Code or Codex, which can look at images; other providers review text only. | None |
+| **Who reviews** | **Model**: Slopify asks the reviewer model below, one paid call per item. **External agent (MCP)**: an agent connected in Settings → Connections → Agents (MCP) answers each review instead, at no API cost. | Model |
+| **Reviewer** | Who runs the review model (greyed for **External agent (MCP)**). Picture reviews (images, the thumbnail and shorts) need Claude Code or Codex, which can look at images; other providers review text only. | None |
 | **Reviewer model** | The model that judges each item. A stronger model catches more but costs more per review. It can differ from the model that wrote the text. | None |
 | **Redos per item** | How many times **Flag and redo** makes a failed item again before it keeps the last one and flags it. Each redo costs the item again plus one more review. | 2; 0 to 5 |
 
@@ -106,16 +109,28 @@ The prompt next to each mode is **Built-in** or a **Review** prompt from the Lib
 4. For each stage you want checked, pick **Flag only** or **Flag and redo**, and optionally a Review prompt.
 5. Check the estimate: each review adds one text-model call. Redos are not in the estimate; each costs what the item cost, at most the redos allowed.
 
+### The External agent reviewer
+
+With **Who reviews** set to **External agent (MCP)**, no model is called: each review waits for an agent connected to Slopify to answer it (see [Agents (MCP)](Agents-MCP)). Every stage can use it, picture stages included, since the agent is shown the pictures. It adds nothing to the estimate.
+
+- While a review waits, what depends on the item waits, as with any review. If nothing else holds the run, the project reads **Waiting for the agent** (header, Projects, Home's Running now, the calendar). It is not in **Needs you**, sends no "Waiting for you" notice and has no **Continue the run**: it goes on by itself.
+- The agent answers **pass** or **fail**. A fail needs at least one reason, at most 10, each up to 500 characters. The answer then follows the stage's mode like a model's verdict: **Flag only** flags it, **Flag and redo** makes it again up to **Redos per item**.
+- The first answer saved wins. A second answer to the same review is refused ("This review was already answered").
+- **No answer in 2 hours:** the review passes by itself. Its badge reads **Passed without review**, the work goes on and a notification says "Passed without review: no agent answered in 2 h". The deadline is saved, so it survives a restart. A paused project's review still passes at its deadline, but nothing runs until you continue the run.
+- **Canceled runs:** canceling stops the run's waiting reviews, and they never pass. Taking the step up again asks again, with a fresh two hours.
+
 ### Reviews on the project page
 
-Beside the article, the narration, the thumbnail and each short, and on each image tile, the verdict shows as **Review passed**, **Flagged by review**, **Waiting to be made again**, **Being made again**, **Redone after review** or **Accepted by you**, with the reasons. For a failed item nobody has acted on:
+Beside the article, the narration, the thumbnail and each short, and on each image tile, the verdict shows as **Review passed**, **Flagged by review**, **Waiting to be made again**, **Being made again**, **Redone after review** or **Accepted by you**, with the reasons. With the External agent reviewer, or when an agent acted on it, it reads **Passed by agent**, **Flagged by agent**, **Redone after agent review**, **Accepted by agent**, **Made again by agent**, or **Passed without review** when no agent answered in time. For a failed item nobody has acted on:
 
 - **Overrule** accepts it as it is.
 - **Redo** makes it again (a new version of the project, then the item and what depends on it are rebuilt), and it is reviewed again.
 
+A flagged item takes one decision. If it was already decided (by an agent, for example), pressing **Overrule** or **Redo** changes nothing and says how it was decided.
+
 Both buttons wait while other work on the project is running, with one exception: while a **Flag and redo** review's automatic redo is still waiting to start (**Waiting to be made again**), **Overrule** stays available and calls the redo off. The item is accepted as it is, the badge turns to **Accepted by you**, and the work waiting on it goes ahead. Once the redo has started, Overrule is greyed: "Slopify is already making this item again; wait for the new version".
 
-When an automatic review flags an item and keeps it (its redos ran out, or the stage is on **Flag only**), Slopify sends a **Review needs a decision** notification (see [Notifications](Notifications)), and the project shows in the Calendar's **Needs you** with **Open to review** (see [Calendar](Calendar#needs-you)). Everything that uses a reviewed item waits for its review, in the same way a checkpoint holds work. Reviewing the same output with the same reviewer and prompt again reuses the earlier verdict.
+When an automatic review flags an item and keeps it (its redos ran out, or the stage is on **Flag only**), Slopify sends a **Review needs a decision** notification (see [Notifications](Notifications)), and the project shows in the Calendar's **Needs you** with **Open to review** (see [Calendar](Calendar#needs-you)). When an agent's review flagged it, the notification ends in **· by agent**. Everything that uses a reviewed item waits for its review, in the same way a checkpoint holds work. Reviewing the same output with the same reviewer and prompt again reuses the earlier verdict.
 
 ## Checkpoints or reviews?
 
@@ -125,6 +140,7 @@ When an automatic review flags an item and keeps it (its redos ran out, or the s
 | Look at the images before the render | **Before Images** is too early; use **Before Video / export** |
 | Catch broken hands or stray text without watching every run | **Images** review, **Flag and redo** |
 | Run unattended on a schedule and fix things later | Reviews on **Flag only**, no checkpoints |
+| Have reviews done without paying a reviewer model | **External agent (MCP)** with an hourly agent routine; see [Agents (MCP)](Agents-MCP) |
 
 ## Tips
 
@@ -140,4 +156,5 @@ When an automatic review flags an item and keeps it (its redos ran out, or the s
 - [Recovery and Retries](Recovery-and-Retries)
 - [Prompts](Prompts)
 - [AI CLIs](AI-CLIs)
+- [Agents (MCP)](Agents-MCP)
 - [Costs and Run Cost](Costs-and-Run-Cost)

package/dist/tutorials/Schedules.md

@@ -95,7 +95,7 @@ Slopify makes the project now, exactly as the schedule would on the day (the tem
 On the scheduled day the schedule finds that project by its title and continues it instead of making another: the hold is lifted and the video, its captions, shorts and YouTube description are made. The same goes for an unfinished project you made yourself under the same title. A finished one counts as a video already made, and the day makes a new one.
 
 - You can open the prepared project and change anything before its day, for example with Edit project.
-- A **Before Video** checkpoint the template already has stays: the day waits for you to approve it.
+- A **Before Video** checkpoint the template already has stays: the day waits for you to approve it, and the project reads **Waiting for your review** and is listed under **Needs you** (and for a connected [agent](Agents-MCP)). A project held only by Prepare's own hold reads **Prepared** and is not listed as waiting anywhere: it waits for its day, not for you.
 - A setup that makes no video has nothing to hold back, so Prepare runs it to the end.
 - A schedule without topics gives every run the same title, so only a prepared project continues there.
 - The spend limit applies to Prepare as it does to a scheduled run.

package/dist/tutorials/Settings-Reference.md

@@ -11,6 +11,7 @@ Every section of Settings, what each control does and its default. Sections with
 | Connections | [Providers](#providers) | API keys, command-line tools, the system voice, health check | [Providers-and-Keys](Providers-and-Keys), [AI-CLIs](AI-CLIs) |
 | Connections | [Voices](#voices) | Voice IDs for narration | [Providers-and-Keys](Providers-and-Keys#add-a-voice) |
 | Connections | [Models](#models) | Model catalogue, retired models | [Models](Models) |
+| Connections | [Agents (MCP)](#agents-mcp) | The MCP address and setup lines for Claude Code and Codex, the last connection, what agents did | [Agents-MCP](Agents-MCP) |
 | Production defaults | [Production defaults](#production-defaults) | Silence gap, volume levelling for new runs | This page |
 | Notifications | [Notifications](#notifications) | Browser and phone notifications | [Notifications](Notifications) |
 | Publishing | [Channel links](#channel-links) | A pointer to each channel's own links | [Channels](Channels#channel-links) |
@@ -99,6 +100,20 @@ See [Providers-and-Keys](Providers-and-Keys#add-a-voice).
 
 Templates and schedules that pick a retired model are also flagged on their own rows, with the same **Switch to <model>**. See [Models](Models).
 
+## Agents (MCP)
+
+"Let an AI agent on this computer, such as Claude Code or Codex, run Slopify."
+
+| Control | What it does |
+|---|---|
+| **MCP address** | This install's address with `/mcp`, for example `http://127.0.0.1:6969/mcp`. No token: only requests from a web page at another address are refused. |
+| **Claude Code** → **Copy** | Copies `claude mcp add --transport http slopify <address>`. Run it once in a terminal. |
+| **Codex** → **Copy** | Copies the `[mcp_servers.slopify]` lines. Add them to `~/.codex/config.toml`. |
+| Last connected | When an agent last connected, or "No agent has connected yet." |
+| **What agents did** | The latest 20 changes agents made, with the project or schedule and the time. |
+
+There is nothing to turn on: the address works whenever Slopify runs. See [Agents (MCP)](Agents-MCP).
+
 ## Production defaults
 
 "How new runs pace the narration and level the volume."

package/dist/tutorials/Troubleshooting.md

@@ -127,7 +127,9 @@ If an install or update fails, the message names what failed and, in Docker, the
 | **Queued** | Other videos in the batch queue go first. The Calendar's **Batch queue** shows the order. |
 | **Waiting for limits** / "Waiting for Codex limits (resets at 14:00)" | A CLI plan is used up; the run waits and carries on after the reset time shown. |
 | **Waiting to try again** | A rate limit or timeout; it retries at the time shown. |
-| **Waiting for you** | A checkpoint is holding the run. Press **Approve ...**. |
+| **Waiting for your review** | A checkpoint is holding the run. Press **Approve ...**. |
+| **Waiting for the agent** | A review set to **External agent (MCP)** waits for your agent. Check the agent's routine is running; with no answer, the review passes by itself after 2 hours. See [Agents (MCP)](Agents-MCP). |
+| **Prepared** | Its schedule made it ahead; the video is made on its day. |
 | A step says **taking longer than usual** | It has run longer than the same step usually takes in your finished runs. It is still going; open **Live** to see whether text or images are still arriving. |
 | **Paused** | Press **Continue the run**. |
 | **Stopped** | The run was interrupted (for example by a restart). Press **Continue the run**. |

package/dist/tutorials/Your-First-Short.md

@@ -109,6 +109,7 @@ It is a normal project: you can edit the script, change an image, pick another v
 - Make a long video with more control: [Play Overview](Play-Overview).
 - Cut shorts from a long video automatically: [Shorts](Shorts).
 - Reuse the style: add the starter pack and pick its template on Play ([Templates](Templates)).
+- Let Claude Code or Codex look after your runs, fix failures and answer reviews: [Agents (MCP)](Agents-MCP).
 
 ## Tips
 

package/dist/tutorials/_Sidebar.md

@@ -49,6 +49,7 @@
 - [Schedules](Schedules)
 - [Calendar](Calendar)
 - [Notifications](Notifications)
+- [Agents (MCP)](Agents-MCP)
 - [Backups](Backups)
 
 **Channels**