{"version":"2.1.260","anchor":"new-stalled-unsent-outcome-for-remote-tool-approvals","canonical_anchor":"new-stalled-unsent-outcome-for-remote-tool-approvals","heading":"New 'stalled_unsent' outcome for remote tool approvals","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-stalled-unsent-outcome-for-remote-tool-approvals","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New 'stalled_unsent' outcome for remote tool approvals\n\nDeleting a job with unpushed commits now tells you the count and lets a second delete force discard.\n\nDeleting a background\/fleet job whose worktree has unpushed commits no longer fails silently. It now reports the unpushed commit count and prompts you to delete again to discard them, tracking a `discardOffer` so a second delete forces `discardUnpushed`.\n\n- Area: Sessions\n- Names: `discardUnpushed`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}