OpenAI Tests Persistent Mode in Codex for Continuous Autonomous Agent Execution

OpenAI is developing a new operational setting for its Codex developer tool called Persistent mode, designed to allow autonomous AI agents to execute tasks indefinitely until manually paused or put to sleep. The feature was identified in recent code commits to the command-line interface (CLI) repository for Codex, as reported by Wired. In the codebase, Persistent mode appears alongside standard reasoning effort settings such as medium, high, and extra-high, but introduces an entirely different

2 min
OpenAI Tests Persistent Mode in Codex for Continuous Autonomous Agent Execution

OpenAI is developing a new operational setting for its Codex developer tool called Persistent mode, designed to allow autonomous AI agents to execute tasks indefinitely until manually paused or put to sleep.

The feature was identified in recent code commits to the command-line interface (CLI) repository for Codex, as reported by Wired. In the codebase, Persistent mode appears alongside standard reasoning effort settings such as medium, high, and extra-high, but introduces an entirely different execution loop.

Autonomous Task Generation and State Persistence

Current AI coding tools typically operate on a request-response cadence. A developer enters an instruction or sets a bounded goal, the model reasons through the task, runs terminal commands or file edits, and returns control to the user once the immediate prompt finishes or an error occurs.

Under Persistent mode, the execution loop is designed to continue autonomously. The internal codebase directives describe the agent as operating under instructions to continue working until put to sleep. Instead of halting after completing a single task or encountering an intermediate blocker, the agent can:

  • Autonomously generate and queue follow-up sub-tasks based on project requirements.
  • Maintain execution state and context across disconnected terminal sessions.
  • Reference historical interactions and user preferences to guide subsequent technical decisions.
  • Proactively notify the developer when critical decisions, test failures, or completed milestones occur.
Codex Persistent Mode Architecture

Shift Toward Always-On Background Agents

The development of Persistent mode highlights an architectural shift from interactive chat-based coding assistants to durable background worker runtimes. Rather than requiring continuous human prompting, background agents are granted long-horizon autonomy to iteratively run test suites, analyze logs, adjust implementations, and verify codebases.

OpenAI frequently tests new architectural features and command-line primitives in its open Codex CLI before rolling them into GUI products such as the Codex desktop application and ChatGPT Work. OpenAI confirmed that the Persistent mode feature is under active internal testing, though no public release timeline has been finalized.

Sources

Written by

More to read

  • Real-Time Voice AI Agent Frameworks in Production: Comparing LiveKit Agents, Pipecat, OpenAI Realtime API, and Ultravox

    Real-Time Voice AI Agent Frameworks in Production: Comparing LiveKit Agents, Pipecat, OpenAI Realtime API, and Ultravox Deploying conversational voice agents in production requires solving a fundamental physics and networking problem: human conversational turn-taking occurs within an average gap of 200 to 300 milliseconds. When an artificial conversational agent exceeds 600 to 800 milliseconds of round-trip latency, users perceive the interaction as sluggish, talk over the assistant, or experie

    1 min
  • Nvidia Pauses Selected Revenue-Sharing Deals with AI Cloud Providers

    Nvidia has paused select partnership deals under its newly introduced AI cloud financing initiative, according to reporting by The Wall Street Journal. The program, unveiled in July 2026, was designed to provide credit support and hardware access to emerging cloud computing providers in exchange for a percentage of future recurring revenues. While Nvidia stated that the broader program remains operational, several individual agreements have been put on hold as the company reassesses customer te

    1 min
  • Claude Code Opus 5 Auto Mode Bypassed via Python Module Shadowing Exploit

    Security researcher Johann Rehberger has published technical details on a multi-stage exploit chain that achieves arbitrary code execution against Claude Code Opus 5 running in Auto Mode. The attack demonstrates how adversarial files can bypass Anthropic's safety classifiers and prompt injection defenses by exploiting standard runtime behavior in Python. Anthropic rolled out Auto Mode as the default starting mode for Claude Code in mid-August 2026. Auto Mode replaces explicit human permission p

    1 min