- Install Git and configure your commit identity. Open the repository root as the Vopit project. A folder without a repository can be initialized by git_prepare after GIT_WRITE approval, or from the Source control panel; the first branch is the configured fallback base branch.
- The native team already contains a Git Manager, disabled: enable it, or create an agent from the Git Manager template. Review its mission, Git actions and before/after instructions, then save it. It is editable and clonable like every other agent.
- In Settings > Project > Git workflow, configure the main branches to maintain, protected names, fallback base, feature branch template, commit template and remote name.
- Check Git inspection, branches/commits, remote synchronization and merge/rebase permissions in Settings > Permissions. Synchronization also needs the matching project switch enabled.
- Submit a task. Preparation runs before coordination; finalization runs after the workflow has run to its end, including review/correction stages when selected, and also when it finished with open points. Ultra-fast speed mode skips both. The request shows its branch and commit evidence.
Main branches can be created
Enable Create missing main branches and list the branches this project actually needs, for example main only, or main and develop. An absent branch starts from an already-known remote-tracking reference, otherwise the configured local base or the starting commit. Preparation does not fetch. Existing branches are never overwritten. Starting on a configured main or protected branch creates a unique feature branch; an existing feature branch is retained.
{
"git": {
"mainBranches": ["main", "develop"],
"protectedBranches": ["main", "master", "develop", "trunk"],
"baseBranch": "main",
"createMissingMainBranches": true,
"featureBranchTemplate": "feature/{slug}-{requestId}",
"remote": "origin",
"allowPush": false
}
}Commit the request, preserve existing work
The commit action selects changed paths recorded as modified by this request and excludes paths already dirty at preparation. Existing staging blocks preparation or finalization instead of being overwritten. An alternate index stages exact paths; no git add . is used. Resume retains the prepared branch and returns an existing request commit rather than creating a duplicate. A branch change or a change during commit approval blocks the operation.
Remote and history operations are optional
Push, fetch/fast-forward-only pull, merge and rebase are disabled in new project profiles. Enable only needed actions; workspace approval still applies. Git uses its installed credential manager or configured SSH identity; Vopit does not send credentials to the agent. There is no force push, destructive reset, forced branch deletion or automatic stash action. Vopit deletes a branch only when a request created it and either never used it (an unused linked-folder request branch after GIT_WRITE approval, the branch of a request worktree that never moved) or merged it back into the branch you chose. Conflicts require an explicit resolution; the agent reports a blocker rather than discarding work.
Parallel requests use their own worktree
Settings > Project > Git workflow > Run requests in parallel (one worktree each) is on by default. When a request that prepares Git would share the project folder with another running request, it works in .vopit/worktrees/<id> on its own branch, named from the feature branch template and started from the branch you chose, the one checked out in the project folder, never from another request's branch left there. Agents, tools, change tracking and the Git Manager use that worktree; project memory and the code graph stay with the project.
- The request waits instead, with the reason shown, when parallel requests are switched off, a branch is already prepared in the project folder, the project has no repository or no commit yet, the project has linked folders, or uncommitted files in the project folder would be missing from the worktree. Vopit tries a worktree again every 60 seconds.
- A finished worktree with nothing left uncommitted is removed; its branch keeps the commit, and a branch that never moved is deleted. A worktree with uncommitted changes is kept and listed as an open point.
- A successful request's branch is merged back into the branch you chose, held for your review, or left alone, depending on Settings > Project > Git workflow > After a successful request. See Finished work goes back into the branch you chose in Speed modes and parallel requests. Pushing stays yours, or an explicitly permitted git_sync action's.
Linked folders and the Source control panel
A project can link up to 16 folders. git_prepare prepares the same request branch in each linked folder's repository, git_branch and git_sync accept folder to target one of them, and git_commit makes one commit per repository, the project first. A linked repository that cannot be committed becomes an open point; the other commits stand. The Source control panel, opened from the Changes tab or Show changes, is for your own Git work: agent permissions do not apply there, and hooks and filters stay off. See Linked folders and source control.
Lifecycle configuration is available to every agent
In the agent Automation editor, Before / after project work exposes both phases, their order and required successful actions. Git Manager defaults require git_prepare before work and git_commit afterwards. These rules depend on configuration, not its name or identity. Missions, phase instructions, required actions and templates can be edited, copied and restored through agent revision history. Stop follow-ups stops new tasks and does not skip current lifecycle finalization.