Upstream gate for the configurator's next CC-compat batch.
Active gate
SchemaStore/schemastore PR #5706 — "feat(claude-code-settings): sync to Claude Code v2.1.143". Opened 2026-05-19 by miteshashar; mergeable_state: clean as of 2026-05-21; awaiting Anthropic CODEOWNER review (sarahdeaton / domdomegg / bogini / ant-kurt). Supersedes the closed PR #5665.
Unblocks on merge (eleven configurator-territory keys)
settings.json keys:
skillOverrides (CC 2.1.129) — off / user-invocable-only / name-only. Candidate for token-efficiency-pro tier.
worktree.baseRef (CC 2.1.133) — fresh / head. Candidate for multi-agent module.
worktree.bgIsolation (CC 2.1.143) — worktree / none. Candidate for multi-agent module.
autoMode.hard_deny (CC 2.1.136). Candidate for safety module.
sandbox.failIfUnavailable. Candidate for safety module.
subagentStatusLine top-level — {type, command}. Candidate for ui module.
statusLine.hideVimModeIndicator. Candidate for ui module.
hookCommand keys:
- Hook
args: string[] exec form (CC 2.1.139).
- Hook
continueOnBlock: boolean for prompt hookCommand (CC 2.1.139).
Env vars (mostly doc-only mentions):
ANTHROPIC_WORKSPACE_ID, CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE, CLAUDE_CODE_PLUGIN_PREFER_HTTPS, CLAUDE_CODE_POWERSHELL_RESPECT_EXECUTION_POLICY, CLAUDE_CODE_STOP_HOOK_BLOCK_CAP
Still held for a future sync PR (NOT in #5706)
- Hook output
terminalSequence field (CC 2.1.141).
- Stop/SubagentStop hook input adds
background_tasks + session_crons fields (CC 2.1.145).
- Skill
context: fork frontmatter (CC 2.1.145) — needs verification whether this is a new frontmatter field or an internal mechanism.
Why we wait
Configurator policy: an unknown key in settings.json can make Claude Code silently drop adjacent sections, so we wait for claude-code-settings.json in schemastore to schema-validate the key before shipping it in any template. This is defensible-by-design and mirrors the unblock pattern from PRs #17 (prUrlTemplate), #18 (sandbox.network.deniedDomains), and #28.
Also: tested_up_to only bumps when a substantive PR ships with it ("no lone tracking-up bumps"). Once #5706 merges, the unblock work will land in one PR that opts users into the new keys + bumps tested_up_to 2.1.132 → 2.1.146 + refreshes the CLAUDE_CODE_COMPAT rationale comment.
Background on the schemastore lag
Anthropic doesn't publish their own settings schema. https://www.schemastore.org/claude-code-settings.json is community-maintained inside SchemaStore/schemastore but Anthropic has CODEOWNERS on the file. Anthropic ships ~3 CC releases/week; sync PRs land ~weekly, so the schema runs structurally 5–15 versions behind. Normal and expected, not neglect.
What was already done in this resurvey
Close criteria
This issue closes when PR #5706 merges and the post-merge unblock batch PR ships in this repo.
Upstream gate for the configurator's next CC-compat batch.
Active gate
SchemaStore/schemastore PR #5706 — "feat(claude-code-settings): sync to Claude Code v2.1.143". Opened 2026-05-19 by
miteshashar;mergeable_state: cleanas of 2026-05-21; awaiting Anthropic CODEOWNER review (sarahdeaton/domdomegg/bogini/ant-kurt). Supersedes the closed PR #5665.Unblocks on merge (eleven configurator-territory keys)
settings.jsonkeys:skillOverrides(CC 2.1.129) —off/user-invocable-only/name-only. Candidate fortoken-efficiency-protier.worktree.baseRef(CC 2.1.133) —fresh/head. Candidate formulti-agentmodule.worktree.bgIsolation(CC 2.1.143) —worktree/none. Candidate formulti-agentmodule.autoMode.hard_deny(CC 2.1.136). Candidate forsafetymodule.sandbox.failIfUnavailable. Candidate forsafetymodule.subagentStatusLinetop-level —{type, command}. Candidate foruimodule.statusLine.hideVimModeIndicator. Candidate foruimodule.hookCommandkeys:args: string[]exec form (CC 2.1.139).continueOnBlock: booleanfor prompthookCommand(CC 2.1.139).Env vars (mostly doc-only mentions):
ANTHROPIC_WORKSPACE_ID,CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE,CLAUDE_CODE_PLUGIN_PREFER_HTTPS,CLAUDE_CODE_POWERSHELL_RESPECT_EXECUTION_POLICY,CLAUDE_CODE_STOP_HOOK_BLOCK_CAPStill held for a future sync PR (NOT in #5706)
terminalSequencefield (CC 2.1.141).background_tasks+session_cronsfields (CC 2.1.145).context: forkfrontmatter (CC 2.1.145) — needs verification whether this is a new frontmatter field or an internal mechanism.Why we wait
Configurator policy: an unknown key in
settings.jsoncan make Claude Code silently drop adjacent sections, so we wait forclaude-code-settings.jsonin schemastore to schema-validate the key before shipping it in any template. This is defensible-by-design and mirrors the unblock pattern from PRs #17 (prUrlTemplate), #18 (sandbox.network.deniedDomains), and #28.Also:
tested_up_toonly bumps when a substantive PR ships with it ("no lone tracking-up bumps"). Once #5706 merges, the unblock work will land in one PR that opts users into the new keys + bumpstested_up_to2.1.132 → 2.1.146 + refreshes theCLAUDE_CODE_COMPATrationale comment.Background on the schemastore lag
Anthropic doesn't publish their own settings schema.
https://www.schemastore.org/claude-code-settings.jsonis community-maintained insideSchemaStore/schemastorebut Anthropic has CODEOWNERS on the file. Anthropic ships ~3 CC releases/week; sync PRs land ~weekly, so the schema runs structurally 5–15 versions behind. Normal and expected, not neglect.What was already done in this resurvey
/simplify→/code-reviewrename in CC 2.1.146 doesn't collide with the configurator's/reviewslash command orcode-revieweragent.docs/07-backlog.mdwith the #5665→#5706 switch.CLAUDE_CODE_COMPATrationale refresh..claude/hooks/check-schemastore-pr.sh, gitignored) that prints a one-line banner on PR state change.Close criteria
This issue closes when PR #5706 merges and the post-merge unblock batch PR ships in this repo.