Video yükleniyor...
Video Yüklenemedi
Jev picking the next command from shell history
46,192 görüntüleme • 19 saat önce •via X (Twitter)
19 Yorum

Here's the code (didn't once look at it):

Also, didn't record the demo, that was all in Amp:

Is it just me, or are there other people who sometimes just go into Copilot-era mode and code with autocompletion because they miss programming by hand but don't want to go that far either? It might turn out Jev could revive some of that ancient practice

Never. I also had Amp built this but will never use it.

if anyone wants to actually use this btw

That's sort of neat, Thorsten. I still need to wrap my head around the possibilities once you have this kind of latency.

This would be sick for anyone still using the command line.

how's this diff from zsh autocomplete plugin?

Shell history is a credential. If the agent can re-fire yesterday’s kubectl from it, you just gave ambient prod access.

shell history is a clean action space. project state is what keeps it from confidently replaying yesterday’s mistake.

is this just not shell aliases?

too much for AI, just build custom TUI

Just when I was about to do this ;-;

This is hot.

is this an insult to gui user (jk)

Super sick

cool

shell history autocomplete is exactly the kind of small workflow win that makes an agent feel magical

The agent is the runtime/os in the future. Omarchy probably the fastest to get there
