Koapanel
IT Try it free
All manual sections

DocumentationAI assistant

AI assistant

The AI assistant diagnoses a site with an artificial intelligence model (Anthropic's Claude): it reads the site's logs, configuration and responses, finds the problems and explains them in plain words. When the remedy is a panel setting, it also proposes the fix, which you apply with one click and can undo.

Turning it on (administrators)

Open AI assistant and enter an Anthropic API key (create it at console.anthropic.com, API Keys section). The key is encrypted on the server, never shown again nor written to the logs; you can replace or remove it at any time.

In the settings you also choose:

  • the model: the recommended one is Claude Sonnet 5, a good balance between quality and cost; you can pick a more capable or a cheaper model, or type another id;
  • the monthly token budget: beyond the limit diagnoses stop until next month (0 = no limit);
  • the nightly check of all sites (optional).

Until there is a key, the assistant is hidden from resellers and users.

Diagnosing a site

From the assistant page pick a site and press Diagnose (or After the migration for a site just moved here: the check focuses on what usually breaks when a site moves, such as paths, PHP version, URLs, HTTPS and caches).

Before sending, the panel shows you what we send to the AI, section by section:

  • the site's panel settings (PHP version and limits, HTTPS, WordPress);
  • HTTP checks made from the server itself (http, https, redirects, certificate, timings);
  • the last lines of the nginx and PHP error logs and of WordPress's debug.log;
  • the site's nginx configuration and the latest failed panel operations.

From all of this, passwords, keys, tokens, cookies, email addresses and the last part of visitors' IP addresses are removed before sending. Nothing else is sent: neither the site's files nor its databases.

Every user can analyse only their own sites; resellers those of their clients.

Fixes

Every finding has a severity, an explanation and the evidence found in the logs. When the remedy is a setting, you find the proposed fix with the "Now / After" table.

The possible fixes are only these, chosen because they are safe and reversible:

  • changing the site's PHP version (among the installed ones);
  • changing the site's PHP limits (memory, uploads, execution time, input vars, error display), within reasonable values;
  • turning WordPress's WP_DEBUG on or off;
  • turning a WordPress protection on or off (xmlrpc, login attempt limit, PHP in uploads…).

The AI cannot run commands, edit files or touch plugins and databases: if it proposes something else, the proposal is discarded and you see it written. Nothing changes until you press Apply; before applying, the panel saves the current values and Undo puts them back.

Checking all sites and usage

Administrators can run the check of all sites (one site at a time, as a background operation) or have it every night at 4:30. Fixes always have to be applied by hand.

The This month's usage box shows the tokens used against the budget, the number of requests and an estimate of the cost at list prices; the real cost is the one on your Anthropic account.