AI news videos

Gemini Notebook Now Asks Before It Builds Your Slides

Google has added a co-creation flow to Gemini Notebook, so the two most popular outputs, Slide Decks and Video Overviews, no longer jump straight from a prompt to a finished file. Writing on Google's own blog, Viraj Doshi, Senior Product Manager for Gemini Notebook, and Shan Wang, Senior UX Designer for Gemini Notebook, say the change came from user feedback and gives more creative control from start to finish. Here is the new flow. You start in the chat and ask Gemini Notebook to create slides or a video overview. Based on your sources, Notebook suggests the topics to include in the artifact. Once you confirm those topics, you can steer the content further and guide the visual style and format. For more control there is a new Review toggle. With it on, you review the plan in the studio panel by opening Review outline notes for slides or Review producer notes for video, and you can give extra feedback, such as asking for an executive summary at the beginning or swapping the order of a scene, before anything renders. When the plan looks right you select Proceed and Notebook produces the final artifact. If you already know what you want, you can say so in the first prompt and Notebook goes straight to the review flow. The older behaviour still works too: skip the review toggle in the studio panel and Notebook generates the artifact in one pass, as usual. Google says these co-creation capabilities are rolling out globally to all Gemini Notebook users over the upcoming week. Worth noting what the announcement does not say. There is no exact availability date beyond that rollout window, no country or region list, no tier or price, no model name, and no figure of any kind anywhere on the page. No benchmark or measured result is offered, no customer is named, and no third party is quoted, so there is no independent verification. Google is both the publisher of the post and the vendor of the product it describes.

Watch on YouTube

Transcript

Sources

Every claim in this video comes from the top ranking coverage of this topic. The claims and where each one came from:

