Manual navigation

Core concepts

Supported agents and compatibility

Enable supported coding agents and interpret Global and Workspace feature compatibility from the VisuAgent Manager support matrix.

Last verified version
1.1.8
Last verified date

VisuAgent Manager ships adapters for many coding agents. Compatibility is not all-or-nothing: each combination of agent, feature, and scope has a status in the product support matrix (verified 2026-07-25 for application version 1.1.8).

Enable an agent

  1. Open Settings → Agents.
  2. Toggle the agent on for use across Workspaces.
  3. Save Changes if the Settings draft requires it (Agents uses the shared draft save bar).
  4. During first-run setup, the same enablement happens on the Confirm agents step.

Some agents expose additional controls. For example, Grok may offer a compatibility-related setting that changes whether Visu leans on shared Claude/Codex-compatible assets. Leave defaults unless you understand the tradeoff.

How to read support status

StatusMeaning for you
Supported (S)Visu manages the feature at that scope with normal import/create/update/delete expectations
Gated (G)Available with a mapping, review requirement, or warning: read the note before relying on it
Unsupported (U)Visu will not manage that combination; use another scope, another feature, or the agent’s native UI
Unverified (?)No stable path confirmed: treat as unavailable

Global in the UI maps to User scope in the matrix. Workspace maps to Project scope.

Feature legend

Columns below use short codes: Mcp servers, Sub agents, Cmd commands, Rul rules, Ski skills, Tri triggers, Ins instruction documents. Each cell is Global/Workspace.

Compatibility matrix

Statuses are summarized from the desktop support matrix for authoring. Prefer in-app messaging when it differs after an update.

AgentMcpSubCmdRulSkiTriIns
Aider?/?U/UU/UG/GU/UU/UG/G
AntigravityS/GU/UG/GG/GG/GU/UU/U
Augment CodeS/GS/SS/SG/GG/GS/GU/U
Claude CodeS/SS/SS/SS/SS/SS/SS/S
ClineS/UU/UG/GG/GU/UU/UU/U
CodeWhaleS/?U/UU/UU/US/UU/UU/U
CodexS/SS/SU/US/SS/SS/GS/S
CursorS/SS/SS/SU/SS/SS/SU/U
DevinS/?U/US/SS/SS/SS/SS/U
GitHub CopilotS/SG/GS/SS/SS/S?/US/S
GitHub Copilot CLIS/US/SU/US/SS/SS/SS/S
Grok BuildS/SU/US/UU/GG/GG/GU/S
Hermes AgentS/UU/UU/UU/SS/UU/UU/S
Kilo CodeS/SG/GS/SS/SG/GU/US/S
KiroS/SS/SS/SS/SS/S?/SU/U
OpenCodeS/SS/SS/SS/SS/SG/GS/S
Roo CodeS/SS/SS/SS/SS/S?/?U/U
ZedS/SU/UU/UU/UU/UU/UU/U

Interpreting unsupported combinations

  • If assignment UI shows an agent as excluded, the feature or scope is not available: pick another destination or agent.
  • Gated entries often map Visu concepts onto a nearby native concept (for example Aider rules as conventions files). Content may need agent-specific wording.
  • Unverified project MCP (examples: some Devin/CodeWhale cases) means Visu will not pretend Workspace MCP is safe.
  • Codex commands are unsupported because custom prompts are deprecated in favor of skills.
  • Cursor user rules are unsupported; project rules remain supported.
  • Instruction documents require Settings → Advanced / Labs → Agent Instruction Documents and still depend on matrix status.

Setup tips

  1. Enable only agents installed on this machine.
  2. Check the matrix before designing a “one Library for everyone” workflow: shared Libraries work best when consumers share overlapping supported surfaces.
  3. After enabling agents, run a reviewed sync so existing native config can import or link cleanly.