Bring Back near-infinite current doc readback for the models that can handle it
My longer novel books pipeline has been quashed by the recent continuity upgrade... Essentially - I can't get beyond 40k in a doc on Excellent or Sonnet 3.7 anymore - and I was regularly getting 60k-100k in one pass without any hick-ups except for Claude issues on the backend - but, I'd just restart and they'd continue and finish... So. The problem is we now have a hard 20k limit on the current doc readback - even on Excellent and Sonnet 3.7 which could handle a higher limit fine. How does this interrupt my process? Essentially - both quit working around around scene 6 reliably - then I can restart them and they go until ~40k. Then I can't restart them - they never get to the thinking or writing phase. One work around is to split the file from 40k down to 20k in continuity and 20k in readback - and that is good for another 20k. But, again, beyond that and it won't write. And, I could be summarizing each chapter and reducing it to fit - but I know it can work fine without this labour intensive step AND I don't think I get better prose this way. My dream come true? Give me some way to get Sonnet 3.7 thinking with the unlimited by SW readback (and the continuity, but I could live without the continuity). Pretty Please? Yes, I could vibe code this myself - but I'd rather stay within the SW ecosystem. I have a little bit of an update to this… Essentially - I can get to 90k as long as the model holds out and doesn’t crash. Getting restarted is the kicker. I recently kicked off a 32 chapter (scenes) book in sonnet 3.7. The model died at 30k. I split it and put 20k into a first doc and 10k into the second doc that I then continued. Second doc made it to the end of the book - 70k in the second doc - 90k in total. You can see why this is frustrating. As long as the model holds out, I end up with a pretty coherent draft. If the model crashes and burns, I have to figure out how to restart with as much info as i can give it… If I’m over 40k in, it will be harder to set it up for success.
John Creson 22 days ago
💡 Feature Request
Bring Back near-infinite current doc readback for the models that can handle it
My longer novel books pipeline has been quashed by the recent continuity upgrade... Essentially - I can't get beyond 40k in a doc on Excellent or Sonnet 3.7 anymore - and I was regularly getting 60k-100k in one pass without any hick-ups except for Claude issues on the backend - but, I'd just restart and they'd continue and finish... So. The problem is we now have a hard 20k limit on the current doc readback - even on Excellent and Sonnet 3.7 which could handle a higher limit fine. How does this interrupt my process? Essentially - both quit working around around scene 6 reliably - then I can restart them and they go until ~40k. Then I can't restart them - they never get to the thinking or writing phase. One work around is to split the file from 40k down to 20k in continuity and 20k in readback - and that is good for another 20k. But, again, beyond that and it won't write. And, I could be summarizing each chapter and reducing it to fit - but I know it can work fine without this labour intensive step AND I don't think I get better prose this way. My dream come true? Give me some way to get Sonnet 3.7 thinking with the unlimited by SW readback (and the continuity, but I could live without the continuity). Pretty Please? Yes, I could vibe code this myself - but I'd rather stay within the SW ecosystem. I have a little bit of an update to this… Essentially - I can get to 90k as long as the model holds out and doesn’t crash. Getting restarted is the kicker. I recently kicked off a 32 chapter (scenes) book in sonnet 3.7. The model died at 30k. I split it and put 20k into a first doc and 10k into the second doc that I then continued. Second doc made it to the end of the book - 70k in the second doc - 90k in total. You can see why this is frustrating. As long as the model holds out, I end up with a pretty coherent draft. If the model crashes and burns, I have to figure out how to restart with as much info as i can give it… If I’m over 40k in, it will be harder to set it up for success.
John Creson 22 days ago
💡 Feature Request
Chapter Draft Status
I would like to have a “Status” per chapter. So I can make chapters in various status [Outlined, Early Draft, Draft, Refined, Revised, Copyedited, Reviewed, Complete] There is no need to do anything with the status or force any kind of a workflow. These would just help authors track where they’ve spent their time and effort and how confident/content they are with each chapter. This is a low-effort/high value feature.
Andrew Pearson 4 days ago
💡 Feature Request
Chapter Draft Status
I would like to have a “Status” per chapter. So I can make chapters in various status [Outlined, Early Draft, Draft, Refined, Revised, Copyedited, Reviewed, Complete] There is no need to do anything with the status or force any kind of a workflow. These would just help authors track where they’ve spent their time and effort and how confident/content they are with each chapter. This is a low-effort/high value feature.
Andrew Pearson 4 days ago
💡 Feature Request
Custom Styles
Feature Request for Style Customization (SudoWrite) Could we please have a way to create and save up to 5–10 custom writing styles within the existing style menu? Ideally, we’d be able to toggle them on or off directly from the same box we already use—no extra tabs or menus needed. This would make it easy to switch between different tone presets for different books or scenes without constantly retyping the same prompts. (Also—40-word limit is tight, but I make it work. Still, an expanded option for power-users would be welcome.)
Tiffany JadeDarkStar About 3 hours ago
💡 Feature Request
Custom Styles
Feature Request for Style Customization (SudoWrite) Could we please have a way to create and save up to 5–10 custom writing styles within the existing style menu? Ideally, we’d be able to toggle them on or off directly from the same box we already use—no extra tabs or menus needed. This would make it easy to switch between different tone presets for different books or scenes without constantly retyping the same prompts. (Also—40-word limit is tight, but I make it work. Still, an expanded option for power-users would be welcome.)
Tiffany JadeDarkStar About 3 hours ago
💡 Feature Request
More precise credit estimation, please!
In chapter generation, the credits used surpass at least 30% the highest estimation. If estimated credit costs says “14.000 to max. 20.000”, I can be sure to see at least 30.000 credits used. This is irritating as hell. Please be aware that I do not mind the cost; this is not about credit anxiety, but about a more reliable estimation.
Gunda Plewe 2 days ago
💡 Feature Request
More precise credit estimation, please!
In chapter generation, the credits used surpass at least 30% the highest estimation. If estimated credit costs says “14.000 to max. 20.000”, I can be sure to see at least 30.000 credits used. This is irritating as hell. Please be aware that I do not mind the cost; this is not about credit anxiety, but about a more reliable estimation.
Gunda Plewe 2 days ago
💡 Feature Request
Let the Story Bible draw from written chapters, not just vice-versa
I have noticed that whenever I make manual changes to a chapter or scene, there is no feature that can draw on said changes to reflect in the Story Bible. Instead I have to manually find every single instance in the character/lore/outline/etc. And manually change it. I would love a function that allowed certain entries in the story bible to draw from written chapters, or at least from each other, since many items in the story bible correlate.
Carlos Toca 14 days ago
💡 Feature Request
Let the Story Bible draw from written chapters, not just vice-versa
I have noticed that whenever I make manual changes to a chapter or scene, there is no feature that can draw on said changes to reflect in the Story Bible. Instead I have to manually find every single instance in the character/lore/outline/etc. And manually change it. I would love a function that allowed certain entries in the story bible to draw from written chapters, or at least from each other, since many items in the story bible correlate.
Carlos Toca 14 days ago
💡 Feature Request
Let The User Decide What The AI Looks At—Everywhere
Feature Request A user shouldn’t have to wonder what the AI is looking at, and we should have settings to tell it exactly what to refer to. Everywhere. Other AI programs already utilize this. This feature would nullify it looking at incorrect things, spoilers, or not looking at needed information. And it shouldn’t be decided by someone else what they think the AI should reference for an author’s work. Style has been left out of referencing for entirely too much when it’s arguably THE most important thing and should impact how everything gets written. As it is, extra work is created because the user has to rewrite every single box or risk all of those cliches and AI-wording being brought in, which it will be if not corrected. Another issue this solves is conflicting information when we are told the AI does or doesn’t look at something. More than once, a statement has been casually made about a particular element being looked at to generate something, however, we were never told that or even told the opposite prior. As a teacher, this makes it worse because now I’m passing along faulty information. If the user is deciding, there’s no wondering for anyone. Put it in the hands of the users. A gear icon on each Story Bible box can open up a menu for users to toggle on or off. Want Outline to influence Characters so an arc can be created? Toggle the Characters option on. Want it simple? If a box toggle is on, it influences what you’re generating; if it’s off, the AI doesn’t see it. As a plus, this also lets the AI read backwards and forwards, resulting in the user being able to best utilize each box for their own workflow. And bonus, there could be a toggle by each document to have it read or not, which is helpful for say a large world-building document or glossary. It’s also simpler and quicker than the three dots menu for continuity. Example use: Instead of the user needing to create templates and fill out traits, information could be contained in the document, thus allowing yet more flexibility in the user’s workflow. The icing on the cake would be that if the other tools were hooked up to Story Bible—and for those that currently are—the user would be able to decide what gets looked at. Want Rewrite to see your entire outline so it can foreshadow or callback properly when it rewrites the current scene? Done. Want Quick Edit or Quick Chat to look at certain documents or Story Bible elements? Toggle it on. The bottom line is this puts the user in control, and they can decide how much or how little to give the AI while also making it very flexible and upfront about what is being looked at.
Nicole Broussard About 1 month ago
💡 Feature Request
Let The User Decide What The AI Looks At—Everywhere
Feature Request A user shouldn’t have to wonder what the AI is looking at, and we should have settings to tell it exactly what to refer to. Everywhere. Other AI programs already utilize this. This feature would nullify it looking at incorrect things, spoilers, or not looking at needed information. And it shouldn’t be decided by someone else what they think the AI should reference for an author’s work. Style has been left out of referencing for entirely too much when it’s arguably THE most important thing and should impact how everything gets written. As it is, extra work is created because the user has to rewrite every single box or risk all of those cliches and AI-wording being brought in, which it will be if not corrected. Another issue this solves is conflicting information when we are told the AI does or doesn’t look at something. More than once, a statement has been casually made about a particular element being looked at to generate something, however, we were never told that or even told the opposite prior. As a teacher, this makes it worse because now I’m passing along faulty information. If the user is deciding, there’s no wondering for anyone. Put it in the hands of the users. A gear icon on each Story Bible box can open up a menu for users to toggle on or off. Want Outline to influence Characters so an arc can be created? Toggle the Characters option on. Want it simple? If a box toggle is on, it influences what you’re generating; if it’s off, the AI doesn’t see it. As a plus, this also lets the AI read backwards and forwards, resulting in the user being able to best utilize each box for their own workflow. And bonus, there could be a toggle by each document to have it read or not, which is helpful for say a large world-building document or glossary. It’s also simpler and quicker than the three dots menu for continuity. Example use: Instead of the user needing to create templates and fill out traits, information could be contained in the document, thus allowing yet more flexibility in the user’s workflow. The icing on the cake would be that if the other tools were hooked up to Story Bible—and for those that currently are—the user would be able to decide what gets looked at. Want Rewrite to see your entire outline so it can foreshadow or callback properly when it rewrites the current scene? Done. Want Quick Edit or Quick Chat to look at certain documents or Story Bible elements? Toggle it on. The bottom line is this puts the user in control, and they can decide how much or how little to give the AI while also making it very flexible and upfront about what is being looked at.
Nicole Broussard About 1 month ago
💡 Feature Request
Store Guided Write Prompts
It would be nice if, instead of seeing the preceding text in the card with Guided Write’s output, you saw the text you gave it in the Guided Write box. We don’t need the preceding text. We see that in the document. I have however, wanted to use the prompt again but can’t since it disappears after each generation. In this instance, even persistent text wouldn’t be enough because I often want to go back after a few runs and grab recent instructions to try something else with them.
Nicole Broussard 17 days ago
💡 Feature Request
Store Guided Write Prompts
It would be nice if, instead of seeing the preceding text in the card with Guided Write’s output, you saw the text you gave it in the Guided Write box. We don’t need the preceding text. We see that in the document. I have however, wanted to use the prompt again but can’t since it disappears after each generation. In this instance, even persistent text wouldn’t be enough because I often want to go back after a few runs and grab recent instructions to try something else with them.
Nicole Broussard 17 days ago
💡 Feature Request
Continue Button Access should always be available
The Draft box continue button only shows up once I’ve drafted some words. I need to be able to start my chapter myself and have Draft finish it off - from scratch without having to first generate prose and then throw that away so I can go back to start it from where I want to start it. Workaround is to NEVER create a new document - just always duplicate an already Continue-able doc or template project that holds one these to start out from.
John Creson 3 days ago
💡 Feature Request
Continue Button Access should always be available
The Draft box continue button only shows up once I’ve drafted some words. I need to be able to start my chapter myself and have Draft finish it off - from scratch without having to first generate prose and then throw that away so I can go back to start it from where I want to start it. Workaround is to NEVER create a new document - just always duplicate an already Continue-able doc or template project that holds one these to start out from.
John Creson 3 days ago
💡 Feature Request
Could you please make it an option to use Muse 1.5 with Rewrite?
I’ve just started experimenting with Muse 1.5 (amazing!) and would love to be able to use it in Rewrite.
bonnielala@gmail.com 9 days ago
💡 Feature Request
Could you please make it an option to use Muse 1.5 with Rewrite?
I’ve just started experimenting with Muse 1.5 (amazing!) and would love to be able to use it in Rewrite.
bonnielala@gmail.com 9 days ago
💡 Feature Request
Highlight Items from the Story Bible in the Chapters
I would like it if in the chapter canvas, while I am typing, if I use a proper noun that exists in the Story Bible, it will be automatically underlined with some colorful line. If I place the mouse over the word, I would like to see a small popup card that shows details from the story bible. Additionally, a tab on the card that can show me other uses of that noun. Example: Billy Bob and Susan drove to the City Movie Theatre to buy some popcorn. Billy Bob and City Movie Theatre exist in the story bible, so they become underscored. If I were to put the mouse over it, I’d get the popup. Susan, not being in the story bible, wouldn’t get the popup or underscore at all.
Andrew Pearson 4 days ago
💡 Feature Request
Highlight Items from the Story Bible in the Chapters
I would like it if in the chapter canvas, while I am typing, if I use a proper noun that exists in the Story Bible, it will be automatically underlined with some colorful line. If I place the mouse over the word, I would like to see a small popup card that shows details from the story bible. Additionally, a tab on the card that can show me other uses of that noun. Example: Billy Bob and Susan drove to the City Movie Theatre to buy some popcorn. Billy Bob and City Movie Theatre exist in the story bible, so they become underscored. If I were to put the mouse over it, I’d get the popup. Susan, not being in the story bible, wouldn’t get the popup or underscore at all.
Andrew Pearson 4 days ago
💡 Feature Request
Planned
Allow users to list certain words that are forbidden
We desperately need a feature that lets us forbid certain words. I have tried everything I can think of but half the time I click the generate button a specific character is given a tail that swishes around to show emotion despite multiple attempts to make it stop. The AI also seems to occasionally get stuck on certain words like “strategic” and attempts to put them in every other sentence for no reason.
Josiah Shaw About 2 months ago
💡 Feature Request
Planned
Allow users to list certain words that are forbidden
We desperately need a feature that lets us forbid certain words. I have tried everything I can think of but half the time I click the generate button a specific character is given a tail that swishes around to show emotion despite multiple attempts to make it stop. The AI also seems to occasionally get stuck on certain words like “strategic” and attempts to put them in every other sentence for no reason.
Josiah Shaw About 2 months ago
💡 Feature Request
Timeline Creation that the bible can draw from
I want to create a time line of key plot points that the bible can look at and reference when writing a scene or paragraph. I put points in the bible for “later on, not yet” but it still tries to put those points in now instead of later on - even in guided mode. Something like a timeline where you can toggle what the bible uses and what it ignores (or half ignores) would be amazing. And it’d be even better if the ignored timeline points were still referenced for things like fore-shadowing.
Maria Harvey 4 days ago
💡 Feature Request
Timeline Creation that the bible can draw from
I want to create a time line of key plot points that the bible can look at and reference when writing a scene or paragraph. I put points in the bible for “later on, not yet” but it still tries to put those points in now instead of later on - even in guided mode. Something like a timeline where you can toggle what the bible uses and what it ignores (or half ignores) would be amazing. And it’d be even better if the ignored timeline points were still referenced for things like fore-shadowing.
Maria Harvey 4 days ago
💡 Feature Request
Writing Prompts
It would be awesome if users could submit writing prompts under a free to use license. Then, other users can click “Random Prompt” and in a new story, and the first chapter would be populated with that prompt. Could be fun for people looking for creative writing exercises.
Andrew Pearson 4 days ago
💡 Feature Request
Writing Prompts
It would be awesome if users could submit writing prompts under a free to use license. Then, other users can click “Random Prompt” and in a new story, and the first chapter would be populated with that prompt. Could be fun for people looking for creative writing exercises.
Andrew Pearson 4 days ago
💡 Feature Request
Way to set "rules" for a particular story that the model will ALWAYS follow.
Right now, even the highest rated model will “go off script” at times. Muse, highly rated for following guidance actually tends to ignore the guidance quite often. In some of my work, there are certain things that are a constant throughout the story and never change. These constants are repeated in many places throughout the story bible, repeated in the instructions for guided write, repeated in instructions in draft mode, etc. Still the model will deviate. This often means I am unable to use the prose generated and must trash that prose. It’s a waste of credits and time.
Al Iwon'tShutUp Hefner 12 days ago
💡 Feature Request
Way to set "rules" for a particular story that the model will ALWAYS follow.
Right now, even the highest rated model will “go off script” at times. Muse, highly rated for following guidance actually tends to ignore the guidance quite often. In some of my work, there are certain things that are a constant throughout the story and never change. These constants are repeated in many places throughout the story bible, repeated in the instructions for guided write, repeated in instructions in draft mode, etc. Still the model will deviate. This often means I am unable to use the prose generated and must trash that prose. It’s a waste of credits and time.
Al Iwon'tShutUp Hefner 12 days ago
💡 Feature Request
PseudoWrite Accessibility for Screen Readers
Hi PseudoWrite Team, My name is Chloe Walton, and I’m a totally blind author currently exploring your platform. I’m deeply excited by what PseudoWrite offers—especially the Story Engine and other generative tools—but I’ve encountered several accessibility barriers that make it difficult to use your features independently and efficiently with a screen reader (I use JAWS/NVDA). Unfortunately, like many blind writers, I’ve become all too familiar with promising writing software that wasn’t built with accessibility in mind. PseudoWrite has enormous potential, but the current interface poses serious challenges: • Navigation is clunky—key elements don’t announce clearly or are difficult to locate. • Form fields and menus are sometimes unlabeled or ungrouped, making it hard to track where I am. • Dynamic content (like scene cards, outlines, or expandable sections) can’t be reliably accessed or interacted with via keyboard or screen reader. • Some buttons or prompts are only visually indicated, with no ARIA labeling or keyboard-friendly alternatives. As a result, I’ve found myself discouraged from fully exploring or subscribing—not because I don’t believe in the tool, but because I can’t access it equally. I hope you’ll consider improving screen reader support across your platform. Writing tools like PseudoWrite could be transformational for blind and visually impaired creatives if designed with accessibility in mind. I'm more than happy to offer insight, feedback, or testing assistance if you're open to it. Thank you so much for your time—and for considering how to make your incredible tool more inclusive for all storytellers. Warmly, Chloe Walton
Chloe Walton 4 days ago
💡 Feature Request
PseudoWrite Accessibility for Screen Readers
Hi PseudoWrite Team, My name is Chloe Walton, and I’m a totally blind author currently exploring your platform. I’m deeply excited by what PseudoWrite offers—especially the Story Engine and other generative tools—but I’ve encountered several accessibility barriers that make it difficult to use your features independently and efficiently with a screen reader (I use JAWS/NVDA). Unfortunately, like many blind writers, I’ve become all too familiar with promising writing software that wasn’t built with accessibility in mind. PseudoWrite has enormous potential, but the current interface poses serious challenges: • Navigation is clunky—key elements don’t announce clearly or are difficult to locate. • Form fields and menus are sometimes unlabeled or ungrouped, making it hard to track where I am. • Dynamic content (like scene cards, outlines, or expandable sections) can’t be reliably accessed or interacted with via keyboard or screen reader. • Some buttons or prompts are only visually indicated, with no ARIA labeling or keyboard-friendly alternatives. As a result, I’ve found myself discouraged from fully exploring or subscribing—not because I don’t believe in the tool, but because I can’t access it equally. I hope you’ll consider improving screen reader support across your platform. Writing tools like PseudoWrite could be transformational for blind and visually impaired creatives if designed with accessibility in mind. I'm more than happy to offer insight, feedback, or testing assistance if you're open to it. Thank you so much for your time—and for considering how to make your incredible tool more inclusive for all storytellers. Warmly, Chloe Walton
Chloe Walton 4 days ago
💡 Feature Request
Chat Style conversation about the book
It would be cool to have a regular Chat style to ask things about the Book, ask for a summary of something of hold a conversation about random ideas that can always refer back to Characters, Chapters and what not
MD 5 days ago
💡 Feature Request
Chat Style conversation about the book
It would be cool to have a regular Chat style to ask things about the Book, ask for a summary of something of hold a conversation about random ideas that can always refer back to Characters, Chapters and what not
MD 5 days ago
💡 Feature Request
character living status
I use the guided writing tool as well as the draft generator tool, and I’ve noticed it’s been pulling in a character that died early in my manuscript, even concocting plots for said character. this was even after I turned off the character’s visibility, included their status as dead in their character bio, and noted their death as a key event in the worldbuilding portion.
A L Diaz 26 days ago
💡 Feature Request
character living status
I use the guided writing tool as well as the draft generator tool, and I’ve noticed it’s been pulling in a character that died early in my manuscript, even concocting plots for said character. this was even after I turned off the character’s visibility, included their status as dead in their character bio, and noted their death as a key event in the worldbuilding portion.
A L Diaz 26 days ago
💡 Feature Request
Adding Visualize option to character description.
While it is nice to be able to have pictures generated in the main story, it would help me if I could have the pictures in the Story Bible as well. You can’t even select text in there to generate anything and that is where I put my most detailed descriptions long before they make it into the story itself.
Blake Betts About 1 month ago
💡 Feature Request
Adding Visualize option to character description.
While it is nice to be able to have pictures generated in the main story, it would help me if I could have the pictures in the Story Bible as well. You can’t even select text in there to generate anything and that is where I put my most detailed descriptions long before they make it into the story itself.
Blake Betts About 1 month ago
💡 Feature Request
Instruct guides to begin with
You should be able to add extra instruction for scenes before generating the scenes or add a way to guide scenes without having to generate prose and have that check scenes if they have the components of extra instructions. Also even with extra instructions, when you regenerate scenes, it still does not use the extra instructions. And rewriting the scenes to add the components in extra instructions either take a while or does not do anything.
PookieAlone 10 days ago
💡 Feature Request
Instruct guides to begin with
You should be able to add extra instruction for scenes before generating the scenes or add a way to guide scenes without having to generate prose and have that check scenes if they have the components of extra instructions. Also even with extra instructions, when you regenerate scenes, it still does not use the extra instructions. And rewriting the scenes to add the components in extra instructions either take a while or does not do anything.
PookieAlone 10 days ago
💡 Feature Request
Force Sudowrite to use Bible Characters instead of inventing New Ones
I add a full character cast to Sudowrite, only to discover that if they are not clearly mentioned in the scenes, they don’t appear and don’t get mentioned. Often, Sudowrite invents other characters instead which ruins my story as then the characters that I have invented are lacking…
Maria Maxine About 1 month ago
💡 Feature Request
Force Sudowrite to use Bible Characters instead of inventing New Ones
I add a full character cast to Sudowrite, only to discover that if they are not clearly mentioned in the scenes, they don’t appear and don’t get mentioned. Often, Sudowrite invents other characters instead which ruins my story as then the characters that I have invented are lacking…
Maria Maxine About 1 month ago
💡 Feature Request