Summary
After running codex-multi-auth uninstall, reinstalling via npm i -g codex-multi-auth, double-clicking the macOS Codex Multi Auth.app, and restarting /Applications/Codex.app, the Codex plugins panel shows plugins toggled off. Automations that rely on those plugins stop working.
Split from issue #486 as the symptom is independent of the pinned-account 503 root cause being tracked there.
Reporter context
Expected
Plugin enable state survives a reinstall cycle.
Actual
Plugin enable state appears reset on first launch after reinstall.
Investigation ideas
scripts/postinstall.js and scripts/preuninstall.js are the most likely overwriters of plugin state.
- Plugin manifest is bundled (
bundleDependencies: ["@codex-ai/plugin"]); confirm whether reinstall rewrites the user-side enable flags from the bundled manifest defaults.
- Cross-check whether plugin enable flags live under
~/.codex/multi-auth/ (wiped during uninstall) or under a path that should survive uninstall.
Compliance Confirmation
Refs #486.
Summary
After running
codex-multi-auth uninstall, reinstalling vianpm i -g codex-multi-auth, double-clicking the macOSCodex Multi Auth.app, and restarting/Applications/Codex.app, the Codex plugins panel shows plugins toggled off. Automations that rely on those plugins stop working.Split from issue #486 as the symptom is independent of the pinned-account 503 root cause being tracked there.
Reporter context
0.134.0, Codex app26.519.81530 (3178)Expected
Plugin enable state survives a reinstall cycle.
Actual
Plugin enable state appears reset on first launch after reinstall.
Investigation ideas
scripts/postinstall.jsandscripts/preuninstall.jsare the most likely overwriters of plugin state.bundleDependencies: ["@codex-ai/plugin"]); confirm whether reinstall rewrites the user-side enable flags from the bundled manifest defaults.~/.codex/multi-auth/(wiped during uninstall) or under a path that should survive uninstall.Compliance Confirmation
Refs #486.