Plugins in Faheem Code
Plugins bundle related agent capabilities, such as skills, MCP servers, hooks, commands, and agent definitions. Faheem Code gives local backends a UI for browsing the plugin catalog, installing plugins, enabling or disabling installed plugins, and attaching plugins when you start a conversation.
Open the plugins area
Open Plugins from the sidebar to manage plugins for the active backend.
From the Plugins page, you can:
- Search the plugin catalog
- Inspect plugin details
- Install a plugin from the catalog or source
- Enable or disable installed plugins
- Uninstall plugins that are managed by Faheem Code
- Confirm locally discovered plugins
Plugin management is backend-scoped. Switching backends changes which installed and local plugins you see.
Installed and local plugins
Faheem Code shows plugin status in the Plugins page:
| Status | Meaning |
|---|---|
Installed | The plugin is managed by Faheem Code and can be enabled, disabled, or uninstalled |
Available | The plugin is visible in the catalog but not installed |
Local | The plugin was discovered from a local plugin directory and is shown as read-only |
Local plugins are discovered from user-level plugin directories such as ~/.agents/plugins and ~/.faheem-code/plugins. They can load into conversations, but Faheem Code does not manage their lifecycle from the UI.
Inspect plugin contents
Select a plugin to open its details. Alongside its metadata, the detail view can show:
- Skills in this plugin bundle — cards for bundled skills, including command-derived skills, with their icons, names, and descriptions.
- Files — an expandable directory tree. Select a file to view it inline with syntax highlighting; select it again to close the viewer.
Plugin content is provided by the active backend. A backend that does not provide this data shows plugin metadata only.
Enable or disable installed plugins
Enabled installed plugins are automatically available to new conversations on that backend. Disabled plugins remain installed, but they are not loaded into new conversations.
Use this when you want to keep a plugin available without making it part of every new conversation.
Attach plugins to a new conversation
When you start a new conversation, use the Plugins picker in the chat launcher to attach catalog plugins explicitly.
Attached plugins are opt-in for that conversation. If you start another conversation without selecting plugins, Faheem Code does not attach any conversation-specific plugins.
Installed and enabled plugins may still load automatically for new conversations, depending on the active backend configuration.
View attached plugins during a conversation
When a conversation has explicitly attached plugins, open the conversation tools menu and select Show Plugins to see them.
This view lists plugins attached when the conversation was created. It is display-only and does not include every ambient or installed plugin that might also be available to the backend.
Trust and backend scope
Plugins can add instructions, tools, hooks, and external integrations. Install plugins only from sources you trust, and review what a plugin contains before enabling it.
Because plugins are managed by the active backend:
- A local backend can discover local plugin directories on that machine
- A remote backend uses its own plugin state, not your laptop's plugin directories
- Switching backends can change which plugins are installed, enabled, or local