Skip to main content
An agent built by one team is often useful to another. Visibility is how it becomes findable, and installation is how another team takes it up without taking it over.

​
Visibility levels

Visibility controls discovery. It does not transfer ownership — the agent stays owned where it was built, and only its owning workspace can change it.

​
The registry

Org-visible agents from sibling workspaces appear in the registry:

​
Installation

Installing gives you your own installation in your active workspace:
An installation runs with your workspace’s credentials, and carries its own schedule. This separation is the point. One team owns and improves the capability. Other teams operate their own instance of it, against their own systems, without forking the definition or acquiring write access to it. To remove your installation:
The original is untouched.

​
Moving and copying

Visibility and installation are for reuse across teams. Two other operations change ownership: Use move when an agent is in the wrong place — most often, when it was drafted in a personal workspace and should belong to the team that owns the work. Use copy when two teams want to evolve the same starting point in different directions. Use install when they want the same capability, kept current by its owner.

​
When to publish

Make an agent org-visible once it has earned production, not while it’s still a draft. A discoverable agent that doesn’t work costs the next team more time than it saves.

​
Sharing with one person

Visibility is organization-wide discovery. To give one person access to one agent or one run, share it by email instead. See Sharing.

​
See also