For inspiration (and, ofc, PR since I'm salty that this gets attention while my pet project doesn't), you can checkout clai[0] which works very similarly but has a year or so's worth of development behind it.

So feature suggestions:

* Pipe data into qq ("cat /tmp/stacktrace | qq What is wrong with this: "),

* Profiles (qq -profile legal-analysis Please checkout document X and give feedback)

* Conversations (this is simply appending a new message to a previous query)

[0]: https://github.com/baalimago/clai/blob/main/EXAMPLES.md

On the stateless part - I increasingly believe that state keeping is an absolute necessity. Not necessarily across requests but on the local storage. Handoffs are proving invaluable in overcoming context limitations and I would like more tools to support a higher level of coordination and orchestration across sessions and with sub-agents.

I believe the best “worker” agents of the future are going to be great at following instructions, have a fantastic intuition but not so much knowledge. They’ll be very fast but will need to retain their learnings so they can build on it, rather than relearning everything in every request - which is slow and a complete waste a resources. Much like what Claude is trying to achieve with skills.

I’m not suggesting that every tool reinvent this paradigm in its own unique way. Perhaps we a single system that can do all the necessary state keeping so each tool can focus on doing its job really well.

Unfortunately, this is more art than science - for example, asking each model to carry out handoff in the expected way will be a challenge. Especially on current gen small models. But many people are using frontier models, that are slowly converging in their intuition and ability to comprehend instructions. So it might still be worth the effort.

Nice, the `qq` part reminds me of this project: https://github.com/tldr-pages/tldr

That said, I rather use claude in headless mode https://code.claude.com/docs/en/headless

Just about everyone has already written one of these. Mine are called "ask" and "please". My "ask" has a memory though, since I often needed to ask followup questions:

https://github.com/pmarreck/dotfiles/blob/master/bin/ask

I have a local version of ask that works with ollama: https://github.com/pmarreck/dotfiles/blob/master/bin/ask_loc...

And here is "please" as in "please rename blahblahblah in this directory to blahblah": https://github.com/pmarreck/dotfiles/blob/master/bin/please

I'm using https://github.com/kagisearch/ask

It's a simple shell script of 204 lines.

I built a similar tool called “lmsh” (LM shell) that uses Claude-code non-interactive mode (hence no API keys needed, since it uses your CC subscription): it presents the shell command on a REPL like line that you can edit first and hit enter to run it. Used Rust to make it a bit snappier:

https://github.com/pchalasani/claude-code-tools?tab=readme-o...

It’s pretty basic, and could be improved a lot. E.g make it use Haiku or codex-CLI with low thinking etc. Another thing is have it bypass reading CLAUDE.md or AGENTS.md. (PRs anyone? ;)

Feel like this might have already been done and beyond by aichat (which I give the alias `ai` on my machines)

https://github.com/sigoden/aichat

Nevertheless it’s good to see more tools with the Unix philosophy!

This is nice. Reminds me how in warp terminal you can (could?) just type `# question` and it would call some LLM under the hood. Good UX.

I usually do this in Raycast but the Groq tip is good...

very cool, can be useful for simple commands, but i find github cli's copilot extension useful for this, i just do `ghcs <question>` and it gives me an command, i can ask it how it works, or make it better, copy it, or run it

This looks really cool and I love the idea but I will stick with opencode run ”query” and for specific agents which have specific models, I can just configure that also in an agent.md then add opencode run ”query” -agent quick

And of course, if you find any bugs or feature requests, report them via issues on Github.

Looks interesting! Does it support multiple tool calls in a chain, or only terminating with a single tool use?

Why is there a flag to not upload my terminal history and why is that the default?

One mistake in your README - groq throughput is actually 1000 tokens per "second" (not "minute"), for gpt-oss-20b.

llm cmdcomp is better:

    - it puts the command in the shell editor line so you can edit it (for example to specify filenames using the line editor after the fact and make use of the shell tools like glob expansion etc.) 
    - it goes into the history. 
    - It can use a binding so you can start writing something without remembering to prefix it with a command and invoke the cmd completion at any place in the line editor. 
    - It also allows you to refine the command interactively.

https://github.com/CGamesPlay/llm-cmd-comp

Can it run local LLM with quick parameters?

Hey Mateusz,

I was looking for exactly something like this, and will give it a spin right now.

But please understand that you have a huge "Trust & Safety" issue.

I've downloaded the 0.8.2 release and extracted it. When I want to run this on my macOS system, a nasty warning pops up:

“qa” Not Opened Apple could not verify “qa” is free of malware that may harm your Mac or compromise your privacy.

Well, fair enough; this is an early-stage project, of course the author did not (yet) jump through the Apple signing process hoops.

Let's do some basic sanity checks: the repo itself is very new, but the matisojka Github profile is established and seem alive and active in a realistic way. Author also builds Podigee, seems legit.

Alright, then let's... wait — why is the HN username iagooar; that doesn't sound even remotely like "matisojka" or "Mateusz" or "Sójka". And the HN profile references edenlm.com, not Podigee.

Okay, a cross-check with https://www.linkedin.com/in/matisojka puts the pieces together, and I'm juuuuust enough convinced that I can give this a try and add the macOS security exception...

...but you see my point, do you?

Good one, but I do not see release for MacOS :(

There is also the llm tool written by simonwillison: https://github.com/simonw/llm

I personally use "claude -p" for this

why use this and not claude code?