Background AI Coding with Isolated Git Worktrees
See a branch become an isolated, runnable task environment while the main checkout remains available for your own work.
Create the branch, prepare the checkout, run the right tools, review the diff, and clean up when the work is finished.
git worktree add creates another working directory. The developer still has to install dependencies, copy ignored environment files, choose non-conflicting ports, open another editor window, and remember which terminals belong to which branch.
Cleanup is also manual. A finished branch can leave behind processes, stale paths, and worktree metadata unless the review, merge, removal, and prune steps are tracked together.
The worktree stays useful through setup, implementation, review, and final cleanup.
Create a worktree for an existing or new branch, either for your own work or for an isolated AI task.
Install dependencies, copy selected local files, and apply project or group defaults.
Open files, terminals, tests, browser tabs, and agents against the selected checkout.
Inspect Git status, commit history, changed files, and the code diff before integration.
Merge locally, push for review, continue the task, or remove the branch and worktree.
A linked checkout has source files. A usable environment also needs dependencies, local configuration, startup commands, and the correct project context.
Run the package-manager or project bootstrap command selected for this codebase.
Bring selected ignored files such as .env or .env.local into the new worktree.
Open files and URLs, run scripts, start tests, or send an HTTP request.
Configure per project or inherit appropriate defaults from a project group.
See a branch become an isolated, runnable task environment while the main checkout remains available for your own work.
Download Flame and manage worktree setup, tools, agents, review, and landing in one IDE.
Free to use on macOS, Windows, and Linux.