Repository navigation
Description
What variant of Codex are you using?
Codex desktop app on Windows, local execution with a ChatGPT account. The installed CLI reports codex-cli 0.150.1; the desktop-bundled version was not available from the command line.
What issue are you seeing?
Two separate Codex desktop chats for the same ordinary local software project became unusable after the system classified the work as a possible cybersecurity risk.
The failing work was explicitly limited to a local Git checkout and a disposable local Multipass Linux VM. The prompts prohibited production/VPS/SSH access, deployment, and unrelated changes. The task was defensive deployment-containment regression testing for the user's own application.
In the first chat, automatic/remote compaction repeatedly failed with:
Error running remote compact task: This content was flagged for possible cybersecurity risk. If this seems wrong, try rephrasing your request. To get authorized for security work, join the Trusted Access for Cyber program / apply for Daybreak access.
Thread: 01a10613-1408-7ce0-b779-87fc8c021b2c
I then followed the documented recovery advice and created a fresh chat with a short, focused continuation summary. That chat initially worked and completed a full local candidate verification. During the next independent verification turn, it ran for approximately 2.5 hours and then returned the same cybersecurity-risk error instead of a final result. Subsequent harmless follow-up messages failed immediately with the same error, leaving the second chat unusable.
Second thread: 01a16938-8cc4-7a41-917d-48ee4d9d59f8
No request ID was shown. No production access or external target interaction occurred in the failing phase.
This appears related to #53238, but this report is specifically about remote context compaction / long-turn finalization causing a false positive and permanently blocking further messages in the chat.
Steps to reproduce
- Open a local project in Codex desktop on Windows.
- Start a long local-only coding/verification task involving shell scripts and a disposable local Linux VM.
- Explicitly prohibit production access, deployment, and external targets.
- Let the task run long enough for automatic context compaction or long-turn finalization.
- Observe the remote compact task fail with the cybersecurity-risk classification.
- Send a simple nontechnical follow-up; it may fail immediately with the same classification.
- Create a new clean chat with a concise continuation summary, as recommended by the troubleshooting documentation.
- Continue the same local-only task for a long turn; the same failure can recur after hours of work.
Expected behavior
Benign local development and defensive regression testing should complete normally. If a particular operation is disallowed, Codex should identify it before a multi-hour run and provide an actionable reason. Context compaction should not retroactively replace a completed local verification result with a cybersecurity-risk error, and one false positive should not make all later harmless messages fail.
A new focused chat should be a reliable recovery path.
Actual behavior
- The first chat repeatedly failed during remote compaction.
- A fresh replacement chat reproduced the same failure after approximately 2.5 hours.
- The final result was lost/replaced by the policy error.
- Subsequent harmless messages in the affected chat were rejected immediately.
- The user has now lost productive use of two chats and cannot reliably finish the local project.
Impact
This causes substantial work loss and makes long-running local Codex tasks unreliable. The user should not need to create an unbounded sequence of replacement chats for the same authorized local project.
Please investigate the false-positive classification, remote-compaction behavior, and whether affected sessions can be repaired. It would also help to return a request/session diagnostic ID and preserve already-completed tool results when finalization or compaction fails.
No credentials, project source, or sensitive logs are included in this public report.
Activity
github-actions commentedon Oct 23, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action