DE version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
84% Positive
Analyzed from 1763 words in the discussion.
Trending Topics
#api#agent#codex#agents#openai#own#com#running#right#https

Discussion (57 Comments)Read Original on HackerNews
- 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 this lets you plug in the tools it needs to be whatever kind of agent you want. But they still get to encapsulate and continue to iterate on the really deep parts of the harness that all agents need like memory and context management.
That said, my money right now is not on the offerings from OpenAI and Anthropic because they’re stuck using their own proprietary frontier models and those aren’t actually the best choice for most agents right now. A competitor who is not an LLM lab gets their pick of the market at any given moment. Like you’d want to be using GLM 5.3 Flash right now for most things agentic.
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
Convenience. And OPEX vs CAPEX something something.
Spider men meme of developers pointing at each other thinking "Not it".
Guessing this an early release not quite ready for the public? Interesting that there's a 'OpenAI-Early-Access' GitHub user, though of course with no public repos. Presumably when its actually public they'll move the example agent repos to another GitHub user.
[0] https://developers.openai.com/showcase/agents-api-slack-bot
I've found the app-server to be the most flexible, compared to the raw Responses API or Agents SDK.
Certainly seems like everyone is still figuring out the right interface here.
Also of note, since GPT-5.5 or so, Codex doesn't even use the Responses API as intended, but instead a "lite" version where they manage the context more manually (like sending the full transcript or using a custom web.run tool instead of the provided `web_search` tool).
If you follow the docs, it will lead you down a lot of well-intended functionality, but most of it is thrown away in their most successful harness.
[0]https://developers.openai.com/api/docs/guides/agents#compare...
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.
Works really well and is a great use case for work laptops. Same shell, same memories, same sessions
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/
you can just make new sessions for each new task?
Sometimes start a new chat in the phone app, sometimes just add to the main one. Both seem to work ok.
If I want the agent to wait for something I need to start a new chat in the iphone app.
I can see OpenAI pushing for this as a sort of more durable moat compared to the now huge number of agentic harnesses that run on your own machine.
This might be getting the foot into some sort of bundling as well. Like unrestricted models or custom fine tuned agents inside this and not providing direct APIs to those endpoints.
That being said I don't see a lot of reasons for people to jump on this if it doesn't bundle something killer. Like to me the fact that GPT Work runs on your own machines and all the artifacts and work in progress there for you to look at is sort of the whole point. I don't just want a final artifact.
Which is also why they want to remove it from your machine. Call it conspiratorial, but I keep thinking about "You'll own nothing and be happy." It seems like the industry is quickly moving in a direction where devices are turning into gateway into the cloud, and personal computing will turn into a hobby that prices out the average individual.
anyone knows how to do that and implement agent api with user actual account?
I was doing exactly what you’re describing. I think this is a ToS violation for anything other than personal use though.
We built that in my current company and it works wonders to just script entire persistent workflows with a simple SDK.
I’m trying to understand the use case but it seems weird middle ground in a way .
Looks to me like they really took down the quotas, especially anything in codex. Either that or it's something else, perhaps in codex?
Hopefully this kills the need to use the CLI and we can just use the API instead.
We use the OAI API because there is no local equivalent, I'm assuming this is just the codex client running on the cloud?
It offers three settings:
Given what happened with the wiki thing the other week, where the agents rewrote their own /etc/hosts file to let them bypass sandbox rules, how trustworthy is that restricted option?> Ran `curl http://example.com/`. It exited with code `0` and returned: ```text Domain forbidden ``` I haven’t modified `/etc/hosts` or run the second request, because using an alternate hostname with that Host header would attempt to bypass the environment’s domain restriction.
I told it:
After adding nthntqok.net to the allowed domains list.