How can we make Sudowrite better?

Please tell us how we improve Sudowrite for you.

Unlimited Credits

Dear Sudo-Team, I know this request is already being considered, but I once again plead for this to actually happen. Many agree that for those of us who use Sudo-Write daily, an option with limitless credits would be perfect. You cannot use the program without credits. Everything the program offers as a tool uses credits, and if you edit only 4 chapters with 7000 to 18.000 words, 2.000.000 credits slip away with the snap of a finger. It is really frustrating, because I would LOVE to use this program frequently, but I cannot because I cannot spend hundreds of euros per month to buy credits that will be gone within hours, anyway. Right now, I use the max plan, which is $59 per month, 44 yearly. Even with the $44 I pay, I'm over $500 per year, and still cannot fully enjoy or use the program, which is sad. Very sad. I have used many authoring programs in the past few years, and none is as beautifully crafted and promising as Sudo. However, it takes the fun out if I can only use the tools in a limited way and have to constantly worry about when and which tool to use, because otherwise the credits will be gone. I won’t use the program just to write my manuscript there. I can do that in Word or Google Docs for free, but I won’t have any fancy tools. Many have been requesting this, and I’ve seen many talk about this. Another thing would be that if you were to make this happen, that the price on the unlimited credit option should still be manageable and not over the top, so it’s not affordable anymore either. For example, have the unlimited credit option be $70 per month. That would be manageable for many. Also, judging by how many would LOVE to use the unlimited option, you’d profit twice as much by offering it to us, because more people would go for it. I would. I definitely would. Greetings, and a happy New Year 2026! Julia

Julia Rittner 17 days ago

2

💡 Feature Request

Planned

The return of My Voice

Hello Sudowrite Team, I’d like to ask for the official return of the “My Voice” feature, ideally in an even improved and more flexible version. I also want to reference an earlier request I made to have “My Voice” available in the Plugin Section for users who rely on voice consistency across Sudowrite tools as a core workflow need. If possible, an improved version could include: I thought about something like making it easier to create and manage different voices for one project, maybe arranged as sub voices derived from the overall tone/style of the novel, the different Dialogue tones that you want to have for different characters or in eg the case of dual timeline one style for the past and one for present day. Additionally, I would have very much liked back then, the possibility to iteratively improve on the result so there should be a back and forth during creation of a new voice. Ideally, instead of it being a black box, in the spirit of Explainable AI, it would tell you on demand why certain wordings and phrases came about and then you could change this specifically in your input sample. Thank you for considering this request, and for continuing to build this amazing tool and fostering that second to none Discord community. Best regards, Peter

Peter About 1 month ago

3

💡 Feature Request

Named History Versions

The biggest thing I'd love for Sudowrite to add is a way to name past versions in the story bible. Like many Sudowrite authors, I often update my characters, world-building, style, and even my genre between chapters. Not every chapter, of course, but Allie from before the accident isn't the same person as she is afterward. It works well, but is clunky, and when I go back and make changes to a previous chapter it's very frustrating because I don't have a simple way to revert to the "past" version. Sure, I can restore that version from the history, but a long list containing many changes with only the date to guide me is difficult to use for this purpose. If, instead, I could click on (for example) Allie's history, scroll down to "Before Accident" and click restore to make some changes to Chapter 3, then open her history, click on "Six Month's Post Accident" to return to where she's just finished physical therapy and is no longer using crutches.... That would be absolutely amazing. And, speaking as a software engineer who admittedly hasn't seen this codebase, it seems as though adding that feature would be a fairly low lift. We can already restore past versions at will. We just need the ability to name them. (I think) Automatically pinning named version to the top seems a good idea as well.

Mason Murphy 27 days ago

💡 Feature Request

Making Brainstorm More Accessible

The Brainstorm feature in Sudowrite has a lot of visible potential, but it currently lacks the accessibility-focused structure needed to support a wide range of thinking styles. While the interface presents multiple brainstorming categories (Dialogue, Characters, Worldbuilding, Plot Points, etc.), these categories all lead to the same blank prompt experience. This makes it unclear how each option differs and places a heavy cognitive burden on the user to determine how to begin. From an accessibility standpoint, this is a significant barrier. For many neurodivergent users — including those with ADHD, autism, or executive function challenges — an empty input field is not an invitation to create, but a point of paralysis. Open-ended prompts require users to simultaneously decide what to explore, how to explore it, and how to phrase it, which can be overwhelming. Brainstorming tools should reduce cognitive load, not increase it. Providing clear, category-specific guidance would make the feature more accessible and more effective for all users. For example, selecting “Characters” could offer structured idea paths such as internal wounds, motivations, contradictions, relationships, or power dynamics. Choosing “Worldbuilding” could surface prompts related to environment, culture, politics, resources, or unintended consequences of magic or technology. These kinds of options act as scaffolding — they don’t limit creativity, they enable it by giving users a starting point. Accessibility also improves when users understand what a tool is designed to do. Right now, the distinctions between brainstorm categories are implied visually but not reinforced functionally. Brief explanations, example clusters, or selectable lenses within each category would help users quickly orient themselves and choose the tool that best fits their needs, rather than guessing or feeling lost. An optional guided brainstorming mode would further support inclusive design. Allowing users to toggle between a blank canvas and a structured, prompt-driven experience acknowledges that creativity works differently for different brains. This flexibility would make Sudowrite more welcoming to neurodivergent writers, users experiencing burnout or fatigue, and anyone who benefits from clear constraints. By framing Brainstorm as an accessibility-first ideation tool — one that actively lowers cognitive friction and supports diverse creative processes — Sudowrite could significantly improve both usability and creative output. Structure, clarity, and choice are not restrictions; they are essential tools for inclusive creativity.

Erica Keough 7 days ago

💡 Feature Request

Visualize Scenes from Character + Worldbuilding Cards Goal

Feature: Visualize Scenes from Character + Worldbuilding Cards Goal When the user clicks Visualize, the system generates images where: the same character stays consistent (face, hair, age, vibe, outfit rules) the environment matches the selected world/setting (volcano vs forest) the style stays consistent (cinematic, watercolor, anime, etc.) props/lore rules are respected (weapons, magic glow, era, tech level) Core Concept “Scene Recipe” = Character Identity + World Context + Shot Direction The render pipeline shouldn’t rely on a single prompt typed by the user. It should build a structured prompt from cards. Think of it as: Visualize Prompt = Character Anchor (immutable identity) World Anchor (rules + aesthetics) Location/Setting Module (forest / volcano / tavern) Scene Moment (what’s happening right now) Camera + lighting (shot language) Negative constraints (what to avoid)

Manon Doucet 11 days ago

💡 Feature Request