{"version":"2.1.311","anchor":"claude-respawn-now-validates-the-job-prefix-before-contacti","canonical_anchor":"claude-respawn-now-validates-the-job-prefix-before-contacti","heading":"claude respawn reports a bad job name before checking the background service","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/claude-respawn-now-validates-the-job-prefix-before-contacti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### `claude respawn` reports a bad job name before checking the background service\n\nA wrong or ambiguous job prefix given to claude respawn is now reported even when the background service is down\n\n**What**\n\n`claude respawn <prefix>` restarts a background job that you pick by the first few letters of its name. Claude Code now checks those letters before it tries to reach the background service that runs jobs. If no job matches, or more than one does, you now see \"No job matching\" or \"Ambiguous prefix\", even when the background service is unavailable. Before, the unavailable-service error came first and hid the problem with the prefix. Running it with `--all` works as before.\n\n**Why**\n\nYou get the error that matters first. A typo in the job name is no longer hidden behind a message about the background service.\n\n- Area: Background Agents\n- Names: `claude respawn`, `--all`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}