Plugins and permissions
Add panels, ⌘K commands and custom features to the editor with plugins: what each permission means, how installs work, and why a plugin can never change your design behind your back.
Plugins add things to the editor: a panel in the right column, commands in ⌘K, or ready-made custom features. They are installed per workspace by its owner or an admin, and everyone in the workspace gets them.
Install a plugin
Open Workspace → Plugins (or ⌘K, Plugins).
- Official plugins are examples from Solid Vibes:
- Gridfinity bin generator adds a parametric Gridfinity bin as a custom feature, and the ⌘K command Insert Gridfinity bin….
- Bolt-circle helper adds a Bolt circle panel that lays out evenly spaced holes and proposes them as one hole step.
- Install from a URL: paste the address of a plugin's
manifest.json(HTTPS). We load the plugin once, check it, and from then on serve our stored copy, so it can't change under you. A new version must use a new version number.
Before anything is installed you see a consent screen: who made it, what it adds, and exactly which permissions it asks for. You approve all of them or nothing.
Permissions
| Permission | What it allows |
|---|---|
Read the open Thing (doc:read) | See the open Thing's pieces, parameters, recipe steps and your selection. It can't send them anywhere: plugins have no network access. |
Propose changes (ops:propose) | Suggest edits. They appear as a ghost preview with Accept and Reject, exactly like the agent's proposals. Nothing changes until you accept. |
Add ⌘K commands (commands) | Put its own commands in the command palette. |
Open a panel (panel) | Show its own panel under the Plugins tab of the right column. |
Add custom features (features) | Install the custom features it comes with (they run in the feature sandbox, like your own). |
How plugins are kept safe
- Every plugin runs in a sandboxed frame with its own blank origin: it can't read your session, cookies or storage, can't touch the rest of the page, and has no network access at all.
- It talks to Solid Vibes only through a small message bridge. Every message is checked: where it came from, its size and rate, its shape, and whether you granted the permission it needs.
- Plugins never write to your Thing. They propose; you decide.
- Solid Vibes can switch a plugin off everywhere at once if a problem is reported. It then stops loading in every editor and shows as "Disabled by Solid Vibes" on the Plugins page.
Manage plugins
On Workspace → Plugins, owners and admins can switch a plugin off for the workspace or Remove it. Recipes that already use a plugin's custom feature keep building: the feature's code is stored in the step.
Use them in the editor
- Commands: press ⌘K and type the command, for example "gridfinity".
- Panels: open the Plugins tab (puzzle icon) in the right column. The Bolt-circle helper reads the active piece's size, you set the number of holes, the circle and the screw, and press Preview bolt circle. Accept the preview to add the step.
Related
Did this help?
Keep reading
For CAD pros
Writing a custom feature
Make your own parametric smart feature in TypeScript, like FeatureScript: typed parameters become a dialog, build() adds recipe steps, and it runs sandboxed in the browser and on our servers.
Pro7 min readAccount and billing
API keys
Create a key for the REST API and the TypeScript SDK, pick its scopes, keep it safe, see where it's used, and revoke it. Included from the Maker plan.
Intermediate4 min readAccount and billing
Workspaces, projects and sharing
How your work is organized (workspaces, projects, Things, pieces), how the trash works, and how to share a Thing with a link without giving away more than you mean to.
Beginner4 min read