{"version":"2.1.281","anchor":"new-telemetry-allowlist-entry-and-small-settingsschema-addi","canonical_anchor":"new-telemetry-allowlist-entry-and-small-settingsschema-addi","heading":"New telemetry allowlist entry and small settings\/schema additions","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-telemetry-allowlist-entry-and-small-settingsschema-addi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New telemetry allowlist entry and small settings\/schema additions\n\nSeveral small internal additions, including a worktree setting beside auto_mode_environment and a new input_low_latency_submit event\n\n**Unclear.** The finding does not say what the new worktree value or most of the other additions do for a user.\n\n**What**\n\nThis release contains a set of small internal additions:\n\n- `input_low_latency_submit` is added to the list of allowed usage events.\n\n- A settings schema, meaning the definition of which settings are accepted, gains a `worktree` true\/false value next to `auto_mode_environment`.\n\n- `reminderFold` is now passed along.\n\n- `hostConfig` is attached to the `rules_unreadable` result.\n\n- The vim keyboard mode's repeat count now tracks `countTyped`.\n\n- The GitHub Enterprise and headers-helper MCP fields gain `availableInVersion` markers.\n\n- An `EGRESS_ENTRY_GRAMMAR` definition is exported.\n\n**Why**\n\nNone of these is described as a feature you use directly. They show where new settings and reporting are being added."}