Skip to main content
Plugins ship skills, slash commands, hooks, and other agent extensions to your environment’s tasks without committing them to a repository. Niteshift uses each agent’s native plugin model, so the same configuration works locally and in tasks: Configure them at Settings → Environments → [environment] → Plugins. The panel has a tab per agent because Claude Code and Codex marketplaces use different manifests, and a plugin written for one does not load in the other.

​
Claude Code

A Claude Code plugin lives inside a marketplace: a git repo with a .claude-plugin/marketplace.json manifest listing one or more plugins. Configure two things:
  • Marketplaces: where plugins come from. Add a GitHub shorthand (owner/repo, owner/repo@ref) or a full git URL.
  • Enabled plugins: which plugins to install, identified as plugin-name@marketplace-name. The marketplace name comes from the manifest’s name field.
Niteshift pre-installs the resolved plugins in the sandbox so they’re available to the agent on task start. Private marketplaces work when the Niteshift GitHub App has access to the repository. Claude Code plugins are loaded into the agent runtime directly, so plugin skills, slash commands, and hooks are available in every Claude Code task. We automatically add the claude-plugins-official marketplace; add any others you need. If you already have plugins configured locally, drag your .claude/settings.json into the Plugins panel. Niteshift imports extraKnownMarketplaces and enabledPlugins directly.

​
Codex

Codex plugins use the same two-part configuration, installed with the Codex CLI:
  • Marketplaces: Niteshift runs codex plugin marketplace add, so Codex clones each marketplace itself. A marketplace must keep its .agents/plugins/marketplace.json at the repository root, and a private marketplace needs the Niteshift GitHub App installed on that repository.
  • Enabled plugins: Niteshift runs codex plugin add. Plugins land in the sandbox’s ~/.codex/config.toml and plugin cache exactly as a local install would, with their skills, MCP servers, and hooks available to Codex tasks.
Codex normally waits for you to trust a plugin’s hooks in its terminal UI before running them. Tasks run unattended, so Niteshift trusts the hooks of plugins you enabled here at session start. Hooks from anywhere else, such as a repository’s .codex/hooks.json, keep Codex’s default trust rules. If you already have plugins installed locally, drag your ~/.codex/config.toml into the Plugins panel. Niteshift imports the [marketplaces.*] git sources and every [plugins."name@marketplace"] entry that is not disabled.