If a plugin's agent.spawn hook sets a cwd on a spawn that is isolated via a worktree, the launch now fails explicitly with an error stating that cwd and isolation: "worktree" are mutually exclusive, instead of silently conflicting.
New spawn-hook error: worktree/cwd conflict
Spawn hooks setting both cwd and worktree isolation now fail with a clear error.
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
Bug FixesKind: in v2.1.260,
Bug FixesSection of the release