AI Integrations

Muru Settings > AI & Automotions is where the Smart AI Assistant gets its connection and related automation settings. The AI provider is configured once at the account level rather than per site, so a new install covered by the same license can use the assistant immediately, with no credentials to copy between sites.

AI Provider Configuration

MuRu Guard supports multiple AI providers, allowing you to choose the service that best fits your setup. The available providers include Claude, OpenAI Codex, OpenAI GPT, Gemini, OpenRouter, and a Custom OpenAI-Compatible API. Only the settings for the selected provider are displayed.

Depending on the provider, you can configure the required API key, optional Base URL, and Model, then use Test Connection to verify the configuration before saving it. You can also set a configured provider as the default for the Smart AI Assistant.

• Connect once, use everywhere -- account-level configuration means every install under an active license shares the same AI connection.
• Multiple provider options -- choose from supported providers or connect a custom OpenAI-compatible API.
• Test before using -- use Test Connection to verify that the configured provider and credentials work correctly.
• Set a default provider -- once configured, a provider can be selected as the default connection for the Smart AI Assistant.

Custom Skill

The Custom Skill lets you give the Smart AI Assistant site-specific instructions that it should follow during every conversation. This is useful for documenting your project's coding conventions, known gotchas, preferred approaches, and things the assistant should always or never do.

You can write the instructions directly in the Skill editor or upload a .md or .txt file. The Skill belongs to the individual Joomla installation, so site-specific instructions remain separate from the account-level AI provider connection.

• Project-specific instructions -- define conventions and rules specific to the site.
• Persistent guidance -- the assistant follows the Skill during every conversation.
• File upload supported -- import existing instructions from a .md or .txt file.
• Site-specific by design -- the Custom Skill is stored with the installation rather than shared through the account-level provider configuration.

Fleet Dashboard Reporting

Fleet Dashboard Reporting allows a scheduled scan to send a compact status summary to your Lyzerslab Fleet Dashboard after each scan. This makes it possible to monitor multiple MuRu Guard installations from one place without sending the contents of your site's files.

The reported information includes finding counts, protection status, and the installed version. MuRu Guard does not send file paths or matched code as part of this dashboard summary.

Autopilot Mode

Autopilot Mode allows a scheduled scan to automatically handle a small set of near-certain threats. Before applying a fix, the action receives an AI double-check, and every automatic fix includes a restore option so the change can be reversed if necessary.

Autopilot requires an AI provider to be configured under AI Integrations. It is intended for narrowly defined, high-confidence cleanup rather than unrestricted automatic changes.

Instant Alert Channels

Instant Alert Channels provide an additional notification path for scheduled scans. When a scan discovers something new, MuRu Guard can send an instant message through a configured channel in addition to, or instead of, email notifications.

Available channels include Slack, Discord, and Telegram. Each channel maintains its own on/off switch and connection settings, and only the configuration fields for the selected channel are displayed.

Slack

For Slack, enter the Webhook URL, use Send Test to verify the connection, and then select Save Settings to store the configuration.

Privacy and Data Handling

• Per-turn, stateless requests -- each turn of the conversation is a separate request. Nothing about your project is retained between sessions on the service side.
• Your files stay on your server -- file tools execute locally. Only tool names, arguments, and results travel over the network.
• Site-specific context stays local -- your custom Skill is written to the install itself, not to your account.
• Account-level credentials -- provider credentials are configured through the account-level AI connection rather than copied into individual site installations.

Optional AI Features

AI integration is optional. You can leave AI Integrations unconfigured and continue using the scanner, cleanup tools, Protection Mode, and .htaccess advisor without an AI provider. Features that specifically depend on AI, such as the Smart AI Assistant and Autopilot Mode, require an appropriate AI provider configuration.

MuRu Guard AI Integrations brings together AI provider configuration, Custom Skill instructions, Fleet Dashboard reporting, Autopilot Mode, and instant alert channels.