Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Why is this flagged?
  • 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!
  • 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)

  • 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.

  • 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.
  • 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!

  • 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).

Explore Birbla archives