Plugins
Plugins add capabilities such as document and presentation creation. Browse, install, enable, and disable them from Plugins.
Find and install a plugin
- Open Plugins from navigation.
- Search by name or capability.
- Review the description, developer, version, skills, and MCP connections.
- Select Install plugin.
- Confirm installation and enabled state.

Catalog contents depend on organization access and app compatibility. Wait for the displayed result before repeating an installation.
Manage installed plugins
Open Manage installed from the top right. You can search installed and user-created plugins.

Use the switch to enable or disable an item, and open its details to review included features. Disabling a plugin does not undo completed actions. For plugins with MCP, review connection and authentication status separately.
Select a plugin in a conversation
Type @ in the composer, choose the plugin, and write the request.
Use the selected document plugin to turn the attached notes into a DOCX report.
Selection helps Aru find relevant capabilities but does not guarantee every tool will run.
Install a local plugin
Prepare a plugin folder or ZIP and ask Aru to install it by path.
Install
plugins/weekly-report.zipfrom the current project as a local plugin. Confirm the result and tell me if authentication is required.
After validation and installation, check Plugins β Installed or Manage installed β Plugins I created. Local plugins may contain executable code, so use trusted packages. Installing the same plugin ID updates the existing local installation. + β Create plugin starts plugin creation; it does not import a package.
Remove a plugin
Select Remove in Manage installed. Consider disabling it first. Removing a local plugin deletes its installed files from all profiles and cannot be undone; keep the source package if needed.
Request a new plugin
Choose + β Create plugin and describe the workflow, inputs, and tools in the new task.

Create a plugin that applies our weekly-report format. First outline the structure and required sources, then produce a package I can review and install.
Creating a package does not install it. Ask for installation separately and review the files and result.