Core concepts
Libraries and Workspaces
Understand Library storage, switching Libraries, Workspace registration, Global versus Workspace scope, and safe management practices.
VisuAgent Manager separates what you store (the Library) from where it is applied (Global and Workspaces).
Libraries
A Library is a directory on this computer. Configuration items live as files inside that directory so you can version them, back them up, or share them through ordinary file workflows (for example Git).
Active Library
- The header shows the active Library name.
- Primary destinations (Home, Library, Workspaces, Activity) require an active Library.
- Switch or register Libraries in Settings → Libraries:
- Add or open a Library directory
- Activate a registered Library
- Rename a registration
- Remove a registration (does not automatically delete files on disk unless you delete them yourself outside the app)
Storage expectations
- Library content is local to the device unless you copy the folder yourself.
- Prefer one active working Library per machine session to avoid confusion.
- Treat the Library folder as source-controlled content: review diffs before sharing, and never commit secrets that belong only on one machine.
Workspaces (projects)
In the product UI, destinations are labeled Workspaces. A Workspace is a registered folder path (typically a code repository root) that can receive project-scoped agent configuration.
Discover and manage Workspaces
- Workspaces shows Global plus registered Workspace destinations and their assignments.
- Workspaces → Manage Workspaces adds, edits, or removes registrations with a staged Save/Discard draft.
- Setup can add the first Workspace or skip the step.
Visu does not invent Workspaces from every folder on disk; only registered paths participate in assignment and sync.
Global versus Workspace scope
| Destination | Typical use | Scope name in support matrix |
|---|---|---|
| Global | User-level configuration shared across projects | User |
| Workspace | Project-specific configuration for one registered folder | Project |
Not every agent supports every feature at both scopes. An item may assign successfully for one agent at Global and remain unsupported at Workspace (or the reverse). Compatibility is evaluated per agent, feature, and scope: see Supported agents.
Safe management practices
- Keep Libraries and Workspaces on paths you control and can back up.
- Prefer assigning reviewed Library items over editing agent files by hand and then fighting sync conflicts.
- When moving machines, copy the Library folder and re-register Workspaces; re-enter sensitive values; re-select assignments; run review/sync on the new computer.
- Removing a Workspace registration or Library registration is separate from deleting files: confirm on-disk intent before using the OS file manager.
- Do not share Library exports that still contain non-sensitive credentials you intended to keep private; mark secrets as Sensitive (see Data and security).