Git worktree IDE

Git worktree IDE: Manage worktrees without multiple IDE windows.

Create the branch, prepare the checkout, run the right tools, review the diff, and clean up when the work is finished.

Review the branch in contextCommit graph, branch labels, changed files, and diff stay on one canvas.
The problem

Git creates the checkout, but it does not create a runnable development environment.

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.

How Flame solves it

From branch idea to a clean base branch.

The worktree stays useful through setup, implementation, review, and final cleanup.

  1. 01

    Create the branch environment

    Create a worktree for an existing or new branch, either for your own work or for an isolated AI task.

  2. 02

    Initialize the checkout

    Install dependencies, copy selected local files, and apply project or group defaults.

  3. 03

    Run in worktree context

    Open files, terminals, tests, browser tabs, and agents against the selected checkout.

  4. 04

    Review the branch

    Inspect Git status, commit history, changed files, and the code diff before integration.

  5. 05

    Land or discard

    Merge locally, push for review, continue the task, or remove the branch and worktree.

Reproducible worktree setupSave the setup once, then apply it to each new checkout.
Beyond Git checkout

Make the branch ready to run.

A linked checkout has source files. A usable environment also needs dependencies, local configuration, startup commands, and the correct project context.

01

Install or initialize

Run the package-manager or project bootstrap command selected for this codebase.

02

Copy local files

Bring selected ignored files such as .env or .env.local into the new worktree.

03

Start the project

Open files and URLs, run scripts, start tests, or send an HTTP request.

04

Reuse shared defaults

Configure per project or inherit appropriate defaults from a project group.

Manual CLI and Flame

Keep Git's model. Remove the coordination overhead.

WorkManual workflowIn Flame
CreateRemember paths and branch flagsCreate or open from project context
InitializeRepeat install and copy commandsApply saved setup and copy rules
NavigateOpen another IDE windowSwitch worktree context in the workspace
RunTrack terminals by folderLaunch worktree-aware actions and sessions
FinishMerge, remove, prune, and clean up manuallyReview, land, push, continue, or discard
Product walkthrough

Watch a background task run in its own worktree.

Official Flame demo

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.

FAQ

Git worktree questions, answered

Make every branch ready to work.

Download Flame and manage worktree setup, tools, agents, review, and landing in one IDE.

Free to use on macOS, Windows, and Linux.