{"version":"2.1.304","anchor":"remote-control-feature-gate-config-validation-tightened-and","canonical_anchor":"entitlement-gate-config-gains-hosttokens-and-refusenotentitl","heading":"Remote-control entitlement gate config gains hostTokens and refuseNotEntitled","tier":"soon","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-control-feature-gate-config-validation-tightened-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote-control entitlement gate config gains hostTokens and refuseNotEntitled\n\nThe server config for the remote-control entitlement gate adds hostTokens and refuseNotEntitled options and is checked more strictly\n\n**Unclear.** Which feature this configuration controls is not known.\n\n**What**\n\nClaude Code reads a configuration from the server that controls who gets a remote-control feature (an entitlement gate, meaning a check of whether your account is allowed to use it). This configuration has new options and stricter checking.\n\n- Two new true or false options, `hostTokens` and `refuseNotEntitled`, are added. Both default to `false`.\n\n- The other defaults are `percent: 0`, `graceTtlHours: 96` and `budgetMs: 6000`.\n\n- The config can now turn the feature on without a `percent` value, but in that case `refuseNotEntitled` must be present.\n\n- `graceTtlHours` and `budgetMs` are now checked to be within a valid range.\n\n- A config where `refuseNotEntitled` is not true or false is rejected.\n\n**Why**\n\nWith both new options off by default, nothing changes for you until the server sets them. They give the server a way to turn on a stricter check that refuses accounts that are not entitled.\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}