Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] "Generate only one line per request" Checkbox #109

Open
alicat22 opened this issue Feb 28, 2025 · 1 comment
Open

[Feature Request] "Generate only one line per request" Checkbox #109

alicat22 opened this issue Feb 28, 2025 · 1 comment

Comments

@alicat22
Copy link

As a user, I'd like to be able to generate responses one paragraph at a time. Essentially this would just add a "\n" stop string to the API.

When using LLMs for story and adventure, having 1 paragraph generate at a time is incredibly helpful. It helps stop the story/adventure from progressing too far. Some models also have bad habits when they're allowed to reach the {eos}. For example, models trained on OAI logs will follow a pattern where the 3rd paragraph is a conclusion. This bias is detrimental to story/adventures.

Possible Solutions

  • Generate only one line per request is how SillyTavern labels this checkbox.
  • Multiline Replies is how Kobold Lite labels this checkbox.

Additional context
When using the OAI-compatible API, adding "\n" as a stop string does the following:
stop: [ "\\n" ]

Unfortunately, because an escape character is added, this option currently does not work.

This checkbox is also very user-friendly, as many frontends have adopted this option. Most users won't know what \n is.

If you require any additional details, please let me know!

@alicat22
Copy link
Author

The OAI-compatible API endpoint I'm using is fixing the \ escape on \n, so this should allow \n to work properly.

I think leaving up this request still holds value, however, as many users won't know what \n is or does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant