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

(Possible feature) Resetting "I apologize, but..." messages? #3

Open
roxygamer opened this issue May 9, 2023 · 1 comment
Open

Comments

@roxygamer
Copy link

Spermack has a system where it automatically deletes and regenerates messages that begin with "I apologize, but..." that reject your input, and gives an error if it regenerates too many times.
Is it possible to implement this feature in any way for this? I prefer this setup overall but that one feature would be very handy to have here.

@PandarusAnon
Copy link
Owner

I'm not ruling it out entirely but it's pretty low on my to-do list and I'm not a huge fan of the feature to begin with. Not that it isn't useful but it's relying on vague assumptions about what meets the criteria for regenerating and it'd be a pretty big change that could introduce a lot of new problems when I haven't even managed to work out all the current kinks.

If there was a reliable way to say for sure that Slack gave us a filtered response I'd get started on the feature right now but as it is there'd always be something that gets through anyway, or a legitimate response that gets auto-swiped away because it tripped our assumptions about what's a filtered response.

Just think it would be a fair amount of work and introduce a lot of new potential bugs just for the convivence of not having to click on the swipe button yourself once or twice and if it's really necessary to swipe more than a couple of times (the current auto-retry default of Spermack) the solution should be to take another look at the prompt and jailbreak not to keep brute forcing Claude until he relents. But that's just my personal opinion.

All that said, the project is open source and can be forked, so if anybody wants to take a stab at the feature before I get around to it myself they're more than welcome to and while I won't just blindly merge any PR straight back into main I will try to review all of them.

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

2 participants