Isolated worktree runs
Running a delegated job in a separate git worktree. Experimental, off by default.
Experimental Enabled with ml-ai.experimental.workspaces, which is false by default.
What it does
When enabled, the delegate picker in background runs offers an option to run a job in a separate git worktree instead of directly in your open workspace. Changes land in that worktree, not in your working copy, and a review step shows you exactly which files changed before you decide what to do with them.
From the review step you can apply the worktree's changes back to your workspace, or leave them in the worktree without applying.
This is off by default because these routes operate on git worktrees and can move or delete uncommitted work, and because some of the underlying engine routes report success in ways that don't match what actually happened on disk. Turn it on only if you understand that risk. Ordinary single-folder workflows don't need this feature at all.
Turning it on
Add this to your VS Code settings:
{
"ml-ai.experimental.workspaces": true
}This single setting gates the entire feature: it unlocks the worktree option in the delegate picker described above, and nothing else changes until you actually pick that option for a specific run. Turning it back off removes the option from the picker again without touching any worktree that's already been created.