CLI Commands

Top-Level Commands

allagents update [--offline] [--dry-run] [--client <client>] [--scope <scope>]

update

Updates plugins in the workspace using non-destructive sync. By default, remote plugins are updated to their latest version. Also available as allagents workspace update or allagents workspace sync.

Flag	Description
--offline	Use cached plugins without fetching latest from remote
--dry-run	Preview changes without applying them
-c, --client <client>	Sync only the specified client (e.g., opencode, claude)
-s, --scope <scope>	Sync scope: project (default) or user

When --scope user is used, sync targets the user-level workspace at ~/.allagents/workspace.yaml and installs plugins to user directories (~/.claude/, ~/.codex/, etc.) instead of the project.

Non-destructive behavior:

• First sync overlays files without deleting existing user files
• Subsequent syncs only remove files previously synced by AllAgents
• User files (not from plugins) are never deleted

Sync state is tracked in .allagents/sync-state.json.

When vscode is in the clients list, sync also generates a .code-workspace file with repository paths resolved to absolute paths. See the Workspaces guide for details.

Workspace Commands

allagents workspace init <path> [--from <source>]
allagents workspace status
allagents workspace plugin install <plugin@marketplace> [--scope <scope>]
allagents workspace plugin remove <plugin> [--scope <scope>]

workspace init

Initialize a new workspace from a template:

Flag	Description
--from <source>	Copy workspace.yaml from local path or GitHub URL

Source formats:

• Local path: ./path/to/template or /absolute/path
• GitHub URL: https://github.com/owner/repo/tree/branch/path
• GitHub shorthand: owner/repo/path or owner/repo

When using a GitHub source, AllAgents fetches workspace.yaml from .allagents/workspace.yaml or workspace.yaml in the target path.

workspace plugin install / remove

Flag	Description
-s, --scope <scope>	Installation scope: project (default) or user

When --scope user is used, the plugin is added to the user-level config at ~/.allagents/workspace.yaml instead of the project workspace. User-scoped plugins sync to user directories (~/.claude/, ~/.codex/, etc.) and are available across all projects.

Self Commands

allagents self update [--npm] [--bun]

self update

Update AllAgents to the latest published version.

Flag	Description
--npm	Force update using npm
--bun	Force update using bun

If neither flag is provided, AllAgents auto-detects the package manager used during installation.

Automatic Update Notifications

When running the interactive TUI (allagents with no arguments), AllAgents checks the npm registry for newer versions in the background. If an update is available, a notice is shown on the next startup:

allagents v0.13.4

  ℹ Update available: 0.13.4 → 0.14.0
    Run `allagents self update` to upgrade.

The check runs at most once every 24 hours and never blocks startup. Results are cached at ~/.allagents/version-check.json.

Plugin Commands

allagents plugin list [marketplace]
allagents plugin validate <path>
allagents plugin install <plugin> [--skill <name>] [--scope <scope>]
allagents plugin uninstall <plugin> [--scope <scope>]
allagents plugin marketplace add <source> [--name <name>] [--branch <branch>]
allagents plugin marketplace list
allagents plugin marketplace remove <name>
allagents plugin marketplace update [name]
allagents plugin skills list [--scope <scope>]
allagents plugin skills remove <skill> [--plugin <plugin>] [--scope <scope>]
allagents plugin skills add <skill> [--from <source>] [--plugin <plugin>] [--scope <scope>]

plugin install

Install a plugin into the workspace.

Flag	Description
-s, --scope <scope>	Installation scope: project (default) or user
--skill <name>	Only enable specific skills from the plugin (can be repeated)

--skill <name>

Only enable specific skills from the plugin. Can be specified multiple times:

allagents plugin install superpowers@marketplace --skill brainstorming --skill tdd

When used, all other skills from the plugin are implicitly disabled. Skills can be added later with plugin skills add.

plugin skills list

List all skills from installed plugins with their enabled/disabled status.

Flag	Description
-s, --scope <scope>	Scope: project (default) or user

plugin skills remove

Disable a skill, preventing it from being synced to the workspace.

Flag	Description
-p, --plugin <plugin>	Plugin name (required if skill exists in multiple plugins)
-s, --scope <scope>	Scope: project (default) or user

After disabling, the skill is added to disabledSkills in workspace.yaml and sync is run to remove it.

