The repo is "open-slide" with 8,942 stars, not "OpenSlide", and the browser comment loop only applies after you run /apply-comments
Watch on TikTok
This is a 36 second, 720x1280 vertical clip posted 2026-10-04 by @github.signals, channel nickname "Github Signals", carrying 26,600 views, 1,196 likes, 1,351 saves, 180 shares and 2 comments when the metadata was captured on 2026-10-05, scored to a track yt-dlp labels "original sound" credited to Github Signals. I read all 18 extracted frames at 2 second intervals and the full 91 word transcript. Every frame except the last is a single slow scroll down one browser screenshot, address bar reading github.com/open-slide/open-slide and tab title GitHub - open-slide/open-slide: A slide framework built for agen, with a persistent @GithubSignals watermark pill. The README hero image shows a dark card reading open-slide over The slide framework built for agents. and a terminal line $ npx @open-slide/cli init, above a black triangle logo and the text VERCEL INC. // 2026 OPEN SOURCE SOFTWARE PROGRAM. Below the open-slide H1 sit three shields.io badges reading STARS 8.8K, FORKS 621 and LICENSE MIT. The body text visible across frames reads The slide framework built for agents. Describe your deck in natural language — your coding agent writes the React. open-slide handles the canvas, scaling, navigation, hot reload, and present mode so the agent can focus on content. and Every slide renders into a fixed 1920 × 1080 canvas. Pages are arbitrary React components, not a constrained DSL., then a copyable code block npx @open-slide/cli init my-slide. Scrolling past Why open-slide and Highlights reveals Agent-native authoring with Works with any coding agent (Claude Code, Codex, Cursor, ...). The scaffolder ships with built-in skills:, the bullets /create-slide — drafts a deck end-to-end. Asks four scoping questions (topic & aesthetic, page count, text density, motion vs. static), picks an id, plans the structure, and writes the pages. and /slide-authoring — the technical reference for the 1920 × 1080 canvas, type scale, palette, and layout rules. The agent reads this before writing., then In-browser inspector with Click any element in the dev server and attach a comment — "make this red", "change to 'Open Slide Rocks'", "shrink the headline". Comments are persisted as @slide-comment markers in source. Run /apply-comments and the agent applies every pending edit, then clears the markers. and The loop: present → click to comment → /apply-comments → repeat., followed by Assets manager + svgl logo search and the start of Professional present mode. Burned-in captions run in sequence: OPENSLIDE / IS THE SLIDE / YOUR CODING / AGENT BUILD / THE ACTUAL / PRESENTATION. / IN PLAIN ENGLISH, / WRITES THE REACT / HANDLING EVERYTHING / FROM LAYOUT / TO ANIMATION. / IS THAT YOU / IN THE BROWSER, / MAKE THIS RED, / APPLIES THAT / CHANGE / TOUCHING THE CODE. / THE BORING RUNTIME / AND NAVIGATION, / A PROFESSIONAL, / FROM A ONE-LINE PROMPT. Frame 18 is a dark end card with a cartoon Octocat avatar and the text Follow for more open-source projects over @GithubSignals.
The spoken name is wrong, and the name it uses belongs to a 2010 pathology library
The narration opens with "OpenSlide is the slide framework that lets your coding agent build the actual presentation." Every frame on screen contradicts that spelling. The address bar reads github.com/open-slide/open-slide, the README H1 reads open-slide in lowercase with a hyphen, the install line reads npx @open-slide/cli init my-slide, and the project homepage is open-slide.dev. The GitHub API record for the repo returns full_name: open-slide/open-slide. The video's own description field gets this right and writes "open-slide"; only the voiceover collapses it.
The collapse matters because "OpenSlide" is already taken. openslide/openslide is a C library for reading virtual slide images, created 2010-08-09, LGPL-2.1 licensed, 519 stars, homepage openslide.org. It is the standard whole-slide image reader in digital pathology and it predates the React project by roughly sixteen years. Searching the spoken name will land a viewer on a microscopy I/O library, not a deck tool.
The in-browser comment loop is not automatic, and the README on screen says so
The transcript claims "you can click any element right in the browser, leave a comment like Make This Red, and the agent applies that change automatically without you touching the code." The caption APPLIES THAT CHANGE sits directly over the README text that disproves the word "automatically". The README states that comments "are persisted as @slide-comment markers in source" and that you "Run /apply-comments and the agent applies every pending edit, then clears the markers." It then spells the cycle out: "The loop: present → click to comment → /apply-comments → repeat."
So clicking an element writes a marker into your source file. A second, deliberate step invokes the agent. The claim "without you touching the code" is also loose, since the mechanism works by writing annotations into the code and the agent's edits land in files you own.
"A one-line prompt" is the README's own marketing line, and the same README lists four questions before anything gets written
The closing caption reads FROM A ONE-LINE PROMPT. The README does contain the sentence "From a one-line prompt to a polished deck, no boilerplate", so the video is quoting, not inventing. Two lines above that sentence, the same README describes /create-slide as a skill that "Asks four scoping questions (topic & aesthetic, page count, text density, motion vs. static), picks an id, plans the structure, and writes the pages." A one-line prompt starts the process. Four answers precede the first written page.
The framework handles the runtime, the agent writes the layout and the motion
The narration says the agent writes the React "handling everything from layout to animation", then says open-slide "handles all the boring runtime stuff like scaling and navigation". The split is real but drawn in the wrong place. The README assigns open-slide "the canvas, scaling, navigation, hot reload, and present mode". Layout is not handled by the framework; /slide-authoring is described as "the technical reference for the 1920 × 1080 canvas, type scale, palette, and layout rules" that "The agent reads this before writing", which makes layout a documented convention the agent follows. Animation is somewhere in between: open-slide.dev documents Page, Step, Transition and Morph as framework components, so the primitives ship with open-slide and the agent wires them up.
The badges on screen are a snapshot, and the project is about five months old
The frames show STARS 8.8K and FORKS 621. At the time of this check the GitHub API returned 8,942 stars and 632 forks, so the screenshot was accurate and the counts have drifted up since capture. LICENSE MIT is confirmed by the same API record and by the MIT license tab visible in the repo nav across every frame.
The repo was created 2026-04-26 and last pushed 2026-10-03, one day before this TikTok went up. It is TypeScript, topics agent, react, slides, with 133 open issues and 16 watchers. Releases show @open-slide/cli@2.0.0 and @open-slide/core@2.0.0 published 2026-09-26 and @open-slide/core@2.0.1 on 2026-09-27. The npm registry record puts @open-slide/cli@2.0.0 at 2026-09-26 13:57:52 UTC. The author is Yiwei Ho, GitHub handle 1weiho, based in Taiwan.
The VERCEL INC. // 2026 OPEN SOURCE SOFTWARE PROGRAM badge in the hero is a real affiliation, not decoration. It links to vercel.com/open-source-program, and open-slide appears in the Spring 2026 cohort alongside Sync UI, Tabularis, Artifact and Rallly. The program gives each project $3,600 in Vercel platform credits over three years, third-party service credits, and guidance from Vercel staff.
The 36 seconds skip most of what the README is selling
The clip scrolls past Assets manager + svgl logo search and stops at the top of Professional present mode, and the narration never mentions either. The README lists a presenter mode with "current/next slide preview, speaker notes, and a timer", an assets panel with svgl brand logo search, a slide manager with folders and drag-and-drop reordering, and export to "static HTML, PDF & PPTX" where the PPTX path "runs entirely in the browser and turns each page into native text boxes, shapes, and images". PPTX export is the feature most likely to decide whether a working team can adopt this, and it does not appear in the video at all.
Key Takeaways
- Correction: the project is
open-slide, lowercase and hyphenated, not "OpenSlide". The video's voiceover says "OpenSlide"; every frame and the video's own description sayopen-slide. - Correction: "OpenSlide" is an unrelated C library for reading virtual slide images in digital pathology, created 2010-08-09, LGPL-2.1, 519 stars, at openslide/openslide. It predates the React project by about sixteen years.
- Partial correction: the browser comment is not applied "automatically". Clicking writes an
@slide-commentmarker into your source, and you then run/apply-commentsto make the agent act. The README text visible in frames 10 through 17 states this. - Partial correction: a "one-line prompt" triggers
/create-slide, which asks four scoping questions (topic and aesthetic, page count, text density, motion vs. static) before writing pages. - Partial correction: the framework does not handle layout. It handles canvas, scaling, navigation, hot reload and present mode. Layout rules live in the
/slide-authoringreference the agent reads. Animation primitives (Page,Step,Transition,Morph) do ship with the framework. - Verified:
STARS 8.8K,FORKS 621andLICENSE MITin the frames match the GitHub record, which read 8,942 stars and 632 forks at check time. - Verified: the
VERCEL INC. // 2026 OPEN SOURCE SOFTWARE PROGRAMbadge is accurate. open-slide is in the Vercel Open Source Program Spring 2026 cohort, worth $3,600 in platform credits over three years. - Verified: the install command on screen,
npx @open-slide/cli init my-slide, matches the README and the published npm package, latest2.0.0from 2026-09-26. - Unstated cost:
@open-slide/clideclaresengines: ^20.19.0 || >=22.12.0, so Node 20.19 or Node 22.12 and up is required, and the Get Started block usespnpm dev. Neither requirement is mentioned in the clip. - Unstated cost: decks are arbitrary React components in a TypeScript pnpm monorepo. When the agent's output breaks, you debug React, not slides. The repo had 133 open issues at check time.
- Omitted by the video: PPTX, PDF and static HTML export, presenter mode with speaker notes and timer, the assets manager with svgl logo search, and the folder-based slide manager.
Resources
- github.com/open-slide/open-slide — the repo shown on screen for the entire clip. MIT, TypeScript, created 2026-04-26.
- Raw README — source of every quoted README line, including the
/apply-commentsloop and the export list. - open-slide.dev — project homepage and docs. Documents the
Page,Step,TransitionandMorphcomponents. - GitHub API record for open-slide — 8,942 stars, 632 forks, MIT, 133 open issues, last push 2026-10-03.
- GitHub releases for open-slide —
@open-slide/cli@2.0.0and@open-slide/core@2.0.0on 2026-09-26,core@2.0.1on 2026-09-27. - npm registry record for @open-slide/cli — version 2.0.0, MIT, published 2026-09-26 13:57:52 UTC.
- packages/cli/package.json — source of the Node engines requirement
^20.19.0 || >=22.12.0and theopen-slidebin entry. - openslide/openslide and openslide.org — the unrelated digital pathology library that owns the name the voiceover used.
- Vercel Open Source Program — program terms behind the badge in the README hero.
- Vercel Open Source Program Spring 2026 cohort — cohort list that includes open-slide.
- GitHub profile for 1weiho — Yiwei Ho, the author named in the README license line.
- svgl.app — the logo catalogue the README's assets manager integrates.
Published October 4, 2026. Writeup generated from a favorited TikTok.