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.
OpenAI Agents API
91–100 of 202 posts
Re: OpenAI Agents API
#92Re: OpenAI Agents API
#93I 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…
> building your own harness is a huge undertaking, a deep rabbit hole. I eventually gave up on this task. It's not possible to fight OpenAI or Anthropic's engineering teams. Their reasoning models have all kinds of undocumented back door access to the base models that you'd never be able to replicate from the outside. Even if you had full access you would not have the engineering man hours or experience to keep up. I…
It is highly custom to my needs and wants, and I think every developer needs to do this. I only talk to my planner which plans, and it subs out to designer, oracle, coders, testers, and reviewers, etc. It is thus highly optimized for correctness. You can TDD or no TDD. You can fast track small changes. I tweak my harness dozens of times as I encounter new edge cases (esp when I switch models and encounter models not as good at following instructions).
As you can start to see, it is better to own the harness because nobody can build something custom that 100% fits your needs or development philosophy.
Re: OpenAI Agents API
#94[flagged]
Re: OpenAI Agents API
#95I 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…
The intent is that anybody can drive it from Claude/ChatGPT/Pi on their phone after MCP sign-in (oauth), the model has full computer use capability, but we can also leverage it to build guided agent workflows in our own dashboard.
Re: OpenAI Agents API
#96Since a week or so everything I ask codex to do, no matter how small, uses at least 1% of my weekly limits and like 5% of my 5h limit. It's getting so bad I'm thinking of just canceling my OpenAI subscription, because this has no use anymore.
I also signed up for a new account and it's right back to working how it used to. They absolutely do not consume tokens equally across accounts. I did TONS of work on the new account and barely made a dent, even on Astra. Old account chews through 20% like it's nothing
Re: OpenAI Agents API
#97Earlier quoted context omitted.
I built several harnesses in different products over the last two years. Fully agree with you that doing it right is a rabbit hole. Certain system properties that you almost always want in a harness used within a SaaS (for example) are non-obvious at the start and require certain architectural choices. It's easy to start down a path and then find a gap a couple days before launch. Async tool calls, having the agent w…
> Async tool calls, having the agent wait indefinitely for a human response, and showing a form or questions to the user via a tool call are a few common capabilities that come up that a product manager might miss at first. All of this is specified in the ACP spec, so if you build your agents from that - you don't end up skipping features. Also vital is proper prompt caching, tool design and some connection retry mec…
Oh good reminder. I need to do that.
> Also vital is proper prompt caching, tool design and some connection retry mechanism.
prompt caching is weirder than i originally thought, and so variable across providers. Retry is easy, but can you explain more on tool design?
Re: OpenAI Agents API
#98Re: OpenAI Agents API
#99Earlier quoted context omitted.
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…
Just letting you know, this comment inspired me to finally just say "screw it" and launch what I've been building for the past year. https://www.cadenya.com
Re: OpenAI Agents API
#100Earlier quoted context omitted.
Just letting you know, this comment inspired me to finally just say "screw it" and launch what I've been building for the past year. https://www.cadenya.com
Truly love the website.
> Steer clear of load-bearing tech debt as your agents evolve.
Satirical?