@gentbajko/slopify 3.25.9 → 4.1.0

package/dist/slices/youtube/answer.js

@@ -1,4 +1,6 @@
 import { z } from "zod";
+import { jsonBetween } from "../../kernel/json-answer.js";
+import { editSettings } from "../../kernel/ports/settings-places.js";
 import { alternativeTitles, descriptionMaxCharacters, hashtagsMax, minChapterSeconds, minChapters, pinnedCommentMaxCharacters, tagMaxCharacters, tagsMaxCharacters, titleMaxCharacters, } from "./model.js";
 import { parseTimestamp, youtubeTimestamp } from "./timestamps.js";
 import { keepsShape, titleShapeRule } from "./titles.js";
@@ -52,7 +54,7 @@ const answerSchema = z.object({
     pinnedComment: z.string(),
     titles: z.array(z.string()),
 });
-const fix = "Try again, or choose another model in Edit project → Providers.";
+const fix = `Try again, or choose another model in ${editSettings.writer}.`;
 // Reads and checks the model's answer. The reason is the sentence the stage shows; the
 // provider wrapper's `check` asks the model again while attempts remain.
 export function checkDescriptionAnswer(text, durationSeconds, 
@@ -60,7 +62,7 @@ export function checkDescriptionAnswer(text, durationSeconds,
 title = "", 
 // Its pattern, whose fixed wording the other titles keep.
 shape) {
-    const parsed = answerSchema.safeParse(jsonOf(text));
+    const parsed = answerSchema.safeParse(jsonBetween(text, "{", "}"));
     if (!parsed.success)
         return {
             ok: false,
@@ -239,17 +241,3 @@ function checkTags(raw) {
         return broke(`the tags come to ${String(length)} characters, over YouTube's ${String(tagsMaxCharacters)}`);
     return { ok: true, value: tags };
 }
-// The object in the answer, wherever the model put it: bare, in a ```json fence, or after a
-// sentence of its own.
-function jsonOf(text) {
-    const start = text.indexOf("{");
-    const end = text.lastIndexOf("}");
-    if (start === -1 || end <= start)
-        return undefined;
-    try {
-        return JSON.parse(text.slice(start, end + 1));
-    }
-    catch {
-        return undefined;
-    }
-}

package/dist/slices/youtube/edits-repo.js

@@ -4,7 +4,7 @@
 import { z } from "zod";
 import { defaultChannelId } from "../channels/model.js";
 import { channelById, projectChannelId } from "../channels/repo.js";
-import { readSetting, writeSetting } from "../settings/repo.js";
+import { readJsonSetting, writeSetting } from "../settings/repo.js";
 import { chapterNotice, fitChapters } from "./chapters.js";
 import { composeDescription, descriptionFields, resolveFields, shownFields, splitDescription, } from "./edits.js";
 import { fillPlaceholders, mergeLinks } from "./placeholders.js";
@@ -36,18 +36,9 @@ export function writeDescriptionEdits(db, projectId, edits, updatedAt) {
      ON CONFLICT(project_id) DO UPDATE SET fields_json=excluded.fields_json,links_json=excluded.links_json,updated_at=excluded.updated_at`).run(projectId, JSON.stringify(edits.fields), JSON.stringify(edits.links), updatedAt);
 }
 export function readChannelLinks(db) {
-    const value = readSetting(db, channelLinksKey);
-    if (value === undefined)
-        return [];
     // A hand-edited row that no longer parses reads as no links rather than breaking the page;
     // saving the list in Settings writes a good one again.
-    try {
-        const parsed = linksSchema.safeParse(JSON.parse(value));
-        return parsed.success ? parsed.data : [];
-    }
-    catch {
-        return [];
-    }
+    return readJsonSetting(db, channelLinksKey, linksSchema, []);
 }
 export function writeChannelLinks(db, links) {
     writeSetting(db, channelLinksKey, JSON.stringify(links.map((link) => ({ name: link.name.trim(), url: link.url.trim() }))));
@@ -68,7 +59,7 @@ export function readChannelLinksFor(db, channelId) {
 // the generated text, the chapters fitted to YouTube's rules (`chapters.ts`; the last one's
 // length only checked when the video's length is given), placeholders filled from the
 // project's and its channel's links (one with no link stays as typed). For anything that hands
-// the description on, such as Prepare upload and the downloads. `chapterNotice` says what the
+// the description on, such as Copy for YouTube Studio and the downloads. `chapterNotice` says what the
 // fitting changed.
 export function effectiveDescription(db, projectId, generated) {
     const edits = readDescriptionEdits(db, projectId);

package/dist/tutorials/AI-CLIs.md

@@ -2,7 +2,7 @@
 
 Slopify can write the text with the Claude Code, Codex or Antigravity command-line tools, and draw the images with Codex, using the sign-in you already have. You need no API key for those steps, and their calls count toward your plan's limits instead of costing per call.
 
-**Where to find it:** Settings → Providers → the **Text** list (Claude Code CLI, Codex CLI, Antigravity CLI) and the **Images** list (Codex CLI).
+**Where to find it:** Settings → Keys & services → the **Writing services** list (Claude Code CLI, Codex CLI, Antigravity CLI) and the **Image services** list (Codex CLI).
 
 ## What each tool does
 
@@ -15,7 +15,7 @@ Slopify can write the text with the Claude Code, Codex or Antigravity command-li
 
 Codex text and Codex images share one sign-in, one executable path and one plan allowance.
 
-Codex CLI must be version 0.149.1 or newer. An older Codex shows **Needs attention** and says to update it.
+Codex CLI must be version 0.149.1 or newer. An older Codex shows **Needs fixing** and says to update it.
 
 ## Set up a CLI
 
@@ -24,11 +24,11 @@ Codex CLI must be version 0.149.1 or newer. An older Codex shows **Needs attenti
    - Claude Code: `claude auth login`
    - Codex: `codex login`
    - Antigravity: run `agy` and sign in with your Google account (a browser opens; over SSH it shows a URL and a code).
-3. Open **Settings → Providers** (reload the page if it was already open).
-4. Pick the tool in the **Text** or **Images** list. Its row should say **Ready**, and its setup shows **Installed, version …** and the **Command** Slopify runs.
-5. Choose **Check all** to confirm it is signed in.
+3. Open **Settings → Keys & services** (reload the page if it was already open).
+4. Pick the tool in the **Writing services** or **Image services** list. Its row should say **Ready**, and its setup shows **Installed, version …** and the **Command** Slopify runs.
+5. Press **Check every service** to confirm it is signed in.
 
-On the very first launch, before any key is saved, Slopify looks for all three tools. If it finds any, it says so and picks one for text on new Play drafts, preferring Claude Code, then Codex, then Antigravity, and Codex for images when found. The CLIs can't speak, but the narration needs no key either: without a voice key, the [System voice](Providers-and-Keys#the-system-voice) reads it with your computer's own speech. See [First-Launch-and-Welcome](First-Launch-and-Welcome).
+On the very first launch, before any key is saved, Slopify looks for all three tools. If it finds any, it says so and picks one for text on new Create drafts, preferring Claude Code, then Codex, then Antigravity, and Codex for images when found. The CLIs can't speak, but the narration needs no key either: without a voice key, the [System voice](Providers-and-Keys#the-system-voice) reads it with your computer's own speech. See [First-Launch-and-Welcome](First-Launch-and-Welcome).
 
 ## Antigravity CLI: what is different
 
@@ -41,21 +41,21 @@ It works differently from the Gemini CLI in a few ways:
 - **No timeout of its own.** `agy` waits as long as the model needs; Slopify's own stall checks end a run that stops making progress.
 - **Busy messages are retried.** When several calls run at once, Google can answer that its capacity for the model is used for the moment. A reset of 5 minutes or less is retried by itself within seconds; a longer reset is handled as a plan limit and the run waits for it.
 - **Its sign-in is checked with `agy models`.** Slopify runs the command: if it lists models, the CLI is **Signed in**; if it says "Please sign in", the CLI is signed out and the check gives the command to run (`agy`); anything else shows as unknown. `GEMINI_API_KEY` is not read.
-- **Old model ids are gone.** Models come from `agy models`. A project that still names a Gemini CLI model such as `gemini-2.5-pro` stops with "The chosen model is not available…" until you pick a new one in **Edit project → Providers**. A saved path to a program still called `gemini` is refused: clear it or set the Antigravity CLI path in Settings → Providers.
+- **Old model ids are gone.** Models come from `agy models`. A project that still names a Gemini CLI model such as `gemini-2.5-pro` stops with "The chosen model is not available…" until you pick a new one under **Written by** in **Edit settings** → **Article**. A saved path to a program still called `gemini` is refused: clear it or set the Antigravity CLI path in Settings → Keys & services.
 
 ## Row states
 
 | State | Meaning |
 |---|---|
 | **Ready** | Found, new enough and not reporting a sign-in problem. |
-| **Needs attention** | Found, but something is wrong (for example an old Codex version). The detail says what. |
+| **Needs fixing** | Found, but something is wrong (for example an old Codex version). The detail says what. |
 | **Not found** | Not on PATH, or not at the saved path. |
 
 ## Set the executable path
 
 Slopify finds each tool on PATH, the list of folders your terminal searches. Set a path when the tool is installed somewhere else, or you have more than one copy.
 
-1. Pick the tool in **Settings → Providers**.
+1. Pick the tool in **Settings → Keys & services**.
 2. Choose **Change path**.
 3. In **Executable path**, type the absolute path to the program file, without quotes or arguments. Leave it blank to go back to finding it on PATH.
 4. Choose **Save path**. Slopify checks the tool answers before saving; a folder or a missing file is refused with the reason.
@@ -67,7 +67,7 @@ Slopify finds each tool on PATH, the list of folders your terminal searches. Set
 
 ## Check the sign-in
 
-**Check all** (Settings → Providers) asks each tool:
+**Check every service** (Settings → Keys & services) asks each tool:
 
 - **Installed**: found, with its version.
 - **Signed in**: Slopify asks each CLI directly. If one is signed out, the line tells you the command to run (`claude auth login`, `codex login` or `agy`). For Antigravity CLI it runs `agy models`: a model list means signed in, "Please sign in" means signed out (run `agy`), and anything else is shown as unknown.
@@ -79,20 +79,20 @@ If a run fails because a tool's sign-in expired, the project offers **Copy sign-
 
 ## Pick a model and thinking level
 
-A CLI's model list comes from the tool installed on your computer, not from the model catalogue. On Play:
+A CLI's model list comes from the tool installed on your computer, not from the model catalogue. On Create:
 
-1. Pick the tool as the text provider (or Codex CLI for images).
+1. Pick the tool as the **Service** under **Written by** (or Codex CLI under **Images by** for images).
 2. Pick a **Text model** from the list. The refresh button beside it (**Refresh models**) asks the tool for its current list; **Custom ID** lets you type a model the list does not show.
-3. If the model offers it, pick **Thinking** (text) or **Effort** (images). **Model default** leaves it to the tool. The levels come from the model: for example Low, Medium, High and Xhigh. Higher levels can write or draw more carefully, but take longer and use more of your plan.
+3. If the model offers it, pick **Thinking** (text) or **Effort** (images). **Model default** leaves it to the tool. The levels come from the model: for example Low, Medium, High and Extra high. Higher levels can write or draw more carefully, but take longer and use more of your plan.
 
-If a model is missing when a run reaches it, the run stops with "The chosen model is not available in the AI command-line tool on your computer." Update the tool, or pick another model in **Edit project** under Providers, then **Continue the run**. A thinking level the model does not support stops the same way.
+If a model is missing when a run reaches it, the run stops with "The chosen model is not available in the AI command-line tool on your computer." Update the tool, or pick another model in **Edit settings** (under **Written by**, or **Images by** for Codex images), then **Continue the run**. A thinking level the model does not support stops the same way.
 
 ## Codex images
 
 Codex draws each image as its own job.
 
 - **Codex default** runs with the tool's own defaults: no model and no effort on the command line.
-- Any other model is one of Codex's own models (the same list the Codex text provider shows), run with the **Effort** you pick. With a chosen model or effort, or a reference picture to match, the agent may look at its work and redraw it.
+- Any other model is one of Codex's own models (the same list Codex shows as a writing service), run with the **Effort** you pick. With a chosen model or effort, or a reference picture to match, the agent may look at its work and redraw it.
 - Each image may take several minutes; the time limit for one image is 30 minutes.
 - Up to 4 images are drawn at once.
 
@@ -106,16 +106,16 @@ The CLIs bill your subscription, which gives a share of a 5-hour and a weekly al
 - **Codex** is asked before and after each call. It reports whole percents, so a short run can show "under 1%".
 - **Antigravity** reports none.
 
-You see these on a project's **Run cost** tab, in the run's **Cost so far** panel, and on Home under **This week**. See [Costs-and-Run-Cost](Costs-and-Run-Cost).
+You see these in a project's cost breakdown (**See the breakdown** on its cost line) and on Home under **This week**. See [Costs-and-Run-Cost](Costs-and-Run-Cost).
 
 When a tool says its allowance is used up, the run does not fail:
 
 1. Slopify stores the reset time the tool gave (per tool, not per project).
 2. Every call to that tool, from any project, waits until 2 minutes after the reset. Without a stated time, it checks again every 30 minutes.
-3. The project's status reads **Waiting for limits**, with a line such as "Waiting for Codex limits (resets at 14:00)." The same words show on Home's Running now, the Projects row and the Calendar.
+3. The project's status reads **Waiting for limits**, with a line such as "Waiting for Codex limits (resets at 14:00)." The same words show on Home's Running, the Projects row and the Calendar.
 4. When the reset passes, the run continues by itself.
 
-Other providers are not held up: a project whose narration uses a key carries on while its Codex images wait. The wait survives a restart; a project that was waiting when Slopify stopped resumes on the next start and waits again. A project you paused or canceled meanwhile is left alone.
+Other services are not held up: a project whose narration uses a key carries on while its Codex images wait. The wait survives a restart; a project that was waiting when Slopify stopped resumes on the next start and waits again. A project you paused or canceled meanwhile is left alone.
 
 Antigravity's quota is handled the same way ("Slopify waits and tries again later by itself").
 
@@ -125,14 +125,14 @@ A container cannot use the CLIs installed on your computer directly. On Linux, t
 
 1. Install and sign in to the CLIs on your computer first.
 2. Run the Docker installer (`npx @gentbajko/slopify@latest --docker`). If a CLI is found, it asks once whether to set up the helper. `--accept-host-cli` approves without asking; `--host-cli=off` skips it.
-3. In Settings → Providers the tools show **Managed on host**. Their path cannot be changed there.
+3. In Settings → Keys & services the tools show **Managed on host**. Their path cannot be changed there.
 
 What to know:
 
 - The helper runs as you, as the user service `slopify-cli-bridge.service`, and talks to the container over a private socket. No network port is opened and no sign-in is copied into Docker.
 - After you install, update or remove a CLI, run the Docker installer again so Slopify sees the change.
 - Run cost and plan-limit shares work the same as without Docker. An older helper may not pass them through, and the cost page then says the share is not known.
-- With the helper off, Settings shows the CLIs as unavailable. API-key providers still work.
+- With the helper off, Settings shows the CLIs as unavailable. Services with an API key still work.
 
 Check or turn off the helper:
 
@@ -141,17 +141,17 @@ systemctl --user status slopify-cli-bridge.service
 systemctl --user disable --now slopify-cli-bridge.service
 ```
 
-Turning it off leaves Docker, your API providers, your data and your host sign-ins as they are. See [Docker](Docker).
+Turning it off leaves Docker, your keyed services, your data and your host sign-ins as they are. See [Docker](Docker).
 
 ## Tips
 
-- A CLI step on Play's estimate reads "$0 on your plan · ~$X via API": what the same tokens would cost with a key.
-- If your plan runs out often, split the work: keep text on a CLI and put images on a keyed provider, or the other way round.
-- Use **Check all** after updating a CLI; a newer tool can drop a model your template still names.
+- A CLI step on Create's estimate reads "$0 on your plan · ~$X via API": what the same tokens would cost with a key.
+- If your plan runs out often, split the work: keep the writing on a CLI and put images on a keyed service, or the other way round.
+- Use **Check every service** after updating a CLI; a newer tool can drop a model your template still names.
 
 ## Related pages
 
-- [Providers-and-Keys](Providers-and-Keys)
+- [Keys and Services](Providers-and-Keys)
 - [Models](Models)
 - [Costs-and-Run-Cost](Costs-and-Run-Cost)
 - [Docker](Docker)

package/dist/tutorials/Agents-MCP.md

@@ -1,35 +1,35 @@
 # Agents (MCP)
 
-Slopify has a built-in MCP server, so an AI agent on your computer (Claude Code, Codex, or any other client that speaks MCP over HTTP) can run Slopify for you. It can start and fix runs, edit the Library and your setup, answer reviews and approve checkpoints, with the same checks, costs and refusals as the buttons in the web page. Run on a schedule, an agent can clear everything that would otherwise wait for you, right up to **Ready to upload**. Uploading stays yours.
+Slopify has a built-in MCP server, so an AI agent on your computer (Claude Code, Codex, or any other client that speaks MCP over HTTP) can run Slopify for you. It can start and fix runs, edit your prompts, templates and settings, answer AI checks and approve pauses, with the same checks, costs and refusals as the buttons in the web page. Run on a schedule, an agent can clear everything that would otherwise wait for you, right up to **Ready to upload**. Uploading stays yours.
 
-**Where to find it:** **Settings → Connections → Agents (MCP)**.
+**Where to find it:** **Settings → AI agents**.
 
-## What the Agents tab shows
+## What the AI agents page shows
 
 | Part | What it is |
 | --- | --- |
-| **MCP address** | The address agents connect to: this install's address with `/mcp` after it, for example `http://127.0.0.1:6969/mcp`. It uses the address in your browser's address bar, so it matches your port and Docker's published port. |
+| **Address for agents (MCP)** | The address agents connect to: this install's address with `/mcp` after it, for example `http://127.0.0.1:6969/mcp`. It uses the address in your browser's address bar, so it matches your port and Docker's published port. |
 | **Claude Code** | The command that adds Slopify to Claude Code, with **Copy**. Run it once in a terminal. |
 | **Codex** | The lines that add Slopify to Codex, with **Copy**. 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 made by agents, newest first: what was done, the project or schedule it was done to, and when. Changes outside a project (a Library prompt, a schedule, a setting) are listed here too. "No agent has changed anything yet." when there are none. |
+| **What agents did** | The latest 20 changes made by agents, newest first: what was done, the project or schedule it was done to, and when. Changes outside a project (a prompt, a schedule, a setting) are listed here too. "No agent has changed anything yet." when there are none. |
 
 If the browser blocks the clipboard, **Copy** says so; select the line and copy it yourself.
 
 ## Connect an agent
 
-Slopify must be running. The address in these examples is the default (`127.0.0.1`, port `6969`); copy the real lines from the Agents tab.
+Slopify must be running. The address in these examples is the default (`127.0.0.1`, port `6969`); copy the real lines from Settings → AI agents.
 
 ### Claude Code
 
-1. Open **Settings → Connections → Agents (MCP)** and press **Copy** next to **Claude Code**.
+1. Open **Settings → AI agents** and press **Copy** next to **Claude Code**.
 2. Paste it in a terminal and run it:
 
    ```
    claude mcp add --transport http slopify http://127.0.0.1:6969/mcp
    ```
 
-3. Start Claude Code. `/mcp` there should list `slopify` as connected, and the Agents tab now shows when it last connected.
+3. Start Claude Code. `/mcp` there should list `slopify` as connected, and Settings → AI agents now shows when it last connected.
 
 ### Codex
 
@@ -49,7 +49,7 @@ Any MCP client that connects by URL over Streamable HTTP takes the same **MCP ad
 
 ### Docker
 
-Nothing changes: the agent runs on your computer and connects to the port Docker publishes, the same address you open Slopify at. Copy the lines from the Agents tab in that Slopify. See [Docker](Docker).
+Nothing changes: the agent runs on your computer and connects to the port Docker publishes, the same address you open Slopify at. Copy the lines from Settings → AI agents in that Slopify. See [Docker](Docker).
 
 ## No token, and what keeps web pages out
 
@@ -63,18 +63,18 @@ If you start Slopify with `--host 0.0.0.0` (or another address other computers c
 
 Anything you can do in the web page, except the few things listed under [What agents cannot do](#what-agents-cannot-do). That includes:
 
-- **Projects:** make projects from Play drafts and templates (after the same review and estimate you see), read them, edit them, pause, continue and cancel runs, **Keep as is**, move projects to another channel, delete and restore them.
-- **Fixing runs:** **Try ... again**, **Soften and retry**, remake a step or one item, regenerate a narration chunk, and **Choose what to remake**, with its estimate.
-- **Reviews:** answer reviews set to **External agent (MCP)**, **Overrule** or **Redo** flagged items, and approve review checkpoints.
-- **Planning:** release times, the posting plan, **Mark uploaded**, **Deleted on YouTube**, and **Prepare upload** up to **Ready to upload**.
+- **Projects:** make projects from Create drafts and templates (after the same review and estimate you see), read them, edit them, pause, continue and cancel runs, **Keep as is**, move projects to another channel, delete and restore them.
+- **Fixing runs:** **Try ... again**, **Soften and retry**, make a step or one item again, make a narration chunk again, and **Choose what to make again**, with its estimate.
+- **Pauses and checks:** answer AI checks set to **Your own AI agent**, **Overrule** or **Redo** flagged items, and approve pauses.
+- **Planning:** release times, the posting plan, **Mark uploaded**, **Deleted on YouTube**, and **Copy for YouTube Studio** up to **Ready to upload**.
 - **Schedules:** schedules, their topic lists, approving or turning down held topics, and **Prepare**.
-- **Library and setup:** prompts (with history), templates, channels and cast, Library import and export, and settings other than those below.
+- **Prompts, templates and settings:** prompts (with history), templates, channels and cast, export and import, and settings other than those below.
 - **Reading:** Home's work list, the calendar, costs and estimates, a project's files (pictures come back as pictures; audio and video as their address in Slopify), and the material a review looks at.
 - **Storage:** **Delete old versions** for one project.
 
-Agents never start paid work you could not see: before a remake they get the same **Choose what to remake** list with its estimate, and they must accept it, as you do. There is no extra budget or limit for agents; the costs are the same as yours. Actions with a consequence (deleting, for example) need the agent to confirm them, as a dialog asks you.
+Agents never start paid work you could not see: before anything is made again they get the same **Choose what to make again** list with its estimate, and they must accept it, as you do. There is no extra budget or limit for agents; the costs are the same as yours. Actions with a consequence (deleting, for example) need the agent to confirm them, as a dialog asks you.
 
-Agents and their tools use the same state words as the page: **Queued**, **Running**, **Paused**, **Waiting for your review**, **Waiting for the agent**, **Prepared**, **Stopped**, **Kept as is**, **Failed**, **Done**.
+Agents and their tools use the same state words as the page: **Queued**, **Running**, **Paused**, **Waiting for your review**, **Waiting for the agent**, **Waiting for its day**, **Stopped**, **Kept as is**, **Failed**, **Done**.
 
 ## What agents cannot do
 
@@ -82,7 +82,7 @@ Agents and their tools use the same state words as the page: **Queued**, **Runni
 | --- | --- |
 | Upload to YouTube, or send a video to the Studio extension (**Fill in YouTube Studio**, **Upload**) | Agents stop at **Ready to upload**. Uploading is yours; Slopify never makes a video public. See [Publishing to YouTube](Publishing-to-YouTube). |
 | The extension's automatic pinned comment setting | It posts comments in your name. |
-| Read or change provider keys, or make the extension's pairing token | They are credentials. Agents see each provider only as configured or missing. |
+| Read or change service keys, or make the extension's pairing token | They are credentials. Agents see each service only as set up or missing. |
 | Read the **Notification URL** | It can hold a secret (a private ntfy topic). Agents see only whether one is configured or missing, though they may set a new one. |
 | Backups: export, import, restore, and the daily backup settings | They are yours, in Settings → Backup & storage. |
 | Update Slopify, start at login, CLI paths, the extension's download | They are yours. |
@@ -97,27 +97,27 @@ Everything an agent changes is marked, so you can always tell its work from your
 
 | Where | What you see |
 | --- | --- |
-| Project page → **Project history** | Versions an agent saved end in **· by agent**, and **Done by agents** lists what agents did to the project (approvals, retries, verdicts and so on). |
+| Project → **Edit settings** → **Versions** | Versions an agent saved read **by agent**, and **Done by agents** lists what agents did to the project (approvals, retries, verdicts and so on). |
 | Review badges | **Passed by agent**, **Flagged by agent**, **Redone after agent review**, **Accepted by agent** (an agent pressed Overrule), **Made again by agent** (an agent pressed Redo). |
 | Notifications | A run an agent started ends its notices with **· started by agent** ("Started: *title* · by agent" in the browser); a flag from an agent's review ends with **· by agent**. |
-| Settings → Agents (MCP) | **What agents did**: the latest 20 changes of every kind. |
+| Settings → AI agents | **What agents did**: the latest 20 changes of every kind. |
 
-## The External agent reviewer
+## Your own AI agent as the checker
 
-Instead of paying a reviewer model, you can let your agent do the [automatic reviews](Reviews-and-Checkpoints#automatic-reviews).
+Instead of paying a model to check, you can let your agent do the [AI checks](Reviews-and-Checkpoints#ai-checks).
 
-1. On Play, open the **Reviews** row (or Edit project → **Reviews** on a project).
-2. Set **Who reviews** to **External agent (MCP)**. **Reviewer** and **Reviewer model** are greyed: the agent needs neither.
-3. Pick **Flag only** or **Flag and redo** for each stage, as usual. Picture stages (images, the thumbnail, shorts) work too: the agent is shown the pictures.
+1. On Create, open the **Pauses and checks** row (or **Edit settings** → **Pauses and checks** on a project).
+2. Under **Have an AI check the results**, open **Checker and stages** and set **Who checks** to **Your own AI agent**. **Checked by** goes away: the agent needs no service or model.
+3. Pick **Flag problems** or **Flag and redo**, for every stage or each on its own, as usual. Picture stages (images, the thumbnail, shorts) work too: the agent is shown the pictures.
 
 Reviews by the agent cost nothing and add nothing to the estimate. Redos it asks for cost what the item cost, as always.
 
 ### What happens during the run
 
 1. When an item is made, its review waits for the agent. What depends on it waits too; other work carries on.
-2. If nothing else holds the run, the project reads **Waiting for the agent** everywhere: its header, Projects, Home's **Running now** and the calendar. The project page says "An agent is reviewing what was made." with nothing to press. It is not in **Needs you**, no "Waiting for you" notice goes out and there is no **Continue the run** to press: it goes on by itself.
+2. If nothing else holds the run, the project reads **Waiting for the agent** everywhere: its title row, Projects, Home's **Running** and the calendar. The project page says "An agent is reviewing what was made." with nothing to press. It is not in **Needs you**, no "Waiting for you" notice goes out and there is no **Continue the run** to press: it goes on by itself.
 3. The agent reads the item and answers **pass** or **fail**. A fail needs at least one reason; at most 10 reasons, each up to 500 characters. The answer goes through the stage's mode, exactly like a model's verdict: a pass lets the work go on, a fail is flagged or made again.
-4. **The first answer wins.** If two agents answer the same review, the first one saved is kept and the second is refused ("This review was already answered"). The same goes for you: once an agent has pressed Overrule or Redo on a flagged item, or approved a checkpoint, pressing it yourself changes nothing and says it was already decided.
+4. **The first answer wins.** If two agents answer the same review, the first one saved is kept and the second is refused ("This review was already answered"). The same goes for you: once an agent has pressed Overrule or Redo on a flagged item, or approved a pause, pressing it yourself changes nothing and says it was already decided.
 
 ### If no agent answers
 
@@ -125,7 +125,7 @@ A review nobody answers **passes by itself 2 hours** after it began waiting. Its
 
 - **Paused project:** the review still passes at its two hours, but nothing runs until the run is continued.
 - **Canceled run:** its waiting reviews stop and never pass. If you (or an agent) take the step up again, the review asks again and waits a fresh two hours.
-- **Item made again meanwhile** (an edit or a remake): the old review is dropped and the new item gets its own.
+- **Item made again meanwhile** (after an edit, or made again on purpose): the old review is dropped and the new item gets its own.
 
 ## Paused and stopped runs
 
@@ -139,12 +139,13 @@ Slopify cannot wake an agent; the agent looks. Its work list is the `needs_atten
 | --- | --- |
 | An external review waiting for a verdict | Reads the item and answers. |
 | A flagged verdict nobody acted on | **Overrule** or **Redo**. |
-| A review checkpoint waiting for approval | Checks the work before it and approves. A checkpoint from the template's own **Before Video** is listed; a schedule's **Prepared** hold is not, since that one waits for its day. |
-| A failed step | Does what the error's own sentence says: for example regenerates narration chunk 5, accepts the **Choose what to remake** estimate, then continues the run. |
+| A pause waiting for approval | Checks the work before it and approves. A template's own **Pause after the images (before the video)** is listed; a schedule's made-ahead project (**Waiting for its day**) is not, since that one waits for its day. |
+| A failed step | Does what the error's own sentence says: for example makes narration chunk 5 again, accepts the **Choose what to make again** estimate, then continues the run. |
 | A paused run, or a run a restart **Stopped** | Continues it once nothing on the project still needs fixing. |
 | Topics a schedule holds for approval | Approves the ones that fit and turns down the rest. |
 | A video marked **Late · upload now** | Reports it. It cannot upload. |
-| A finishing touch the Studio extension failed (captions, end screen, pinned comment) | Reports it. Fixing it is the extension's or yours. |
+| A finishing touch the Studio extension failed (captions, end screen, pinned comment), or a post it couldn't fill on another site | Reports it. Fixing it is the extension's or yours. |
+| A post filled in another site's form, waiting for your **Post** (`post-due`) | Reports it. Posting is yours. |
 
 Projects that are **Kept as is** are not listed. Each entry says whether Slopify is already retrying or redoing it by itself (the agent leaves those alone and looks again later) and whether the agent can act on it at all.
 
@@ -152,13 +153,13 @@ The steps above are the **attend routine**. Slopify hands it to every agent that
 
 ## Tips
 
-- Pair the External agent reviewer with an hourly attend routine, and a [Notification URL](Notifications#get-notifications-on-your-phone-notification-url) so you hear when a review passed without an answer: that usually means the routine stopped running.
-- Check **What agents did** in the Agents tab now and then; each project's **Project history** has the full story for that project.
+- Pair your own AI agent as the checker with an hourly attend routine, and a [Notification URL](Notifications#get-notifications-on-your-phone-notification-url) so you hear when a review passed without an answer: that usually means the routine stopped running.
+- Check **What agents did** in Settings → AI agents now and then; each project's **Edit settings** → **Versions** has the full story for that project.
 - If an agent's request is refused because the project changed meanwhile, it reads the project again and retries once; you do not need to do anything.
 
 ## Related pages
 
-- [Reviews and Checkpoints](Reviews-and-Checkpoints)
+- [Pauses and Checks](Reviews-and-Checkpoints)
 - [Notifications](Notifications)
 - [Recovery and Retries](Recovery-and-Retries)
 - [Home and Projects](Home-and-Projects)

package/dist/tutorials/Assistant.md

@@ -0,0 +1,42 @@
+# Assistant
+
+The assistant is a chat inside Slopify. Ask it how something works, or ask it to do something on the screen you have open: "Which templates do I have?", "Why did this run stop?", "Make the thumbnail of this project again". It runs on your own **Claude Code** or **Codex** sign-in, so it uses your plan's allowance and is not added to a project's run cost.
+
+**Where to find it:** **Assistant** in the left rail, under the search field. On a phone it is the sparkle button in the top bar. It opens beside the page without moving it.
+
+## What it can and can't do
+
+- It uses only Slopify's own tools, the same ones an [agent](Agents-MCP) uses, with the same checks and refusals as the buttons in the page. It reads this guide to answer questions about Slopify.
+- It has no web search, can't run commands and can't open files on your computer. None of your Claude Code or Codex settings, hooks, plugins, skills, memory or other MCP servers are loaded for it. If the CLI ever offers it a tool from outside Slopify, Slopify stops the answer at once and says so.
+- It never answers an external AI check, exports or imports a backup, uploads a file from disk, empties the Trash or deletes old versions. Uploading to YouTube, backups, service keys and updates stay yours.
+- What it changes shows as **by assistant** in a project's **Versions**, in notifications and in **Settings → AI agents**.
+
+## It asks first
+
+Anything that costs money (starting a run or making something again, retrying a step, generating topics, a cast picture or a voice sample), anything a button would confirm, anything that removes something, and anything that sends to or changes an address outside Slopify (where notifications go, a test notification) waits for you. The chat shows a card with what it wants to do, for which project, and what it costs: the estimate **Choose what to make again** or Create's **See everything this run will do** showed, or "Slopify can't price it here" when there is none.
+
+| Press | What happens |
+| --- | --- |
+| **Allow** | The assistant does that one thing, with exactly what it asked for, and tells you what happened. An Allow is used once and only in that chat. |
+| **Don't** | Nothing runs. The assistant sees your answer the next time you write. |
+
+An ask you don't answer within 15 minutes expires: ask again, so it can check the cost again. The assistant can't press Allow for you; only a press in the page counts.
+
+## Using the chat
+
+- **Send** (or Enter) sends your message; Shift+Enter starts a new line. The answer streams in as it is written, with a line for each tool it used.
+- **Stop** ends the answer at once. Whatever it already did stays done. An answer that takes longer than 10 minutes is stopped for you.
+- **New chat** starts over. Each chat keeps its last 200 messages; the assistant remembers the last 20 of them (up to about 24,000 characters) when it answers.
+- **Runs on** picks the CLI: **Auto** takes Claude Code when it is installed and signed in, otherwise Codex.
+- It knows the page you have open: the project, schedule, channel or template on it, the section, and the rows you selected in a list.
+
+## When it can't start
+
+The panel says why and links to the fix:
+
+| Message | Fix |
+| --- | --- |
+| Neither Claude Code nor Codex is ready | Install one and sign in, then check it in **Settings → Keys & services** ([AI CLIs](AI-CLIs)). |
+| Claude Code (or Codex) is signed out | Run `claude auth login` (or `codex login`) in a terminal, then send your message again. |
+| Codex is too old | Update Codex CLI to the version the message names. |
+| The Docker version | The assistant isn't available in Docker: there the CLIs run on your computer through the host helper, which can't hand them Slopify's tools safely. Install Slopify with npm ([Install](Install)) to use it. |

package/dist/tutorials/Backups.md

@@ -1,6 +1,6 @@
 # Backups
 
-A backup is one `.tar` file with everything you made in Slopify: every project with its files and history, your library, templates, schedules, channels and settings. Make one by hand at any time with **Export everything**, or let Slopify write one every day. Bring one back with **Import a backup**. Provider keys are never included.
+A backup is one `.tar` file with everything you made in Slopify: every project with its files and versions, your prompts, templates, schedules, channels and settings. Make one by hand at any time with **Export everything**, or let Slopify write one every day. Bring one back with **Import a backup**. Provider keys are never included.
 
 **Where to find it:** **Settings → Backup & storage**: daily backups and Back up now, Export everything and Import a backup.
 
@@ -8,18 +8,18 @@ A backup is one `.tar` file with everything you made in Slopify: every project w
 
 | Included | Left out on purpose |
 |---|---|
-| Every project with its files and history, and its channel | Provider keys |
-| Automatic review verdicts and run cost of each project | The Notification URL |
+| Every project with its files and versions, and its channel | Service keys |
+| AI check verdicts and run cost of each project | The Notification URL |
 | Prompts, intros and outros, with their history | The Studio extension's pairing |
-| Document themes and uploaded fonts | The tutorial's progress |
-| Templates, schedules and Play drafts | The daily backups' folder and status |
+| PDF looks and uploaded fonts | The tutorial's progress |
+| Templates, schedules and Create drafts | The daily backups' folder and status |
 | Channels: brand kit, series brief, episode memory and AI disclosure settings, cast with pictures, end screen images, episode summaries, existing videos, and the last **Keep only titles containing** filter | The telemetry machine id |
-| Channel links and the provider defaults a new Play form starts with | State that only matters while this install runs: the queue, plan-limit waits |
+| Channel links and the service defaults a new Create draft starts with | State that only matters while this install runs: the queue, plan-limit waits |
 | AI use marks: voices marked as a real person, image prompts marked photorealistic, projects with real footage | |
 | Settings and usage history | |
 | The trash: trashed items come back still in the trash, with their original date | |
 
-After an import you add your provider keys again in [Providers and keys](Providers-and-Keys).
+After an import you add your provider keys again in [Keys and Services](Providers-and-Keys).
 
 ## Export everything (a backup right now, downloaded)
 

package/dist/tutorials/Calendar.md

@@ -1,46 +1,38 @@
 # Calendar
 
-The calendar shows the coming four weeks on one screen: what needs you, every scheduled run with the topic and title it will use, the projects running or finished on their day, and the batch queue. You can drag a topic to another day, move it to another schedule, add topics, and accept or reject topics Slopify suggested.
+The calendar shows the coming four weeks on one screen: how much needs you, every scheduled run with the topic and title it will use, the projects running or finished on their day, and the batch queue. You can drag a topic to another day, move it to another schedule, add topics, and accept or reject topics Slopify suggested.
 
-**Where to find it:** **Calendar** in the sidebar. It has two tabs: **Coming weeks**, described here, and **Schedules**, where you create, edit, pause and resume the schedules themselves (see [Schedules](Schedules)).
+**Where to find it:** **Calendar** in the rail. It has two tabs: **Coming weeks**, described here, and **Schedules**, where you create, edit, pause and resume the schedules themselves (see [Schedules](Schedules)).
 
 ## What the calendar shows
 
 The calendar starts on this week's Monday and shows four weeks, Monday to Sunday.
 
 - **Scheduled runs**, each with the project title it will make. A run shows **Queued** when a topic is lined up, **Needs a topic** when its topic is still waiting for your approval or for generation, and **Paused** when its schedule is paused.
-- **Needs you**, above the weeks: every project that is waiting on you or ready to upload (see below).
-- **Projects** running or finished on their day, with their state: **Running**, **Waiting for the agent**, **Paused**, **Queued**, **Waiting for your review**, **Prepared**, **Stopped**, **Kept as is**, **Failed**, **Done with problems**, **Done** or **Canceled**. A project waiting for a CLI plan says so, for example **Waiting for Codex limits (resets at 14:00)**.
-- **Batch queue**: projects waiting to start (see below).
+- **Needs you**, above the weeks: one line with Home's counts of what waits on you and what is ready to upload (see below).
+- **Projects** running or finished on their day, with their state: **Running**, **Waiting for the agent**, **Paused**, **Queued**, **Waiting for your review**, **Waiting for its day**, **Stopped**, **Kept as is**, **Failed**, **Done with problems**, **Done** or **Canceled**. A project waiting for a CLI plan says so, for example **Waiting for Codex limits (resets at 14:00)**.
+- **Waiting to start**: the batch queue, videos started together that wait their turn (see below).
 - **Suggested topics**, beside the weeks, for schedules that hold generated topics for approval.
 
-The calendar follows the channel picked in the sidebar, or shows every channel. See [Channels](Channels).
+The calendar follows the channel picked under **Showing:** in the page header, or shows every channel. See [Channels](Channels).
 
-Each queued run has **Prepare**, which makes its video ahead of the day and leaves only the render for the day; a prepared run shows **Prepared** and **Open**. See [Schedules](Schedules#prepare-a-video-ahead).
+Each queued run has **Make ahead**, which makes everything but its video now (and spends what the run costs) and leaves only putting the video together for its day; such a run shows **Waiting for its day** and **Open**. See [Schedules](Schedules#make-a-video-ahead).
 
 ## Needs you
 
-Above the weeks, **Needs you** lists what cannot move on without you, then what is ready to upload. Its heading counts them, for example "2 waiting for you · 1 ready to upload". It is hidden when there is nothing.
+Above the weeks, one line says what Home's **Needs you** and **Finished** count, in Home's words, for every project of the channel shown (not only the ones in these weeks), for example "1 decision · 1 failed · 2 ready to upload. Open Home to act on them.", with **Open Home**. Decisions are projects held at a pause, paused or **Stopped**; failed are the failed projects and the steps that failed beside a wait; ready to upload are finished videos not marked uploaded. It is hidden when there is nothing, and the bundled samples never count.
 
-| Item | Status | Button |
-| --- | --- | --- |
-| A failed project | **Failed** | **Open to fix** |
-| A project you paused | **Paused** | **Open to continue** |
-| A project a restart stopped before it finished | **Stopped** | **Open to continue** |
-| A project held at a review checkpoint, or with an automatic review that flagged an item and waits for **Overrule** or **Redo** | **Waiting for your review** | **Open to review** |
-| A finished video not marked uploaded | **Ready to upload** | **Prepare upload** |
-
-The bundled samples never show here. A press anywhere on an entry opens its project. See [Reviews and Checkpoints](Reviews-and-Checkpoints) and [Publishing to YouTube](Publishing-to-YouTube).
+Acting on them is Home's job: **Needs you** there lists each one with its button. The calendar keeps its space for what is planned. See [Home and Projects](Home-and-Projects), [Pauses and Checks](Reviews-and-Checkpoints) and [Publishing to YouTube](Publishing-to-YouTube).
 
 ## The batch queue
 
-Videos started together, such as extra videos queued from Play, run one at a time. **Batch queue** lists them in the order they run, numbered (**1 in line**, **2 in line**, …), each marked **Running now**, **Waiting its turn** or **Paused**. Its heading says how many are waiting to start. Pausing a queued project holds the whole queue; when one fails or is canceled, the next one starts. The batch queue is only shown on the calendar; Projects links here and has a **Queued** filter. It is hidden when nothing is queued.
+Videos started together, such as extra videos queued from Create, run one at a time. **Waiting to start** is the same list as Home's: the videos still to start, numbered in the order they start (**1.**, **2.**, …), each marked **Queued** (or **Paused**) with **Earlier**, **Later** and **Remove**. Its heading says how many there are; the one already running is on Home under **Running**. Pausing the started project holds the whole queue, and the list says so; when one fails or is canceled, the next one starts. It follows the channel shown under **Showing:**, and is hidden when nothing waits.
 
 ## Switch between weeks and a list
 
-Use **Calendar view** at the top:
+Use **Show the weeks as** at the top:
 
-- **Weeks** (the default) shows the four weeks as a grid.
+- **Grid** (the default) shows the four weeks as a grid.
 - **List** shows the same runs day by day, with buttons to move each topic.
 
 This browser remembers your choice.
@@ -64,10 +56,10 @@ The topic now runs with the other schedule's template.
 
 ## Add topics
 
-1. Press **Add to calendar**.
+1. Press **Add topics to a schedule**.
 2. Pick the **Schedule** the topics join. Only active and paused schedules are listed, each with the number of topics already queued.
 3. Type or paste **Topics, one per line**. Blank lines are skipped.
-4. Press **Add N topics** (the button counts them). **Keep the calendar as it is** closes the form without adding anything.
+4. Press **Add N topics** (the button counts them). **Cancel** closes the form without adding anything.
 
 The topics go to the end of the schedule's queue, in order, and take its next free runs. Each topic fills the schedule's topic keyword; every other keyword keeps its every-run value. To give topics their own values, edit the schedule's topics as a table on the **Schedules** tab (see [Schedules](Schedules)).
 
@@ -80,7 +72,7 @@ Schedules set to **Generate and hold for approval** list their suggestions under
 - **Queue** adds a topic to the end of that schedule's queue.
 - **Reject** drops it for good; it is never suggested again.
 - **Queue all** adds every suggestion of that schedule, in order.
-- **Suggest topics now** asks the schedule's LLM for more at once (one LLM call).
+- **Suggest topics now · 1 AI call** asks the schedule's AI for more at once.
 
 While Slopify is asking, the panel says so and the topics appear when it finishes. If the last try failed, the panel says so with the reason. When nothing is waiting it says **No suggestions are waiting.**
 
@@ -94,9 +86,9 @@ Editing a suggestion's words before approving it is done under **Topics waiting*
 
 - Use the list view if dragging is fiddly, for example on a touch screen or a narrow window.
 - A browser notification for new suggestions opens the calendar's **Suggested topics** when you click it. See [Notifications](Notifications).
-- `Ctrl+K` → **Add to calendar** works from any screen: it opens the calendar with the form. `G` then `C` goes to the calendar.
+- `Ctrl+K` → **Add topics to a schedule** works from any screen: it opens the calendar with the form. `G` then `C` goes to the calendar.
 - To change a schedule's queued topics one by one (rename, reorder, remove), use the **Schedules** tab. See [Schedules](Schedules#edit-the-queued-topics-in-place).
-- To start one video right now instead of waiting for a run, use [Play](Play-Overview).
+- To start one video right now instead of waiting for a run, use [Create](Create-Overview).
 
 ## Related pages