Workspace storage

By default VirtuProbe Studio keeps your workspace — bundles, probes, projects, chains, scripts and environments — in a local database on your machine. You can instead point it at a folder, where the same workspace is stored as plaintext files. A team then shares that folder through whatever it already uses: git, Dropbox, OneDrive, Syncthing, or a network share.

Note

Folder storage is a desktop feature — it needs access to a local filesystem.

Switching storage

Open Settings → Workspace storage. It shows the active source — Local database or Shared folder (with its path) — and lets you switch:

• Use a folder… opens a native folder chooser.
• Use local database switches back to the built-in database.

After a switch the app reloads so every view reflects the new source.

Choosing what happens to an empty folder

When you pick an empty folder, VirtuProbe asks how to set it up — it never copies your data in silently:

• Initialize a new workspace — start empty. Your local database is left untouched.
• Clone current workspace — copy your current bundles, probes, projects, chains, scripts and environments into the folder.

A folder that already contains a VirtuProbe workspace is adopted as-is (nothing is overwritten), so cloning a teammate’s repository and pointing VirtuProbe at it just works.

What the folder looks like

<your folder>/
├── bundles/      one folder per bundle; one file per probe
├── projects/     project.json + environments / chains / scripts
└── credentials/  credential configuration only — never secrets

Files are written deterministically (stable ordering, one entity per file), so a commit diff shows only what actually changed — clean to review and merge. Conflict resolution happens in your own tooling: a merge conflict in git is the conflict-resolution step.

Sharing with git

VirtuProbe never runs git for you — it only reads and writes the folder. A typical flow:

cd <your folder>
git init
git add -A
git commit -m "Share VirtuProbe workspace"
git remote add origin <your repo>
git push -u origin main

Teammates clone the repository, point VirtuProbe at the folder (it’s adopted automatically), and git pull to pick up changes — VirtuProbe reloads when the folder changes underneath it.

Secrets are never in the folder

Credential secrets (passwords, tokens, keys) always stay in the local encrypted store on each machine — they are never written to the shared folder. Only non-secret credential configuration travels with the workspace. Share the secret out of band, or have each teammate enter it locally. See Credentials & Auth for how secrets are stored.