[ChatGPT Chronicle] System Skill Creator is deleted from shared system Skills
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
Summary
A ChatGPT Chronicle/background run deletes the canonical system Skill Creator from the shared Codex system-Skills installation.
The Chronicle worker starts the bundled Codex runtime with skills.bundled.enabled=false. The resulting cleanup appears to remove the shared $CODEX_HOME/skills/.system directory instead of merely disabling bundled Skills for that worker. The system Skill Creator then becomes unavailable to unrelated, ordinary Codex tasks.
This report concerns the canonical OpenAI-provided system Skill Creator—not a personal or copied substitute.
This have been like that since codex app released months ago, this is unacceptable.
Affected environment
- ChatGPT Desktop: 26.803.41515 (build 6321)
- Bundled Codex CLI: 0.147.0-alpha.6.5
- macOS: 26.6.1, Apple silicon
Reproduction
- Start ChatGPT Desktop and confirm the canonical system Skill Creator is present under
$CODEX_HOME/skills/.system/skill-creator. - Enable Chronicle and allow a Chronicle background task to start.
- Observe that the Chronicle worker invokes the bundled Codex runtime with
skills.bundled.enabled=false. - Inspect the shared system-Skills installation after the worker starts.
- Start an unrelated Codex task and attempt to use the system Skill Creator.
Actual result
$CODEX_HOME/skills/.systemis removed.- The canonical system Skill Creator disappears and cannot be discovered by later ordinary tasks.
- The system OpenAI Docs Skill disappears in the same event, confirming that this is a shared system-directory mutation rather than a failure isolated to one Skill.
- A fresh normal Codex startup can restore the bundled system Skills, but a later Chronicle run removes them again.
- Turning Chronicle off prevents recurrence only after any already-running Chronicle worker exits.
The deletion is also reproducible with a disposable CODEX_HOME, without user cleanup scripts or scheduled automations.
Expected result
skills.bundled.enabled=false should control availability only for that worker. It must not delete, overwrite, or mutate the shared canonical system-Skills installation.
In particular, a Chronicle task must never uninstall the system Skill Creator used by other tasks.
Related upstream work
This may share the cleanup defect reported in #19265 and addressed by #36989, but the currently distributed ChatGPT Desktop build above still reproduces the Chronicle-specific Skill Creator failure.
Please confirm:
- which released ChatGPT Desktop/Codex build first contains the fix;
- whether Chronicle workers are covered by that fix; and
- whether a guard will prevent background tasks configured with bundled Skills disabled from mutating
$CODEX_HOME/skills/.system.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing handling of skills.bundled.enabled=false and the cleanup that affects $CODEX_HOME/skills/.system. Reproduce with a disposable CODEX_HOME, then verify that a Chronicle worker leaves the shared system-Skills installation unchanged while still disabling bundled Skills for that worker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100