Open
Description
Is there an existing issue for this?
- I have searched the existing issues
Contact Details
No response
What should this feature add?
Rich text support in the web UI's prompt field would enable several useful QoL improvements.
- Syntax highlighting could help to quickly distinguish prompt syntax and keywords from prompt tokens. It would also help to reveal simple typos with drastic effects, such as mismatched parentheses or quotation marks, and clarify the expected behavior in some edge cases:
- commas interpreted as either parameter delimiters or prompt tokens depending on presence of quotation marks
- hyphens and parentheses can be interpreted in unexpected ways. For example, these 3 sets of prompts give identical results within their set, but distinct results from each other. (
--log_tokenizationin the CLI makes their interpretation far clearer):(hot-dog)==hot-dog==hot - dog; hyphen is treated as a token(hot- dog)==(hot)-dog==hot- dog==(hot)0.9dog; the hyphen is now attention weighting syntax(hot - dog)==\(hot-dog\); the parentheses and hyphens are now both treated as tokens (possible bug?)
- Prompt tokenization could be indicated by the hue of tokens in the prompt, as with
--log_tokenizationin the CLI. - Attention weighting could be indicated by variations in brightness, saturation, or boldness (within the limitations of legibility).
- A floating panel above selected text could allow for easily increasing or decreasing attention weighting of the selected text, as with bolding or italicization in word processing applications.
As for implementation, something like Slate may be useful. It plays nicely with React and is what's used for Discord's text entry, but I haven't looked deeply into the full details yet.
Alternatives
I often open a CLI instance of InvokeAI alongside my web session simply to use --log_tokenization for prompt debugging, but this has a severe impact on available VRAM.
Aditional Content
Example UI as seen in Discord's text entry area:
