Plugins and marketplaces

Plugins extend Claude Code and Codex with extra commands, agents, hooks, and MCP servers, and marketplaces are the catalogs you install them from. GitDB Desktop gives both CLIs one Plugins dialog: open a thread's ··· menu and choose Plugins….

Two things hold on both CLIs:

• Local threads only. Like Skills, the dialog works on local-folder threads. On a GitDB workspace thread it tells you plugins are managed from a local thread.
• The CLI makes every change, not the app. GitDB Desktop never writes a plugin file or CLI config itself. Claude Code performs its changes through its own plugin commands, and Codex through its own configuration — the same mechanisms their terminal and IDE versions use.

Claude Code pluginsCopy Anchor Link

The dialog opens showing its last reading with an "as of" time stamp, and reads nothing until you press Load (or Refresh). It has two tabs, Plugins and Marketplaces.

Install, enable, update, uninstallCopy Anchor Link

The Plugins tab lists your installed plugins and the plugins available from your marketplaces, with a search box ("Search plugins…"). Before your first marketplace it reads: "No plugins available. Add a marketplace to discover plugins."

Installing shows Claude Code's own caution first:

Make sure you trust a plugin before installing, updating, or using it. Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won't change.

Then you pick one of the three install scopes:

Each installed plugin row has an enable switch ("Enable plugin" / "Disable plugin — stays installed but will not load"), Update plugin for a newer version, and Uninstall and remove plugin. If an update fails, the dialog offers recovery actions such as Try again, Refresh list, or Refresh the marketplace and retry. When Claude Code needs an interactive confirmation for an install, the dialog shows you the exact command it wants confirmed.

Installing and updating need Claude Code 2.1.278 or newer; older CLIs get a message saying so. Running Claude Code sessions pick plugin changes up without a restart.

MarketplacesCopy Anchor Link

The Marketplaces tab adds a marketplace from a "GitHub repo, URL, or path…", and each marketplace row has Refresh marketplace and Remove marketplace. The official catalog is badged "Official Claude Code marketplace". Before any are configured it reads: "No marketplaces configured. Add one above to discover plugins."

From the composerCopy Anchor Link

Typing /plugin — or its aliases /plugins and /marketplace — and sending it opens this dialog instead of going to the CLI ("Manage Claude Code plugins").

Codex pluginsCopy Anchor Link

On a Codex thread the same dialog shows your installed plugins and the catalog from your local marketplaces, with a plain on/off toggle per plugin ("Enable plugin" / "Disable plugin") and install/uninstall. Codex needs to be connected; the dialog says so if it isn't.

One difference to know: Codex plugin changes are app-wide. Codex writes them to its own configuration and plugin cache and reloads every Codex thread on this machine — not just the one you opened the dialog from.

Add a marketplace ("Add plugin marketplace — Add from a GitHub repo, Git URL, or local folder.") takes a Source (for example openai/plugins or git@github.com:org/repo.git), an optional Git ref (for example main), and optional Sparse paths (for example plugins/codex). Marketplaces can be refreshed and removed, and if some fail to load the dialog says "Some marketplaces could not be loaded" with the details and a retry.

Codex has no /plugin composer command — open the dialog from the thread's ··· menu.