Libraries and sharing
A Library (shown in Studio as a Resource Store) holds one type of resource: agents, workflows, data connectors, execution environments or knowledge graphs. A Contributor shares one version of a resource into it; Readers and Contributors download a copy into their own deployment. An Organisation administrator manages Libraries and their members (Libraries).
Share a resource
- Open the resource's page and click Share. A workflow's Share is disabled until it has an active version; environments have no versions.
- In Share to a Resource Store ("Share "name" into a resource store you contribute to"; no admin review, your access is checked automatically), choose the Version (the active one is preselected, else the newest) and the Resource store (only Libraries you contribute to for this type).
- A workflow shows how many agents, connectors, environments and knowledge graphs it uses and a checkbox: ticked, "Agents, connectors, environments and knowledge graphs travel with this workflow"; unticked, "Share the workflow only - the recipient wires each step to their own agents".
- An AWS connector shows a notice: the copy lands complete, but the recipient's account must be added to the role's trust policy before it can connect.
- Click Share: "Share request sent to store."; the status appears under Shared to within a minute. Close.
The Shared to strip under the header lists requests newest first: Pending ("Shared to library · v2"), Accepted ("… · accepted as library v5 · date"; sharing the same resource again becomes library v6, v7 under the same item) or Rejected ("rejected: reason", or "rejected: no reason was recorded"). It refreshes every 15 seconds while a request is pending.
Download a copy
- Open Libraries from the dock; the left sidebar offers Resource Stores and My Pulls. The stores list shows Name, Type and Your role (contributor or reader); search with Search by resource store name…; click a row or Browse.
- The items screen lists what was shared, with columns per type (agents: Agent type; workflows: Nodes and Agent nodes, plus "Travels with 3 agents · 1 knowledge graph · 1 connector" and "Arrives ready to activate"; connectors: Connector type; environments: Digest; graphs: Nodes and Edges), Latest version ("v5 · from deployment v2": the Library version, then the source's own) and who pushed it, when.
-
Click Download vN. For an environment, Download environment offers Provision now (ticked by default: "build and start the runtime image immediately after the copy lands. Leave unchecked to provision later from the Environments screen."). The button reads Requesting… then Requested, and a banner reads "Download requested for "name"." and "It usually lands within a few minutes; a workflow with its dependencies can take longer." with an Open Agents (Workflows, Data Connectors, Environments or Knowledge Graphs) button.
-
Version history on a row opens a panel with one row per Library version ("v5 · latest", "· your copy" on the one you hold), who pushed it and when, and a download button per version; Close version history hides it ("No version history is available yet for this item." when empty).
-
When you already hold a copy and the Library has a newer version, the button reads Update my copy to vN (disabled as Up to date, "Your copy already has vN", when current). For an environment it asks "Replace the image of name with digest sha256:… and re-provision? Agents using it pick up the new image on their next run."; confirm with Update my copy. It is offered only for a copy pulled from this same item; anything else gets a second copy.
-
Follow requests under My Pulls (Type, Name, Version, Status):
Status What you see Pending Waiting to be processed. In flight A phase such as Exporting 3/12 pages or Pulling agents, with "Pulling 5 dependencies · 3 mapped · 1 pulled · 1 waiting" and one line per dependency ("Agent · name · v3 → local v1") marked mapped, pulled, waiting, failed, pending, running or unknown. Done The Name becomes Open your copy; a workflow adds "Ready to activate" or "N dependencies need attention - open the copy to wire them." Rejected The reason, word for word. Rows for the same item and version collapse into one tagged "n attempts"; the table refreshes every 15 seconds while anything is in flight.
What travels and what lands
Studio writes only a request. Organisations checks your membership, reads the resource from your deployment and catalogues a small, non-secret description; the body moves at download time straight from your deployment to the recipient's, usually within a few minutes; a workflow bundle with its dependencies takes longer (about seven minutes in our testing). Every copy carries a Provenance line: "Pulled from deployment · library vN · date".
| Type | Catalogued (never the secret) | Your copy after Download | Update my copy |
|---|---|---|---|
| Agent | Name, type, description, the version and its dependencies with versions; never the prompt or model settings | A new agent whose connectors, environment and graph are mapped to copies you hold or pulled alongside; active when everything landed, otherwise inactive with a reason naming what did not land | A new version with its pins rewired; activated when everything landed |
| Workflow | The graph, each step's agent version and pins, and the dependency list when ticked | A new workflow, Draft · ready to activate, each step wired to the pulled agents, connectors, environments and graphs, which land Active; a knowledge-graph update step points at your copy of its graph; Needs attention (hover for the dependency) when one did not land | A new draft version; the version you had activated keeps running until you activate the new one in Workflow Versions |
| Data connector | Type, name, endpoint host, authentication type, status, header count | A new connector with the credential copied from the sharing deployment's secret store into yours during the download; run Test connection before relying on it; an AWS copy (role ARN and External ID carried as they are) connects only after your account is added to the trust policy | A new version; the credential is copied again |
| Execution environment | The row and the image reference | A new environment; a custom image is copied by digest into your registry and, with Provision now, built and started; a prebuilt image travels by name | The image replaced by digest and re-provisioned; agents pick it up on their next run |
| Knowledge graph | A pointer to the version with its node and edge counts | A new graph with the pulled version imported as its first | A new version imported; agents keep their pin until moved (use, move agents, delete) |
Notes
- Contributors only, re-checked when the request is processed ("not a contributor on this Library" means your membership was removed or is Reader). You pull into the deployment you are signed in to; in a governed deployment the copy lands for everyone assigned.
- A deleted source shows "No longer available" with the deployment and date and disables Download; a version with no number cannot be requested ("This version has no number recorded, so it cannot be requested"); older Organisations releases hide Update my copy.
- "You don't have Contributor access to any type library yet. Ask an Organisation admin to add you to one." and "You aren't a member of any resource store yet": ask your administrator. "Failed to request this download", "Failed to load this resource store's items" or an error line in the strip: reload and retry.
- A workflow copy Needs attention: point that step at a local agent or pull the missing item, save a version and activate. A knowledge-graph update step whose graph did not travel reads "node
<slug>: knowledge graph<id>did not land (<why>) - pick a local knowledge graph on the node before activating"; an item shared by an older Organisations release lands this way until shared again from the source. An inactive agent copy: wire the named dependency in Configure and activate. A connector copy needing attention: the credential was gone from the sharing deployment; enter it and Test connection.