> ## Documentation Index > Fetch the complete documentation index at: https://docs.overcut.ai/llms.txt > Use this file to discover all available pages before exploring further. # Workspace Library > Share agents, MCP servers, skills, and secrets across every project, and install workflow and orchestration templates as project-owned copies. Every workspace has one **Workspace Library**: a shared place for the agents, MCP servers, skills, and secrets that more than one project needs, and for the workflow and orchestration templates that projects install. Projects attach Library resources by reference, so a change in the Library reaches every project at once. Templates are copied, so each project owns what it installs. Open the Library from the sidebar project picker. It sits below the project list, next to **New project**. Inside, the sidebar shows **MCP Servers**, **Skills**, **Agent Roles**, **Workflow Templates**, **Orchestration Templates**, and **Vault**. The Library is not a project. Nothing runs there: it has no Playground, no runs, no repositories, no channels, no context parameters, and no team access of its own. It cannot be deleted, only renamed or recolored, and it does not count toward your project limit. The typical path is to promote a resource from the project that built it, attach it from the projects that need it, and install templates into the projects that will run them. ## Shared by reference or installed as a copy | Library resource | How a project uses it | After reuse | | ---------------------- | ----------------------------------------------------- | ------------------------------------------------------------- | | Agent | Select it in an Agent Run or Agent Session step | Stays in the Library; edits apply everywhere it runs | | MCP server | Attach it to a project agent | Stays in the Library; edits apply to every agent that uses it | | Skill | Attach it to a project agent | Stays in the Library | | Secret | Attach it to a project agent, MCP server, or workflow | Stays in the Library; the value is never copied | | Workflow template | **Install from Library** | An independent, project-owned draft | | Orchestration template | **Install from Library** | An independent, project-owned draft | A Library resource can depend only on other Library resources. A Library agent attaches Library MCP servers, skills, and secrets; a Library MCP server uses Library secrets. Project resources can mix both: a project agent can use a Library MCP server alongside a project one. ## Use a Library resource from a project Library resources do not appear in a project's own **MCP Servers**, **Skills**, or **Project Vault** lists. Those pages show what the project owns. Library resources appear where you attach them: * In an agent's **Add MCP Server**, **Add Skill**, and **Add Secret** dialogs, Library items carry a **Library** badge. Attached Library items show the same badge in the agent's panels. * In a workflow's **Secrets** panel and an MCP server's secrets picker, Library secrets carry the **Library** badge. * In the agent picker of an Agent Run or Agent Session step, agents are grouped under **Project** and **Workspace library**. To edit a Library resource, switch to the Workspace Library. Attached items in a project are read-only there. ## Promote a resource Promotion moves a project-owned MCP server, skill, secret, or agent into the Workspace Library. It is a move, not a copy: the resource keeps its identity, every existing link keeps working, and there is no way to move it back. Workflows and orchestrations are not promoted; author templates in the Library directly. Select **Promote to library** on the MCP server, skill, or agent page, or on the secret's row in **Project Vault**. A dialog titled `Promote '' to the workspace library?` explains what changes: * **MCP server**: every project can attach it, it is edited from the Library after promotion, and its linked secrets must already be Library secrets. * **Skill**: every project can attach it, and it is edited from the Library after promotion. * **Agent**: every project can run it in workflows, it is edited from the Library after promotion, and its MCP servers, skills, and secrets must already be Library items. * **Secret**: every project can link it, and it is edited from the Library Vault after promotion. If the secret is available for all executions, the dialog also warns that it will be injected into every run in the workspace. Confirm with **Promote**. Overcut opens the resource at its new location in the Library, or, for a secret, shows **Secret promoted to the workspace library**. Promote dependencies first, from the bottom up: Promote the secrets that the MCP server or agent links. No value re-entry is needed. Promote MCP servers once their secrets are in the Library. Otherwise promotion stops with `Promote these secrets to the workspace library first: `. Promote the agent last. If it still links a project MCP server, skill, or secret, promotion stops with `Promote these to the workspace library first: `. Skills have no dependencies and can be promoted at any time. A promoted resource keeps its name, and names must be unique within the Library. If a Library MCP server, agent, or secret with the same name already exists, or a Library skill already points at the same repository path, promotion stops and names the conflict. ## Library Vault and shared secrets The Library's **Vault** page is titled **Library Vault**. Secrets there work like project secrets: encrypted, never shown to the model, and injected as environment variables. Two things differ: * **Reach.** A Library secret can be linked by agents, MCP servers, and workflows in every project. A Library secret with **Available for All Executions** turned on is injected into every run in the workspace, and its tag reads **Available for All Executions in All Projects**. * **Precedence.** A project secret with the same name as a Library secret wins in that project's runs. The project secret's row shows **Overrides the library value in this project's runs**. Use this when one project needs its own credential for a shared MCP server. At run time Overcut collects secrets from both the project and the Library: secrets available for all executions, secrets linked to the workflow, secrets linked to each agent in the step, and secrets linked to those agents' MCP servers. See [Vault](/docs/reference/vault) for creating, assigning, and referencing secrets. Promoting a secret that is available for all executions expands it from every run in one project to every run in the workspace. Restrict it first if that is not what you want. ## Author a Library template A template is a workflow or orchestration created inside the Workspace Library, in the same builder you use in a project. The **Workflow Templates** page notes that templates never run, and the **Orchestration Templates** page has no active state. Each template has **Builder** and **History** tabs only. You can start a template from a Playbook: **Add from Playbook** works inside the Library and adds the Playbook as an inactive template. Publish the template before anyone installs it. Installing copies the last committed version, never the draft, and the install pickers list only templates with a committed version. ## Install a workflow template In a project, open **Workflows** and select **Install from Library**. The **Workflow Templates** dialog lists every committed template. The **Install Workflow Template** dialog prefills the **Workflow Name** from the template. Map each project-owned agent the template references to an agent this project can use. Agents that live in the Library need no mapping. Select **Install**. Overcut confirms with **Template installed as a draft workflow!** and offers **Open Workflow**. Review agents, conditions, and repository references, then publish the workflow. The copy belongs to the project. Later changes to the template do not reach it, and changes to the copy do not reach the template. If the template references a context parameter, that parameter must be a workspace parameter, or publishing the copy fails until you define it. See [Context Parameters](/docs/reference/context-parameters#lifecycle-and-governance). For a JSON file instead of a Library template, see [Import & Export Workflows](/docs/workflows/workflow-import-export). ## Install an orchestration template In a project, open **Orchestrations** and select **Install from Library**. The **Orchestration Templates** dialog lists every committed template. In the **Install Orchestration Template** dialog, set the **Orchestration Name**, then map each workflow the template references. Choose an existing workflow in this project, or select **Install a copy** to install the template's workflow into the project and use it here. Every row needs a mapping. Select **Install**. Overcut confirms with **Template installed as a draft orchestration!** and offers **Open Orchestration**. The copy is an inactive draft. Review the mapped workflows, triggers, gates, and limits, then publish and activate it. See the [Orchestration Builder](/docs/orchestrations/builder) for the publish and activation flow. ## Delete safeguards A Library MCP server, skill, secret, or agent cannot be deleted while something still uses it. The delete fails with a message in this form: ```text theme={"dark"} Cannot delete agent 'Reviewer': it is still used by workflow "PR Review" in project "Web". Detach it there first. ``` Usage means an agent linking the MCP server or skill; an agent, MCP server, or workflow linking the secret; or a workflow in any project whose draft or committed version references the agent. Uses inside the Library count too. The message is the only list of usages, so detach or replace the references it names, then delete. Templates are never protected. Deleting a workflow or orchestration template does not affect the copies projects installed. ## Permissions Access to the Library is controlled by two workspace-level permissions on a role: viewing the Library, and editing it. Editing includes creating and changing Library resources and promoting resources into the Library. Workspace admins have both. The built-in non-admin roles can view the Library but not edit it; create a custom role to let a team maintain shared resources. Members without view access do not see the Library in the project picker and cannot install templates. If a non-admin member cannot find the Library, check that their role grants view access. ## Troubleshooting | Symptom | Cause | Fix | | --------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | **Install from Library** shows `No committed workflow templates yet` | The template has only a draft. | Publish the template in the Library, then install. | | Promotion stops with `Promote these ... first` | The resource links a project-owned secret, MCP server, or skill. | Promote the named dependencies, then retry. | | Deleting a Library resource fails with `Cannot delete ...` | A project or Library resource still references it. | Detach the references the message names, then delete. | | An installed workflow does not publish, citing an unknown context parameter | The template references a project parameter that this project cannot see. | Promote that parameter to the workspace, or define it at the workspace level. | | A workflow in the Library shows no **Run** button | Templates never run. | Install the template into a project and run the copy. | ## Chat Overcut chat can list and create Library resources, promote a project resource after you confirm, and install a template into a project you choose; the copy stays a draft until you approve publishing it. Chat can create a secret entry but never accepts its value; enter that in the **Library Vault**. Inside the Library, chat cannot run, activate, or inspect runs, because nothing runs there. See [Chat with Overcut](/docs/how-to/chat-with-overcut). ## Related * [Reuse Across Projects](/docs/concepts/reuse-across-projects): when to share, copy, or scope. * [Context Parameters](/docs/reference/context-parameters): values that differ per project, repository, workflow, orchestration, or agent. * [Vault](/docs/reference/vault): creating, assigning, and referencing secrets. * [Import & Export Workflows](/docs/workflows/workflow-import-export): JSON snapshots of a workflow. * [Multi-Project Workspaces](/docs/concepts/multi-project-workspaces): the workspace and project boundary.