{"version":"2.1.315","anchor":"report-findings-mode-choice-gated-by-tengu-purring-micali","canonical_anchor":"report-findings-mode-choice-gated-by-tengu-purring-micali","heading":"Review findings now reported in 'spawn' or 'message' mode, chosen by a new check","tier":"notice","area":"Code Review","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/report-findings-mode-choice-gated-by-tengu-purring-micali","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Review findings now reported in 'spawn' or 'message' mode, chosen by a new check\n\nHow review findings are reported is now chosen as 'spawn' or 'message', replacing the old `CLAUDE_CODE_REPORT_FINDINGS` check\n\n**Unclear.** It is not stated what the \"spawn\" mode does or which tool these findings come from.\n\n**What**\n\nWhen Claude Code assembles the prompt it uses for reviewing code, it now picks one of two ways to report findings (the problems or observations the review turns up). The previous check is gone. That check only looked at whether the `CLAUDE_CODE_REPORT_FINDINGS` environment variable was set and whether a findings tool was in the list of available tools. An environment variable is a setting passed to a program from outside it.\n\n- `spawn` mode is used whenever `CLAUDE_CODE_REPORT_FINDINGS` is set.\n\n- `message` mode is used otherwise, but only when all of these hold: the client is `desktop_app` or `web_claude_ai`, the session was started from a remote entrypoint, and the `tengu_purring_micali` gate is true. A gate is a switch Anthropic can turn on or off remotely. Nothing has been read about this gate in this release, so whether it is on is unknown.\n\n- In `message` mode the prompt gains an extra section asking for one line per finding, each with its outcome.\n\n- `message` mode is skipped when the output format is text or json.\n\n- The prompt's `uses_report_findings_tool` value is now worked out from this new mode choice instead of the old check, and some parts of the review prompt were moved around.\n\n**Why**\n\nIn practice, the way review findings are presented can now differ between the terminal and the desktop app or claude.ai on the web. In those apps, findings may arrive as a short one-line-per-finding message. Anyone who relies on `CLAUDE_CODE_REPORT_FINDINGS` still gets the `spawn` behaviour. Because the review prompt itself changed, the wording and layout of review output may also shift.\n\n- Flag `tengu_purring_micali`: Not enough to say (read for one account on one subscription tier against v2.1.315; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Code Review\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}