Skip to content

Plugins

Plugins extend Kitly with new operations, new "Open With" targets, and extra settings. They install from repositories with a click, and a workflow you build can become one (see Workflows).

The Plugins dialog

Open the burger menu and choose Plugins.... Three tabs:

  • Installed (N): what you have.
  • Browse: what's available from your repositories.
  • Repositories: where plugins come from.

What plugins add

  • Operations. Plugin operations appear in the regular Pipelines browser. Filter to them with the provider checkbox "Local (Plugins)".
  • Open With handlers. Extra entries on the asset right-click's "Open With" menu, beyond your configured external apps.
  • Settings fields. A "Plugins" section appears in Settings when an enabled plugin declares settings of its own.

Some repositories also ship preset packs: bundles of operation presets rather than code, installed with Install Presets.

Installing

  1. Open the Browse tab. Plugins are grouped by repository.
  2. Click Install on the one you want.
  3. Check the Installed tab: each card shows the name, category, version, an "Enabled" checkbox, Update and Uninstall buttons, and the operation ids the plugin contributes.

Restart notes

Some plugin changes show a "restart recommended" note on the card. The plugin isn't fully wired in until you restart Kitly. Quit from the tray (remember, closing the window only hides it) and relaunch.

Disable a plugin by unticking "Enabled" instead of uninstalling; its operations vanish from the browser but your copy stays for later.

Repositories

A repository is a published index of plugins. Kitly seeds one by default, the official repository at https://github.com/vltmedia/Kitly---Official-Plugins.

Add more on the Repositories tab, by GitHub URL or by a direct index.json link. That's how a studio shares internal tools: publish an index, have every artist add the URL once, and updates flow through the Update button.

Install what you trust

Plugins run code on your machine. Stick to the official repository and sources you trust, the same judgment you'd apply to any DCC script or extension.

From workflow to plugin

Any workflow can be exported as a plugin folder (Export..., then Plugin folder...). The result installs like any other plugin and registers the graph as a regular operation, prompts and inputs included. Build the graph once, ship it to the whole team as a one-click tool.