codex - 💡(How to fix) Fix Codex Windows Desktop: Agent uses stale plugin cache path after plugin update, and session execution details are lost after restart

What version of the Codex App are you using (From “About Codex” dialog)?

26.521.10419

What subscription do you have?

business

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I am seeing two issues in Codex Windows Desktop related to plugin usage and session diagnostics.

First, after the openai-curated/superpowers plugin was updated, the Agent appeared to use a stale plugin cache path instead of the current plugin path.

In my current Codex workspace, the visible plugin path is:

.codex/plugins/cache/openai-curated/superpowers/6188456f/skills/using-superpowers/SKILL.md

6188456f appears to be the current plugin cache hash on my machine. This path was created/updated around May 23.

However, when I used @superpower in a project conversation, the Agent reported that the superpower plugin was unavailable. When I inspected the plugin path details at that time, the Agent appeared to reference a different cache hash instead of 6188456f.

This suggests that after the plugin update, Codex may not have injected the latest valid plugin path into the Agent environment.

Second, after restarting Codex / reopening the same conversation, the previously visible command/thinking details were no longer available. Only file-edit records and browser-call records remained visible. Because of this, I could no longer recover the exact stale path that the Agent had referenced.

What steps can reproduce the bug?

1. Open a project workspace in Codex Windows Desktop.
2. Make sure the openai-curated/superpowers plugin exists in the local Codex plugin cache.
3. Confirm the current visible plugin path. In my case it was: .codex/plugins/cache/openai-curated/superpowers/6188456f/skills/using-superpowers/SKILL.md
4. In an existing or active project conversation, ask the Agent to use @superpower to continue project work.
5. Observe that the Agent reports the superpower plugin as unavailable.
6. Inspect the Agent's plugin path / environment details.
7. Compare the path used by the Agent with the current plugin path in the Codex workspace.
8. Keep Codex open and observe that more command/thinking details are visible at this point.
9. Restart Codex Desktop or reopen the same conversation later.
10. Try to inspect the same command/thinking details again.
11. Observe that the previous diagnostic details are no longer visible, and only file-edit records and browser-call records remain.

What is the expected behavior?

After a plugin update, Codex should ensure that the Agent receives the current valid plugin cache path.

Expected behavior for plugin loading:

• The Agent should use the latest valid plugin cache path automatically.
• Existing conversations should refresh plugin path injection after the plugin is updated, or Codex should clearly indicate that the conversation/session needs to be restarted.
• The Agent should not silently use or reference a stale plugin cache path that causes the plugin to be reported as unavailable.
• If a plugin cache hash changes, Codex should detect stale paths and re-resolve to the latest valid path.

Expected behavior for session diagnostics:

• After restarting Codex or reopening a conversation, enough diagnostic information should remain available for debugging and bug reporting.
• At minimum, Codex should preserve command execution records, command outputs or summaries, tool calls, plugin paths used by the Agent, and relevant environment/path details.
• If full thinking details are intentionally not persisted, command/tool execution details should still remain available.

Additional information

Environment:

• Product: Codex Windows Desktop
• OS: Windows
• Codex Desktop version: <fill in version>
• Workspace type: Project workspace
• Plugin involved: openai-curated/superpowers

Current visible plugin path:

.codex/plugins/cache/openai-curated/superpowers/6188456f/skills/using-superpowers/SKILL.md

Observed behavior:

• The Agent reported that the superpower plugin was unavailable.
• The Agent appeared to reference a plugin cache path whose hash did not match 6188456f.
• After restarting/reopening Codex, the detailed command/thinking records that showed this path were no longer visible.
• Only file edit records and browser call records remained visible.

Impact:

• The Agent may fail to use an installed/updated plugin because it references an outdated plugin cache path.
• Users cannot easily confirm which plugin version/path the Agent is actually using.
• After restarting Codex or reopening a conversation, diagnostic details may disappear.
• Users lose the evidence needed to file a precise bug report.
• This makes plugin-related failures hard to reproduce, verify, and report.

Questions:

1. Does Codex Windows Desktop refresh plugin path injection after a plugin cache update?
2. Can existing conversations retain stale plugin cache paths after a plugin update?
3. Is it expected that @superpower can become unavailable if the Agent has an outdated plugin cache path?
4. Are command execution details and tool-call details expected to persist after reopening a conversation?
5. If full thinking details are not persisted by design, could Codex still preserve the command/tool execution history needed for debugging?