Projects
A project is a workbench that groups related chains, scripts, environments, and probes into one place. Where bundles are containers for probes, projects are the working context for automation — the thing you open when you start a testing session.
The active project
Section titled “The active project”One project is always the active project. The active project is shown as a chip in the app bar at all times. All newly created chains and scripts are automatically assigned to the active project.
The Chains and Scripts views always show only the items that belong to the active project. Switching the active project immediately refreshes both views.
Switching projects
Section titled “Switching projects”Click the project chip in the app bar to open the project picker. It shows all your projects; click any one to make it active. The picker also has shortcuts to add a new project or open the project dashboard.
When you switch to a project, its last-selected environment is restored automatically — including the variable values for that environment.
Environments
Section titled “Environments”Each project has its own named environments. Click the environment chip in the app bar (next to the project chip) to switch the active environment for the current project.
To create or edit environments and their variables, open the project dashboard — the environment editor is shown inline on the left side of the view. Select an environment to edit its variables, add new environments using the name field at the top, and click Save to apply changes.
See Environments & Variables for full documentation.
Project dashboard
Section titled “Project dashboard”Click Project Dashboard in the project picker (or navigate via the menu) to open the dashboard for the active project. It has the following sections:
Project bundles
Section titled “Project bundles”Control which bundles belong to this project. Each visible bundle has a checkbox — tick it to link the bundle to the project, untick to unlink. The list shows bundles that are free (linked to no project) or already linked to this project.
Linking matters because bundles are scoped: a bundle linked to one or more projects only appears in the sidebar (and in probe/bundle pickers) when one of those projects is active. A free bundle is always visible. See Bundles → Bundles and projects.
Linked probes
Section titled “Linked probes”Probes from any bundle can be linked to a project for quick reference. Click Link Probe to pick a bundle and then a probe. Linked probes remain owned by their bundle — they are not moved or copied.
Chains
Section titled “Chains”All chains assigned to this project are listed here. Click any chain name to open it in the Chains editor. Click New Chain to create one directly assigned to this project.
Scripts
Section titled “Scripts”All scripts assigned to this project are listed here. Click any script name to open it in the Scripts editor. Click New Script to create one directly.
Creating a project
Section titled “Creating a project”Click + Add Project in the project picker in the app bar and enter a name. The new project is automatically set as the active project and the app navigates to the Chains view, ready for you to start building.
On first launch with an empty workspace, a Default project with a Dev environment is created automatically.
Starting a new session
Section titled “Starting a new session”When you open VirtuProbe, the app always starts at the Dashboard and restores the project that was active when you last closed it. The last-selected environment for that project is also restored so variable resolution works immediately without any manual setup.
Renaming and deleting
Section titled “Renaming and deleting”Open the project dashboard and use the pencil icon to rename or the trash icon to delete the active project. Deleting removes the project and its environments but does not delete chains, scripts, or probes (they remain in the Chains view, Scripts view, and their bundles).