workspace structure

Keep submodules and worktrees in view.

FluxGit surfaces submodules, worktrees and parent-child repository context so multi-part workspaces stop hiding dirty state and inconsistent parent commits.

Two agent worktrees race the same task · compare the attempts, then merge the winner through the guarded flow · real interface, synthetic demo data

The problem: multi-part repos hide inconsistent state.

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.

Honest beta limit

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.

How FluxGit helps.

submodules

Parent-child context

Clone initializes submodules by default and you can open the child or parent from context.

worktrees

Create / open / delete

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.

safety

No silent destruction

Destructive submodule and worktree actions ask before acting.

Privacy and security posture.

Workspace inspection is local-first. FluxGit reads your local structure without sending it anywhere.

Related features.