Plugins
Add-ons for your workspace and your apps.
A plugin teaches a workspace something new: translate a spreadsheet, read an invoice, call a service with your own key. It runs on a server that belongs only to your workspace, never on Xuda's. Your AI chats, skills and workflows can use a plugin as a tool by themselves, and you can run one by hand.
Plugins is a tab of your workspace. Switching it on is free. The workspace server it runs on is paid on its own, and its price is shown before you agree to it.
This section is about adding, building and running plugins in the dashboard. If you want to write a plugin as a package and publish it, see the plugin developer guide.
Start
Switch Plugins on
With Plugins off, the page is a short landing page that says what plugins are and shows the plans. Choose a plan to switch Plugins on. Only the owner of the workspace can do this. You can start on the Free plan.
Create the server
The first run has two numbered cards, and the order is the truth: the server first, then a plugin. Press Create the server. The server window shows its price a month, billed by the hour, and the card that pays. Tick the consent and press Agree and create. It is ready in a few minutes, and nothing is charged today: its hours go on your next invoice.
Add or build your first plugin
Press Add plugin to pick one from the marketplace, or Build a plugin to say what you need and have it written.
Add a plugin from the marketplace
Add plugin opens the marketplace in two panes. Search the list or narrow it with the type chips, then press a plugin to see its page: what it adds, what it may do and who can use it. The page lists each method, whether it needs keys, who published it and whether it bills AI to your credits.
The consent is the foot of the window. Tick that you agree it runs on this workspace's server, then press Agree and add. The window shows the install's real steps and closes when it is done. The first plugin also sets up the plugin host on the server, which can take a few minutes. If you close the window, the install goes on and the plugin's card shows its progress.
Build your own
Build a plugin opens a form. Choose the type, give it a name and a title, and say in words what it should do. It is written and tested for you, and a progress panel shows every step. A build takes a few minutes and goes on if you close the window.
A plugin you built keeps its own menu items. Rebuild with changes asks what to change. Publish to marketplace offers it to everyone and needs the Agency membership and a seller account. Make private keeps it for this workspace and needs the Agency membership or the Plugins Pro plan.
Run a plugin
A plugin's card has a Run button. It opens the Run window on the plugin's first method, with the form that method declares. Press Run and the answer shows in the window: a file card, text or JSON, or the reason it failed. Every run is kept, newest first, under the plugin's own list and under All runs.
A plugin that needs keys shows Needs setup on its card and the Set up button. Its Setup window keeps the keys in your workspace and sends them with each run. They are never stored on the server.
What the page tells you
- The summary line says how many plugins are on, where they are, and how many runs there were today and how many failed.
- The server rail is your workspace server drawn as a bar across the page. It says if the server is running, asleep or waking up, and shows two lanes, the runs it allows at once. A dashed bar means the server cannot run plugins yet, with one line that says why.
- Each plugin card is plugged into the rail. Its foot says when it last ran, that it is running, that it waits for the server or that it needs setup. Press the card to open the plugin's window: what it can do, its last runs and its setup.
- A second, quieter rail, On Xuda's servers, lists the plugins your projects use. They run with the project, not on the workspace server.
Remove a plugin
Open the card's menu and press Remove. It asks first, then takes the plugin off the workspace and deletes its files from the workspace server. Its setup is kept.
Connectors
The Connectors tab links the workspace to outside services such as mail, chat, files or a CRM. Each person connects their own account, and only you can use the accounts you connect. Switch a service on and its own sign-in opens in a popup. Switch it off and Xuda asks the service to cancel its access. Some services ask first what they may do: YouTube can be connected to read only, or to read and publish, and its sign-in asks Google for that much and no more. A connection that may publish changes nothing until you approve each change. When the workspace has a server, you also pick where it runs: on Xuda, or on your workspace server, which then makes the calls itself with a short lived access Xuda hands it for each one. Your sign-in stays with Xuda either way. A public assistant you give YouTube shows its visitors only your public videos and playlists, never a private or unlisted one. Cast can also post a finished video to a YouTube connection that may publish, from its Publish window. Connectors you built yourself are listed first.