RepoJournal
OpenAI OpenAI
150 wires and counting

$ follow OpenAI

Keep up with OpenAI in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-06-27
stories 58
RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

CODEX LOCKS DOWN THREAD HISTORY, ADDS FORK PRECISION

By RepoJournal · Filed · About OpenAI · Composed from the cited sources · methodology

Codex shipped three structural upgrades overnight that tighten session management, prevent thread degradation across binary versions, and give you surgical control over fork boundaries.

The biggest move is immutability enforcement on thread.history_mode [1]. An older binary could append metadata that omits this field; when a newer binary replays it, serde defaults to legacy and SQLite downgrades a paginated thread. That's now locked after the canonical first SessionMeta write. Separately, the process-owned code-mode session client landed [2], a complete rewrite of session lifecycle that makes dropped calls cancellation-safe with explicit ownership handoff and validates cell/delegate state transitions end-to-end. On the API side, thread/fork now accepts an optional turnId parameter [3], letting you fork up to and including a specific turn while dropping everything after it, replacing the deprecating thread/rollback endpoint with something more granular. Finally, Codex can now consult user-level code-review skills in addition to repo-level ones [4], giving you a cleaner way to inject custom review criteria without forking configuration.

$ ls openai/reviews/ # the step-back reads

the week in review Codex hands model defaults to the server the month in review Agents API lands in both OpenAI SDKs
Full archive → Weekly reviews →

Quick answers

What shipped in OpenAI on June 27, 2026?
Codex shipped three structural upgrades overnight that tighten session management, prevent thread degradation across binary versions, and give you surgical control over fork boundaries. In total, 28 commits, 28 pull requests, and 2 releases landed.
What were the notable OpenAI updates?
ensure thread.history_mode is immutable (#30261), [codex] add process-owned code-mode session client (#30112), and feat(app-server): add optional turn_id to thread/fork (#30277).
♥

$ log OpenAI --recent

Safety identifiers reach images, plugin approvals bind to contents 93 shipped Credential masking lands in Codex, Live gains Decisions across both SDKs 100 shipped Codex stabilizes environment tools, python adds residency options 135 shipped openai-python restores streaming connection reuse, browser and computer toolsets land in both SDKs 123 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training verl rejects conflicting vLLM engine_kwargs, open-instruct adds MILES OPD behind a Megatron learner Interpretability nnsight 0.8.0 cuts import time from 7.6s to 1.6s

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.