{"version":"2.1.227","anchor":"query-profiling-now-needs-an-environment-variable","canonical_anchor":"query-profiling-now-needs-an-environment-variable","heading":"Query profiling now needs an environment variable","tier":"use","area":"Performance","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/query-profiling-now-needs-an-environment-variable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Query profiling now needs an environment variable\n\nQuery profiling only runs when you set CLAUDE_CODE_PROFILE_QUERY, so ordinary sessions skip it.\n\n**What**\n\nTiming marks, memory snapshots and the timeline dump only run when `CLAUDE_CODE_PROFILE_QUERY` is set, so ordinary sessions no longer collect them.\n\n**Details**\n\n- Marks and memory snapshots are cleared at the start of each query.\n- The ASCII bars in the dump are built with a repeat helper.\n\n**Usage**\n\n`CLAUDE_CODE_PROFILE_QUERY=1 claude` **Evidence** `CLAUDE_CODE_PROFILE_QUERY`\n\n- Area: Performance\n- Names: `CLAUDE_CODE_PROFILE_QUERY`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}