Syntic Code plugins
⚠️
Preview — this feature is being built; the design below is the spec.
Syntic Code can be extended with plugins: extra slash commands, hooks that run before or after edits, and MCP servers. Organizations can manage which plugins their members get from a central plugin catalog.
Policies
| Policy | Effect on members’ Syntic Code |
|---|---|
required | Installed automatically and cannot be disabled. Use for house rules, compliance hooks. |
available | Shown in /plugins for members to install if they want. |
blocked | Cannot be installed, even from a public marketplace. Already installed copies are removed at next start. |
Policies can be limited to members of particular workspaces.
Where plugins come from
- Upload a bundle (a zip with
plugin.jsonat its root) through Add a plugin. - Connect a marketplace: a Git repository with a
marketplace.jsonindex. Syntic syncs it every 6 hours and adds new plugins asavailable.
Every version is scanned before it can be served. The scan checks that executables are declared hooks, that no file is over 10 MB, and that declared MCP servers use HTTPS.
Rolling out a change
- Upload the new version. It is scanned; members do not get it until it passes.
- Pin
latest_versionto the old version while a pilot workspace tests the new one with a workspace-limited policy. - Unpin to release to everyone. Clients update at next start or within the hour.
What members see
/plugins in Syntic Code lists required plugins with a lock icon, available ones with an install button, and explains blocked ones. A blocked plugin’s commands answer “blocked by your organization” instead of failing silently.
Was this page helpful?