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

--set-<value> should have a --value counter part for session based options #36

Open
nopeless opened this issue Mar 22, 2024 · 4 comments

Comments

@nopeless
Copy link
Contributor

nopeless commented Mar 22, 2024

--set-<value> writes to file. I wouldn't want that.

@kardolus
Copy link
Owner

@nopeless flags would be one way of doing that, however you can already use the environment variables. Every configuration option has an associated environment variable, eg:

OPENAI_MODEL=gpt-3.5-turbo chatgpt what is the capital of Belgium?

or

OPENAI_ROLE='you extract wisdom' cat README.md | chatgpt summarize

@nopeless
Copy link
Contributor Author

nopeless commented Mar 22, 2024

@kardolus environment variables are hard to keep in closures especially in powershell they don't have something like env to keep them temporarily :/

@kardolus
Copy link
Owner

@nopeless ahh gotcha. I didn't know that about powershell. I can add the --value flags. May take me a week or two.

@nopeless
Copy link
Contributor Author

btw by --value i was thinking about --max-tokens for example. i hope it isn't that confusing

e.g.

chatgpt-cli --role "You are developer" -i

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