Components

1. Open the app, workflow, or agent.
2. Open its menu and choose Save as Component.
3. On a workflow canvas, choose Save Node as Component for the selected nodes.
4. Confirm. The new component is private and appears under My Components.

You should see a confirmation that names the component. The original app, workflow, or agent stays where it was. The component is a copy you can put in a template.

1. Open My Components.
2. Choose + Component.
3. On Details, set the name, the language, the visibility, and a short description.
4. On Code, paste the code and choose Save component.

Set visibility to Private until you want other people to find it. Public components appear in Store discovery. Languages you can store are JavaScript, SQL, TypeScript, Python, HTML, CSS, JSON, YAML, and Markdown. Install only acts on the kinds in the next section. The other languages stay as code you copy from the component page.

• Apps become a new app in the workspace. The new app is private.
• Workflows become a new workflow. It is turned off. Open it and enable it after you have read the trigger.
• Workflow nodes become a new workflow that contains those nodes. That workflow is turned off too.
• Agents become a new agent, with the prompt, tools, and settings from the component.
• SQL scripts run on the SQL connector you pick during install. They do not create a saved query.
• JavaScript (manual) stays on the result list as manual. Copy the code from the component page into the app, workflow node, or agent tool where you need it.
• Unsupported fails with Could not detect a supported snippet type. Open the component and use a kind from this list, or copy the code yourself.

On a component page, Fork component asks Create a private copy of this component? Confirm. You land in the editor of the copy. If you already own it, the button says Duplicate and does the same thing. The copy is private. Edit it, then add it to a template.