plugin skills add

Add a skill from a plugin, or re-enable a previously disabled skill. The <skill> argument can be a skill name or a GitHub URL pointing to a skill.

Flag	Description
-f, --from <source>	Plugin source (GitHub URL, owner/repo, or plugin@marketplace) to install if the skill is not already available
-p, --plugin <plugin>	Plugin name (required if skill exists in multiple plugins)
-s, --scope <scope>	Scope: project (default) or user

Adding a skill from a new plugin

Use --from to specify the plugin source when the skill isn’t already installed:

# Add a specific skill from a GitHub repo
allagents skills add reddit --from ReScienceLab/opc-skills

# Or pass a GitHub URL directly — the skill name is extracted from the URL path
allagents skills add https://github.com/owner/repo/tree/main/skills/my-skill

Source formats for --from:

• GitHub shorthand: owner/repo
• GitHub URL: https://github.com/owner/repo
• Marketplace: plugin@marketplace

Re-enabling a disabled skill

allagents skills add brainstorming
allagents skills add brainstorming --plugin superpowers

After enabling, the skill is removed from disabledSkills and sync is run to restore it.

Tip

allagents skills add is a shorthand for allagents plugin skills add.

MCP Commands

allagents mcp add <name> <commandOrUrl> [options]
allagents mcp remove <name>
allagents mcp list
allagents mcp get <name>
allagents mcp update [--offline]

Manage MCP servers at the workspace level. Servers are persisted in a top-level mcpServers: field in workspace.yaml (parallel to mcpProxy:) and synced to all configured clients that support project-scoped MCP (claude, codex, vscode, copilot).

mcp add

Add a new MCP server to workspace.yaml and immediately sync it to all configured clients.

Flag	Description
--transport <type>	Transport type: http or stdio (auto-detected from URL by default)
--arg <value>	Argument for the stdio command (repeatable)
-e, --env <KEY=VALUE>	Environment variable for stdio transport (repeatable)
--header <KEY=VALUE>	HTTP header for http transport (repeatable)
--client <csv>	Comma-separated list of clients that should receive this server (default: all project-scoped clients)
-f, --force	Replace an existing server with the same name

Transport auto-detection: if <commandOrUrl> starts with http:// or https://, http transport is selected; otherwise stdio is selected. Passing --transport stdio with a URL, or --transport http with a non-URL command, is rejected.

# HTTP server
allagents mcp add deepwiki https://mcp.deepwiki.com/mcp

# HTTP server with headers and client filter
allagents mcp add internal https://mcp.internal.corp --header Authorization=Bearer-token --client claude,copilot

# stdio server with args and env vars
allagents mcp add gh-server npx --arg=-y --arg=@modelcontextprotocol/server-github -e GH_TOKEN=ghp_xxx

# Replace an existing server (update workflow)
allagents mcp add deepwiki https://new.example.com --force

mcp remove

Remove a server from workspace.yaml and unsync it from all clients. Only servers AllAgents added are removed; pre-existing user-managed servers in client MCP configs are preserved.

allagents mcp remove deepwiki

mcp list

List all MCP servers defined in workspace.yaml.

allagents mcp list

mcp get

Print the workspace.yaml definition for a specific server as YAML.

allagents mcp get deepwiki

Exits with status 1 if the server is not defined in workspace.yaml.

mcp update

Re-sync MCP servers only, without touching skills, agents, hooks, or other plugin artifacts. Useful when you’ve edited workspace.yaml’s mcpServers: block manually and want to push the changes to clients without running a full workspace sync.

Flag	Description
--offline	Use cached plugins without fetching from remote marketplaces

allagents mcp update
allagents mcp update --offline

To modify a server definition, use allagents mcp add <name> ... --force.

Ownership model

AllAgents only tracks MCP servers it added. This means:

• mcp add marks the server as AllAgents-owned in .allagents/sync-state.json.
• mcp remove only removes servers from client MCP configs that AllAgents originally added. User-managed servers (added manually to .mcp.json, .vscode/mcp.json, etc.) are never touched.
• If you manually add a server to a client config first, and then run mcp add with the same name, the existing user-managed entry is left alone (AllAgents will skip it with a warning).

See CLAUDE.md — MCP Server Sync for the full ownership rule.