Run Multiple Plugins Locally Using the Flex Plugins CLI

You need to install the latest version of the Flex Plugins CLI in order to use these features. If you're migrating a legacy plugin to use the new CLI, refer to our Migration Guide.

Plugins on your development machine must be registered with the Plugins CLI if you want to include them in a test environment. To register your plugins:

Option 1: Download your plugin source using the CLI

twilio flex:plugins:create --template <github url of plugin> --install

Option 2: Register a plugin already on your machine

1
# Executed within the directory of your plugin
2
twilio flex:plugins:start
3

The Plugins CLI can access any plugin that you have deployed to your Flex account (remote plugins) and any plugin that you are developing on your own machine (local plugins).

You can choose the plugins you want to run locally by using the --name argument. The name corresponds to the name field in the package.json of your plugin. When you run the command in your plugin directory, you don't have to pass the name of the plugin.

plugin-agent-response $ twilio flex:plugins:start --name plugin-sample

The command does the following:

• Starts a local instance of Flex
• Since the command is being run in a plugin directory, it loads plugin-agent-response
• Since plugin-sample is being passed using the --name argument, it also loads the plugin plugin-sample

By default, your local Flex instance can be accessed from localhost:3000. If you see a login page, the 'Login with Twilio' option will log you into Flex without configuring SSO.

Refer to your Terminal output for information on the plugin directories being used by the local server:

Expand image

You can view the plugins currently deployed on your Flex application by accessing the Plugins Dashboard or by running the following command via the CLI

twilio flex:plugins:list:plugins

Use the --include-remote argument to load every plugin that is already enabled on your live Flex application. This shortcut allows you to test any new changes against your normal Flex environment, without manually downloading & running each plugin individually.

plugin-agent-response $ twilio flex:plugins:start --include-remote

The command does the following:

• Starts a local instance of Flex
• Since the command is being run in a plugin directory, it loads plugin-agent-response
• Since --include-remote is used, it accesses your live Flex application, fetches the list of all currently enabled plugins, and loads each of these alongside plugin-agent-response

If plugin-agent-response is already deployed to your live Flex application, your local version will be used in place of the remote version.

An example output is shown below:

Expand image

You can use the @remote tag if you only want to run a subset of your live plugins. The @remote tag will automatically load the version that is currently enabled on your Flex application. Each plugin you want to include must be identified with the --name flag.

plugin-agent-response $ twilio flex:plugins:start --name plugin-agent-notes@remote

An example output is shown below:

Expand image

You can choose a version of a plugin to load by using the format plugin name@version. You need to ensure that the version has been deployed to your Flex application. This lets you run a remote plugin locally without enabling it on your account.

plugin-sample $ twilio flex:plugins:start --name plugin-agent-notes@1.0.0

An example output is shown below:

Expand image

The Plugins CLI keeps track of all your registered plugins in a settings file. To view details on your registered plugins:

Run the following command in your Home Directory ( C:\Users\$USERNAME)

type .twilio-cli\flex\plugins.json

• Deploy your plugins to your agents, and keep your development environment up-to-date.
• Learn about other common use cases for the Plugins CLI.