Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenAI Agents API

developers.openai.com

Post reply on HN
Print view View original

41–50 of 202 posts

Re: OpenAI Agents API

#41

Post by windexh8er »

andrewchambers wrote: post #39
windexh8er wrote: post #37

Earlier quoted context omitted.

Considering the harness needs to be running how else would this work? Pretty easy these days with old school tools like tmux but more modern tooling like herdr [0] is really the path you'd want to take. [0] https://herdr.dev/

codex itself has a remote control mode that runs continuously. I wrote a systemd service to start it boot and interact with it via my phone.

But Codex doesn't survive a reboot by default or a laptop going to sleep. Also, herdr is abstracted up a level from the agent, so you actually get more benefit by using Codex with herdr because herdr knows how to operate Codex, and other harnesses. So if you're using multiple Codex instances you can orchestrate them because each harness can talk to the others. You can still interact with Codex running in herdr via remote control (ideally you'd target your "orchestration" Codex instance). It just gives you way more power.

Re: OpenAI Agents API

#42

Post by TZubiri »

colesantiago wrote: post #21

This was sorely needed. Hopefully this kills the need to use the CLI and we can just use the API instead.

Why would you prefer to use the API if you can have something running locally?

We use the OAI API because there is no local equivalent, I'm assuming this is just the codex client running on the cloud?

Re: OpenAI Agents API

#43

Post by zackify »

bluesnowmonkey wrote: post #40

I think we’re still figuring out the right abstraction for offering agents as a product. - LLMs are a great foundation but building your own harness is a huge undertaking, a deep rabbit hole. - There are harnesses available as open source libraries but that’s still coupled to an environment. Where does the state persist? Like maybe I’m a Cloudflare worker and don’t even have a file system. Agent as a service like thi…

I just have a slack bot running on a VM that sees a message and invokes pi.

It would be trivial for every request to clone a full lxd container and have all the tools and repos required if I wanted to allow it to do even more.

Not sure why anyone prefers to choose locked in options

Re: OpenAI Agents API

#44

Post by [deleted] »

blfr wrote: post #35
andrewchambers wrote: post #31

I've recently had great success running codex in a regular qemu VM and using codex remote control to talk to it from my phone. Honestly works extremely well as a personal assistant. I can see why turning it into an API makes sense, just be aware you might not need to lock yourself in if you can setup your own VMs.

Yes, I do the same with Claude Code. Create an instance on the server for a project and then can create sessions from any device, close my laptop while claude code keeps working, etc. without losing the convenience of dedicated apps.

[deleted]

Re: OpenAI Agents API

#45

Post by kyxsc »

andrewchambers wrote: post #31

I've recently had great success running codex in a regular qemu VM and using codex remote control to talk to it from my phone. Honestly works extremely well as a personal assistant. I can see why turning it into an API makes sense, just be aware you might not need to lock yourself in if you can setup your own VMs.

Yep I run `claude remote-control` as daemons (systemd/launchctl) on whatever paths/repos I wanna be able to create a session from on-to-go.

Works really well and is a great use case for work laptops. Same shell, same memories, same sessions

Re: OpenAI Agents API

#47

Post by notatoad »

bluesnowmonkey wrote: post #40

I think we’re still figuring out the right abstraction for offering agents as a product. - LLMs are a great foundation but building your own harness is a huge undertaking, a deep rabbit hole. - There are harnesses available as open source libraries but that’s still coupled to an environment. Where does the state persist? Like maybe I’m a Cloudflare worker and don’t even have a file system. Agent as a service like thi…

I think the abstraction is only part of the problem. The other part is that all these companies offering ai products are deeply untrustworthy, and I don’t want to let them any further into my stack than I have to. Claude code and codex are great because they are lightweight, and operate on top of the rest of my tools with little to no change needed, so they can be eliminated or migrated away from with zero cost. They’re not a dependency of anything. And that’s as much as I’m willing to trust OpenAI or Claude.

Re: OpenAI Agents API

#48

Post by krashidov »

windexh8er wrote: post #37
krashidov wrote: post #32

Earlier quoted context omitted.

Do you have 1 long running session?

Considering the harness needs to be running how else would this work? Pretty easy these days with old school tools like tmux but more modern tooling like herdr [0] is really the path you'd want to take. [0] https://herdr.dev/

> Considering the harness needs to be running how else would this work?

you can just make new sessions for each new task?

Re: OpenAI Agents API

#49

Post by krashidov »

dist-epoch wrote: post #38
krashidov wrote: post #19

you can't use your subscription with this so it's likely the largest companies in the world that can truly use this

`codex -p` is the subscription equivalent. or ACP if you want to be fancy

yep. I'm saying that the managed agent API described in the article is API only.
Post reply on HN