Codex Automations Now Run in Thread, Preserving Full Context
What shipped
As of April 16, 2026, Codex automations can run inside the same thread, preserving original context and enabling scheduled, self-waking tasks for long-running work like open PRs and ongoing conversations.
Smarter Work
Before, automations lost context when they ran — every session started cold. Now Codex can pause, schedule future work, wake itself up, and resume exactly where it left off, with full thread history intact. That's the difference between a tool you operate and one that operates on your behalf.
How a team used this
Yusuf is a solo developer juggling four open PRs while onboarding a new client. He used to lose an hour each morning reconstructing what Codex had done and where things stood. Now he assigns Codex to a thread, tells it to follow up on reviewer comments and flag blockers. Codex schedules its own check-ins, wakes up when activity happens, and resumes with the full thread intact. By Friday, two PRs are merged without Yusuf writing a single follow-up message. He estimates he reclaimed six hours of interrupt-driven context-switching in one week.