Interactive Codex ignores disabled state for remote installed plugins
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Codex version
0.149.0
Platform
Linux x86_64
Problem
Interactive Codex does not persist or honor the disabled state for an installed remote plugin. This was reproduced with Superpowers.
Reproduction
- Open /plugins in interactive Codex.
- Select Superpowers and press Space.
- The row changes from [*] to [-].
- Press Esc and reopen /plugins.
- The row is back to [*].
- Restart Codex and create a completely new chat.
- Superpowers skills are still injected and used.
Persisted configuration
The toggle correctly writes:
[plugins."superpowers@openai-curated-remote"]
enabled = false
The setting remains false after restart and there are no project or profile overrides.
Direct runtime evidence
Inspecting the recorded developer payload of a completely new interactive session with source cli shows all superpowers-prefixed skills, including superpowers:using-superpowers, despite enabled=false.
By contrast, a brand-new non-interactive session created by codex exec with source exec omits every Superpowers skill under the same config. The earlier conclusion that this was display-only was based on that non-interactive path and was incorrect.
This isolates the failure to the interactive CLI startup/plugin-loading path: interactive codex ignores enabled=false for this remote installed plugin, while codex exec honors it.
Launching a fresh interactive TUI with explicit false overrides for both superpowers@openai-curated-remote and superpowers@openai-curated still renders [*] and loads the interactive plugin state.
Expected behavior
After disabling an installed plugin, reopening /plugins should show [-], and new interactive chats must not receive its skills.
Actual behavior
The plugin returns to [*], and new interactive chats receive and use its skills. Only codex exec honors the disabled setting.
Remote plugin
Name: Superpowers
Remote plugin id: plugins~Plugin_60aea7460bd4819199fd97a9553a5e12
Uploaded diagnostics
Feedback upload thread: 01a02329-a61a-7033-b0b1-abe0fb0729bf
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 the interactive CLI startup/plugin-loading path and compare it with the codex exec path, using the /plugins reproduction and the persisted enabled=false configuration. Done means reopening /plugins preserves the disabled state and new interactive chats omit the disabled plugin's skills, matching codex exec behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100