OpenAI CLI

I've been working on something in a similar class for about a year called llcat

It came out of a lack of their being an LLM-native tool that feels like cURL or other unix-friendly things such as awk or sed.

I wanted something stateless, explicit, low-level, and composable without "settings" just like you don't with grep or sort.

Instead, you can index into files with jq or line numbers and save invocations for later for instance

    llcat --save invocation.json \
      -k "@~/credentials.txt:12" \
      -u "@settings.json:.[3].host" \
      -s "@system_prompts:8" \
      -m "@settings.json:.[3].model" \
         "@query.txt:12" > output.txt

and then

   llcat --load invocation.json { ... parameters you want to override ... }

That means there's no hidden state and you can use it in shell scripts and get operational guarantees.

I've put a lot of effort into this and use it daily. I really wish people would give it a go and give me feedback and file bugs!

https://github.com/day50-dev/llcat

2 trillion dollar company can't put 1 single sentence describing what something is, why it's useful, what it's for - instead barfs technical jargon.

It's like if someone handed you an arcane set of page 20-40 of an IKEA assembly manual and expected you to be excited.

About what? Exactly?

Be careful getting too deep in OpenAI tooling because they end up deprecating almost everything in under two years, sometimes without even a formal notice.

Everything they make these days looks to be strongly vibecoded without a decent review or functional testing. This leads to basic avoidable bugs that annoy vast numbers of users.

Not only this, but when you point out an issue to them on GitHub, they have a history of blocking the reporting user instead of tackling the technical issue.

Wait, wasn't codex the "openai cli"? Their product names are so confusing (chat, vs. work ?!).. almost like the whole thing is vibecoded.

When should I use this over Codex? Is this supposed to be called by other tools/agents?

Does this consume the monthly flat rate subscription quota or API credits.

Does Anthropic have something similar.

I understand "claude -p" has been unreliable to use with subscription quota and often required "extra usage" credits.

I imagine the play is RL your model to solve problems using your own tools which it knows how to use most efficiently until it defaults to using services like managed agents, etc.

Honestly surprised this wasn't available sooner.

[flagged]