Plugins for programs
A plugin packages commands, skills, hooks, MCP servers and other parts into one unit that a run can load. A program can load a plugin for one run, or turn plugins off. This page covers the options a script uses. Writing and publishing plugins is covered in the plugins section.
The Syntic Code SDK packages are not released yet. The options on this page are the ones the syntic command supports today.
Load a plugin for one run
--plugin <name@marketplace> installs a plugin for this run before it starts, and the plugin is active for the session. Repeat it to install several. The marketplace must already be saved with syntic plugin marketplace add. --plugin-scope chooses where the install is stored: user (the default), project or local.
syntic -p "review the pull request" --plugin review-kit@my-marketplace --plugin lint-kit@my-marketplaceTo try a plugin in one session with no install, pass --plugin-dir <folder or .zip>; a folder that holds several plugins loads each one. --plugin-url <https URL> fetches a plugin .zip for the session, and falls back to the last good copy if the download fails. Both flags can be repeated.
syntic -p "review the pull request" --plugin-dir ./plugins/review-kitRun without plugins
--bare is meant to skip plugins, settings hooks, skills and memory. Confirm the exact set it skips for your version before you rely on it. A run with --bare and --mcp-config uses the MCP servers you pass:
syntic -p "summarise this file" --bareTo read only some settings files, use --setting-sources.
What a plugin brings into a run
These parts take effect in a run:
- Commands, which appear as slash commands.
- Skills.
- Hooks.
- MCP servers.
- Plugin agents, which
--agentcan name. - Language servers from
.lsp.json, which serve theLsptool and start on first use.
A plugin’s output styles are offered in the interactive app (/output-style). A print run does not pick them up, so pass a project or user style with --output-style instead.
Write paths inside the plugin relative to the plugin’s folder.
Check what loaded
The start record of a streaming run lists the tools, slash commands and MCP servers the run has. When a plugin failed to load, the record also has a plugin_errors list. The debug log written with --debug has more detail.
Limits
- Reloading a plugin without a restart is done in the app with
/reload-plugins.
Related
- Skills for programs covers the skills a plugin can bring in.
- Plugin manifest reference lists the fields of a plugin.