[dead]
Codex starts encrypting sub-agent prompts
121–130 of 272 posts
Re: Codex starts encrypting sub-agent prompts
#122Earlier quoted context omitted.
> but also store data and sell to whoever is training I see this as an argument against using them/Chinese models all the time, but I don't get it. I totally understand wanting to keep your data private if you're using an LLM for personal chats. But coding? I'm not working for the military, I'd gladly donate my codebase to Chinese labs if that means they can keep releasing 6-months-behind level models for 100x cheape…
How do you know that they don't train their models or append your prompts to add backdoors, or compromise your supply chain by including evil dependencies? This seems hugely irresponsible.
> How do you know that they don't train their models or append your prompts to add backdoors, or compromise your supply chain by including evil dependencies?
I read the code.
Re: Codex starts encrypting sub-agent prompts
#123Ah I was wondering why the Chinese black market resellers stopped working yesterday, I guess that's it
Interesting. Got a link for this?
Re: Codex starts encrypting sub-agent prompts
#124This 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"
It's also not the first time Codex started encrypting stuff. Their excellent compaction endpoint has served up a giant encrypted blob since at least five months ago.
Feels strongly like we're in the late-stage-AI-unicorn phase. If this is really their moat then the Chinese companies will win.
Re: Codex starts encrypting sub-agent prompts
#125Earlier quoted context omitted.
It still just sounds like fancy obfuscation to me. I've read alot of examples trying to understand but I can't get past that being able to run processes on ciphertext in a way you can learn something doesn't make sense without me changing my definition of what I think encryption means.
I thought though the idea is that you cannot learn anything from the ciphertext, how it is processed, or what the final result is? Unless you are a participant of the computation and you have the key, that is.
To actually make it work, you would need to preformat your data very specifically, and the data you want to allow to be processed would need a subkey to unlock the parts you want processed.
I don't see a way to make it a open standard. The processing steps would need to be part of the key.
Anyway If someone figured it out I would be very interested to be sure they weren't just trying to slap a it's encrypted to meet some standards required. And..also, what amount of data processing does Alice need to do that required outsourcing to Bobs machines. Data processing and anaysis is cheap.
Re: Codex starts encrypting sub-agent prompts
#126Every day I get closer to only using pi
Re: Codex starts encrypting sub-agent prompts
#127This 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"
It seems likely to me this was driven by the `ultra` mode in 5.6, which fans subagents to do work. This mode was previously only available in the web UI (what was previously known as pro?) It seems possible they trained this by doing full RL rollouts of agents interacting with each other. They likely view these prompts somewhat the same as raw reasoning traces, they don't want people to train directly on them. I am u…
I think you hit the nail on the head here. Having subagent dispatch in the loop for RLVR is something we've already seen in open models, like Kimi K2.5 and later, so it's no great stretch to assume OpenAI are doing it too.
If you keep RL'ing the dispatch then the prompts are likely to keep diverging from the type of prompt a person would write (like CoT becoming increasingly incomprehensible), and that divergence is part of their competitive advantage.
> rather a latent space representation of the conversation
Student/teacher models derived from the same checkpoint convey a lot of latent information through token choice, as in: https://techxplore.com/news/2026-04-ai-chatbot-student-owls....
I wonder if this is something they can take advantage of by training on compaction inside of the RLVR loop?
Re: Codex starts encrypting sub-agent prompts
#128This 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"
It's sort of insane though, you not only have dozens/hundreds of stochastic agents running on your machine, but you cannot even inspect the instructions those agents are working off of?
I've gone in to look at Claude subagent/workflows and sometimes been like "no this was a mistake to spin up" ... Codex users just get to token yolo the encrypted telephone operator instructions+shell from orchestrator to subagents?
Re: Codex starts encrypting sub-agent prompts
#129Re: Codex starts encrypting sub-agent prompts
#130Earlier quoted context omitted.
Agreed, I immediately thought that homomorphic encryption was at play here or some other kind of computation on ciphertext, given the mention of "inferencing" in the title.
My bad, fixed now, please do refresh and try with latest updated IE if you still don't see the changes.
> with latest updated IE
Internet Explorer?