What version of Codex CLI is running?
codex-cli 0.101.0
What subscription do you have?
Team
Which model were you using?
gpt-5.3-codex
What platform is your computer?
Linux 5.4.0-42-generic x86_64
What terminal emulator and version are you using (if applicable)?
VSCode
What issue are you seeing?
In the same session, /skills changes (enable/disable) update the UI picker, but the assistant still uses the old session-start Available skills snapshot. So behavior is out of sync: UI state changed, model-visible skill list did not.
What steps can reproduce the bug?
- Start a new CLI session with skills A/B/C enabled.
- Ask: “What skills do you have?” (assistant reports A/B/C).
- Run
/skills and disable one/all skills, or enable a new skill D.
- Ask again in the same session: “What skills do you have?”
- Assistant still reports old A/B/C (or misses D), despite
/skills UI showing
updated state.
What is the expected behavior?
/skills changes should be reflected in the model-visible skill list in the same session (at least on next turn), or the UI should clearly indicate changes apply only to new sessions.
Additional information
Likely related to the staged rollout discussed in:
What version of Codex CLI is running?
codex-cli 0.101.0
What subscription do you have?
Team
Which model were you using?
gpt-5.3-codex
What platform is your computer?
Linux 5.4.0-42-generic x86_64
What terminal emulator and version are you using (if applicable)?
VSCode
What issue are you seeing?
In the same session,
/skillschanges (enable/disable) update the UI picker, but the assistant still uses the old session-startAvailable skillssnapshot. So behavior is out of sync: UI state changed, model-visible skill list did not.What steps can reproduce the bug?
/skillsand disable one/all skills, or enable a new skill D./skillsUI showingupdated state.
What is the expected behavior?
/skillschanges should be reflected in the model-visible skill list in the same session (at least on next turn), or the UI should clearly indicate changes apply only to new sessions.Additional information
Likely related to the staged rollout discussed in: