anthropics
[Feature Request] Support centralized enterprise policy management and centralized memory context files on a file share
Bug Description It is operationally risky to define centralized enterprise policy settings and memory context files but then to have to push them locally to all Claude Code user local file systems on an ongoing basis compared to simply having one central copy of these files on a shared file server. There is always the risk that some developers are using outdated settings or are missing settings.
This is a feature request to 1) enable enterprise managed policy settings to come from a central SMB file share and 2) to enhance the Markdown @ file reference operator to support referencing a markdown file on a remote SMB folder location so that shared centralized memory context files can be used.
With support for referencing a file share, most of the files we now put in the local C:\ProgramData\ClaudeCode\ settings folder and all its subfolders would be instead centrally located and managed from a file share that all dev team members use. Claude Code would still have a local C:\ProgramData\ClaudeCode\managed-settings.json file but this would just contain a pointer to a remote SMB share folder location like //UNCpath/moreUNCpath/ClaudeCode/managed-settings.json.
If Claude Code starts, tries to load a centralized policy file and cannot for whatever reason, Claude Code should exit as a failure to load and apply enterprise policy files should be a fatal error.
In addition, Markdown memory context file @ references would support a file share location also, e.g. @//UNCpath/moreUNCpath/ClaudeCode/model-reference-input/SQL/SQL-best-practices.md. We want some best practice and corporate standard coding practice markdown files universally applied across all repositories and by all developers.
Environment Info
- Platform: win32
- Terminal: windows-terminal
- Version: 2.0.47
- Feedback ID: 49c32996-8efb-4d2a-a38d-54bc109b440e
Errors
[]
Found 3 possible duplicate issues:
- https://github.com/anthropics/claude-code/issues/4442
- https://github.com/anthropics/claude-code/issues/2815
- https://github.com/anthropics/claude-code/issues/7992
This issue will be automatically closed as a duplicate in 3 days.
- If your issue is a duplicate, please close it and 👍 the existing issue instead
- To prevent auto-closure, add a comment or 👎 this comment
🤖 Generated with Claude Code
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Try this solution. ...
WARNING: The zip appears to be malware and the user a malware bot.
Found 3 possible duplicate issues:
- Feature Request: Implement Unified Hierarchical Configuration with System-Wide Managed Settings #4442
- Feature Request: Managed MCP Servers #2815
- Add MCP Registry support for centralized enterprise management of MCP servers #7992
This issue will be automatically closed as a duplicate in 3 days.
- If your issue is a duplicate, please close it and 👍 the existing issue instead
- To prevent auto-closure, add a comment or 👎 this comment
🤖 Generated with Claude Code
None of these are duplicates. (1) is about the general idea of a configuration hierarchy but not that enterprise configuration files be able to be on a central file share. (2) and (3) are specifically about managed MCP server configurations but not centralized enterprise configuration files or memory context files on a central file share.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.