{"version":"2.1.239","anchor":"one-shared-test-for-whether-a-run-is-headless","canonical_anchor":"one-shared-test-for-whether-a-run-is-headless","heading":"One shared test for whether a run is headless","tier":"internal","area":"CLI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/one-shared-test-for-whether-a-run-is-headless","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### One shared test for whether a run is headless\n\nOne shared check now decides whether a run is non-interactive, covering print mode and piped output.\n\n**What**\n\nA single helper now decides that a run is non-interactive, covering `-p`, `--print`, `--init-only`, any argument starting with `--sdk-url`, and stdout not being a terminal.\n\n**Evidence**\n\n`--init-only`\n\n- Area: CLI\n- Names: `-p`, `--print`, `--init-only`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}