{"version":"2.1.235","anchor":"new-opt-in-prompt-input-spell-checking-aspellhunspellispe","canonical_anchor":"new-opt-in-prompt-input-spell-checking-aspellhunspellispe","heading":"New opt-in prompt-input spell checking (aspell\/hunspell\/ispell)","tier":"use","area":"Spell Check","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/new-opt-in-prompt-input-spell-checking-aspellhunspellispe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### New opt-in prompt-input spell checking (aspell\/hunspell\/ispell)\n\nClaude Code can now spell-check prompt input using aspell, hunspell, or ispell if you opt in\n\nA new `spellcheck` settings block adds spell checking to the prompt input, underlining misspelled words. It ships off by default; the schema's default is `enabled: false`, and turning it on shells out to whichever of aspell, hunspell, or ispell it finds on `PATH` (or a specific one via the `checker` sub-key, default `auto`), parsing the tool's ispell-protocol output. Other sub-keys are `language` (a plain dictionary name) and `color`. The block is only honored from user, flag, or managed settings; a `spellcheck` block in project `.claude\/settings.json` or `.claude\/settings.local.json` is ignored with a warning. If no supported checker is installed, spell checking silently stays off. Usage is reported via `input_spellcheck` telemetry.\n\n- Area: Spell Check\n- Names: `spellcheck`, `checker`, `language`, `color`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5"}