Skip to main content

Chat AI/UX for the Interface Itself Separate from the Chat for Writing Stories

The writing Chat AI is useless as a source of documentation about the behaviors and operations of the technical systems themselves.

For example, I can’t discern easily how or why the “Generate Synopsis” button is greyed out; my inclination is to as the LLM/AI chat, but the writing assistant chat is fixated—as it should be—on the prose and narrative not on the technical details of the interface.

2 comments

Log in to comment and vote

Comments2

  • Oliver

    •

    Sep 3, 2025

    We appreciate the request! Have you tried using the “@” to tag worldbuilding or character cards? That’s something you can do if you want to check something from those sections

    • Ian Mclean

      •

      Sep 5, 2025

      I use the /@ function quite a bit. It is useful for querying diegetic information, but it is not useful for querying the SudoWrite UX/UI itself. It can’t be used for asking about how specific buttons work or conditions that need to be met for the meta-system outside the diegesis.

      If I ask the chat why I can’t generate a synopsis it tells me how to write a synopsis myself which doesn’t even acknowledge the question.

      Like, I realize that I can for that specific example use the chat and at functionality to effectively have it generate a synopsis as a work around, but this doesn’t answer the question of what conditions need to be met for the button to work, so the synopsis generation becomes a one button press instead of the elaborate workaround.

      Similarly, I can ask on the forums how to do something, but this doesn’t help if the functionality changes or new otherwise undocumented functionality is added or if for whatever reason I can’t or don’t manage to find the specific feedback that some other users have gotten or gave about what may be extremely obscure or “obvious” functionality.

      Having a chat that specifically is NOT for querying the diegesis but the UX/meta-system provides a lot more functionality than just patch fixing around a specific problem; it potentially can go a long way towards a self-documenting and community-documenting system as the devs making upgrades, changes, improvements, depreciations, and so on.