This title is easy to misinterpret. If I understand correctly: Codex now encrypts sub-agent prompts and hides those prompts from the user. edit: originally was "Codex starts encrypting prompts, uses cyphertext for inference instead"
I imagine this will be because a decent chunk of the IP in Codex is probably within its prompts, how they're built, and how they're sequenced and orchestrated, rather than in the codebase per se. We had this discussion a few months ago where we talked about allowing people to choose an AI provider and provide their API key, thinking about enterprises with "preferred" (read: mandated) AI suppliers. We also wanted to o…
Codex starts encrypting sub-agent prompts
101–110 of 272 posts
Re: Codex starts encrypting sub-agent prompts
#102Re: Codex starts encrypting sub-agent prompts
#103What's the idea here? Why does this seem important to OpenAI?
Seems fairly obvious what the point from OpenAI's side is (protect what they see as the moat, that a model is "good at spawning sub-agents"), but what's really strange to me is that the team somehow didn't manage to push back on this, it's so clearly disadvantageous to developers who are trying to rely on Codex for real work. For this we need introspection into what exactly is going on, hiding the prompts is just so…
Yes, that is the obvious answer. I was looking for an explanation as to why and why now. Codex is open source after all. They used to not do it. Agent prompts more generally are also not encrypted, and continue to be.
This particular change just looks unintuitive to me.
Re: Codex starts encrypting sub-agent prompts
#104Earlier quoted context omitted.
I imagine this will be because a decent chunk of the IP in Codex is probably within its prompts, how they're built, and how they're sequenced and orchestrated, rather than in the codebase per se. We had this discussion a few months ago where we talked about allowing people to choose an AI provider and provide their API key, thinking about enterprises with "preferred" (read: mandated) AI suppliers. We also wanted to o…
I'm unable to understand how much value can be in low-definability non deterministic prompts. It feels like the kept the right divinity spell into a chest.
Re: Codex starts encrypting sub-agent prompts
#105I wonder if there was any safeguard failure due to loss of visibility into what the sub-agent was trying to do?
Re: Codex starts encrypting sub-agent prompts
#106This title is easy to misinterpret. If I understand correctly: Codex now encrypts sub-agent prompts and hides those prompts from the user. edit: originally was "Codex starts encrypting prompts, uses cyphertext for inference instead"
Re: Codex starts encrypting sub-agent prompts
#107This title is easy to misinterpret. If I understand correctly: Codex now encrypts sub-agent prompts and hides those prompts from the user. edit: originally was "Codex starts encrypting prompts, uses cyphertext for inference instead"
Yeah I thought "wow, some homomorphic encryption* stuff", but then "nah, usual greed". * https://en.wikipedia.org/wiki/Homomorphic_encryption
Re: Codex starts encrypting sub-agent prompts
#108Re: Codex starts encrypting sub-agent prompts
#109Earlier quoted context omitted.
The prompts are now encrypted, not just the transit connections...
Ok, so help me get this right: I ask the LLM for something, it generates prompts for sub-agents and sends them back to my client for it to call the sub-agents. Now, those sub-agent prompts are encrypted messages that the sub-agents will decrypt (by hitting a backend) to do their work. Might as well just stuff the prompts in a database and only hand back the primary key to the client to hand off to the sub-agents. Kee…
Re: Codex starts encrypting sub-agent prompts
#110The only way these AI labs can get the app layer lock-in they need is if they can get customers used to writing them a blank check: “here, take my data and my system, do ‘stuff’ and bill me for it.”
Between this and the recent Grok upload breach, I consider these products radioactive.