Plugins

Plugins extend the app with code generators, scaffolding and integrations. Each workspace can enable a subset of the catalog, configure them, and run their actions.

Where to find them

• Header → Plugins opens the workspace plugins dialog (visible only when a workspace is selected).
• Edit workspace → Plugins toggles which plugins are enabled and exposes a ⚙ per plugin to edit its connection values.
• Settings → Plugin defaults stores app-wide defaults that are copied into new workspaces when the plugin is enabled.

Plugin types

• Setup actions — one-time scaffolding (e.g. Setup AI codegen scaffold). Shown at the top of each plugin card; the same card lets you view files or download the run after success.
• Workspace actions — full-workspace builds. Same row offers Run, View files, Download.
• Operation actions — appear in the Execute bar inside the spec view, scoped to a single operation.

Connection settings

Settings are stored as keys like plugins.<workspaceId>.<pluginId>.<field> and as plugins.global.<pluginId>.<field> for app-wide defaults. Required fields are marked; password fields show a Clear saved password option once a value is stored. Per-field ? buttons open a help dialog.

Common flow. Enable a plugin → fill in connection values via ⚙ → run Setup once → run Workspace build or per- operation actions → download the resulting files.

Plugin reference (from server)

When the backend is reachable, extended Markdown documentation for each catalog plugin may load below (sanitized HTML from GET /api/v1/plugins/documentation). If this area stays empty, the request failed or no HTML was returned for any plugin.

Extended plugin documentation loads from the server when the backend is reachable.