# Voice Brain: AI writing that remembers what you have already said · ScriptGrain > Voice Brain remembers the ideas, claims and stories in everything you have written, so new drafts build on them instead of repeating them. Why we built it and how it works. Canonical: https://scriptgrain.com/voice-brain # Voice Brain: a memory of everything you have written *By Jack Stovell · published 2026-09-22* Voice Brain reads what you have written with ScriptGrain, and anything you add, and remembers it properly: the ideas, the claims, the stories, the frameworks, each tied to the exact words it came from. Every new brief gets checked against that memory first, so drafts build on what you have said instead of repeating it or quietly contradicting it. ## Why we built it I'm Jack Stovell, founder of ScriptGrain. Here's the thing: we didn't design this feature from a whiteboard. We built it because we were already running a version of it ourselves. We have run a version of this memory inside our own setup for more than three months. It is how every AI agent we run already knows the product, and it is how they write content for us through ScriptGrain. That's not a small detail. It made a clear difference to new content and to improving older pieces, so we built it into the product. So the origin story is boring, in the best way. We needed it, we used it, it worked. That's why it exists. ## What it remembers Voice Brain reads your finished drafts, including your edits. It reads your writing samples. It reads pieces you add yourself, pasted or by URL, as long as they run to 60 words or more. And it reads the pages your voice monitor watches. Every half hour it checks for new and changed pieces and reads only those. From each piece, it keeps the ideas, claims, stories and frameworks it contains, and it keeps them with the exact words they came from. No verbatim quote, no memory. Anything that can't be traced back to the text gets thrown away. That's a deliberate constraint, not a limitation someone forgot to fix. Pieces then get grouped into topics, and memories get linked to each other: 'repeats' when you have said this before, 'builds on' when a new piece extends an old one, 'contradicts' when two pieces disagree, and 'refines' when a later piece sharpens an earlier claim. Contradictions surface as 'you changed your mind', which sounds blunt because it is. You can mark one as not a change of mind if it isn't, but the system doesn't pretend the tension away by default. ## Better new pieces Here's where it earns its keep. Before you write, the novelty check reads your brief against the memory and tells you plainly whether it repeats something, builds on something, or is genuinely new. It also suggests angles grounded in what you have already argued, not generic ones pulled from thin air. While it writes, once a voice has 10 or more pieces in its memory, every outline and draft gets handed two things: what is established, to build on, and what is already argued, so it isn't repeated. There's a setting called 'Avoid repeating myself', on by default. Turn it off when similar content is genuinely fine, a landing page variant, say, where repetition is the point. Say the brief is "why founders should write their own content." The novelty check might flag that you have made this argument twice already, once as a claim about authenticity and once as a story about a client who outsourced it and regretted it. It won't stop you writing a third version. It'll tell you what angle hasn't been used yet, so the third piece adds something instead of echoing the first two. What next asks the memory for five angles that build on what you keep saying and go where you haven't been. Not five random topics. Five extensions of an argument you have already started, aimed at the gaps. ## Better older pieces New pieces aren't the only thing that benefits. Page rewrites use the same memory, so an old page rewritten in your voice builds on everything you have said since it first went live. So an old page comes back in your current voice, building on what you have argued since. And the memory tells you where to look. The 'changed your mind' list surfaces genuine contradictions worth resolving. Topics you haven't written about for a while surface too, which is a quieter but useful signal: if a subject has gone cold, that's often exactly where an old page needs a second pass. ## One brain or several Every voice starts with its own brain. That's the default, and for most people it's also the right answer. Share a brain when the voices genuinely overlap: a founder and their company is the clear case, or a team writing on a single subject where consistency matters more than individual flair. Each voice still writes in its own style; sharing memory doesn't flatten anyone into sameness. Keep separate brains when the voices shouldn't bleed into each other: different clients, different audiences, anywhere a contradiction in one context shouldn't show up as baggage in another. This matters more than it sounds, particularly for agencies and ghostwriters juggling several client voices under one account: mixing memories there isn't a convenience, it's a liability. Joining a shared brain brings the voice's memory with it. Leaving takes a copy, so nothing is lost either way. New voices get their own brain unless you pick one when you create them, which means the safe default is always there and the shared option is always a deliberate choice, never an accident. ## You stay in charge None of this is a black box you have to trust blindly. You can reword any memory, delete it outright, or forget the piece it came from entirely. Edits and deletions survive the piece being read again, so correcting something once is enough; the system won't quietly resurrect an old version. And a forgotten piece is never read again, full stop. It's available on every plan, including Free, in the app, through the API, and over MCP. For teams already building their own agents against the [AI writing API and MCP server](https://scriptgrain.com/ai-writing-api-and-mcp-server), the memory travels with the voice, not just the interface. ## The brain behind this page This page was written by ScriptGrain, in its own brand voice, with Voice Brain switched on. The brain behind it holds 17 pieces and 210 memories: 70 ideas, 81 claims, 23 stories, 36 frameworks, spread across 37 topics. It has traced 421 'builds on' links between those pieces, and spotted 58 places where one piece repeats an earlier one. That last number is the one we watch: what is already argued goes into every outline and draft as a list of points not to repeat. Voice Brain is one of several things that changed this month, all on [what's new](https://scriptgrain.com/whats-new), alongside [the new tools](https://scriptgrain.com/whats-new/tools). It works next to the loop that [learns from your edits](https://scriptgrain.com/learns-from-your-edits): the brain remembers what you said, the profile learns how you say it. That's the whole pitch, really. Not more content. Content that remembers what came before it. ## Related - [What's new](https://scriptgrain.com/whats-new) - [The new tools](https://scriptgrain.com/whats-new/tools) - [It learns from your edits](https://scriptgrain.com/learns-from-your-edits)