@gentbajko/slopify 3.25.9 → 4.1.0

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

@@ -1,33 +1,33 @@
 # Publishing to YouTube
 
-Slopify never uploads or publishes for you: there is no YouTube sign-in and no upload API. Instead, **Prepare upload** lists everything YouTube Studio asks for, in the order it asks, with a Copy button for each value, for the long video and for every short. You upload in Studio in your own browser and press Publish yourself. The optional [Studio-Extension](Studio-Extension) can fill Studio's upload dialog from the same list.
+Slopify never uploads or publishes for you: there is no YouTube sign-in and no upload API. Instead, **Copy for YouTube Studio** lists everything YouTube Studio asks for, in the order it asks, with a Copy button for each value, for the long video and for every short. You upload in Studio in your own browser and press Publish yourself. The optional [Studio-Extension](Studio-Extension) can fill Studio's upload dialog from the same list.
 
-**Where to find it:** a finished project → **Prepare upload** (the next action, and in the **YouTube** section), Home → **Needs you** → **Prepare upload** on a video marked **Ready to upload**, or the Calendar's **Needs you** → **Prepare upload**. Settings → **YouTube Studio** holds the playlists, and each channel's **Brand** tab holds the links it uses.
+**Where to find it:** a finished project → **Copy for YouTube Studio**, in the heading of its **Video** part and of its **YouTube** part, or `Ctrl+K` → **Copy for YouTube Studio** on the project. Settings → **YouTube Studio and posting** holds the playlists, and each channel's **Name and look** tab holds the links it uses.
 
 ## Before your first upload
 
