How can we make Sudowrite better?

Please tell us how we improve Sudowrite for you.

Skill Leveling

HI! I think Suduwrite is a great tool for people who want to write, people who do write and for people who are learning to write. However, I think that the level of skill differs from person to person, so I think the level of creative freedom for the AI should also vary. I am a writer, I generally use Sudo because sometimes it's hard for me to articulate my ideas cohesively. A few times I’ve gotten frustrated with generations. For example, I basically tell every single conversation/dialogue, interaction, setting, emotions of the characters in the outline summary of a chapter. When I click generate scenes, I expect, especially since the scenes are how the story is being told, for the scenes to be more detailed if not as detailed and not generalized or generic. However, I have to edit heavily and put back specific details that I already shared in the chapter outline summary section. I understand that there are people who have Sudo create the story for them, but I am an author who brings my already concepted WIPS here and I was just hoping that there could be something to aid in that? I don’t know if I am explaining this correctly. But I’ll post anyway, just in case someone understands what I mean. Thank you XOXO

R. Menezes 4 days ago

2

💡 Feature Request

A better ”stream of thought” to prose workflow

I use sudowrite to turn stream-of-thought into almost finished prose. I don’t exactly write drafts, but more like something inbetween a draft and finished prose. When I put these in the draft creator and ask to generate them into prose, I often get a prompt that it’s ”already finished prose”, but it still works as I wish it to if I continue anyway. Using sudowrite this way is a bit wonky with the current work flow. I need to be conscious of where I do the scene splits in order to not have sudowrite cut any of the material, or start inventing stuff on its own to fill out the 1-1.5k words per scene. It’s also a bit annoying to have to work in single-paragraph chunks to create appropriate length scenes within the draft. My suggestion is to have a type of document called ”stream of thought” that works like a normal document, but has the prose generator functions at the bottom; ie without the use of scenes or the confines of ”how a draft should be written”. That way you can write very crude stream-of-thought style prose, making use of paragraphs, etc, to keep things organized and easy to overview, and then when you’re done, get to press the ”generate prose” (with the extra instructions), just like in the draft tool, but without having to worry about sudowrite inventing extra stuff to fill out pre-set word amounts for scenes, or cutting away material because it’s too much.

Kristoffer Lindgren 10 days ago

💡 Feature Request

AI Consistency & Workflow Limitations Overview

AI Consistency & Workflow Limitations Overview This report outlines significant challenges encountered when using Sudowrite for long‑form fiction writing. The issues primarily relate to context retention, continuity, instruction adherence, and workflow disruption, all of which directly impact writing efficiency and creative flow. 1. Inconsistent Context Retention Across Scenes and Chapters Despite providing detailed outlines, explicit instructions, and directions for each chapter, the AI frequently fails to maintain continuity. Specific issues include: Forgetting what was written in previous scenes or chapters Ignoring established facts, character knowledge, or worldbuilding rules Reintroducing contradictions even after being corrected Losing track of emotional arcs, tone, and pacing previously set This results in the need to repeatedly restate the same information, which significantly slows down the writing process. 2. Failure to Follow Explicit Instructions The AI often disregards direct, clear guidance, such as: Characters not knowing they are on the same planet or in the same room Characters not recognizing or sensing anything familiar about each other Maintaining uncertainty about whether a rift was natural or artificial Even when these constraints are emphasized, the AI introduces: Hints of recognition between characters Knowledge the characters should not possess Retcons that contradict earlier chapters This forces manual rewrites and undermines the intended narrative structure. 3. Continuity Errors in Worldbuilding and Plot Logic Examples of recurring continuity issues include: Characters suddenly “knowing” the rift was artificially created, despite earlier chapters establishing that they believed it was natural Shifts in plot logic that contradict the outline or previously generated content Scene‑to‑scene inconsistencies that break immersion and disrupt the story’s internal logic These errors require extensive correction and reduce the usefulness of the AI for long‑form storytelling. 4. Workflow Disruption Due to Chat Reset Limitations When the system indicates that a chat is full and requires starting a new one, all prior context is lost. This creates several problems: The entire plot, worldbuilding, and character knowledge must be re‑explained The direction for the chapter must be restated from scratch Previously established tone, style, and narrative goals must be reintroduced Creative flow is interrupted, making it difficult to maintain momentum This significantly increases the time required to produce a chapter and reduces the effectiveness of the tool for ongoing projects. 5. Impact on Productivity and User Experience The cumulative effect of these issues is substantial: More time is spent correcting the AI than writing with it Creative momentum is repeatedly broken The tool becomes unreliable for long‑form fiction The user is often forced to write scenes manually after multiple failed attempts The overall experience becomes frustrating rather than supportive For writers who already provide detailed outlines, worldbuilding, and direction, the expectation is that the AI should support the process—not require constant correction. 6. Recommendation: Need for Robust Consistency & Memory Tools To address these challenges, the following capabilities would be highly valuable: A Consistency Checker that tracks character knowledge, world rules, timelines, and prior events A Chapter Memory or “Read Previous Chapter” function that reliably retains context Stronger adherence to explicit user instructions Improved long‑form continuity across scenes and chapters Better handling of multi‑chapter projects without losing context when chats reset These improvements would dramatically enhance the tool’s usefulness for fiction writers and reduce the need for repeated manual intervention.

Tabatha Jo Ewart about 11 hours ago

💡 Feature Request

Series Page Improved

When entering the series page, Sudowrite shows the SERIES TIMELINE and below the PROJECTS that are usually sorted by last access. Would be much useful to have the following improvement in that interface: Clicking the PROJECTS title in the TIMELINE should directly open the PROJECT (faster then scroll down to look for the right PROJECT for long series with several PROJECTS in it). Near each PROJECT of the Series you can add a button that will create a summary of that PROJECT that will appear in a special section below sorted following the TIMELINE sequence. This summary will contain a short summary of the document story and a short summary of the actual situation of each Series Characters (The list of the Series Characters will be shown below and they can be selected in the Story Bible) Below you can add a “Whole Series Story Bible” that will show Brainstorms, Notes, A series synopsis, and the Summaries of each PROJECT of the series sorted by Timeline and the Characters Evolution through the Serie (generated with the procedure explained above). The Whole Series Story Bible can be used by AI or not (a trigger will enable or disable this) The option to add an image cover for the Series and for each Document of the Series Another great improvement would be to have a esteemed toke use near each filed that will actually used by AI when generating text, this way the user can choose if to enable or disable parts of the Story Bible from being used by AI. And When choosing Write or Extend or something that will actively use the AI, you can show a Confirmation prompt showing how many token we are using (esteemed).

Techno Dominium 15 days ago

💡 Feature Request