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

Show option to skip future "Was Open Interpreter helpful?" messages #1410

Open
metatrot opened this issue Aug 18, 2024 · 1 comment · May be fixed by #1442
Open

Show option to skip future "Was Open Interpreter helpful?" messages #1410

metatrot opened this issue Aug 18, 2024 · 1 comment · May be fixed by #1442

Comments

@metatrot
Copy link

Is your feature request related to a problem? Please describe.

The "Was Open Interpreter helpful?" message frequently appears when I attempt to close the program with ctrl-c. Programs not following the ctrl-c convention (of closing themselves immediately) make themselves appear suspicious, much like websites that try to stop users from leaving them.

Since this is a program that suggests code to execute on my system, the fact that it doesn't turn off immediately when I tell it to is especially suspect.

Describe the solution you'd like

My preferred solution is not to show the message at the end of chats when the user presses ctrl-c, but instead show it in the banner printed when the program starts. The user could use a separate command or flag to submit their feedback.

Describe alternatives you've considered

In the same message, a brief tip on how to disable the message in the future could be shown like:

Was Open Interpreter helpful? Set show_survey to False in ~/.config/open-interpreter/profiles/default.yaml to disable seeing this message in the future (y/n):

Additional context

I've really enjoyed using this program so far. It's the closest thing I've seen to a "smart terminal".

@CyanideByte CyanideByte linked a pull request Sep 5, 2024 that will close this issue
6 tasks
@CyanideByte
Copy link
Contributor

CyanideByte commented Sep 5, 2024

Using command line arg --disable_telemetry should skip this.
Environment variable DISABLE_TELEMETRY should as well but it was bugged. (#1442)

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

Successfully merging a pull request may close this issue.

2 participants