Clone Shared Task
Clone a shared task into a specified project.
This endpoint allows authenticated users to clone a shared task into their own project. The cloned task will:
- Copy all task settings (name, description, configuration)
- Copy only the shared revision (not all revisions)
- Automatically resolve name conflicts by appending (2), (3), etc.
- Set cloned_from_task_revision_id to maintain a link to the original
- Be set as active with 100% weight
MCP-backed Task revisions are cloned by reusing a compatible target-project MCP server or copying non-secret MCP server/tool metadata. MCP credentials and auth_config are never copied. Direct Task clone rejects auth-required MCP dependencies with 422 until this response model can represent setup-required clones.
Requires create_task permission on the target project.
Authentication
API key or access token, sent as Authorization: Bearer <token>. The simplest option: create an API key in your dashboard under Settings, then paste it here.
API key or access token, sent as Authorization: Bearer <token>. The simplest option: create an API key in your dashboard under Settings, then paste it here.
Path parameters
Response
When true the Task is active and callable. false denotes the Task is not yet operational.
When true the Task is public and can be accessed by any User.
When true the Task is accessible to agents through the unauthenticated agent endpoint.
Controls who can view all task runs. ‘owner_only’ - only task owners see all runs (default), ‘editors_and_owners’ - task editors and owners see all runs, ‘all_viewers’ - all users with view permission see all runs.
Each update to a Task results in a new Revision being created. Task Revisions are a powerful concept that can be used to assist with A/B testing, comparing responses from different LLM’s, etc.