Skip to content

v0.9.2

Choose a tag to compare

@github-actions github-actions released this 20 Nov 22:15
· 14 commits to main since this release
  • MCP server: four new tools. create_explainer (a case explainer from a topic and sources, or one continuous animation), dub_video, list_videos and publish_video (previews by default; it posts only when dry_run is false, to your Upload-Post account or your own YouTube channel). The MCP server could only clip and make idea shorts before.
  • Browser app: a Publish videos card (pick any finished video of any run, filter by tall, wide or square, preview it, edit title, description and tags, publish through Upload-Post or direct to your own YouTube channel, or use a file from this PC), a Settings card (keys, upload defaults, YouTube connect) instead of the accordion, and Publish later: queue a video for a time you type; the app sends it while open.
  • Packaging: the Mermaid checker (remotion-video/scripts/check_mermaid.mjs) is now included in the wheel and the source archive, so a pip install can check diagrams before drawing them.
  • README and demo page: the Highlights video (a long video cut to its best moments in story order) is listed; MCP Docker check expects the 9 tools.
  • README: leads with everything ShortsFlow makes (clips, case explainers, animated explainers, idea-to-video, recaps, dubs, publishing), not only clipping; new case-explainer section.
  • Browser app, Settings: Connect YouTube directly. Choose the Google OAuth client file, press Connect YouTube (the Google sign-in opens in the browser on this PC, once), and publish to your own channel as private, unlisted or public, from the Publish box or automatically after a run; several channel slots; no third party. Real uploads have not been tried with a live Google account, only with fakes.
  • Case explainer: a news template (the headline, what happened in order, who says what side by side, what to watch next; every claim attributed, no side taken); use it with --case theme=newsroom for a news look.
  • Sources: a page that shows no text until its JavaScript runs (news and patch-note sites such as dota2.com) is now opened in the headless Chrome the video renderer already uses, on this PC, and its rendered text is read; this only happens for a page that would otherwise be skipped as empty. Page text is now read as statements and bullets with menus, language pickers, version lists and footers dropped, so the first part of a long page is no longer navigation.
  • Mermaid: a diagram the model wraps in JSON is unwrapped (it was missed before, and the section silently fell back to Manim); a fallback now says why in the log; sequence diagrams reveal one message at a time with the participants always visible, and their type size is set at render time.
  • Case explainer: Mermaid diagrams. The model can draw a section as any Mermaid diagram type; it is parsed by Mermaid itself (in Node, no browser) with a 6-node limit and held to the sources, a problem goes back to the model once, and a diagram that still fails falls back to the plain flow. Mermaid places everything, so nothing can overlap; the video draws it in the glass panel with large type, steps revealed in order, the current one glowing, and a camera that follows chains longer than four steps. The "how it happened" sections of the case, postmortem and explainer templates are diagrams by default. Manim is unchanged. --mode CASE review text has a DIAGRAM: block.
  • Case video layout: every scene is measured and fitted into the room between its heading and the caption bar (AutoFit), and the caption zone is one shared definition (captionZone), so a long caption or long labels can no longer overlap a scene whatever the topic; timeline labels grow away from the line; landscape animations use a wider panel and a two-row chain; a hook line on the cover. scripts/layout_stress.py writes a worst-case script to check a layout change against.