Credits
I think you should reconsider the general rules regarding the use of credit. I believe that, since we pay for them, we shouldn’t lose them, and any that remain unused – because for some reason we can’t sit down to write in a given month – should be carried over to our account for the following month, together with those for the month after that, provided the subscription remains active. I think thats a fair option.After all, we pay for the credits you offer as part of the plan, as well as for any extra ones we buy. We don’t get them for free, right?
xd xd 26 days ago
💡 Feature Request
Credits
I think you should reconsider the general rules regarding the use of credit. I believe that, since we pay for them, we shouldn’t lose them, and any that remain unused – because for some reason we can’t sit down to write in a given month – should be carried over to our account for the following month, together with those for the month after that, provided the subscription remains active. I think thats a fair option.After all, we pay for the credits you offer as part of the plan, as well as for any extra ones we buy. We don’t get them for free, right?
xd xd 26 days ago
💡 Feature Request
Increase the word count to import into Sudowrite.
Most new authors create manuscripts that are too long for a conventional novel. Sudowrite doesn’t seem to handle transitions if you’ve broken apart your story to fit the word limit. For instance, if I change anything in the Story Bible for one part, I have to remember to go and change it in the other to prevent Sudowrtie from getting confused on details across the parts. Giving Sudowrite a better ability to handle the entire story to suggest edits and the author the ability to search with flipping across parts would be tremendously helpful.
Bryan Carter 4 days ago
💡 Feature Request
Increase the word count to import into Sudowrite.
Most new authors create manuscripts that are too long for a conventional novel. Sudowrite doesn’t seem to handle transitions if you’ve broken apart your story to fit the word limit. For instance, if I change anything in the Story Bible for one part, I have to remember to go and change it in the other to prevent Sudowrtie from getting confused on details across the parts. Giving Sudowrite a better ability to handle the entire story to suggest edits and the author the ability to search with flipping across parts would be tremendously helpful.
Bryan Carter 4 days ago
💡 Feature Request
Better Style Controls: Longer Instructions + Multiple Labeled Style Examples
The current 40-word Style limit is very restrictive for writers with a specific established voice. Forty words is enough for broad directions like “warm, intimate, funny contemporary prose,” but not enough to communicate more nuanced preferences around paragraph structure, interiority, dialogue, humour, description, sentence rhythm, things to avoid, etc. The 1,000-word Style Examples feature is extremely useful, but I’d also love to be able to provide multiple labeled examples rather than one general sample. For example: Dialogue / Banter [sample] Interiority / Emotional Scenes [sample] Setting / Description [sample] Romantic / Physical Tension [sample] Action / Fast-paced Scenes [sample] These aren't different “styles” — they're different expressions of the same author's voice. A novelist's prose doesn't behave identically in every kind of scene. Ideally: increase the 40-word Style instruction limit substantially; allow several named Style Examples; increase the total example allowance beyond 1,000 words; let examples be stored per project, rather than account-wide; optionally allow us to select which examples are most relevant for a particular Scene/Draft; make the same style examples available to Write as well as Draft. The current system works well for establishing a broad vibe, but authors bringing in an existing manuscript need enough room to teach Sudowrite the finer mechanics of an already-developed voice. I don't just want to tell the AI what my voice is. I want to be able to show it how that voice behaves in different situations.
Natalie 14 days ago
💡 Feature Request
Better Style Controls: Longer Instructions + Multiple Labeled Style Examples
The current 40-word Style limit is very restrictive for writers with a specific established voice. Forty words is enough for broad directions like “warm, intimate, funny contemporary prose,” but not enough to communicate more nuanced preferences around paragraph structure, interiority, dialogue, humour, description, sentence rhythm, things to avoid, etc. The 1,000-word Style Examples feature is extremely useful, but I’d also love to be able to provide multiple labeled examples rather than one general sample. For example: Dialogue / Banter [sample] Interiority / Emotional Scenes [sample] Setting / Description [sample] Romantic / Physical Tension [sample] Action / Fast-paced Scenes [sample] These aren't different “styles” — they're different expressions of the same author's voice. A novelist's prose doesn't behave identically in every kind of scene. Ideally: increase the 40-word Style instruction limit substantially; allow several named Style Examples; increase the total example allowance beyond 1,000 words; let examples be stored per project, rather than account-wide; optionally allow us to select which examples are most relevant for a particular Scene/Draft; make the same style examples available to Write as well as Draft. The current system works well for establishing a broad vibe, but authors bringing in an existing manuscript need enough room to teach Sudowrite the finer mechanics of an already-developed voice. I don't just want to tell the AI what my voice is. I want to be able to show it how that voice behaves in different situations.
Natalie 14 days ago
💡 Feature Request
Feature Request: Let the Expand Feature Respect the Highlighted Text’s Ending Beat
I use Expand a lot, and it may be my favorite feature in Sudowrite. For the kind of drafting I do, I find it more useful than any of the Rewrite options. My typical use case is taking a rough chapter or scene that has all the correct story beats but still feels flat—too much talking heads, summarized emotion, or scene direction—and using Expand to add the missing layers. With Muse 1.5 especially, it can turn that rough scene skeleton into something much closer to a polished chapter. I still need to revise the result into my own voice, but it gives me strong material to work with and is excellent for getting past writer’s block. Expand is valuable enough that I could see myself using Sudowrite primarily for this feature if the boundary behavior were dialed in. The main problem is that Expand does not reliably respect the narrative boundaries of the highlighted text. In my testing, medium and larger selections often produce around 1,500 words of output regardless of the amount selected: 949 words highlighted → 1,520 words output → 21,938 tokens 245 words highlighted → 1,549 words output → 6,278 tokens 19 words highlighted → 344 words output → 3,305 tokens So it clearly is not always targeting exactly 1,500 words, but the amount of expansion does not seem to scale naturally with the selected material. This creates two opposite problems. With shorter selections, Expand can reach the final beat of the highlighted text and then continue inventing what happens next. Because it does not appear to consider the following chapter, that new material can take the story in a completely different direction from what is already written next. With longer selections, the prose can be excellent, but the generation simply stops around the output limit while it is still partway through the selected scene. Trying to solve this by highlighting several smaller sections and expanding them separately does not work very well either, because each section can continue beyond its ending beat. The pieces then overlap or introduce events that were never supposed to happen. What I would really like is for the highlighted text to function as a narrative container. Expand should essentially follow this instruction: Start with the first beat represented in the highlighted text. Expand the lived experience between the existing beats. Preserve the events and direction of the selected material. Reach the final beat represented in the selection and stop there. Do not continue the story beyond that ending beat. Even better would be an optional way to specify a Start Beat and End Beat, with the End Beat treated as a hard boundary. For example: Start Beat: Main character arrives at the storage unit. End Beat: Main character finds the old key. Expand everything between those beats, but do not continue beyond the discovery of the key. I don’t necessarily need Expand to produce a particular number of words. In fact, I think output length should be subordinate to covering the selected material. A 250-word scene skeleton might need 800 or 1,200 words. A 950-word rough scene might need 2,000 or more. A tiny selection may only need a few hundred. A Light / Medium / Deep expansion setting would be useful, but the more important feature is simply: fully expand the selected material without going beyond its ending beat. I have also tried using Key Details under Write Settings to explicitly tell the model what beat it must end on. That does not seem to reliably constrain Expand; Muse will still continue beyond the ending beat. If Key Details is supposed to apply to Expand, there ma
Kenji about 11 hours ago
💡 Feature Request
Feature Request: Let the Expand Feature Respect the Highlighted Text’s Ending Beat
I use Expand a lot, and it may be my favorite feature in Sudowrite. For the kind of drafting I do, I find it more useful than any of the Rewrite options. My typical use case is taking a rough chapter or scene that has all the correct story beats but still feels flat—too much talking heads, summarized emotion, or scene direction—and using Expand to add the missing layers. With Muse 1.5 especially, it can turn that rough scene skeleton into something much closer to a polished chapter. I still need to revise the result into my own voice, but it gives me strong material to work with and is excellent for getting past writer’s block. Expand is valuable enough that I could see myself using Sudowrite primarily for this feature if the boundary behavior were dialed in. The main problem is that Expand does not reliably respect the narrative boundaries of the highlighted text. In my testing, medium and larger selections often produce around 1,500 words of output regardless of the amount selected: 949 words highlighted → 1,520 words output → 21,938 tokens 245 words highlighted → 1,549 words output → 6,278 tokens 19 words highlighted → 344 words output → 3,305 tokens So it clearly is not always targeting exactly 1,500 words, but the amount of expansion does not seem to scale naturally with the selected material. This creates two opposite problems. With shorter selections, Expand can reach the final beat of the highlighted text and then continue inventing what happens next. Because it does not appear to consider the following chapter, that new material can take the story in a completely different direction from what is already written next. With longer selections, the prose can be excellent, but the generation simply stops around the output limit while it is still partway through the selected scene. Trying to solve this by highlighting several smaller sections and expanding them separately does not work very well either, because each section can continue beyond its ending beat. The pieces then overlap or introduce events that were never supposed to happen. What I would really like is for the highlighted text to function as a narrative container. Expand should essentially follow this instruction: Start with the first beat represented in the highlighted text. Expand the lived experience between the existing beats. Preserve the events and direction of the selected material. Reach the final beat represented in the selection and stop there. Do not continue the story beyond that ending beat. Even better would be an optional way to specify a Start Beat and End Beat, with the End Beat treated as a hard boundary. For example: Start Beat: Main character arrives at the storage unit. End Beat: Main character finds the old key. Expand everything between those beats, but do not continue beyond the discovery of the key. I don’t necessarily need Expand to produce a particular number of words. In fact, I think output length should be subordinate to covering the selected material. A 250-word scene skeleton might need 800 or 1,200 words. A 950-word rough scene might need 2,000 or more. A tiny selection may only need a few hundred. A Light / Medium / Deep expansion setting would be useful, but the more important feature is simply: fully expand the selected material without going beyond its ending beat. I have also tried using Key Details under Write Settings to explicitly tell the model what beat it must end on. That does not seem to reliably constrain Expand; Muse will still continue beyond the ending beat. If Key Details is supposed to apply to Expand, there ma
Kenji about 11 hours ago
💡 Feature Request
Line Numbers
Having line numbers would greatly help when writing chapters. The scroll bar on the side is slightly helpful, but since it takes into consideration the story bible added to the bottom of every chapter, it is minimal in helping to maintain position within the narrative. Line numbers would greatly help locating repeating information and determining the location of prose and other information.
Dawn Garcia 18 days ago
💡 Feature Request
Line Numbers
Having line numbers would greatly help when writing chapters. The scroll bar on the side is slightly helpful, but since it takes into consideration the story bible added to the bottom of every chapter, it is minimal in helping to maintain position within the narrative. Line numbers would greatly help locating repeating information and determining the location of prose and other information.
Dawn Garcia 18 days ago
💡 Feature Request
retain AI model used in a chapter
It would be useful to store what AI model was used in the generated text of a chapter- e.g. in the History. That way when I come back to the text at a later time for continuation or improvement purposes I can recall it.
Anonymous author 5 days ago
Web app
💡 Feature Request
retain AI model used in a chapter
It would be useful to store what AI model was used in the generated text of a chapter- e.g. in the History. That way when I come back to the text at a later time for continuation or improvement purposes I can recall it.
Anonymous author 5 days ago
Web app
💡 Feature Request
Story Bible Reference Library — Upload Our Own Docs & Images as AI Context
I’d love a freeform Reference Library inside Story Bible where we can upload our own existing materials — DOCX, PDF, TXT, images, etc. — and allow Sudowrite to use them as project context without requiring us to convert everything into individual Story Bible fields first. The structured Story Bible is great for writers who like that workflow or are developing a project from scratch. But many writers come to Sudowrite with an established manuscript and years of existing development material: character bibles, relationship arcs, timelines, continuity documents, location research, visual references, style guides, maps, photographs, and so on. Re-entering all of that information manually into separate Character and Worldbuilding fields is extremely time-consuming, and it also forces everyone into the same organizational system. I’d love the option to simply upload something like: Luke Character Architecture.docx Visual Continuity.pdf Relationship Timeline.docx Austin Locations.pdf reference images for characters, homes, clothing, locations, etc. …and tell Sudowrite: these are authoritative reference materials for this project; use them when relevant. Ideally, uploaded references could be: searchable/readable by Chat, Write and Draft; optionally enabled or disabled as AI context; organised into folders or categories; referenced with # mentions when we specifically want the AI to consult one; supplemented by images the AI can actually interpret when describing characters or settings. Smart Character Import is useful, but I don’t necessarily want the AI to extract my carefully organised documents and redistribute their contents into dozens of form fields. Sometimes the document itself is already the best Story Bible. Keep the structured forms for writers who want them — but give experienced writers and imported projects a freeform option too. This would make Sudowrite dramatically easier to adopt for writers who already have a mature project rather than beginning a new novel inside the app.
Natalie 14 days ago
💡 Feature Request
Story Bible Reference Library — Upload Our Own Docs & Images as AI Context
I’d love a freeform Reference Library inside Story Bible where we can upload our own existing materials — DOCX, PDF, TXT, images, etc. — and allow Sudowrite to use them as project context without requiring us to convert everything into individual Story Bible fields first. The structured Story Bible is great for writers who like that workflow or are developing a project from scratch. But many writers come to Sudowrite with an established manuscript and years of existing development material: character bibles, relationship arcs, timelines, continuity documents, location research, visual references, style guides, maps, photographs, and so on. Re-entering all of that information manually into separate Character and Worldbuilding fields is extremely time-consuming, and it also forces everyone into the same organizational system. I’d love the option to simply upload something like: Luke Character Architecture.docx Visual Continuity.pdf Relationship Timeline.docx Austin Locations.pdf reference images for characters, homes, clothing, locations, etc. …and tell Sudowrite: these are authoritative reference materials for this project; use them when relevant. Ideally, uploaded references could be: searchable/readable by Chat, Write and Draft; optionally enabled or disabled as AI context; organised into folders or categories; referenced with # mentions when we specifically want the AI to consult one; supplemented by images the AI can actually interpret when describing characters or settings. Smart Character Import is useful, but I don’t necessarily want the AI to extract my carefully organised documents and redistribute their contents into dozens of form fields. Sometimes the document itself is already the best Story Bible. Keep the structured forms for writers who want them — but give experienced writers and imported projects a freeform option too. This would make Sudowrite dramatically easier to adopt for writers who already have a mature project rather than beginning a new novel inside the app.
Natalie 14 days ago
💡 Feature Request
Reviews/Ratings for Plugins
Lately I’ve been enjoying exploring different plugins. I’ve tried several and even created a couple of my own. It would be really helpful if there were a way to rate plugins (1-5 stars) and/or leave brief reviews/comments on them. For example, I found several that promise to improve a fight scene, and I would love to see which one(s) other users find the most helpful, and why, before I spend my credits using one that may not be as useful as others. I would also like to leave my own reviews so that in the future I could look back and remember that this one didn’t serve my purposes well, but that one was great. It would also be nice to leave a question/suggestion for the person who created the plugin, such as requesting they consider editing it to add additional parameters that would make it more useful. (I’d love to hear that kind of feedback from anyone who uses mine.)
Annie Douglass Lima 14 days ago
Web app
💡 Feature Request
Reviews/Ratings for Plugins
Lately I’ve been enjoying exploring different plugins. I’ve tried several and even created a couple of my own. It would be really helpful if there were a way to rate plugins (1-5 stars) and/or leave brief reviews/comments on them. For example, I found several that promise to improve a fight scene, and I would love to see which one(s) other users find the most helpful, and why, before I spend my credits using one that may not be as useful as others. I would also like to leave my own reviews so that in the future I could look back and remember that this one didn’t serve my purposes well, but that one was great. It would also be nice to leave a question/suggestion for the person who created the plugin, such as requesting they consider editing it to add additional parameters that would make it more useful. (I’d love to hear that kind of feedback from anyone who uses mine.)
Annie Douglass Lima 14 days ago
Web app
💡 Feature Request
Able to buy credits without having to have a subscription
I think that you should be able to buy credits from a marketplace without having a subscription. And it should also be that if you buy them and don’t use them, then you still get to keep them, and they don’t disappear. The AI that Sudowrite has is really good, but the UX could be improved on the credit front.
Olive Burgess 15 days ago
💡 Feature Request
Able to buy credits without having to have a subscription
I think that you should be able to buy credits from a marketplace without having a subscription. And it should also be that if you buy them and don’t use them, then you still get to keep them, and they don’t disappear. The AI that Sudowrite has is really good, but the UX could be improved on the credit front.
Olive Burgess 15 days ago
💡 Feature Request
Should consider a daily credit system
I'm not sure if I'm going to resubscribe because I already used all of my credits. I bought the hobby plan because that's what I can afford. I somehow scrounged up enough for a 5$ credit pack and went through that too. Now I have to go almost a full month before I can write again, and it's frustrating.
Tiffany Phelps about 1 month ago
Mobile app
💡 Feature Request
Should consider a daily credit system
I'm not sure if I'm going to resubscribe because I already used all of my credits. I bought the hobby plan because that's what I can afford. I somehow scrounged up enough for a 5$ credit pack and went through that too. Now I have to go almost a full month before I can write again, and it's frustrating.
Tiffany Phelps about 1 month ago
Mobile app
💡 Feature Request
Full Export of project to a Scrivener project
An added feature now allows for importing into Sudowrite from a Scrivener project. How about the reverse: all a full export from Sudowrite to a Scrivener project?
Terry Bauer 25 days ago
Web app
💡 Feature Request
Full Export of project to a Scrivener project
An added feature now allows for importing into Sudowrite from a Scrivener project. How about the reverse: all a full export from Sudowrite to a Scrivener project?
Terry Bauer 25 days ago
Web app
💡 Feature Request
Scroll Bars and Scroling
Maybe it’s just me, but I see this is an issue that has come up before. I’ll add my voice to it. 🤔 Scrolling and selecting the scroll arrows are really difficult as they are virtually invisible and so small. It is a little better on a large-screen PC. However, on a laptop, having to use the touchpad, it is a real pain and very frustrating to see or click on the scroll arrows or the bar. Making them more visible and bigger would surely be a significant improvement.😉
Michelle about 1 month ago
🗳️ Feedback
Scroll Bars and Scroling
Maybe it’s just me, but I see this is an issue that has come up before. I’ll add my voice to it. 🤔 Scrolling and selecting the scroll arrows are really difficult as they are virtually invisible and so small. It is a little better on a large-screen PC. However, on a laptop, having to use the touchpad, it is a real pain and very frustrating to see or click on the scroll arrows or the bar. Making them more visible and bigger would surely be a significant improvement.😉
Michelle about 1 month ago
🗳️ Feedback
Add a Thai language menu for users who primarily use Thai.
Add Thai language support for Thai-speaking users like myself to write stories.
Valkyrie Toyota about 23 hours ago
Web app
💡 Feature Request
Add a Thai language menu for users who primarily use Thai.
Add Thai language support for Thai-speaking users like myself to write stories.
Valkyrie Toyota about 23 hours ago
Web app
💡 Feature Request
Query Ready!
I would love a feature that helps us tighten the synopsis for marketing/query letters or book proposals. This would be SO helpful as we launch our manuscripts into the world. Great features could include Loglines Short Synopsis (Under 500 words) Medium Synopsis (501-1000 words) Long Synopsis (1001-1200 words) Pitch (2 short paragraphs Backcover Blurbs (under 500 words)
Mia Burke about 1 month ago
💡 Feature Request
Query Ready!
I would love a feature that helps us tighten the synopsis for marketing/query letters or book proposals. This would be SO helpful as we launch our manuscripts into the world. Great features could include Loglines Short Synopsis (Under 500 words) Medium Synopsis (501-1000 words) Long Synopsis (1001-1200 words) Pitch (2 short paragraphs Backcover Blurbs (under 500 words)
Mia Burke about 1 month ago
💡 Feature Request
Character Insopration Photos
I think it would be helpful if we were able to add or create character photos to add to the character generation section of the story bible.
Teagon Malone 1 day ago
Web app
💡 Feature Request
Character Insopration Photos
I think it would be helpful if we were able to add or create character photos to add to the character generation section of the story bible.
Teagon Malone 1 day ago
Web app
💡 Feature Request
series help
It is a series type it would nice be able to combine character profiles so four sections it does not list four versions of the character
lameone about 1 month ago
Web app
💡 Feature Request
series help
It is a series type it would nice be able to combine character profiles so four sections it does not list four versions of the character
lameone about 1 month ago
Web app
💡 Feature Request
Remove the black tool bar that pops up annoyingly often
It gets in my way when I’m highlighting text, and I have never once used it. I would like to option to simply turn it off.
F Rogers about 1 month ago
💡 Feature Request
Remove the black tool bar that pops up annoyingly often
It gets in my way when I’m highlighting text, and I have never once used it. I would like to option to simply turn it off.
F Rogers about 1 month ago
💡 Feature Request
