A tool stores a reusable workflow. A deployment places that tool on the Tools page, Power Strip, Ribbon, or a project folder.
The same tool can have several deployments. Each deployment can have its own name, context, settings, AI model, and triggers.
Add a Tool to the Tools Page
- Open the project that should own the deployment.
- Open the Tools page.
- Select Add from Library.
- Choose a saved tool, an existing deployment, or an automation.
- Confirm the deployment action.
Selecting a saved tool creates a new deployment. Selecting an existing deployment copies its configuration onto the Tools page. To copy a deployment owned by another project, open that source project first.
The Project | Global switch changes only what you can see. It does not change the destination: Add from Library always creates the new placement in the open project.
Use + New Tool when the workflow does not exist yet. After creating it, return to Add from Library to place it on the Tools page.
Find a Deployment
Project view shows deployments from the open project. Global view shows deployments from every project.
Use the Deployed to filters to show Tools page, Power strip, Ribbon, or Project folder placements. In Project view, the magnifying glass searches indexed deployments by purpose.
Deployment-Owned Configuration
Tool settings on a selected deployment changes that deployment only. This includes instructions, execution preferences, Python configuration, connected-service fields, and other settings contributed by the tool.
Changing one deployment does not change another deployment of the same tool. A reusable tool definition supplies defaults when a new deployment is created, but each placement owns its settings after that.
Change model also belongs to the selected deployment. Use Default Profile follows the application's active AI profile. Clear it to choose a provider and model override for this deployment without changing the global default or another deployment.
Manage a Deployment
Open More on the selected Tool to manage that deployment or one of its placements.
Rename
Rename changes the deployment name. It does not rename the reusable Tool definition or another deployment of that Tool.
Duplicate
Duplicate creates an independent Tools-page deployment with a (Copy) suffix. The copy keeps the source settings, instructions, context, and AI route. Copied triggers start paused so the copy does not immediately run on the same schedule or folder watch.
Copy to Tools
Copy to Tools appears for a placement on another interface. It creates an independent copy on the Tools page.
Pin and Unpin from Ribbon
Pin to Ribbon creates a Ribbon placement from the selected deployment. Unpin from Ribbon removes that Ribbon placement. Neither action deletes the reusable Tool.
Open in a Separate Window
Open in separate window opens the selected deployment in the normal runner with its saved settings and context.
View the Tool Definition
View tool definition shows the reusable workflow behind the selected deployment. Viewing the definition does not change the deployment.
Remove a Placement
Remove from Tools or Remove from removes only that placement. It does not delete the reusable Tool or its other deployments. Removing a deployment also removes triggers that belong to that deployment.
Inspect Deployment Details
Expand Details in the selected Tool inspector to see where the deployment is available and the identifiers and metadata used for inspection or troubleshooting. Depending on the Tool, this can include the deployment ID, Tool ID, category, memory and logging state, and tags.
Details are read-only information. Expanding the section does not change the deployment, and the displayed tags describe the Tool rather than editing project document tags.
Deployment Context
Each deployment can save:
- Documents or folders — primary input.
- Optional guidance — secondary reference entries. The current beta stores these but does not read their content.
- Save New Files To — the destination used by tools that support a configurable output folder.
Different deployments of the same tool can use different context.
Schedules and Folder Watches
A deployment can have multiple schedule and file-watch triggers. Triggers belong to that deployment and use its settings, context, and AI route.
Copied triggers begin paused. Review them before resuming the copy.
Other Surfaces
- A Power Strip Agent command owns its placement.
- A Ribbon pin owns its placement.
- Project Navigator, Power Strip Folder panels, and linked Mind Map nodes can share one project-folder placement.
Changes to one placement do not alter independent placements on other surfaces.
Automation Deployments
An automation placement contains its own copies of the connected tools. Renaming, duplicating, configuring, or removing that placement does not change the original automation canvas or another automation deployment.