• LINE BY LINE BACKING AUDIT. Hook sentence one, "Google says its notebook now asks before it builds your slides." Backed by "Based on your sources, Notebook will suggest topics to be included in your artifact. Once you confirm, you will be able to steer the content further and guide visual style and format" and by "With this on, you can review the plan in the studio panel ... before anything renders." The asking step is the suggest and confirm sequence that the page places ahead of the render. Attribution phrase: Google says. Hook sentence two, "Here is what changed." Editorial framing, asserts no fact, and sets up scene 1. It exists in part so the hook is exactly two sentences, because a one sentence hook renders the second beat of the hook card as undefined. Scene 1 sentence one, "The post states Gemini Notebook now offers more creative control." Backed verbatim by "Based on your feedback, Gemini Notebook now offers more creative control from start to finish on two of our popular outputs: Slide Decks and Video Overviews." The figurative clause in that sentence covering start and finish is not reused in narration and survives only inside the labelled verbatim quote on the scene 1 card. Attribution phrase: the post states. Scene 1 sentence two, "Slide Decks and Video Overviews both change." Backed by the same source sentence, which names those two outputs as the ones affected. This is a two item pair, not a list of three or more, so it is safe for the audio timing. This sentence continues the attribution opened by the sentence before it. Scene 2 sentence one, "Google's product team notes the notebook suggests topics from your sources." Backed verbatim by "Start in the chat and ask Gemini Notebook to create slides or a video overview for you. Based on your sources, Notebook will suggest topics to be included in your artifact." The phrase product team is an accurate plain description of the two bylines, a Senior Product Manager and a Senior UX Designer on Gemini Notebook. Attribution phrase: Google's product team notes. Scene 2 sentence two, "You confirm before it builds." Backed by "Once you confirm, you will be able to steer the content further and guide visual style and format" and by "Instead of jumping from an initial prompt straight to a final output, Gemini Notebook can now walk you through the creation flow in a quick process based directly on your sources." The source verb steer is printed on screen inside the verbatim quote but is not spoken, because the plainer word is safer for the idiom gate. This sentence continues the attribution opened by the sentence before it. Scene 3 sentence one, "The company writes that a new Review toggle lets you read the plan first." Backed verbatim by "If you want to have even more creative control, you can use our new Review toggle." and by "With this on, you can review the plan in the studio panel ... before anything renders." Attribution phrase: the company writes. Scene 3 sentence two, "Request changes before rendering." Backed by "plus give additional feedback, like asking to include an executive summary at the beginning or swapping the order of a scene, before anything renders." The two worked examples from that source sentence, the executive summary and the reordered scene, are printed on the scene 3 card and are not spoken, because narrating them would add a list and push the word budget over. This sentence continues the attribution opened by the sentence before it. Scene 4 sentence one, "The article reports a global rollout to all users over the upcoming week." Backed verbatim by "These co-creation capabilities are rolling out globally to all Gemini Notebook users over the upcoming week." The sentence deliberately says over the upcoming week and not a date, so it cannot be heard as a promise that the feature is live for everyone today, and the scene 4 card states plainly that no exact availability date is published. Attribution phrase: the article reports. Scene 4 sentence two, "You can also skip review." Backed by "If you prefer a quick output, you can still just go to the studio panel, click your artifact, skip the review toggle and have Notebook generate the artifacts, as usual." and by "If you already know what you want to create, you can specify this in your prompt and the notebook will go straight to the review flow." The three step mechanics in the first of those source sentences are condensed to a single clause rather than narrated as a list. This sentence continues the attribution opened by the sentence before it. Scene 5 sentence one, "Google published this on its own blog and sells the product described." Backed by the page's own identity as a post on Google's blog written by two Gemini Notebook staff, and by the fact that the product the page describes, Gemini Notebook, is Google's own. Attribution phrase: Google published this. Scene 5 sentence two, "The page reports no supporting number." Backed by absence, verified by reading the captured body text end to end: there is no percentage, no user count, no price, no benchmark, no latency figure and no measured result anywhere. The qualifier supporting is deliberate and load bearing, because the body does contain one quantity word, the count of the two popular outputs affected, and that count is a description of scope rather than evidence for any claim. This absence is restated in full on the scene 5 NOT PUBLISHED line. Endcard sentence one, "Inboxsmith builds AI receptionists for small businesses." A channel description that asserts no fact about the story and needs no source. Endcard sentence two, "Please like and subscribe for more news." The fixed subscribe line, copied exactly as specified, asserting no fact. CLAIMS DELIBERATELY LEFT UNSPOKEN. The quick output path is described in the source as a sequence of three actions, going to the studio panel, clicking the artifact and skipping the review toggle, and that three item sequence is never narrated because multi item lists wreck the audio timing; it is condensed in scene 4 to the single clause about skipping review and printed in full inside the verbatim quote on the scene 5 card. The two embedded walkthrough media captions, which read Co-creation Slides walkthrough and Co-creation Video Overview walkthrough, are not narrated and are not printed on screen, because they are labels on media we cannot show or verify and they carry no fact of their own. The Proceed button mechanics, specifically the source line about everything looking right and then selecting Proceed to produce a final artifact, are left out entirely: the sentence is interface detail, it contains a figure of speech about how the plan looks, and it would have required nested quotation marks inside an on-screen verbatim line. The two named review entry points, the outline notes label for slides and the producer notes label for video, are elided from the scene 3 quote with an ellipsis for the same nested quotation reason, and are not narrated. The page's figurative phrasings, specifically the start to finish phrasing, the jumping from a prompt phrasing, the walking you through phrasing and the going straight to the flow phrasing, are all refused for narration and appear only inside labelled verbatim quotes. No outside knowledge about Gemini Notebook is used anywhere: the three beats our channel has already covered, the rename of the product, its study tools and its flexible usage limits, are named only in the provenance note and are narrated nowhere. VOICE SAFETY AUDIT, re-run against the fourteen sentences listed above. No em-dash, no en-dash and no double hyphen appears anywhere in this file; the only hyphens are single ASCII hyphens inside words such as first-party, co-creation, nine-sixteen written as a ratio in the broll prompts, two item, load bearing and yt-dlp. No idiom, metaphor or figure of speech appears in any copy field: every figurative phrase in the source was either replaced with a plain verb or confined to a labelled verbatim quote. No digit is spoken in any narration field, because the source body contains no figure to speak; the only numerals in the file sit in on-screen date lines, the broll aspect ratio, the storyDate field and this audit. No numeric stat is spoken, so no scene carries two figures close together, and no narrated token glues a brand to digits. No dotted domain brand is narrated: inboxsmith.com appears in endcard on-screen text only. No calendar date is spoken anywhere; Oct 19 2026 appears in on-screen source lines only, and the only time word spoken is the phrase over the upcoming week, taken verbatim from the source. The banned adjective form of the word agent does not appear in any narration field, and was never reached for. No narration field contains a list of three or more items; the only pair spoken is Slide Decks and Video Overviews in scene 1. The word that a downstream gate reads as a countdown does not appear in any field. Attribution phrases actually used, in order of appearance: Google says in the hook, the post states in scene 1, Google's product team notes in scene 2, the company writes in scene 3, the article reports in scene 4, and Google published this in scene 5. All six are distinct from one another, and the five scene phrases are each distinct from the hook phrase as well. The second sentence of each scene carries no separate phrase of its own and runs on the attribution opened by the first sentence of the same scene, a deliberate trade made to hold the narration inside the word budget. Scene 5 states in plain spoken words that Google published the page on its own blog, that Google sells the product described, and that the page reports no supporting number. No dated event sequence block appears anywhere in this file, by design, so the story cannot be aged out of its same-day tier. WORD COUNT RECONCILIATION. Hook 15 words, counted as Google, says, its, notebook, now, asks, before, it, builds, your, slides, Here, is, what, changed. Scene 1 narration 17. Scene 2 narration 16. Scene 3 narration 18. Scene 4 narration 18. Scene 5 narration 18. Endcard narration 14. Scene subtotal 17 plus 16 plus 18 plus 18 plus 18 equals 87. Grand total 15 plus 87 plus 14 equals 116, which matches the wordCount field exactly, sits inside the 110 to 117 target band, and is 16 words under the 132 word hard gate. Sentence count: two in the hook, two in each of the five scenes, two in the endcard, fourteen sentences in total. No individual scene narration exceeds the 30 word hard cap, the longest being 18 words in scenes 3, 4 and 5. The hook is 15 words, inside its own 20 word cap, and is exactly two sentences. The five durationS planning integers are each 8 and sum to 40, inside the 30 to 50 band the quality gate checks.(PROVENANCE NOTE, not a video title. This Short rests on exactly one source: the first-party page titled "How to shape your slides and videos with Gemini Notebook", published on Google's own blog and written by two members of the product group, Viraj Doshi, Senior Product Manager, Gemini Notebook, and Shan Wang, Senior UX Designer, Gemini Notebook. The page was captured at 2026-10-19T17:01:57Z and that snapshot is stored alongside this script as article.txt. Google is both the publisher of this page and the vendor of Gemini Notebook, the product the page describes, so every claim narrated here originates with the company that profits if the claim is believed. No third party is quoted anywhere on the page, and the page contains no independent verification of anything it asserts: there is no benchmark, no measured result, no named customer and no outside reviewer. The page reports no figure of any kind in support of any claim; the only quantity word in the body is the count of the two output types affected, and no metric, percentage, user count, price or exact date appears. Availability is stated only as rolling out globally to all users over the upcoming week, which is why no narrated line claims the feature is live for anyone today. Corroboration research returned nothing usable: the pipeline retrieved zero of five candidate transcripts because the installed yt-dlp build on this host cannot fetch captions, and transcripts.json contains an empty array. No transcript therefore informs any line of this script, and every narrated fact is drawn from the first-party page alone. Our channel has already published separate Shorts on the rename of this product, on its study tools and on its flexible usage limits, so none of those beats are retold here and the Short leads only on the co-creation and Review toggle flow that is new today. EXCLUSION NOTE: the captured page also contains site navigation, product menus, related-story cards and footer links belonging to Google's wider website. None of that page furniture is narrated or printed on screen.)