Custom Provider CLI

Mopheus supports two ways to add a provider that is not in the built-in list:

A custom alias clones a built-in provider's protocol and behavior while changing its command, path environment variable, or startup arguments.
An ACP provider connects any CLI that implements the Agent Client Protocol.

Registrations are stored in the current Mopheus profile's providers.json.

Custom alias

Use --uses-provider to inherit a built-in provider:

mopheus provider register my-claude \
  --uses-provider claude \
  --cmd-name my-claude \
  --env-var MY_CLAUDE_PATH

The alias inherits the source provider's protocol, skill injection path, filesystem-sandbox capability, and default interaction behavior. Registration options can override the command and environment variable.

ACP provider

mopheus provider register my-agent acp --cmd-name my-agent

mopheus provider register kiro acp \
  --cmd-name kiro-cli \
  --env-var KIRO_PATH

ACP providers use next-turn interaction delivery unless the provider advertises a stronger capability. The default home and workdir subdirectories use the command basename, not the provider alias. Override them explicitly when needed:

mopheus provider register qoder acp \
  --cmd-name qodercli \
  --home-subdir .qoder \
  --workdir-subdir .qoder

Unattended ACP commands

Provider-specific startup arguments and unattended permission policies can be declared during registration:

mopheus provider register qoder acp \
  --cmd-name qodercli \
  --acp-args=--acp,--permission-mode,bypass_permissions \
  --blocked-custom-args=--permission-mode,--dangerously-skip-permissions \
  --unattended-mode bypassPermissions \
  --verify-unattended-before-prompt

Use the minimum permission policy required by the CLI. The filesystem sandbox is documented in Filesystem Sandbox.

Manage registrations

mopheus provider list
mopheus provider remove my-agent

Only a registered command that can be found through its configured path environment variable or $PATH is advertised as an available runtime.