Sharing and cloning

Publish a read-only Task or agent revision and clone it into another Project.

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

ActionEndpoint
List Task shares across a ProjectGET …/task_share
List shares for one TaskGET …/task/{task_id}/share
Create a sharePOST …/task/{task_id}/share
Revoke a shareDELETE …/task/{task_id}/share/{share_id}
Clone into the current ProjectPOST …/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

ActionEndpoint
List agent shares across a ProjectGET …/task_agent_share
List shares for one agentGET …/task-agent/{agent_id}/share
Create a sharePOST …/task-agent/{agent_id}/share
Revoke a shareDELETE …/task-agent/{agent_id}/share/{share_id}
Clone into the current ProjectPOST …/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.

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.