Manual navigation

Overview

VisuAgent Manager documentation

Learn how VisuAgent Manager organizes Libraries, Workspaces, and supported agent configuration so you can install, configure, and troubleshoot with confidence.

Last verified version
1.1.8
Last verified date

VisuAgent Manager is a desktop application for managing reusable AI coding-agent configuration on your computer. You keep one Library of MCP servers, skills, sub-agents, commands, rules, triggers, and optional instruction documents, then assign compatible items to Global or Workspace destinations and apply them to the agents you enable.

This manual describes the current generally available application (verified against version 1.1.8). It focuses on what you can see and do in the product, not internal APIs or contributor docs.

Who this manual is for

  • Developers and teams who maintain configuration for more than one coding agent
  • Users moving a reviewed setup between computers
  • Anyone who needs clear guidance when an agent, feature, or scope is only partially supported

Key concepts

ConceptWhat it means
LibraryA folder on this device that stores reusable configuration items as files
GlobalUser-level destination that applies across Workspaces for agents that support user scope
WorkspaceA registered project folder that can receive project-scoped configuration
Configuration itemAn MCP server, skill, sub-agent, command, rule, trigger, or instruction document in the Library
Assignment / linkingConnecting a Library item to Global or a Workspace for specific agents
EnablementTurning an agent on in Settings, or enabling items (such as MCP servers or triggers) that support an on/off state
SynchronizationComparing the Library with agent files, reviewing conflicts, and writing supported configuration

Manual map

  1. Getting started: install the app, complete first-run setup, and confirm discovery
  2. Core concepts: Libraries, Workspaces, item lifecycle, and supported-agent compatibility
  3. Configuration guides: MCP servers, skills, sub-agents, commands, rules, triggers, instruction documents
  4. Operations: application settings, data and security expectations
  5. Troubleshooting: common failures, diagnostics, and support escalation

Start here

How verification works

Every page shows the last verified version and last verified date for the product behavior it describes. When the desktop app changes a documented workflow, setting, item type, agent, feature, or scope, maintainers update the affected pages (or record a tracked follow-up) before release.

Support status values used in this manual:

  • Supported: Visu can import, create, update, and delete the feature for that agent and scope
  • Gated: available with a semantic mapping, review requirement, or caution noted on the page
  • Unsupported: not managed by Visu for that combination
  • Unverified: no stable file path or behavior has been confirmed; treat as unavailable until verified