RepoJournal
OpenAI

OpenAI

Codex, the SDKs, and the engine behind ChatGPT

Pick a date

  1. Sat 2 may
  2. Sun 3 may
  3. Mon 4 may
  4. Tue 5 may
  5. Wed 6 may
  6. Thu 7 may
  7. Fri 8 may
  8. Sat 9 may
  9. Sun 10 may
  10. Mon 11 may
  11. Tue 12 may
  12. Wed 13 may
  13. Thu 14 may
  14. Sat 16 may
  15. Sun 17 may
  16. Tue 19 may
  17. Wed 20 may
  18. Thu 21 may
  19. Sat 23 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

V8 SANDBOXING GOES LIVE IN SOURCE BUILDS

By RepoJournal · Filed · About OpenAI

Codex ships the first phase of in-process V8 sandboxing, hardening the JavaScript execution layer while two critical startup bugs get fixed.

The V8 sandboxing rollout [1] lands build system and Rust feature plumbing to run V8 in a hardened sandbox for source-built Bazel paths, deliberately keeping published rusty_v8 artifacts on their current non-sandboxed contract so this ships independently before changing any released artifacts. Two blocking sandbox issues got resolved overnight: a startup probe on NFS/autofs hosts that was stalling Codex launch [2] now times out gracefully instead of blocking initialization, and bubblewrap build failures [3] no longer panic but propagate as ordinary sandbox failures with proper symlink carveout handling. On the app-server side, /diff commands now route through the workspace abstraction [4] so remote sessions compute diffs against the correct machine, and Turn payloads added an itemsView enum [5] to disambiguate unloaded, summary, and fully hydrated turn states — unblocking future lazy-loading work. This is a coordinated hardening sprint across the execution sandbox, startup paths, and remote workspace semantics.

Action items

References

  1. [1] Enable V8 sandboxing for source-built builds (#21146) openai/codex
  2. [2] fix(sandboxing): Bound advisory system bwrap startup probe (#20111) openai/codex
  3. [3] fix(linux-sandbox): avoid panic on bwrap build failures (#21127) openai/codex
  4. [4] feat(tui): route /diff through workspace commands ↗ openai/codex
  5. [5] add turn items view to app-server turns ↗ openai/codex

FAQ

What changed in OpenAI on May 6, 2026?
Codex ships the first phase of in-process V8 sandboxing, hardening the JavaScript execution layer while two critical startup bugs get fixed.
What should OpenAI teams do about it?
Verify V8 sandboxing builds in your local Bazel workflow and flag any feature gate issues before next release candidate • Test /diff behavior on remote app-server sessions to confirm Git operations run against active workspace • Review Turn.items consumers to handle new itemsView metadata in app-server payloads
Which OpenAI repositories shipped on May 6, 2026?
openai/codex

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.