Troubleshoot plugins

Open Settings → Plugins and select the package. Its settings show missing configuration and API keys. Where it works checks the currently selected chat; select the chat you intend to use before checking its availability.

Add to Farero opens the Desktop app on the package’s review screen. Allow your browser to open Farero when it asks. Choose Install to continue to the plugin’s settings. If Farero is not installed, choose Get the app on the directory page first. An already installed plugin opens its settings.

If an agent cannot find a pstack or gstack skill, check that the package is turned on for its chat. Ask the agent to read that package with plugin_guide; the catalog lists the skills included in your installed version.

Under Turned on for, choose the chats that can use the plugin. An Off preference in a workspace overrides its repository, and Pause everywhere takes priority over every scope. Resume previous settings restores the saved choices.

A command can also require a workspace, full chat access, a supported platform, a configuration value or a key. Use the displayed reason to choose the appropriate chat or provide the missing value. Installing a package does not change a chat’s permissions.

Enter or replace the key under Keys on the plugin page. Keep it out of chat messages. Choose a key for the provider configured by the package. A provider rejection may require you to check that account’s key, access or balance; saving a key does not prove the provider will accept it.

The Version section identifies candidate configuration that is missing or invalid, required keys and package diagnostics. Complete the candidate’s settings or correct the source package. The installed revision remains available until the reviewed candidate can activate.

Ask the agent to report the existing command’s status. Farero keeps the accepted action and reconciles it with the runtime. A lost response is not evidence that the command failed, especially when it could have made a paid request.

While an outcome is uncertain, avoid asking for another paid action just to discover what happened. Farero observes the original action without repeating it. If the provider’s outcome cannot be established, that uncertainty remains part of the result.

Removal is unavailable while a running command or active Workflow uses the plugin. Farero names the work that still needs it. Once that work finishes, the plugin can be removed. Files produced in your workspaces remain.

Review the diagnostic named by validation or installation. The package may contain an unsafe path, a link, a missing executable or a malformed declaration. Fix the authoring folder and validate again. For downloaded archives, check that the URL and digest describe the same artifact.

farero plugins validate ./my-plugin --json

init, validate and pack operate on local files and can run without the app. Commands that inspect or change installed plugins need the running Farero app. If the CLI reports an accepted operation, the app continues it after the terminal stops waiting.

Automation can read that operation’s existing receipt without repeating the action:

farero plugins inspect --operation <operation-id> --json