Skip to content

Plugins

Claude Code plugins add skills, commands, agents, hooks and MCP servers. Plugins in Computer settings lists what each Claude Code profile on your computer has, and from a phone paired as Admin you can add marketplaces and install, update, enable, disable and uninstall plugins.

  1. Open Computer settings, then Integrations, then Plugins.
  2. If the computer has more than one Claude Code profile, pick one.
  3. Choose a view: Installed, Discover or Marketplaces.

Plugins shows for an admin phone, on a computer whose Claude Code is 2.1.286 or newer. Older versions say the version is too old to list plugins.

  • Installed lists each plugin with where it is installed (all your projects, or one project) and whether it is enabled. A plugin the maker withdrew says why.
  • Discover lists plugins the profile’s marketplaces offer and it has not installed. The list stops at 200. Use the search box to narrow it.
  • Marketplaces lists the sources the profile knows, with how many plugins each offers. A marketplace Claude Code ships itself reads Built in.

Tap a plugin id to copy it.

Under an installed plugin, MCP servers lists the servers it bundles. Each https server has Test connection. When the server asks for an account, as Figma does, the result shows Sign in for the profile, and the sign-in runs through Claude Code on the computer the same way as for any other MCP server. When the test can’t reach a server as it’s configured, it says so and gives the command to check it on the computer.

A plugin installed both for all your projects and for one project shows its servers once, from the copy for all your projects.

  • Install on a plugin in Discover, Update, Enable, Disable and Uninstall on one in Installed. Uninstall asks whether to keep the plugin’s saved data.
  • Add marketplace in Marketplaces takes a GitHub repository (owner/repo), an https address on a public server without a password, or a full folder path on the computer. Each marketplace has Update and Remove, and Update all fetches every catalog.

Changes apply to the profile’s own user settings, so every project on that profile gets them. Plugins installed for one project stay read only. One change runs at a time.

Installing or updating a plugin runs code from its maker on your computer: its hooks, MCP servers and scripts. Every install, update and marketplace add opens a confirm sheet that shows what it is and where it comes from. Your tap on Install there is the approval.

Some plugins install by running a command, or fetch their files through one. Claude Code shows that command before it runs it, and so does the phone: a card with the exact command and its fingerprint. Accept and install runs exactly that command once. If the marketplace changes the command, you’re asked again.

From a session’s Plugins sheet, the phone offers to reload the session so it picks up the change. After an update, restart the session instead.

Open the session menu and choose Plugins. The list is for that session’s profile, and project plugins show for the session’s folder.

Terminal window
remotxai plugins list --profile work --available --query lint
remotxai plugins marketplace add acme/team-plugins
remotxai plugins install lint@team-plugins
remotxai plugins uninstall lint@team-plugins --keep-data

When a marketplace declares a command, install prints it with its sha256. Read it, then run the same command again with --accept-command <sha256>. If an agent runs a change, it waits for an Admin phone to approve it on that agent’s session, and an agent can’t accept a declared command at all. See Commands.

  • Only a phone paired as Admin, or you in your own terminal.
  • A person who reaches your computer through your organisation’s access list can see the list but can’t change it.
  • To turn changes off on a computer, add "harness_plugins": { "writes": "deny" } to ~/.remotxai/policy.json. To allow plugins only from some marketplaces, list their sources: "harness_plugins": { "marketplaces": ["acme/team-plugins", "https://git.example.com/tools/plugins.git"] }. A marketplace can then be added only from a listed source, and a plugin installed, updated or enabled only when its marketplace’s source is on the list. Sources must match exactly, so acme/team-plugins and its https://github.com/... address are two different entries. If the policy file can’t be read, changes are off.

The computer runs Claude Code’s own claude plugin commands under the profile’s config folder. remotxai never edits Claude Code’s plugin files itself. A change runs with no terminal, with git prompts off and without your API keys or tokens, and stops after two minutes. Each change writes a line to the computer’s audit log with the profile, marketplace and plugin. Credentials in a marketplace address are never sent to the phone.