Skip to content
gentic.news — AI News Intelligence Platform
Connecting to the Living Graph…

Listen to today's AI briefing

Daily podcast — 5 min, AI-narrated summary of top stories

A macOS desktop with a Codex dialog showing a locked state and options for background code tasks

Codex 'Locked Use' Feature Spotted on macOS

Codex may get locked-use mode on macOS, per screenshot. Enables background AI coding without screen.

·3h ago·3 min read··7 views·AI-Generated·Report error
Share:
Is OpenAI's Codex getting a 'locked use' mode for macOS?

OpenAI's Codex is testing a 'locked use' mode for macOS, allowing the AI coding tool to operate while the Mac's screen is locked, per a screenshot shared by @kimmonismus.

TL;DR

Codex may soon work on locked Macs. · Feature spotted by @kimmonismus on X. · Enables background AI coding without screen.

Codex may soon work on locked Macs, per a screenshot shared by @kimmonismus on X. The feature would let Codex run background tasks like code generation or refactoring without the user's Mac being actively used.

Key facts

  • Feature spotted via screenshot by @kimmonismus on X.
  • Toggle labeled 'Let Codex use your Mac while it's locked'.
  • Codex is OpenAI's AI coding assistant for macOS.
  • No official announcement or release date from OpenAI.
  • Feature would require macOS permissions for background execution.

OpenAI's Codex, the AI coding assistant, appears to be testing a 'locked use' mode for macOS that would allow the tool to operate while the Mac's screen is locked. The feature was spotted by X user @kimmonismus, who shared a screenshot of a settings toggle labeled 'Let Codex use your Mac while it's locked' [According to @kimmonismus].

The screenshot shows the toggle inside the Codex settings pane, alongside existing options like 'Launch Codex at login' and 'Show Codex in menu bar.' The feature would require macOS permissions to run processes with the screen locked, similar to how background apps like backup tools or media servers operate on the platform.

The unique take: This is less about convenience and more about OpenAI positioning Codex as an autonomous agent, not just a chat-based assistant. A locked-use mode enables Codex to execute long-running tasks—like refactoring a codebase, running tests, or generating documentation—without demanding the developer's attention. It aligns with the broader industry shift toward agentic AI tools that act independently, as seen with GitHub Copilot's recent 'workspace' mode and Anthropic's Claude for coding.

OpenAI has not officially announced or confirmed the feature, and no release date is known. The company's recent social media imagery, which @kimmonismus referenced, may have teased the feature's arrival. The toggle suggests the feature is in internal or beta testing.

If released, the feature would differentiate Codex from competitors like GitHub Copilot, which currently requires the IDE to be active and the user's screen unlocked for most operations. It could also raise new security questions: a locked machine running an AI that can read and write code presents a vector for potential misuse if compromised.

What to watch

Watch for OpenAI's official announcement or beta release of Codex locked-use mode. If released, compare adoption rates and security incidents against GitHub Copilot's similar 'background tasks' feature, which is reportedly in development. Also watch for macOS permission prompts and developer backlash over security concerns.

Source: gentic.news · · author= · citation.json

AI-assisted reporting. Generated by gentic.news from multiple verified sources, fact-checked against the Living Graph of 4,300+ entities. Edited by Ala SMITH.

Following this story?

Get a weekly digest with AI predictions, trends, and analysis — free.

AI Analysis

The locked-use feature for Codex is a subtle but significant signal of OpenAI's agentic ambitions. Most AI coding tools today require the user's active participation—tab-completing lines, answering follow-ups, or clicking accept. A locked-use mode flips that: the AI becomes a background worker, not a copilot. This moves Codex closer to the 'autonomous software engineer' vision that startups like Devin and Factory AI are pursuing. From a competitive standpoint, GitHub Copilot has not yet shipped a similar feature, though it has discussed 'background tasks' internally. If OpenAI ships this first, it gains a positioning advantage: Codex is not just a chat interface but a persistent agent that works while you sleep. The security implications are non-trivial. A locked machine with file system access and network permissions running an AI model creates a new attack surface. OpenAI will need to address this in documentation and permission models. The feature also raises questions about macOS resource usage. Running a large language model locally or even cloud-based inference while the machine is locked could drain battery or consume bandwidth. The implementation details—whether the model runs locally or via API—will determine performance trade-offs.

Mentioned in this article

Enjoyed this article?
Share:

AI Toolslive

Five one-click lenses on this article. Cached for 24h.

Pick a tool above to generate an instant lens on this article.

Related Articles

From the lab

The framework underneath this story

Every article on this site sits on top of one engine and one framework — both built by the lab.

More in Products & Launches

View all