-1. Open **Settings → YouTube Studio**, press **Add playlist** and type each playlist exactly as it is called in Studio (up to 150 characters). Tick **On by default** for the ones every video goes into, then press **Save playlists**. The list is the default for every channel; pick a channel above it to give that channel its own list.
-2. Open **Channels** → your channel → **Brand** and, under **Channel links**, add any links your descriptions use, such as `Patreon` or `Discord`. See [Channels](Channels#channel-links).
-3. In **Settings → Voices**, turn on **Real person** for any voice cloned from, or made to sound like, a real person.
-4. In **Library → Prompts**, turn on **Draws photorealistic pictures** for any Image prompt whose style looks like real photos or film.
-5. Turn on **YouTube description** on Play (Outputs row) for new videos, so they come with a description, chapters and tags.
+1. Open **Settings → YouTube Studio and posting**, press **Add playlist** and type each playlist exactly as it is called in Studio (up to 150 characters). Tick **On by default** for the ones every video goes into, then press **Save playlists**. The list is the default for every channel; pick a channel above it to give that channel its own list.
+2. Open **Channels** → your channel → **Name and look** and, under **Channel links**, add any links your descriptions use, such as `Patreon` or `Discord`. See [Channels](Channels#channel-links).
+3. In **Settings → Voices**, turn on **Sounds like a real person** for any voice cloned from, or made to sound like, a real person.
+4. In **Prompts**, turn on **Draws photorealistic pictures** for any Image prompt whose style looks like real photos or film.
+5. Turn on **YouTube description** on Create (Extras row) for new videos, so they come with a description, chapters and tags.
 
 Steps 3 and 4 decide the AI use answer; see [AI use disclosure](#ai-use-disclosure).
 
 ## Upload a video
 
-1. Open the finished project and press **Prepare upload**. The button is available once the video has been made.
+1. Open the finished project and press **Copy for YouTube Studio**. The button is available once the video has been made.
 2. If the project has shorts, pick what to upload under **What to upload**: **Video**, **Short 1**, **Short 2** and so on. Each is uploaded to YouTube on its own, with its own title, description and tags.
 3. Open YouTube Studio in your browser and start an upload.
 4. Work down the list **In the order Studio asks**, using **Copy**, **Download** or **Open folder** on each row:
 
-| Step | What Prepare upload gives you |
+| Step | What Copy for YouTube Studio gives you |
 |---|---|
 | **Video file** | The file name, with **Download** and **Open folder** as small buttons. |
 | **Title** | The project's title (up to 100 characters), or the short's title. **Copy**. |
 | **Description** | The description with chapters and hashtags, links filled in. For a short: its description, the "Watch the full video:" line and its hashtags. **Copy**. |
 | **Thumbnail** | The thumbnail file, with **Open folder**. With three thumbnails: "The first under Thumbnail; all 3 in A/B Testing (beside the title)." Shorts have no thumbnail step, since Studio shows a frame of a short. |
-| **Playlist** | The project's channel's playlists from Settings → YouTube Studio (or the default list), or "None set". With more than one, each has a tick: tick the ones this project goes into (saved for this project; the others keep the defaults). **Copy**. |
+| **Playlist** | The project's channel's playlists from Settings → YouTube Studio and posting (or the default list), or "None set". With more than one, each has a tick: tick the ones this project goes into (saved for this project; the others keep the defaults). **Copy**. |
 | **Audience** | "No, it's not made for kids". |
 | **AI use (under Show more)** | **Yes** or **No**, with the reason. |
 | **Tags (under Show more)** | The tags, comma-separated. For a short, its hashtags without the `#`. **Copy**. |
@@ -38,18 +38,18 @@ Steps 3 and 4 decide the AI use answer; see [AI use disclosure](#ai-use-disclosu
 
 Below the list, the thumbnails are shown side by side as **A**, **B** and **C**, each with **Download**.
 
-With the extension installed and paired, press **Fill in YouTube Studio** instead of copying by hand. Each press queues the item under **Waiting for Studio**, so you can queue the video and its shorts and upload them one after another. While no extension is paired, Prepare upload shows how to install and pair it, with **Open YouTube Studio**. See [Studio-Extension](Studio-Extension). Prepare upload ends with "Slopify never publishes."
+With the extension installed and paired, press **Fill in YouTube Studio** instead of copying by hand. Each press queues the item under **Waiting for Studio**, so you can queue the video and its shorts and upload them one after another. While no extension is paired, Copy for YouTube Studio shows how to install and pair it, with **Open YouTube Studio**. See [Studio-Extension](Studio-Extension). Copy for YouTube Studio ends with "Slopify never publishes."
 
 ## When something isn't ready
 
-If a part isn't made yet, Prepare upload says so at the top under "Some of it isn't made yet." and tells you what to do, for example:
+If a part isn't made yet, Copy for YouTube Studio says so at the top under "Some of it isn't made yet." and tells you what to do, for example:
 
-- The video isn't made yet: let the Video stage finish (or use Continue the run), then open Prepare upload again.
-- No YouTube description is written: turn on **YouTube description** in Edit project → **Prompts** to have one written with chapters and tags.
-- The thumbnail isn't made yet, or only 1 of 3 thumbnails is made: regenerate the missing ones in the project's Images section.
+- The video isn't made yet: let the Video stage finish (or use Continue the run), then open Copy for YouTube Studio again.
+- No YouTube description is written: turn on **YouTube description** in **Edit settings** → **Extras** to have one written with chapters and tags.
+- The thumbnail isn't made yet, or only 1 of 3 thumbnails is made: make the missing ones in the project's Images part (**Make the thumbnail again**).
 - This project makes no thumbnail, so YouTube will pick a frame.
-- No playlist is set: set one in Settings → YouTube Studio.
-- A short isn't rendered yet.
+- No playlist is set: set one in Settings → YouTube Studio and posting.
+- A short isn't made yet.
 
 ## AI use disclosure
 
@@ -59,15 +59,15 @@ Studio asks every upload one question, behind **Show more**: whether AI was used
 2. Alters footage of a real event or place.
 3. Generates a realistic-looking scene that didn't actually occur.
 
-Selecting Yes adds YouTube's AI label to your video. YouTube does not ask for the label for clearly unrealistic content, minor edits such as colour or filters, or AI used for the script, title, thumbnail or captions.
+Selecting Yes adds YouTube's AI label to your video. YouTube does not ask for the label for clearly unrealistic content, minor edits such as color or filters, or AI used for the script, title, thumbnail or captions.
 
 Slopify answers **Yes only when one of those three cases applies**, and **No** otherwise. An AI narrator and stylised AI pictures on their own are none of the three. Each case is something you mark, and every mark is off until you set it:
 
 | Case | What you mark | Where |
 |---|---|---|
-| 1. A voice that imitates a real person | **Real person** on a voice cloned from, or made to sound like, a real person. A video or short narrated by that voice (the narration voice or any speaker) gets Yes. | Settings → **Voices**, the Real person column |
-| 2. Real footage that is altered | In Prepare upload's AI use step, the switch **The uploaded clip is real footage (filmed, not made by AI)** (or "The N uploaded clips are…"). It appears when the project's images include uploaded video clips. With it on, the video gets Yes when the Look's **Atmosphere** overlay (embers, dust or fog) is laid over them. A colour grade, vignette or grain alone counts as a minor edit and stays No. | Prepare upload, per project |
-| 3. Photorealistic AI pictures | **Draws photorealistic pictures** on an Image prompt whose style looks like real photos or film. A video whose images are drawn from such a prompt, or a short whose **Image style** is one, gets Yes. The Built-in shorts style is not photorealistic. | Library → **Prompts**, in the Image prompt's editor (save the prompt first) |
+| 1. A voice that imitates a real person | **Sounds like a real person** on a voice cloned from, or made to sound like, a real person. A video or short narrated by that voice (the narration voice or any speaker) gets Yes. | Settings → **Voices**, the Real person column |
+| 2. Real footage that is altered | In Copy for YouTube Studio's AI use step, the switch **The uploaded clip is real footage (filmed, not made by AI)** (or "The N uploaded clips are…"). It appears when the project's images include uploaded video clips. With it on, the video gets Yes when the Look's **Atmosphere** overlay (embers, dust or fog) is laid over them. A color grade, vignette or grain alone counts as a minor edit and stays No. | Copy for YouTube Studio, per project |
+| 3. Photorealistic AI pictures | **Draws photorealistic pictures** on an Image prompt whose style looks like real photos or film. A video whose images are drawn from such a prompt, or a short whose **Image prompt** is one, gets Yes. The Built-in shorts style is not photorealistic. | Library → **Prompts**, in the Image prompt's editor (save the prompt first) |
 
 The AI use step shows the answer and why, naming the case in YouTube's words, for example that the narration uses a named voice marked in Settings → Voices as imitating a real person. When none applies, it says No and lists what was checked.
 
@@ -75,7 +75,7 @@ Shorts are judged on their own: they show new pictures, never your uploaded clip
 
 ### Override per channel
 
-1. Open **Channels**, pick the channel and open its **Brand** tab.
+1. Open **Channels**, pick the channel and open its **Name and look** tab.
 2. At the top, set **YouTube AI disclosure**:
 
 | Setting | Answer |
@@ -88,24 +88,24 @@ It saves as you pick. A channel's Always Yes or Always No wins over every mark.
 
 ## Chapters and the description
 
-The description in Prepare upload is the same one the project page shows: your edits kept, `{{Name}}` links filled in from the project's channel's links (its **Brand** tab) and the project's own **Previous video**. The **YouTube description (.txt)** and **YouTube tags (.txt)** downloads on the project page are this same text.
+The description in Copy for YouTube Studio is the same one the project page shows: your edits kept, `{{Name}}` links filled in from the project's channel's links (its **Name and look** tab) and the project's own **Previous video**. The **YouTube description (.txt)** and **YouTube tags (.txt)** downloads on the project page are this same text.
 
 Its chapters are fitted to YouTube's rules first (the first at 0:00, at least three, each at least 10 seconds). When anything was changed, the Description step says what, in a line starting "Chapters adjusted for YouTube:". To change the text itself, edit it on the project page; see [YouTube-Description](YouTube-Description).
 
 ## Edit the description and tags before uploading
 
-Prepare upload shows what the project has; it has no editor of its own.
+Copy for YouTube Studio shows what the project has; it has no editor of its own.
 
-1. Close Prepare upload.
-2. In the project's **YouTube** section, press **Edit** beside Summary, Chapters, Hashtags or Tags, change it and save.
-3. For a link, paste it under **Previous video for this project** and press **Save links**, or add it under **Channel links** on the channel's Brand tab.
-4. Open Prepare upload again; it shows your edits.
+1. Close Copy for YouTube Studio.
+2. In the project's **YouTube** part, press **Edit** beside Summary, Chapters, Hashtags or Tags, change it and save.
+3. For a link, paste it under **Previous episode** in the project's YouTube part and press **Save**, or add it under **Channel links** on the channel's Name and look tab.
+4. Open Copy for YouTube Studio again; it shows your edits.
 
-A short's title, description and hashtags come from the shorts pick; to change which moments are used, see [Shorts](Shorts). Its full video line comes from **Full video link** in Edit project → **Shorts**.
+A short's title, description and hashtags come from the shorts pick; to change which moments are used, see [Shorts](Shorts). Its full video line comes from **Full video link** in **Edit settings** → **Extras** → **Shorts**.
 
 ## Three thumbnails
 
-With **Thumbnails** set to 3 on Play or in Edit project → Images, Slopify draws the thumbnail prompt twice more with a different composition each time, for YouTube's A/B Testing (it replaced Test & compare). Prepare upload lists all three. In Studio, set the first under **Thumbnail**, then add all three with the **A/B Testing** button beside the title. Each extra thumbnail costs one image. See [Play-Outputs](Play-Outputs).
+With **How many thumbnails** set to 3 on Create or in **Edit settings** → **Extras**, Slopify draws the thumbnail prompt twice more with a different composition each time, for YouTube's A/B Testing (it replaced Test & compare). Copy for YouTube Studio lists all three. In Studio, set the first under **Thumbnail**, then add all three with the **A/B Testing** button beside the title. Each extra thumbnail costs one image. See [Create: Extras](Create-Extras).
 
 ## Mark a video uploaded
 
@@ -119,7 +119,7 @@ Slopify does not check YouTube, so it can't know when you've published. After yo
 
 ## Tips
 
-- 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.
+- 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 Copy for YouTube Studio.
 - 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.

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

@@ -1,35 +1,35 @@
 # Recovery and Retries
 
-Provider calls fail now and then: a rate limit, a timeout, a dropped connection, a refused prompt. Slopify retries what time can fix by itself, waits for used-up CLI plans instead of failing, and for everything else puts one button on the project page that fixes the cause or walks you through it. Work already made is never thrown away.
+Calls to the services fail now and then: a rate limit, a timeout, a dropped connection, a refused prompt. Slopify retries what time can fix by itself, waits for used-up CLI plans instead of failing, and for everything else puts one button on the project page that fixes the cause or walks you through it. Work already made is never thrown away.
 
-**Where to find it:** a project → the next action panel in the right rail, and the failed step's own section.
+**Where to find it:** a project → the next action in the title row, and the failed step's own part.
 
 ## What happens when a call fails
 
-Slopify handles a failed provider call in three tiers:
+Slopify handles a failed call to a service in three tiers:
 
 | Tier | What happens | You see |
 | --- | --- | --- |
-| 1. Quick retries | The call is tried up to four times in about 40 seconds: the first try plus retries after 2, 8 and 30 seconds. A provider's own Retry-After (up to a minute) replaces the fixed wait. | Nothing; the step keeps running. |
-| 2. Waiting it out | If the quick retries run out on a failure time can fix, the step is not failed. It waits and runs again by itself, up to four more times, after about 2, 4, 8 and 16 minutes (about half an hour in all). Each wait is spread by a quarter either way, and is never shorter than the provider's Retry-After. | **Waiting to try again**: "Images will try again by itself at 14:05." No button; the run carries on when it does. |
+| 1. Quick retries | The call is tried up to four times in about 40 seconds: the first try plus retries after 2, 8 and 30 seconds. A service's own Retry-After (up to a minute) replaces the fixed wait. | Nothing; the step keeps running. |
+| 2. Waiting it out | If the quick retries run out on a failure time can fix, the step is not failed. It waits and runs again by itself, up to four more times, after about 2, 4, 8 and 16 minutes (about half an hour in all). Each wait is spread by a quarter either way, and is never shorter than the service's Retry-After. | **Waiting to try again**: "Images will try again by itself at 14:05." No button; the run carries on when it does. |
 | 3. Failed | When the waits are used up, or the failure is one time cannot fix, the step fails and says why. | **Failed**, the error, and a fix-it or **Try ... again** button. |
 
 ### What is waited out
 
-- Rate limits (HTTP 429 and each provider's own rate-limit errors).
+- Rate limits (HTTP 429 and each service's own rate-limit errors).
 - Timeouts.
-- Dropped calls: a connection that never reached the provider or broke mid-answer, a provider server error (5xx), or a CLI the system killed mid-run.
+- Dropped calls: a connection that never reached the service or broke mid-answer, a server error at the service (5xx), or a CLI the system killed mid-run.
 
 ### What is never retried
 
 - A refusal by a content filter.
-- A key the provider rejected, or no key saved.
-- A request the provider does not support.
+- A key the service rejected, or no key saved.
+- A request the service does not support.
 - A lost CLI submission (Slopify cannot tell whether the CLI already did the work).
 
-These are the provider's final answer, and retrying would only spend your money again.
+These are the service's final answer, and retrying would only spend your money again.
 
-A provider asking for a wait longer than an hour (a daily quota) is reported as a failure rather than waited out.
+A service asking for a wait longer than an hour (a daily quota) is reported as a failure rather than waited out.
 
 ### Time limits per call
 
@@ -39,7 +39,7 @@ A provider asking for a wait longer than an hour (a daily quota) is reported as
 | Image | 300 seconds |
 | Image animated into a clip | 900 seconds |
 
-A call that passes its limit is stopped (a streamed call when it sends nothing for that long), and the message says so, for example "The AI model did not answer within 120 seconds. It may be overloaded: wait a few minutes, then use Try again, or choose another model in the Providers section of Edit project."
+A call that passes its limit is stopped (a streamed call when it sends nothing for that long), and the message says so, for example "The AI model did not answer within 120 seconds. It may be overloaded: wait a few minutes, then use Try again, or choose another model in Edit settings → Article → Written by."
 
 ### Waits survive a restart
 
@@ -49,11 +49,11 @@ The wait is saved in the database, so quitting or restarting Slopify keeps it: t
 
 When Claude Code, Codex or Antigravity says your plan allowance is used up, the call does not fail: it waits. Slopify stores the reset time for that CLI, and every call to it, from any project, waits until two minutes after the reset. Without a stated reset time it checks again every 30 minutes.
 
-The next action panel shows **Waiting for limits**, for example "Waiting for Codex limits (resets at 14:00)." with "Nothing to do: the run carries on by itself when they reset, and work that does not need Codex keeps going." There is nothing to press. A reset on another day shows the weekday (`Tue 14:00`); with no reset time, it says "(checking again at 14:30)"; with two plans, "Waiting for Codex and Claude limits".
+The project's state reads **Waiting for limits**, and the note under the title says, for example "Waiting for Codex limits (resets at 14:00)." with "Nothing to do: the run carries on by itself when they reset, and work that does not need Codex keeps going." There is nothing to press. A reset on another day shows the weekday (`Tue 14:00`); with no reset time, it says "(checking again at 14:30)"; with two plans, "Waiting for Codex and Claude limits".
 
-The same words appear everywhere the project shows up: on Home under Running now, on its row in Projects and on the Calendar, so you can tell a waiting run from a stuck one without opening it.
+The same words appear everywhere the project shows up: on Home under Running, on its row in Projects and on the Calendar, so you can tell a waiting run from a stuck one without opening it.
 
-- Other providers are not held up, and a waiting call holds no place in the provider queue.
+- Other services are not held up, and a waiting call holds no place in the service's queue.
 - The wait survives a restart: a stage that was waiting when Slopify stopped waits on the stored reset again at the next start.
 - A project paused or canceled meanwhile is left alone.
 
@@ -61,15 +61,15 @@ See [AI CLIs](AI-CLIs) and [Costs and Run Cost](Costs-and-Run-Cost) for the plan
 
 ## Fix-it buttons
 
-A failed step's fix becomes the project's next action, shown in the right rail and beside the step in its section. The mapping lives in one place in the code, so the page always offers the same fix for the same failure.
+A failed step's fix becomes the project's next action, shown in the title row and beside the step in its part. The mapping lives in one place in the code, so the page always offers the same fix for the same failure.
 
-| Failure | What the panel says | Button | What to do |
+| Failure | What the page says | Button | What to do |
 | --- | --- | --- | --- |
 | A CLI is signed out or its sign-in expired | "Codex is signed out, so images stopped." | **Copy sign-in command**, then **Check again** | See [Sign a CLI in again](#sign-a-cli-in-again) below. |
 | A content filter refused an image or thumbnail prompt | "A content filter refused a prompt, so images stopped." | **Soften and retry** | See below. |
-| A content filter refused any other prompt | "A content filter refused a prompt, so the article stopped." | **Edit the prompt** | Opens Edit project so you can reword it, then try again. |
-| The model was retired | "The model for images is no longer offered." | **Switch model** | Opens Edit project; pick another model in **Providers**, save, and try again. |
-| A key was rejected, or none is saved | "The provider did not accept its key, so narration stopped." | **Open Settings → Providers → *provider*** | Paste a current key, save, then come back and try again. |
+| A content filter refused any other prompt | "A content filter refused a prompt, so the article stopped." | **Edit the prompt** | Opens Edit settings so you can reword it, then try again. |
+| The model was retired | "The model for images is no longer offered." | **Switch model** | Opens Edit settings; pick another model (under **Written by**, **Read by** or **Images by**), save, and try again. |
+| A key was rejected, or none is saved | "The service did not accept its key, so narration stopped." | **Open Settings → Keys & services → *service*** | Paste a current key, save, then come back and try again. |
 | The disk is full | "The disk is full, so the video stopped." | **Free space** | Opens Settings → Backup & storage, which shows what uses the space and offers **Keep outputs only** per finished project. Then try again. |
 | Anything else | "Images stopped with an error." | **Try images again** | Trying again keeps everything already made. |
 
@@ -96,20 +96,20 @@ For a refused image or thumbnail prompt, **Soften and retry** asks first ("Softe
 2. The new wording streams onto the step as it is written.
 3. The image is drawn from it and keeps it as its prompt.
 
-The AI call and the new image are charged like any other. Press **Keep the prompt** to back out and edit it yourself in **Edit project → Images**.
+The AI call and the new image are charged like any other. Press **Keep the prompt** to back out and edit it yourself in **Edit settings** → **Images**.
 
 ## Try again
 
-**Try ... again** (for example **Try the article again**, **Try images again**) runs the failed step again. It does not ask first, because it destroys nothing: the pieces and outputs already made stay where they are and are reused.
+**Try ... again** (for example **Try the article again**, **Try images again**) runs the failed step again. It does not ask first, because it destroys nothing: the pieces and files already made stay where they are and are reused.
 
 ## Done with problems
 
-A failed step stops only the steps that need its output. The video never reads the thumbnail, so a failed thumbnail leaves the video rendering. When the run's main output was made (the video; the narration when there is no video; the article when there is neither) but another step failed, the project ends **Done with problems** instead of **Failed**. Each failed step shows its error and its fix.
+A failed step stops only the steps that need what it makes. The video never reads the thumbnail, so a failed thumbnail leaves the video being made. When the run's main result was made (the video; the narration when there is no video; the article when there is neither) but another step failed, the project ends **Done with problems** instead of **Failed**. Each failed step shows its error and its fix.
 
 ## 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 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.
+- A project that has unfinished work nothing will start on its own reads **Stopped** in its title row, 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.
 
@@ -120,17 +120,17 @@ A failed step stops only the steps that need its output. The video never reads t
 - **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).
+A canceled run's AI checks waiting for an agent stop, and never pass on their own. See [Pauses and Checks](Reviews-and-Checkpoints#your-own-ai-agent-as-the-checker).
 
-## Checkpoints and paused runs
+## Pauses 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 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 pause holds the run after a step so you can check what it made. While held, the project shows **Waiting for your review** and an **Approve and make the …** button; nothing after it runs until you approve. Pauses are stored with the project, so a restart does not lose them; when you save a new version, a pause whose work changed asks for your review again (its card in **Edit settings** → **Pauses and checks** says "What it was made from has changed. Look at the current version before approving."). See [Pauses and Checks](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
 
-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.
+When a step fails while another step of the run is waiting (for an agent's check, your approval at a pause, or the day of a video made ahead), 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
 
@@ -142,14 +142,14 @@ When an update or install cannot finish, Slopify puts the previous version back.
 
 - If a step keeps failing with the same error after **Try again**, open **Error details** and follow what it says. Most messages name the exact screen to fix it in.
 - Rate limits usually clear by themselves; you rarely need to do anything.
-- A kept output from an earlier revision is still in **History** if a remake goes wrong. See [Editing a Project](Editing-a-Project#history-and-saved-revisions).
+- A file from an earlier version is still under **Edit settings** → **Versions** if making it again goes wrong. See [Editing a Project](Editing-a-Project#versions).
 
 ## Related pages
 
 - [Troubleshooting](Troubleshooting)
 - [Project Page](Project-Page)
 - [Editing a Project](Editing-a-Project)
-- [Providers and Keys](Providers-and-Keys)
+- [Keys and Services](Providers-and-Keys)
 - [AI CLIs](AI-CLIs)
-- [Reviews and Checkpoints](Reviews-and-Checkpoints)
+- [Pauses and Checks](Reviews-and-Checkpoints)
 - [Agents (MCP)](Agents-MCP)

package/dist/tutorials/Remote-Access.md

@@ -0,0 +1,63 @@
+# Remote Access
+
+Open Slopify on your phone, tablet or laptop while it runs on your computer. Slopify uses the [Tailscale](https://tailscale.com) already installed on that computer: one switch, and Tailscale serves Slopify's page at an `https://` address that only devices signed in to your tailnet can open.
+
+**Where to find it:** Settings → **General** → **Remote access** → **Open on my other devices (Tailscale)**.
+
+Default: off.
+
+## Before you start
+
+- Tailscale is installed and signed in on the computer Slopify runs on, and on the device you want to use.
+- Your tailnet has **MagicDNS** and **HTTPS Certificates** turned on: in the Tailscale admin console open **DNS** (login.tailscale.com/admin/dns), turn on MagicDNS if it is off, then under **HTTPS Certificates** press **Enable HTTPS**. Slopify tells you when this is missing.
+- On Linux, Tailscale lets only root or its *operator* change serve settings. Allow your user once with `sudo tailscale set --operator=$USER`.
+
+## Turn it on
+
+1. Open Settings → **General** → **Remote access**.
+2. Turn on **Open on my other devices (Tailscale)**.
+3. The address appears, for example `https://mypc.tail1234.ts.net`, with **Copy address** and a QR code.
+4. On your phone, scan the QR code with the camera (or open the address in its browser). The phone must be signed in to the same tailnet.
+
+Slopify itself keeps listening only on this computer (`http://127.0.0.1:6969`). Tailscale receives the https request on your tailnet address and passes it to that local address.
+
+## Turn it off
+
+Turn off **Open on my other devices (Tailscale)** on the computer Slopify runs on. Slopify removes the serve setting it added, and nothing else.
+
+A page opened through the remote address shows the switch but can't change it: remote access is turned on or off only on the computer itself.
+
+## What stays private
+
+- **Tailnet only, never the public internet.** Slopify uses Tailscale *Serve*, never *Funnel*. Slopify has no login and holds your service keys, so a public address is never an option: Slopify never runs `tailscale funnel`, and it refuses every request that Tailscale marks as coming through Funnel, even if someone turns Funnel on by hand.
+- **Agents stay on this computer.** `/mcp` (agents) and `/mcp/assistant` (the in-app assistant) answer only requests made on the computer Slopify runs on. Remote access is for the Slopify page alone. Agents can read the setting (`get_remote_access`) but can't turn it on or off, and neither can the assistant.
+- **The page does almost everything it does at home.** A device on your tailnet is you, so the remote page can do what the page on the computer does, paid work included: starting runs, template samples, Compare models and Make samples for all spend from the same daily sample budgets and plans as at home. What sets up the computer itself stays there: saving or removing service keys, a CLI's path, importing a backup, installing updates, Start with this computer, moving the Files or backup folder, clean-ups that delete files and the assistant's **Allow**. Each is refused over the tailnet with where to do it instead.
+- **Only your account.** While remote access is on, a request through Tailscale from any account other than the one that turned it on is refused.
+- **Only the page at the address you opened.** A change is accepted only from the Slopify page at the very address the browser opened for that request, so a web page at any other address can't make one through your browser. **Open folder** on a remote device opens the folder on the computer Slopify runs on.
+
+## When Slopify stops and starts
+
+The address works while Slopify runs. When Slopify stops, it removes its serve setting, so the address never points at a port that another program could take while Slopify is stopped; opening it then shows Tailscale's own error. When Slopify starts with the switch on, it adds the address back by itself. If Slopify was stopped without warning (a crash, a power cut), the next start replaces what was left.
+
+## Your own serve settings
+
+Slopify changes only the one serve setting it added, and only while it is still exactly what Slopify set. If you already serve something on HTTPS port 443 (even Slopify itself, set up by hand), Slopify leaves it alone and offers **Use port 8443**, which gives Slopify its own address such as `https://mypc.tail1234.ts.net:8443`. Or remove yours with `tailscale serve --https=443 off` and press **Check again**.
+
+Slopify served by your own `tailscale serve`, or behind a reverse proxy such as Caddy or nginx, keeps working without the switch: the page saves settings and starts work as it does through Slopify's own address. The same things stay on the computer itself (keys, updates and the rest above), agents still connect only at `http://127.0.0.1:<port>/mcp`, and a proxy on a name other than a `ts.net` address needs that name in `SLOPIFY_ALLOWED_HOSTS` (see [Install](Install)).
+
+## What the notices mean
+
+| Notice | What to do |
+| --- | --- |
+| Tailscale isn't installed on this computer | Install it from [tailscale.com/download](https://tailscale.com/download), sign in, then press **Check again**. |
+| Tailscale is installed but not running | Open the Tailscale app and connect, or run `tailscale up`, then **Check again**. |
+| Tailscale is signed out | Open the Tailscale app and sign in, or run `tailscale up`. |
+| Your tailnet has no HTTPS certificates | Admin console → **DNS**: turn on MagicDNS, then **Enable HTTPS** under HTTPS Certificates. |
+| Tailscale won't let your user change its serve settings | Linux: `sudo tailscale set --operator=$USER` once, then **Check again**. |
+| HTTPS port 443 is already used by another serve setting | **Use port 8443**, or remove the other setting with `tailscale serve --https=443 off`. |
+| Tailscale Funnel was on for Slopify's address | Slopify removed its address. Turn Funnel off with `tailscale funnel --https=<port> off`, then **Check again**. |
+| The switch is on, but Slopify's address isn't in Tailscale right now | Someone removed it outside Slopify: press **Check again** to add it back. |
+
+## Docker
+
+From inside a container Slopify can't set up Tailscale on the computer itself, so the switch is unavailable there. Start Slopify with `npx @gentbajko/slopify` to use it, or set Tailscale up yourself on the host: `tailscale serve --bg --https=443 http://127.0.0.1:6969` (use Slopify's published port). Set up that way, the address isn't one Slopify made, so updating Slopify, opening folders and the YouTube Studio settings work only on the computer itself.