Just-bash: Bash for Agents
41–50 of 78 posts
Re: Just-bash: Bash for Agents
#42I wonder the reason.
Maybe 'do one thing well'? The piping? The fact that the tools have been around so long so there are so many examples in the training data? Simplicity? All of it?
The success of this project depends on the answer.
Even so, I suspect that something like this will be a far too leaky abstraction.
But Vercel must try because they see the writing on the wall.
No one needs expensive cloud platforms anymore.
Re: Just-bash: Bash for Agents
#43Earlier quoted context omitted.
I've been working with the shell long enough that I know just by looking at it. Anyway, it was rethorical. I was making a point about portability. Scripts we write today run even on ancient versions, and it has been an effort kept by lots of different interpreters (not only bash). I'm trying to give sane advice here. Re-implementing bash is a herculean task, and some "small incompatibilities" sometimes reveal themsel…
The project does not list portability as a concern. It's for agent use; they are not trying to re-use existing bash code.
> they use it because there's a lot of training material.
Now, you say:
> they are not trying to re-use existing bash code.
Can't you see how this is a contradiction?
---
I'm sorry, I can't continue like this. I want to have meaningful conversations.
Re: Just-bash: Bash for Agents
#44Re: Just-bash: Bash for Agents
#45Re: Just-bash: Bash for Agents
#46This ends up reading files into node.js and then running a command like grep but implemented in JS. I love the concept but isn’t this incredibly slow compared to native cli tools? Building everything in JS on top of just readFile and writeFile interfaces seems pretty limited in what you can do for performance.
[Disclaimer: I made the thing]
Re: Just-bash: Bash for Agents
#47Earlier quoted context omitted.
The project does not list portability as a concern. It's for agent use; they are not trying to re-use existing bash code.
Before, you said: > they use it because there's a lot of training material. Now, you say: > they are not trying to re-use existing bash code. Can't you see how this is a contradiction? --- I'm sorry, I can't continue like this. I want to have meaningful conversations.
Re: Just-bash: Bash for Agents
#48https://github.com/vercel-labs/just-bash/blob/main/src/spec-... That's a lot of incompatibilities. LLMs like to use the shell because it's stable and virtually unchanged for decades. It doesn't need to worry much about versions or whether something is supported or not, it can just assume it is. Re-implementing bash is a herculean effort. I wish good luck.
In practice it works great. I haven't seen a failed command in a while
[Disclaimer: I made the thing]
Re: Just-bash: Bash for Agents
#49At this point why not make the agents use a restricted subset of python, typescript or lua or something. Bash has been unchanged for decades but its not a very nice language. I know pydantic has been experimenting with https://github.com/pydantic/monty (restricted python) and I think Cloudflare and co were experimenting with giving typescript to agents.
They use bash in ways a human never would, and it seems very intuitive for them.
Gotta work with what's in the training data I suppose.
Re: Just-bash: Bash for Agents
#50last weekend I vibe-coded a project called `openfs` that plugs into just-bash https://github.com/jeffchuber/just-bash-openfs it puts a bash interface in front of s3, filesystem (real and in-memory), postgres, and chroma. still very much alpha - but curious what people think about it. see an example app here: https://github.com/jeffchuber/openfs-incident-app