Changelog

The team dedicated this entire week to bug fixes and quality of life improvements. Buckle up.

Improvements

• Find & Replace Improvement - We recently shipped an improved Find & Replace, which better focuses the active instance of a located word. (It also just looks nicer!)

• Write Button Improvements - If you've used Write (Auto or Guided) in a blank document, you may have seen its tendency to "continue" from the end of a linked chapter summary. We improved the way Write works, and it will now use that context to start your chapter from the beginning.

• Right-sized Story Bible Boxes - When empty, the Braindump, Genre, Style, and Synopsis boxes had too much padding. We made them leaner and more elegant.

• Trait Button Improvements - The "Fill this in" button in empty trait fields now disappears once you've started typing. Meanwhile, the Rewrite and Visibility buttons in those fields now appear beneath the text (rather than in the upper right corner)—making those fields work just like Outline.

• Improved Trait Label Handling - Identical or blank trait names on a card ran the risk of tripping up the Rewrite trait functionality. We improved how that's handled behind the scenes to prevent any issues.

• Prevent Unwanted Scrolling - We agreed with feedback saying you shouldn't lose your position in your doc when collapsing the sidebars or changing your editor size, so your scroll position now persists.

• Smarter Quick Tools - We updated the models powering Quick Tools to 4o and 4o mini. Aside from making them smarter and faster, this also means they're less likely to break (even with obscenely long Outline chapter summaries).

Fixes

• Fixed Document Shuffle - We fixed an issue with switching between documents, where doing so in rapid enough succession could cause the selected document to continue to toggle even once you'd stopped clicking.

• Resolved Toolbar Overflow - We shipped a fix preventing the text formatting toolbar at the top of the editor from spilling off to the right at really narrow widths.

• Plugin Testing Fix - The Plugin testing panel was producing a "too much or too little text" error. We fixed that issue, and testing now works as expected.

• Character History Formatting - Story Bible's Characters section has its own History, which appeared narrow and blank when first creating a character card. We fixed that.

• Model Ranking Audit - We resolved a few inconsistencies in the Prose Mode selector's model performance rankings.

• Project Word Count Fix - Total project word counts, as displayed on the homepage's project card, were sometimes incorrect. We found the issue and fixed it so that you always have a proper word count.

• Return to Last Position - We fixed the auto-scroll functionality so that when returning to a document you were working in previously, you're now correctly returned to your last active position.

• Quick Tools Shortcut Fix - The keyboard shortcut for Quick Tools (Mac: ⌘ + K, PC: Control + K) wasn't working unless your cursor was in the document editor. We fixed that, so you can pop open a Quick Tools window from elsewhere in your project.

• Describe Icon Swap - The Describe icon in the Selection Menu was wrong. We fixed it so that it now matches the Toolbar Menu.

• Trait Field Backgrounds - When using dark themes, Characters and Worldbuilding traits used white (rather than theme-appropriate) colored backgrounds. We fixed them, and they look much better.

• Something Went Wrong Fix - Recently we received increased reports of the "Something went wrong" error when using Write with a retired prose mode (such as Fastest or Unfiltered). We identified the issue and shipped a fix.

• Broken Worldbuilding Chiclets - Having an empty Worldbuilding card in your Story Bible caused a broken chiclet to appear as "Looked at" context when using the Write button. We fixed that, so only context actually used is included.

• Scroll to Draft - We made it so you'll now be returned to the Draft box if you click the Typewriter icon while halfway down your document.

• Collapse Hover Consistency - When you mouse over the collapse button for the toolbar or sidebars in a project, you should see that button turn grey. This was not the case for the right (History) bar, but we fixed that.

• Custom Rewrite Text Centering - The text in the Custom Rewrite field was not vertically centered. We fixed that, and Ryan breathed a sigh of relief.

• Fill This In Fix - The "Fill this in" button in an empty trait field would occasionally generate exclusively into the History, leaving the trait field itself blank. We resolved the issue and it will now always populate the trait field.

• Fixed Creativity 11 Muse - If you cranked Muse all the way up to 11, it would sometimes say it was "thinking" while it was actually "writing" which... well, as authors, you can probably appreciate the difficulty there. We fixed that, and a handful of minor associated issues.

• Quick Tools Cut Off - We fixed an issue that would occasionally cause the Quick Tools window to appear cut off inside the editor.

• Restored Draft Border - The bottom border on the Draft tool was missing if you scrolled down in your document while it was open, but we put it back.

• Random Generation Fix - Choosing Random from the Generate menu in Characters or Worldbuilding would occasionally produce a blank card. We identified and fixed the issue, in a stunning refutation of determinism.

