Use plugins

Plugins add skills, commands and reusable roles to your chats. Install a plugin from the directory, then finish its setup in Settings.

Open the plugin directory and choose Add to Farero under Jevgrep, pstack or gstack. Your browser opens the app on that package’s review screen.

Review the package and its data use, then choose Install. Farero opens the plugin’s settings, with required configuration and API keys first.

For another source, open Settings → Plugins and use Add a plugin. Folder reads a folder on the computer running Farero. GitHub needs the repository and a full commit hash. Archive needs an HTTPS URL and the archive’s SHA-256 hash. Directory accepts an entry name such as jevgrep, pstack or gstack.

Choose Review package to inspect that source. Farero copies the package into a fixed revision, so the review describes the files that installation will use.

In the plugin’s settings, choose where to use it under Turned on for.

Trust the author before running a command. Plugin commands run with your chat’s access to the host computer. The listed data destinations are the author’s declarations, not a network restriction. A package that uses a paid provider uses your account with that provider.

For Jevgrep, choose your provider under Configuration and save that provider’s API key under Keys. TypeSafe is the default; Vercel AI Gateway, OpenRouter and OpenCode Zen are also supported. Each search sends parts of your source to that provider and uses your account with it.

Open the installed plugin. Where it works shows command availability for the selected chat and gives a reason when a command cannot run. A workspace requirement, chat permissions, missing configuration or a missing key can make an installed command unavailable. A read-only chat can run only commands the package marks read-only, such as Jevgrep’s search and files. Creating the sample needs a chat that can change the workspace.

Under Configuration, save the values the package needs. Enter API keys under Keys. Farero keeps these separate from chat messages and ordinary settings and passes declared keys privately to the command. The command itself receives those keys, so the author remains part of your trust decision.

Turned on for contains a default, repository preferences and workspace preferences. A workspace preference takes priority over its repository; the repository takes priority over the default. The inherited option shows the value it inherits.

Pause everywhere stops new use while commands already running finish. Resume previous settings restores your saved scope choices. You can change those choices while paused without resuming the plugin.

Use the File summary plugin to summarize its bundled fixture with the label First try. Show the counts and the first two lines.

Example: First try
Lines: 3
Words: 6
First 2 lines:
One small example
Two words

Turn the installed package on for your workspace, then describe the task. Each chat tells the agent which plugins are on, so the agent can choose the skill; you can also ask for a skill by name. Farero supplies the package’s instructions and lets the agent read each skill and its reference files as needed. Long files arrive in pages.

Use pstack’s architect skill to compare two ways to add offline drafts. Explain the tradeoffs before changing code.

The agent reads architect and uses its method to compare the approaches. Review its assumptions and proposed design before asking it to implement a choice. You can also ask for gstack’s office-hours or review skill. Browser work requires a chat with Farero’s browser tools.

For a process with tracked participants, pick one of the package’s Workflow templates from the Workflow gallery in a new chat. pstack includes Poteto mode and Interrogate a change. gstack includes Autoplan review and Pre-landing review. Each template shows the roles it will use, and its starting text fills an empty prompt for you to edit before starting.

Packages that contain roles show them under Roles, with names such as review-panel/reviewer or jevgrep/explore. You can keep the author’s choices, choose compatible models, or bind a package role to one of your local roles. The package’s access and independence requirements still apply. A read-only role needs only commands the package marks read-only: Jevgrep’s explorer starts with a search of your repository and reports files, locations and evidence.

To run a template, open a new chat and choose Workflow, then pick the template from the gallery. The plugin’s templates appear only where the plugin is on. Review the workspace, roles and objective before starting.

Each started Workflow keeps the package revision, saved configuration and role choices it started with. Updates and later configuration changes apply to future starts. Choose a template and start it when you want to begin a Workflow.

Remove plugin deletes its installation, saved settings and keys after running commands and Workflows that use it finish. Files it created in your workspaces remain.