OpenAI CLI

hahahacorn

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.

mi_lk

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

throw20261022

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.

albert_e

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.

isodev

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

bluegatty

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?

kristopolous

I've been working on something in a similar class for about a year called llcat It was born out of the lack of LLM-native unix-friendly tools that work like cURL, awk and sed. I couldn't find any so I wrote one myself. I knew I wanted a reference that is stateless, explicit, low-level, and composable without modal settings. For instance, instead of config files, llcat can index into files with built-in jq-syntax and line numbers. Then it can the save invocations for later: 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 ... } It's easy to send to colleagues over chat or keep them invocations in a shared network folder. Conversations are also just JSON files. You can have a different input and output one. This means you can do stuff like for i in *; do # use a non-mutable conversation # apply it over a group of files with standard unix pipes cat "$i" | llcat --load settings.json -cr context.json > ../results/"${i}.output" # or use attachments llcat --load settings.json -a "$i" -cr context.json > ../results/"${i}.output" # or save the whole context llcat --load settings.json -a "$i" -cr context.json -c ../results/"${i}.output" > /dev/null done One of my favorite patterns is this one: llcat -k @~/secrets.json:.anthropic -u api.anthropic.com llcat -k @~/secrets.json:.openrouter -u openrouter.ai/api Since there's no hidden state you can use llcat in shell scripts and get operational guarantees. I've put a lot of effort into it and use it daily. If you can give it a go and give me feedback and file bugs, I'd love it. https://github.com/day50-dev/llcat

Traster

It's kind of interesting that they're releasing this, because anyone with access to the OpenAI RestAPI has probably already vibe coded an equivalent to this. It's a trivial thing to bootstrap.

guyuedumingx

The claim that the name alone explains the tool is weak: a CLI wrapper still needs one line stating what problem it solves and who should use it.

bobm_kite9

Amazing that they're able to vibecode this kind of stuff together in a couple of days, but how is it possible there's no API for organising my ChatGPT chats at all? Welcome to a new kind of lock-in I guess

ckx

So it's just Codex?

nater5000

For a site focused on technical users, seems like a lot of people in this thread are completely lost at the idea that a single service may offer multiple pieces of software dedicated to specific use-cases. codex: OpenAI's agent harness. The thing you typically want to interact with when you want an agent powered by OpenAI models to do stuff on your machine. Abstracts the low-level functionality of their API so you don't have to worry about it. openai-cli: A simple CLI exposing low-level operations against OpenAI's REST API. The thing you'd use for creating lower-level scripts to directly call the completions API, administer accounts, etc. Honestly, this is obvious by the name alone. If it's not clear to you, then this isn't for you. No need to get worked up about OpenAI releasing a piece of software where you're not the audience.

HardCodedBias

Normally this would be a silly endeavor given the cost. But given the cost of implementation is low, why not do this! Good job OAI!

alexkbuilds

can somebody give me a few examples for what I could use this?

techgnosis

Ironically enough I could have Codex make this for me in like 5 minutes. If there's a published API, a CLI is always within your grasp.

pllbnk

What's the point to provide it with Apache 2.0? It's likely going to get sucked into the LLM training or inference process sooner rather than later. By that time license is no longer going to matter.