[BUG] Managed settings aren't validated causing silent failures
Resolved 💬 3 comments Opened May 14, 2026 by kegsay Closed Jul 10, 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?
If an Admin in a Team modifies settings.json, no validation is applied on what they insert (e.g. values of wrong type). This causes the JSON to fail downstream on Claude Code:
2026-05-14T12:45:37.671Z [DEBUG] Remote settings: Settings validation failed - [
{
"expected": "object",
"code": "invalid_type",
"path": [
"allowedChannelPlugins",
0
],
"message": "Invalid input: expected object, received string"
}
]
..causing the settings to not be applied as you'd expect.
What Should Happen?
The same schema validation that runs on clients should run before it allows you to save settings.json
Error Messages/Logs
2026-05-14T12:45:37.671Z [DEBUG] Remote settings: Settings validation failed - [
{
"expected": "object",
"code": "invalid_type",
"path": [
"allowedChannelPlugins",
0
],
"message": "Invalid input: expected object, received string"
}
]
Steps to Reproduce
- As an Admin of a Team, go to managed settings
- Type this for settings.json:
{
"channelsEnabled": true,
"allowedChannelPlugins": ["discord"]
}
- Login to your org and see that you can't use the plugin.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.140 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