Operations
Data and security
Understand local Library storage, encrypted sensitive MCP values, what synchronization changes, backups, and safe sharing practices.
VisuAgent Manager is designed around local control. Configuration libraries, agent files, and most operational state stay on your computers unless you move them.
Local storage expectations
| Data | Where it lives | Portable? |
|---|---|---|
| Library items | Active Library folder on disk | Yes, as files you copy or version |
| App registrations (Libraries, Workspaces, settings) | Application-managed local state | Partially: recreate registrations after migration |
| Agent configuration files | Each agent’s native paths | Written by sync when supported |
| Sensitive MCP env values | Encrypted local secret storage | No: re-enter on each machine |
| Activity feed | Current application session | No |
| Diagnostic log | Path shown in Settings → Diagnostics | Local file |
Signing in for licensing verifies entitlement. It does not upload Library content to Angry Software Solutions.
Sensitive MCP environment values
- Mark credentials and tokens Sensitive in the MCP server editor.
- Sensitive values are encrypted for local use and excluded from portable Library files.
- After cloning a Library, re-enter secrets before expecting agents to authenticate.
- Review imported env vars: import may bring values that should be reclassified as Sensitive before you share the Library.
What synchronization changes
Synchronization may:
- Create, update, or delete supported agent configuration files for enabled agents and scopes
- Import external agent items into the Library when you approve review actions
- Link matching items without rewriting files
- Preserve unknown native fields when adapters merge managed keys
Synchronization does not:
- Move accounts, OAuth tokens owned solely by the agent, chat history, or unrelated app state
- Guarantee unsupported features or unverified scopes
- Bypass review when both Library and agent copies changed
Backups
- Back up the Library folder with your normal file or Git workflow.
- Export or note Workspace paths you rely on.
- Keep a record of which agents are enabled.
- Do not rely on Activity history as a backup: use Diagnostics logs and Library version control.
Safe handling of Library content
- Assume anything not marked Sensitive could be committed or shared.
- Strip or rotate credentials found in non-sensitive fields.
- Prefer private repositories for team Libraries.
- When receiving a Library from someone else, review MCP env vars, triggers, and shell commands before enabling live updates or sync.