Settings types or JSON Schema

Status Fixed / completed
Maintainer reply ✓ Yes — bogini
Activity 5 comments · opened Jul 1, 2025 · closed Sep 29, 2025
💡 Likely answer: A maintainer (bogini, collaborator) responded on this thread — see the highlighted reply below.

Would it be possible to publish TypeScript types or a JSON Schema for the settings file?

I'm building a tool to help manage the settings file in the repo and this would be immensely helpful.

Thank you.

View original on GitHub ↗

5 Comments

nitsanavni · 1 year ago

Could also help auto-complete settings.json in an IDE

josefaidt · 1 year ago

I found a schema on schemastore that looks correct, but alas claude-code does not like this $schema key

https://www.schemastore.org/claude-code-settings.json

{
  "$schema": "https://www.schemastore.org/claude-code-settings.json"
}
Invalid Settings
 /Users/josef/.claude/settings.json
  └ Unrecognized field: $schema

 Check for typos or refer to the documentation for valid fields
 Learn more: https://docs.anthropic.com/en/docs/claude-code/settings
waynesbrain · 12 months ago

For VS Code you can also assign schemas to specific files or file patterns in your .vscode/settings.json file or in your multi-root project.code-workspace file under "settings" or even in your global settings e.g.

    "json.schemas": [
      {
        "url": "https://cdn.deno.land/deno/versions/v1.30.0/raw/cli/schemas/config-file.v1.json",
        "fileMatch": ["deno.json", "deno.jsonc"]
      }
    ],

_EDIT: Unfortunately it looks like the schemastore schema is out of date. I'm looking for the additionalDirectories setting mentioned here and that schema causes an error Property additionalDirectories is not allowed._

bogini collaborator · 11 months ago

https://json.schemastore.org/claude-code-settings.json has been updated with the latest settings. Claude Code now also supports the $schema field:

{
  "$schema": "https://json.schemastore.org/claude-code-settings.json",
  ...
}
github-actions[bot] · 10 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.