> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.rightbrain.ai/v-1/docs/production/sharing/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.rightbrain.ai/_mcp/server. # Sharing and cloning > Create and revoke public share links, inspect shares across a Project, clone shared revisions, and handle dependencies that require setup. Share links publish a read-only snapshot of one Task or agent revision. An authenticated user can clone that revision into a Project they can create resources in. Sharing does not copy source permissions, run history, stored credentials, or secret connection configuration. ## Revision snapshots When a share request omits the revision ID, Rightbrain shares the resource's active revision. Later edits to the source create other revisions and do not change the shared snapshot. A Task share can include an existing run from the shared revision. The public view then exposes that run's input, output, files, modality, and usage metadata as the share example. ## Task shares | Action | Endpoint | | --------------------------------- | ------------------------------------------ | | List Task shares across a Project | `GET …/task_share` | | List shares for one Task | `GET …/task/{task_id}/share` | | Create a share | `POST …/task/{task_id}/share` | | Revoke a share | `DELETE …/task/{task_id}/share/{share_id}` | | Clone into the current Project | `POST …/task/clone/{short_id}` | Project-wide results are paginated and can be filtered by active status, Task ID, or partial Task name. A single Task's share list is a plain array. The clone copies only the shared revision, makes it active at full traffic weight, and resolves name conflicts. It records the source revision on the cloned Task. ## Agent shares | Action | Endpoint | | ---------------------------------- | ------------------------------------------------- | | List agent shares across a Project | `GET …/task_agent_share` | | List shares for one agent | `GET …/task-agent/{agent_id}/share` | | Create a share | `POST …/task-agent/{agent_id}/share` | | Revoke a share | `DELETE …/task-agent/{agent_id}/share/{share_id}` | | Clone into the current Project | `POST …/task-agent/clone/{short_id}` | Project-wide results are paginated. A single agent's share list is a plain array. An agent clone can copy dependent Tasks, Skills, integrations, and MCP metadata when the caller has the corresponding create permissions. The clone response includes a dependency report. When `runnable` is `false`, one or more dependencies require setup before the agent can run. Treat the dependency report as the post-clone setup contract. `ready` dependencies can run in the target Project; `setup_required`, `warning`, and `failed` entries need review. A structurally complete clone can still require model access or Connection authorization. ## Share tags Project tags can classify Task and agent shares. Use the Tags API with entity type `task_share` or `task_agent_share` to attach and remove tags. Project share responses include their tags; sanitized public share responses do not. ## Connection and collection boundaries Credentials and MCP `auth_config` are never copied. A clone can reuse compatible Connection metadata already present in the target Project or create non-secret metadata that must be authorized there. Task revisions backed by a RAG Collection cannot be shared because Collections are Project-local. An agent also cannot be shared when any attached Task revision depends on a RAG Collection, including a disabled Task attachment. ## Revocation Revoking a share sets `active` to `false` and prevents further use of its public link or clone operation. The record and view count remain available for Project management and analytics. Create another share if the revision must be published again. ## Related #### [Versioning & revisions](/docs/production/revisions) Understand the immutable revision captured by a share. #### [Tasks](/docs/concepts/tasks) Review Task revisions and RAG configuration. #### [Agents](/docs/concepts/agents) Review agent tools, Skills, and Connections. #### [Connections](/docs/concepts/connections) Authorize cloned Integration and MCP metadata in the target Project. #### [Skills](/docs/concepts/skills) Understand revision and capability dependencies. #### [API Reference: Agents](/api-reference/api-reference/agents) Read the complete agent share and clone contracts. > Build reliable AI agents that run inside your existing tools and workflows. Rightbrain developer documentation.