{"version":"2.1.251","anchor":"eligibility-check-reports-eval-confined-separately","canonical_anchor":"eligibility-check-reports-eval-confined-separately","heading":"Eligibility check reports eval_confined separately","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/eligibility-check-reports-eval-confined-separately","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Eligibility check reports eval_confined separately\n\nBackground remote eligibility now has its own rejection reason for confined evaluation runs.\n\n**What**\n\nThe check deciding whether a session can run remotely in the background now has a distinct rejection reason for confined evaluation runs, alongside the existing blocked-by-policy and no-git-remote reasons.\n\n**Evidence**\n\n`u.push({ type: \"eval_confined\" }`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}