30+ changes in September. The 10 that matter most.
Walnut .
- Product
- Walnut
- Sent from
- walnut.io
- Sent
No dark-mode styles — this email renders the same in a dark client.
Walnut. PRODUCT UPDATE September 2026 30+ changes. Here are the 10 that matter most. Hi Emre, September was our heaviest shipping month of the year. 30+ changes went out, and almost all of them came from the same place: you asking us to run Walnut inside your own stack, under your own controls, at the scale you actually work at. These are the 10 that will change the most for your team. 1. The Walnut MCP and the Walnut API Run Walnut from wherever you already work: ask your AI assistant, or call the API. • Onboard a whole region in one sentence instead of one person at a time • Stop finding out you are short on seats halfway through • Hand over everything a leaver owned in a single step • Pull seat and usage data straight into your own dashboards, no exportsConnect it › What it can do › Prompt library › API docs › 2. Bring Your Own Key Your legal team already negotiated an AI contract. Walnut's AI can now run inside it. • AI spend lands on the provider contract you already signed • Prompts stay under your retention terms, and need not be stored at all • Keys are write-only, so nobody can read one back out of Walnut • If your provider goes down, you choose whether Walnut picks it upRead more here › 3. Re-skin a whole template to another brand Reusing a template for another customer meant hunting every colour and logo by hand. • One template now covers every customer you demo to • You approve the colour and logo mapping before a pixel moves • Fonts and guide themes change in the same pass • Anything it is unsure about is left alone, not guessed atRead more here › 4. Let the buyer tell you what matters You normally learn what a buyer cared about afterwards, from clickstream, by guessing. • Know what they came for before the demo starts • They see what matters to them first, without you building a playlist per persona • Insights shows what buyers prioritise across every viewing • Optional, so it never gets in anyone's wayRead more here › 5. Comment on a template, and approve it before it ships Feedback lived in a doc nobody opened, and nothing stood between a template and a buyer. • Feedback lands on the work itself, where the person fixing it will see it • Nothing reaches a buyer without the sign-off you require • One status, the same answer everywhere you look • Edit an approved template and it goes back for review on its ownRead more here › 6. Demo Presets: one demo, every segment Ten variables across ten segments is a hundred values to keep straight, and redo on every change. • One demo serves every segment you sell to • Fix a screen once and every segment gets the fix • Describe a new segment in a sentence and let AI fill the values • Narration says the same names the screen doesRead more here › 7. Turn a deck, a design or a mobile screen into a demo Not everything worth demoing is a product URL. Sometimes it is a deck, and sometimes it does not exist yet. • Demo what has not been built, months before it ships • Your existing deck becomes a clickable demo, speaker notes and all • Mobile and tablet designs land in the right device frame, not a desktop one • When the design moves on, the screen follows and keeps the guides you addedImporting from Figma › 8. Gradient brand colours reach the demo editor Gradients arrived for Playlists and Deal Rooms earlier this year, and stopped at the demo boundary. • Your brand looks like your brand all the way through the demo • Save a gradient once and it is waiting everywhere you brand something • Set it for the workspace, or override it on a single templateRead more here › 9. Thirteen changes to Playlists and Deal Rooms One release reworked how playlists and rooms get built, and who is allowed to see what inside them. All of it works on the advanced playlist, not only on Deal Rooms. • Change a shared section once and everywhere it appears follows • Nothing is rewritten under a buyer mid-deal. Published pages ask first • Hide a page from everyone except the people who should see it • That stays true after someone duplicates the room • Roll back any edit, and see which PDF pages actually got read 10. Narration that keeps up with your demo Four changes to how your demos sound, three of them straight off the public roadmap. • Slow down the dense steps and speed up the obvious ones • Your product names get said correctly, in every language • Change a step's wording and the narration catches up, in its original voice • Keep the voiceover without the player control on screenText to speech › Pronunciation dictionary › And 20+ more • Dynamic values in simulated typing, so a form types the day your buyer is looking at it • One AI writer behind every guide, reading the whole demo before it writes a word • Lead forms in Insights, so you can tell which demos actually generate leads • Drag and drop between sections, with comment threads following the item • Clean up unused and duplicate screens, find every screen no link, guide or flow reaches, and delete them in bulk • Share a demo from the player, without going back to the editor to copy a link • Per-link playback settings, override autoplay, looping, narration and step delay on one share link • A clearer way around the app, one place for filters, saved views, and search that sits where you expect it • A quieter editor topbar, version history behind the last-saved timestamp, help in the profile menu Plus a batch of smaller fixes across the editor, Insights and the library. All of them are in the release notes. See everything we shipped › Most of this started with you Customer votes steer more than half of what we build, and a lot of this release came straight off the public roadmap. So tell us what should be next. Browse what is coming, upvote what matters to you, and comment on anything you would shape differently. Vote on the public roadmap › Looking forward to seeing the demos you create with these. Adi from Walnut 🐿💜 You are receiving this because you have a Walnut account. Unsubscribe
- Accession
- nse/walnut/2026-10-01/3016
- From
- Adi from Walnut · adi.bo@walnut.io
- Sent
- 1 October 2026 · 16:00 UTC









