Desktop: "Suggested task" chip card always defaults to "Start with worktree" - saved spawn-target preference regressed (~Jul 21)

Additional suggestion: the spawn_task tool (which creates these suggestion chips from within a session) currently only accepts title, tldr, prompt, and cwd - the chip creator has no way to influence the start target. An optional target field (e.g. local | worktree | cloud) would let the creating session pre-select a sensible default for the chip's primary action. That would complement the remembered-preference fix above: the user's remembered choice (or the chip's declared target) should win over a hardcoded worktree default.

Still happening on macOS today (macOS 26.6.2, Claude Desktop 2.9939.4, Claude Code 2.1.281). And there's a case where the forced default doesn't just cost a click, it always fails.

I have a repo where worktrees make no sense (a big notes vault synced across machines), so its .claude/settings.json has a WorktreeCreate hook that deliberately exits 1. Every chip for that repo defaults to "Start with worktree", and clicking it gives a bare "Error". The app knows exactly why: ~/Library/Logs/Claude/main.log has WorktreeCreate hook failed: <the hook's message> then Worktree creation failed with error: worktree_hook_failed, aborting session. None of that reaches the card.

What would fix it, simplest first:

1. Remember the last pick from the dropdown, as it did before ~Jul 21.
2. When a repo's WorktreeCreate hook refuses, fall back to "Start locally", or respect worktree.bgIsolation: "none" as #94263 asks.
3. Show the hook's message on the card instead of "Error". It's already in the log (#94610 asked for the same).

+1 to the target field on spawn_task suggested above too.

Same on macOS with a folder of markdown notes: "Start locally" works, but it's an extra dropdown click on every spawn, and a worktree start silently misses uncommitted edits. +1 to a target field on spawn_task, and to remembering the last pick / honoring worktree.bgIsolation: "none" (#94263).

Workaround for anyone hitting this meanwhile: a project-level WorktreeCreate hook that exits 1, as mentioned above. In .claude/settings.json:

{
  "hooks": {
    "WorktreeCreate": [
      {
        "matcher": "*",
        "hooks": [
          {
            "type": "command",
            "command": "echo 'Worktrees are disabled here. Use \"Start locally\".' >&2; exit 1"
          }
        ]
      }
    ]
  }
}

Tested: clicking "Start with worktree" now shows "Couldn't start the suggested task" (the chip stays), and "Start locally" opens normally. It doesn't fix the default, it just makes the wrong click harmless instead of silently starting in a worktree without your uncommitted edits. It affects anything else that creates worktrees in that project too.