-
Notifications
You must be signed in to change notification settings - Fork 7
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
populate shell history? #2
Comments
That's a good suggestion. I will need to check how that would work with child_process. I was already thinking of feeding LLM the terminal history to chain commands via natural language better. |
@benwhalley So this is sort of possible but complex. The issue is adding to the user history will differ based on the shell user is using. I can add shell specific code to add history but I think we can only cover the major ones such as |
Agree that this would be helpful! I'm using bash. Find myself wanting to run the same command several times and the "up arrow, enter" muscle memory keeps getting me as I resend the same slow gpt network call. |
This is really cool, but I can't use the up arrow to re-run a command. Is it possible to populate the terminal history to enable this, or just enter the command to be used to the terminal without running it so that actual execution happens normally rather than inside wz?
The text was updated successfully, but these errors were encountered: