Worktree: another checkout of the same repository
A linked worktree lets you work on a different branch in another folder without changing the checkout you already have open. Use it for parallel tasks or agent attempts within one repository.
FluxGit surfaces submodules, worktrees and parent-child repository context so multi-part workspaces stop hiding dirty state and inconsistent parent commits.
Submodules can drift from their parent commit and worktrees multiply branches across folders. When that state is invisible, you commit a parent that points at the wrong submodule.
Submodule and worktree workflows are in beta. Pending state is surfaced per workspace, and destructive submodule and worktree operations route through the same guarded confirmation flow as everything else.
A linked worktree lets you work on a different branch in another folder without changing the checkout you already have open. Use it for parallel tasks or agent attempts within one repository.
A submodule has its own history. The parent repository records the specific submodule commit it expects, so you can include another project while choosing when to update that reference.
They solve different problems: a worktree gives one repository multiple working folders; a submodule connects two repositories. FluxGit shows linked worktrees and parent-child submodule state in the same workspace view. See the Git worktree and Git submodule documentation for the underlying Git behavior.
Clone initializes submodules by default and you can open the child or parent from context.
Worktree actions are gated with help when a desktop backend is required. When parallel attempts at the same task land in linked worktrees, you can compare them side by side and merge the winner through the guarded flow.
Destructive submodule and worktree actions ask before acting.
Workspace inspection is local-first. FluxGit reads your local structure without sending it anywhere.
Submodules in the sidebar with their path, commit and whether they are dirty.