AIToday
Large Language ModelsAI Business & IndustryTHE DECODERPublished: Jul 15, 2026, 19:01 JST

OpenAI's Codex encrypts agent instructions, blocking developer visibility

OpenAI's Codex encrypts agent instructions, blocking developer visibility

3 Key Points

  1. What happened

    Since early June, OpenAI's Codex coding tool has encrypted the instructions that main AI agents pass to subagents. Developers can no longer see readable task descriptions in session history—only an unreadable encrypted string. GPT-5.5 initially blocked the ability to turn off encryption entirely; OpenAI has since re-enabled the toggle for GPT-5.5, but the larger GPT-5.6 variants (Sol and Terra) remain encrypted. Only the smallest variant, Luna, still displays readable agent communication.

  2. Why it matters

    As coding tools become agentic systems that autonomously break down and delegate tasks, the ability to track internal processes is critical for developers managing and debugging their workflows. The encryption also appears unreliable—several developers report that encrypted handoffs between agents fail because the content cannot be decrypted, even when both agents use the same model. OpenAI has not confirmed whether the change aims to prevent competitors from training on agent communication (a suspected concern after Zhipu AI's GLM-5.2 was suspected of distillation from GPT-5.5 and Opus 4.8), to protect user privacy in API data handling, or both.

  3. What to watch

    A GitHub bug report requests that OpenAI store a readable copy of encrypted tasks locally alongside the encrypted version, offering a path to restore developer visibility. OpenAI's eventual clarification of the encryption's purpose—distillation prevention, privacy, or both—and any decision to address the decryption failures will shape how developers adopt these agentic features.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

OpenAI's move to encrypt agent-to-agent communication reflects a critical tension in the evolution of agentic AI systems. As coding tools increasingly adopt the ability to autonomously break down tasks, delegate them to subagents, and operate without direct human supervision, the question of transparency becomes both a technical and competitive concern. The body notes that agent-to-agent communication is valuable training data—a suspected reason that Zhipu AI's open GLM-5.2 model drew suspicion of distillation from GPT-5.5 and Opus 4.8. By encrypting these internal handoffs, OpenAI may be attempting to protect intellectual property embedded in reasoning traces and task delegation patterns from competitors seeking to train weaker models toward stronger performance levels.

However, the immediate cost is substantial. Developers lose visibility into how their own agents delegate work, making debugging and auditing of agentic behavior harder at precisely the moment when autonomous decision-making is becoming more common. The fact that the encryption appears unreliable—failing to decrypt even within matched model pairs—suggests the feature may not yet be mature. OpenAI's decision to restore the toggle for GPT-5.5 while keeping Sol and Terra encrypted hints at ongoing internal debate about the trade-off between competitive protection and developer usability. Until OpenAI clarifies its intent and addresses the decryption failures, developers will face both a visibility problem and a reliability risk.

FAQ
Which OpenAI models are affected by the encryption?
GPT-5.6 variants (Sol and Terra) now use encrypted agent communication. GPT-5.5 initially had no toggle to disable encryption, but OpenAI has since restored the ability to turn it off. Only Luna, the smallest variant, still displays readable instructions.
What problems are developers experiencing with the encryption?
Several developers report that encrypted handoffs to subagents fail to decrypt, sometimes even when the main agent and subagent use the same model. Session history now shows an unreadable string instead of a readable task description, blocking visibility into internal delegation.
Why might OpenAI have added this encryption?
OpenAI has not confirmed the reason. Community members suspect it prevents competitors from training on agent communication (given concerns about distillation—such as Zhipu AI's GLM-5.2 being suspected of distillation from GPT-5.5 and Opus 4.8). A simpler explanation is that OpenAI's API already encrypts intermediate states for secure forwarding in follow-up requests without storing plaintext on servers.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAlleyCorp raises $335M second fund, bets early on unfashionable ideas