HN Explorer

Show HN: Bash4LLM+ – A lightweight, dependency-free Bash wrapper for LLM APIs (github.com)

60 points by kamaludu ↗ HN
Bash4LLM is a single-file Bash wrapper for interacting with LLMs from the terminal. I created it because I wanted something simple that worked without installing Python, Node, or any other runtime.

It uses only Bash, curl, and jq. You can send prompts, start a small chat, process files line by line, stream output, and save session metadata in JSON format.

I tried to make it safe and predictable: no use of the system /tmp, no use of eval. Groq is supported by default, and other providers can be added with dedicated Bash scripts in the extras/providers/ folder.

Example:

  echo "explains the command: ls -l" | ./bash4llm

9 comments

[ 3.3 ms ] story [ 30.3 ms ] thread
Chu4eeno
You really should either just write it manually, or at least clean it up, 5kLOC of bash for POSTing and reading/writing files is a bit overkill (the code is extremely repetitive, verbose and just hard to follow).
kamaludu
well, i write Bash4LLM to be:

. Portable - You need only: bash, coreutils, findutils, util-linux, gawk, curl, jq. No Python (slow), no Node (heavy), no Golang (need too many binaries, one for each OS, hard to maintain for one single person like me).

. Single file - only one. I write many extras, but all are optional.

. Idempotent - you copy it where you want and go!

. Transparent - open the file and read.

. Extras for all, and all optional: help file, extra providers, improved session engine, small GUI/CGI, etc...

Default (embedded) provider is Groq, because when I start the project, was the best free API service for AI.

I'm ready to answer to your question... with my terrible english...

Cristian (kamaludu)

athrowaway3z
You need to figure out how to prompt to get much more concise code.

This is just a casual scroll through for 2 seconds at function names i recognize and can tell are crap.

https://github.com/kamaludu/bash4llm/blob/d7258163dc1cbeb6ae...

https://github.com/kamaludu/bash4llm/blob/d7258163dc1cbeb6ae...

https://github.com/kamaludu/bash4llm/blob/d7258163dc1cbeb6ae...

Sorry but this is crap. If you trust it to be an entirely self-contained abstraction that is fine. But if I'm building a brick house, and smash open 1 of the bricks, i dont want it to look this shoddy.

Any LLM you point at it, is going to be drastically dumber in editing it or auditing it because it needs to first parse all the crap a previous LLM generated. The fewer lines of code things use the better - it keeps models smarter when it matters. Plus it saves money in the long run.

kamaludu
I've applied a set of corrections, on Bash4LLM core, to reduce redundancy and make the flow more deterministic. Optimized safe_mkdir to eliminate superfluous calls to chmod, simplify temp file management by removing a redundant pre‑validation, remove repeated controls on ensure_run_tmpdir, unified internal standards but with backward compatibility, to correct duplications on providers management caused by a second redundant scan of provider modules, preserved diagnostic mode (CLI and environment variables). These are small jobs, but useful for clean and consistent runtime.
bonigv
oh! I thought this was like bash w/o verbosity. That is a tool I would love to see. bash4llm . May be llike Gandhi said - I should be the change you want to see!
cloudkj
Heh, I just wrote something very similar - bash, curl, and jq scripts that wrap local Ollama calls to produce a REPL/agent: https://github.com/cloudkj/llayer

Seems like the core idea is the same, but I took it farther down the Unix philosophy line of thinking and tried to make the individual components small and composable.

Feel free to check it out and compare!