Plugins

Plugins add local tools for tasks such as enterprise file processing, dedicated programs, and internal systems. Unlike Skills, plugins execute code, so check their sources and permissions carefully.

Install and manage

Open Settings > Extensions > Plugins:

• Installed plugins are enabled by default.
• Open an entry for its name, version, source, tools, and permissions.
• Temporarily disable with the toggle.
• Uninstall from the more menu.
• Refresh to rescan local plugins.

Local plugins usually live in:

~/.keenkind/<environment>/plugins/<plugin-id>

The interface displays readable manifest names and tool titles rather than internal routing names.

Use in chat

Enabled plugin tools are available when permitted by the current mode and permissions. Describe the goal without memorizing internal tool names:

Use the installed text plugin to process hello-keenkind and report its result.

Plugin results return to the current tool call so the model can read and summarize them.

Plugin debugging

Plugin debugging provides a limited developer view to:

• Refresh plugin status.
• View diagnostics and logs.
• Inspect registered tools.
• Restart a plugin runtime.

It does not expose the full app’s developer tools.

Safety recommendations

• Install only from trusted sources.
• Check file, network, and process permissions.
• Test first in Ask for approval mode.
• Disable plugins that repeatedly fail or request unrelated access.
• Review permission changes after updates.

See KeenKind plugin development to build a plugin and Pi extension compatibility to migrate Pi extensions.