Feedback

WHy do I need to re-add all the details if the information is all within the text? The point of AI should be able to scrub through the text and gather that data.

Being able to see snippets across a series instead of only in the book you are currently in. This could be helpful for if you no longer want a snippet to be in the current book, but instead am leaving it to add later in the series.

I would love the ability to edit chats like in chatgpt and playground. I find that I sometimes don't like the answers i'm getting and have to start the entire chat in another window. it would be great to just edit the chat.

Prompts have tabs like "General", "Instructions", "Advanced", and "Description", how not all prompt types have the same tab types. For example, Prompt Components don't have a "General" tab. However, because the UI remembers the index rather than the tab name, moving from one type to another presents an UX issue. Example: If I have a prompt selection and "Instructions" (the second) tab open and then select a prompt component, it opens the "Advanced" tab instead since it's the second tab for prompt components. This makes it quite cumbersome to compare and copy stuff between them, particularly when trying to combine parts of a prompt into a new component.

The new inputs for prompts are great and it's convenient that you can easily copy them between prompts, but it would be great to also have a button that copies to your clipboard the {input("InputName")} string so it's easy to add to the instructions, maybe even preview the string somewhere in the input options? If a preview would clutter the UI too much, maybe the copy instruction button could be part of the "This input is not used by the prompt" warning? I feel this might help particularly new users to start using the feature when they start looking into the more advanced stuff.

I understand the reason we cannot do anything with the default settings in AI. But it would be sensible to be able to remove the defaults from the horizontal list when we write and chose the models. Also the order should be customizable.

I'm a developer and want to say that storing API keys in the browser is probably the least secure place to store them. They are sniffable and vulnerable (XSS, or other attacks) by other apps. This software looks amazing but this issue makes this a no go for me until a better solution to API Key storage is found. If you do store them in the browser, you need to encrypt them first and still need to keep a private encryption key on your own servers. You can also check out some "secure key vault" services that may be able to help you solve this problem. They should be stored and encrypted on your own servers or you should seek out other solutions, but browser storage is definitely not a secure option.