{"version":"2.1.288","anchor":"config-file-watching-can-use-fs-events-on-linux-behind-an-e","canonical_anchor":"config-file-watching-can-use-fs-events-on-linux-behind-an-e","heading":"Opt-in faster config file watching on Linux","tier":"use","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/config-file-watching-can-use-fs-events-on-linux-behind-an-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Opt-in faster config file watching on Linux\n\nOn Linux, setting `CLAUDE_CODE_CONFIG_WATCH_EVENTS` makes Claude Code spot config file changes through system change events\n\n**What**\n\nClaude Code watches its config file so it notices when the file changes. It used to check the file at regular intervals, which is called polling. On Linux, if you set the environment variable `CLAUDE_CODE_CONFIG_WATCH_EVENTS`, it now asks the system to report changes in the file's folder instead. An environment variable is a setting you give a program when you start it.\n\nIt still polls now and then as a safety check. It goes back to polling if watching fails or a change is missed. Without the variable, or on other systems, Claude Code keeps polling as before.\n\n**Why**\n\nThis changes how edits to your config are picked up, but only on Linux and only if you set the variable.\n\n- Area: Settings\n- Names: `CLAUDE_CODE_CONFIG_WATCH_EVENTS`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}