Hi PH Fam π
My name is Rushi, and I am a software engineer. I built IDK to solve my three biggest pain points:
β’ Before: Remembering thousands of terminal commands | Now: `idk [prompt]`
β’ Before: Going back and forth reading READMEs for private scripts | Now: `idk [prompt] --readme [file]`
β’ Before: Spending hours setting up a new project | Now: `idk --setup`
I discussed this with some of my engineer friends and realized many team collaboration opportunities with this.
But for now, I'm taking a pause to listen to all of you and take directions from there.
Very excited for y'all to try it.
(Oh did I mention, I kept IDK client open source? So you don't have to guess what stays on your terminal and what goes to the server)
Hi Rushi, this is a pretty awesome tool. I can especially find it useful for situations where there is a very long commands that folks might not use frequently enough to alias but still need on some occasions. Being able to have the LLM context within the terminal is awesome for this use case. Additionally, I can imagine using it to ask about an error right in the terminal window.
DontRef.Me