[BUG] Admin Console Skills — changes don't propagate to clients (cached indefinitely)
Resolved 💬 2 comments Opened Mar 4, 2026 by dherceg-eyeo Closed Apr 1, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Description:
Skills pushed via the Admin Console (Team Management Console) appear to be cached client-side on
first fetch and never re-synced, regardless of updates or deletion in the Admin Console.
Expected behavior:
- Skill updates should propagate within the documented polling interval (hourly per managed
settings docs)
- Deleted skills should no longer be available after restart
Actual behavior:
- Client is stuck on the first-fetched version indefinitely
- Neither updates nor deletions propagate
- Restarting Claude Code doesn't trigger a re-fetch
- /skills command in projects with no local skills shows "No skills found" — yet the skill still
executes when invoked by name
Environment:
- Claude Code CLI (latest version)
- macOS
- Team Plan
What Should Happen?
Expected behavior:
- Skill updates should propagate within the documented polling interval (hourly per managed
settings docs)
- Deleted skills should no longer be available after restart
Error Messages/Logs
Steps to Reproduce
- Add a skill via Admin Console → Claude Code → Skills
- Open a Claude Code session in any project — skill works correctly
- Update the skill content in Admin Console
- Restart Claude Code, open a new session — old version of the skill is still served
- Wait 12+ hours — still the old version
- Delete the skill entirely from Admin Console
- Restart Claude Code — deleted skill is still available and runs
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude Code CLI version 2.1.68
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