A workspace’s main folder holds the team in .vopit. Linked folders let the same team work across other folders, for example separate frontend and backend checkouts. The Changes panel shows what changed in each repository, grouped by request, and lets you run everyday Git actions yourself.
Link folders to a workspace
- Choose the workspace folders button in the header, then Link a folder and select a folder beside the main one.
- Check Name for agents, the alias agents use for this folder. Add What it contains, for example “Node API, PostgreSQL, tests with vitest”, to help agents.
- Choose Done. Use Relink when a folder has moved, and Unlink to remove the link; the folder and its files are not touched.
- A workspace can link up to 16 folders. An alias uses letters, digits, dots, dashes or underscores (up to 40) and must be unique. Reserved device names and names already at the top of the main folder are refused.
- You cannot link the workspace folder itself, a folder containing it, a folder already inside it (agents see it without linking), or a folder overlapping another linked one. A folder can be linked to only one workspace.
- Opening a linked folder in Vopit opens its workspace, with its team and its other folders. If the linked folder has its own Vopit project, that project’s history stays in its own .vopit folder.
- Paths are absolute and personal to this computer: .vopit is never committed. A folder not found on this computer is shown as missing, and agents do not see it until you relink it.
How agents use linked folders
- With Vopit project tools, agents prefix paths with the alias, for example api/src/index.ts, and use the alias as working directory to run a command in that folder. Paths without a prefix are in the main folder.
- Native tools use the absolute folder paths. Claude Code receives each linked folder as an additional directory, and Codex can write in linked folders when it has project write access. Vopit still checks every path against its protections.
- Agents are told to keep each change in the folder that owns it and to run each folder’s own build and tests there.
Git across several repositories
- git_prepare prepares the same request branch in the repository of each linked folder. Every repository is checked before any is changed: a detached HEAD, existing staged changes or an existing branch name stops the request before work starts.
- git_commit makes one commit per repository with request changes. A linked repository without changes returns to its starting branch.
- A linked repository Git could not commit is listed as an open point; the rest of the request stands.
- Linked folders without a Git repository are reported; their changes are not committed.
- git_branch and git_sync accept a folder name to act on a linked folder’s repository.
- Projects with linked folders run their Git requests one at a time instead of using parallel worktrees.
Review changes
Open the Changes tab in the project sidebar, or choose Show changes in Quick actions (Ctrl/Cmd+K). Use Repository to switch between Main folder and each linked folder’s repository. If the folder is not a Git repository yet, Initialize repository creates a local one on your base branch; your files stay as they are, and nothing is staged or committed.
- Changes are grouped by the request that made them, with the agent’s name on each file. Other changes covers your edits, generated files and anything Vopit did not record.
- Click a file to see its diff. Open in window shows Changes, History and Stashes, with Side by side or Inline diffs.
- Stage, Unstage and Discard act on one file; Stage all and Unstage all act on the list. Discarding a new file deletes it. A conflict cannot be discarded: resolve it and choose Mark resolved, or abort the merge.
- Files that look like credentials or excluded paths are listed with a lock, but their content is never displayed, and Stage all skips them.
Commit, branch and synchronize
| Action | Behavior |
|---|---|
| Commit | Write a message and choose Commit N files, or press Ctrl+Enter (Cmd+Enter on macOS). With nothing staged, Commit all N files stages every unstaged file except protected files and conflicts, then commits. |
| Amend last commit | In More Git actions. Leave the message empty to keep the previous one. |
| Branches | The branch button lets you find, switch to, create, delete or merge a branch into the current one. A remote branch is checked out as a tracking branch. Main and protected branches from the project’s Git settings cannot be deleted, and Git refuses to delete a branch with unmerged work. |
| Merge | Merges without editing the message. With conflicts, fix the files, mark them resolved and commit the merge, or choose Abort. |
| Stash | Stash all changes (including new files), Pop latest stash, or View stashes to Apply, Pop or Delete one. |
| Fetch / Pull / Push | Fetch from the upstream or the configured remote. Pull is fast-forward only. Push is never forced; a branch without upstream shows Publish and is pushed with tracking to the configured remote. |
| Commit graph | Shows the 200 most recent commits and their changes. |