{"version":"2.1.247","anchor":"the-job-versus-task-wording-test-for-mcp-background-work-is-","canonical_anchor":"the-job-versus-task-wording-test-for-mcp-background-work-is-","heading":"The \"job\" versus \"task\" wording test for MCP background work is gone","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/the-job-versus-task-wording-test-for-mcp-background-work-is-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### The \"job\" versus \"task\" wording test for MCP background work is gone\n\nThe status line always calls MCP background work a \"task\" instead of sometimes saying \"job\".\n\n**What**\n\nThe status line no longer chooses between calling MCP background work a job or a task. It always says `1 MCP task` or `N MCP tasks`.\n\n**Details**\n\n- The flag that drove the choice, `tengu_copper_thistle`, still exists and still gates footer layout elsewhere; it just no longer decides this label. Its in-build fallback is false.\n\n**Evidence**\n\n`return e === 1 ? \"1 MCP task\" : `${e} MCP tasks`;`\n\n- Flag `tengu_copper_thistle`: Off in both readings (read for one account on one subscription tier against v2.1.247; this account: off, anonymous baseline: off, compiled default: off)\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}