I do this ever since I switched to a Mac in 2015 and my history has over 60,000 lines. So that’s basically my knowledge base :)
But your project looks nice. Will check out.
You can build your own workflow by hand by doing something like:
1. Turn on your shell’s feature to record command history.
2. Look into its feature set to control things such as how many entries it remembers, whether it remembers duplicate entries, and whether it timestamps each entry. (Don’t forget to restart each instance of your shell, if needed, for changes to take effect.)
3. Install a tool such as fzf that allows interactive filtering of arbitrary text. (Via Homebrew it’s `brew install fzf`. It’s likely something similar for other package managers.) These tools usually: read lines of input, prompt the user to optionally filter but eventually select a line, then just print that line.
4. Write the necessary shell script(s) / functions / aliases to do things like:
+ invoke the fuzzy-finder on the shell’s history file or a modified version of that file (for example, a modified version that excludes bash’s timestamp lines, or that joins them - perhaps in a human-readable format - with the command it timestamps.)
+ process the output of the fuzzy-finder tool (for example, to copy the command to the clipboard, paste it into the shell, or execute it immediately - which will necessitate things like removing any timestamps or additional notation added in the previous step.)
Step 4 can be easy as something approximating (I’m on mobile right now):
fzf “$HOME/.bash_history” | copy-to-clipboardraise ValueError("OPENAI_BASE_URL and OPENAI_API_KEY must be set. Try running `zev --setup`.") ValueError: OPENAI_BASE_URL and OPENAI_API_KEY must be set. Try running `zev --setup`
even when I run (for example) set -x ZEV_USE_OLLAMA 1; zev 'show all files and all permissions'
That said, did you run `zev --setup`?
It uses locally hosted (or remote) LLMs to create and execute shell commands that you describe. You can go as far as writing "shell scripts" in natural language.
Recently some of my friends reported that it just wants to do comments and I've noticed that it actually biases towards that nowadays, so I start it with something to get it kicked off.
I've been managing to try to figure out what in the prompt makes it like that, but for the moment that little workaround gives me both the comment and the command in my history so it's easier to r-i-search for it.
https://x.com/arjie/status/1575201117595926530
You just set up copilot for neovim normally and set it as your EDITOR. https://wiki.roshangeorge.dev/index.php/AI_Completion_In_The...
Instead of being a separate command, I released a set of key bindings you can push that start the LLM prompt with your current command line, and if you successfully accept the suggestion, replace your command line with the result, bypassing the manual clipboard step, and making it so that the result goes into your shell history as a normal command.
2) this doesn’t run anything. It goes to your clipboard and you have to run it yourself
3) this a good callout… what do u think? I’m thinking maybe ask the models to return a Boolean is_dangerous plus a small explanation and then I can display dangerous commands in red and show the warning when you select one.
Looks like cw from aws
Search for `fzf --bash`. Note that the version in the ubuntu repos is too old to have this feature (I think)
What I love about this is the fzf's fuzzy narrow down. You don't have to start at the beginning of command, you don't have to worry about exact spelling. Just a few snippets you remember, it will narrow it down really fast.
I use the same fuzzy search narrow downs in Emacs.
I miss it everywhere else.
0x696C6961•1y ago
dtnewman•1y ago