Thanks so much for bringing these issues to our attention!

You can now collect comments from your friends, editors, and beta readers!

Now when you share a Sudowrite document and send the link to a bunch of people, each reader gets their own clean copy.

That means readers can leave you feedback without seeing anyone else's comments—but as the author, you'll see everyone’s comments in one place!

Comments appear just to the right of your document. And of course, this means you can also now comment on your own document. Just highlight a passage and select New Comment in the selection menu. It’s super handy for revision workflows and situations where you'd just like to leave yourself notes.

Refresh Sudowrite to use Clean Copy.

If you've already shared a document, you will need to unpublish and republish that document for comments to work.

We’ve been listening to your great feedback on Muse and making it even better.

• Muse now writes longer scenes in Draft

• Muse uses more dialogue when appropriate in Draft

• Muse writes more varying and interesting prose

• Muse expands more when using Expand - on average, about 4 times the length of the original passage

• Muse will now pay even more attention to your style examples (be sure to use these, they vastly improve quality!)

🐛 We also fixed a bug where Muse was ignoring style examples in certain cases.

Lots more in the works. Keep the feedback coming!

It’s finally here! You may have heard rumors for months now, many of you have been beta testing it, and we’ve been working on it *checks calendar* for over a year. So you can understand why we’re so very excited to announce that…

Sudowrite Muse is available today!

• Muse writes prose you’ll actually want to read — no more "tapestries" and "delving"

• Muse will write anything — no more moralizing or forced happy endings

• Muse is the best AI for fiction — it’s not for emails or sales copy

How does it work?

Muse employs pioneering narrative engineering, combining everything we've learned about writing great fiction with AI over the past four years.

Storytelling intelligence helps it take apart elements of your story, analyze them to extract important information, create a plan, refine, revise, and guide your chapter to its best-possible first draft. Under the hood, it's a “model system” with AI expert "agents" working together through a multi-step pipeline.

What does all that mean?!? Muse writes peerless prose, with longer generations, stellar openings, and without the AI-isms and bad habits of other models. It's great!

Why did we make it?

Stories are core to what makes us human. They help us understand and empathize with one another, and these days, we can use a whole lot more of that. We believe storytelling is more important than it’s ever been, and that great storytellers deserve great tools.

But other AI models just aren’t made to tell tales. They’re trained to give answers. Factual, sanitized, lifeless answers. We think we can do better. Muse is our first attempt at just that.

Is it perfect?

Yes! Well, no. We've been working on this non-stop for over a year and we think it's the best thing out there. Many of you have been beta testing it, using it to publish novels, and have told us how much you love it. We are so very proud of what we’re releasing today. And we have so many ideas for how to make it even better. More to come!

How to Try Muse

• In Write, select Muse in settings under "Prose Mode"

• In Draft (formerly Chapter Generator), choose it using the drop-down on the Generate button.

• Use Expand in the selection menu. It's now powered by Muse.

N.b. In Draft, Muse only works with Scenes, so you'll need to make sure your project is upgraded to use Scenes, or start a new Project, first.

What our Beta Testers Think

Real feedback from writers who’ve used Muse

Want to learn more?

• Learn more about Sudowrite Muse

• Attend a class with Muse experts…

  • Thursday, March 6

  • Friday, March 7 — Sign up here

  • Saturday, March 8 — Sign up here

That’s all, now go try it!

Thank you to our amazing ambassadors, our brave beta testers, and all the writers who’ve been asking for this. All of you had a hand in this.

We’ve greatly improved how Sudowrite writes chapters! It can now write better prose by following your directions more closely, maintaining your style better, and accepting extra instructions.

To enable these improvements, beginning today Sudowrite is transitioning away from Beats in the Chapter Generator, to use something more familiar and intuitive: Scenes. Scenes simplify the process of breaking your chapters into logical narrative units—so you can focus on the action, the characters, and the heart of your story. And they also make sure you’ll get the best prose possible out of Sudowrite.

Why Scenes?

• More Familiar, More Natural
  Scenes are a universally understood concept for storytelling. Instead of puzzling over where one “beat” ends and another begins, Scenes let you structure your chapter by its natural shifts in location, time, or characters.

• Better Prose
  In our testing, Scenes consistently generate clearer, more focused prose. You’ll see fewer tangents and a smoother narrative flow—this new approach helps Sudowrite “think” more like a storyteller.

• Easier to Format & Fine-Tune
  Scenes appear as a numbered list by default, so there’s no guessing whether your outline is too short or too sprawling.

• Extra Instructions for Every Scene
  Got special requests for a scene’s point-of-view, style, or pacing? Our new “Extra Instructions” field is the perfect place for these notes. They’ll carry into your generation so that your draft matches your vision more closely.

• Scene Validation and Instant Improvements
  If your Scenes span too many locations or skip vital characters, Sudowrite will gently nudge you—suggesting helpful fixes before you click generate.

How to Use Scenes

1. Update to Scenes
   You can choose which of your projects you’d like to update to use Scenes now. If you’re in the flow with Beats on a given project, you can continue to use those until March 31st.

2. Generate Scenes (Instead of Beats)
   There is now a Generate Scenes button in the Chapter Generator that will create scenes from the Chapter Summary in your linked Outline. You can also write your own!

3. Watch for Helpful Warnings
   Sudowrite highlights potential trouble spots, like missing characters or Scenes that look too sprawling. Accept suggestions to “fix” scenes—splitting them, adding detail, etc.—or skip straight to generation if you’re feeling bold.

4. Click “Generate”
   Sudowrite will analyze your Scenes, generate an accurate word count and credit estimate, then produce your scene-accurate chapter in prose.

FAQs

Q: Do I need to do anything to update my project?
A: We’ll automatically convert your Beats into Scenes on March 31st. Until then, you’re free to keep using Beats—or you can get started with Scenes right away by clicking the “Update Now” option in your project’s Chapter Generator.

Q: What happens to my old Beats?
A: Your old Beats are magically converted to Scenes during the update. Those Beats are also saved to your Scenes History section though, so you can always recover the original beats as written.

Q: Can I write Scenes manually without using AI to generate them?
A: Absolutely! You can simply type your Scenes into the new interface and skip the “Generate Scenes” step. You’ll still benefit from the new Scene validation.

Q: Do Scenes support the special instructions I used to include in Beat headers?
A: Yes. Scenes come with an Extra Instructions box that serves the same purpose as Beats headers. That means you have an official home for your POV, tense, or style requests—except now it’s even more flexible and precise.

Q: What if my Scenes don’t match the “one location/one moment in time” guideline?
A: We won’t force you to break your Scenes. If Sudowrite detects that a Scene might be sprawling, it will suggest how to split or clarify it, but you can always proceed as-is.

We’re really excited to share Scenes with you, both because of how they work today and what they unlock for Sudowrite in the very near future. If you have questions, drop a note in our community Discord. Thanks for all of the feedback that got us here—and here’s to your next great chapter, powered by Scenes!

Ready to try Scenes? Pop open your project’s Chapter Generator click “Update Now” to make the switch.

We’ve been hard at work this week on some big upcoming launches, but here’s a handful of fixes we made along the way.

Moving Worldbuilding Cards - Moving a Worldbuilding card and then adding a trait caused the card to revert to its old position and the trait to be lost. We’ve resolved that issue.

Rewrite Refusal Fix - Since increasing the word limit on the Rewrite button, we’ve been receiving reports of Rewrite refusing to work with spicy or violent prose. We identified the issue and fixed it.

Basic Plugin Creation - There was an issue preventing Basic plugins from being created, but we fixed it and you’ll no longer receive an error message when trying to do so.

Thanks for bringing these to our attention!

Last week we added DeepSeek Instant, a super fast AI model, to Sudowrite. Last night, we made it 6x faster. It’s now Sudowrite’s fastest AI model ever—and it’s still free to use, for now.

Here’s a (quick) look at just how fast it is.

It’s available now in the Write button, Chapter Generator, and Plugins.

First, the big news: We've increased the word limit on the Rewrite tool to 6,000 words!

That means you can now rewrite an entire chapter at once—previously something only doable with Plugins—using the stock or custom Rewrite options. We’ve also increased the size of the custom rewrite instruction field by over 5x, meaning you can now write up to ~100 words (500 characters) worth of instructions.

This update is available now, but you may need to refresh Sudowrite to use it.

We also have a handful of bug fixes we wanted to share with you.

Jump Scroll to Story Bible - Some users reported a sudden scroll down to Story Bible each time they toggled between documents. We identified and resolved this issue.

Blank Outline Fix - We fixed an issue that occasionally caused blank results when generating long Outlines (despite being charged credits). It now works consistently for outlines of any length.

More Permissive Outlines - We also made Outline generation and rewrites more permissive where spicy and/or violent content is concerned. You should no longer see refusals for either.

Restored the Fun Part - There’s a box at the bottom of Story Bible (“Now the fun part begins!”) that lets you create a linked chapter from your Outline. It had disappeared after a recent fix, but we brought it back.