Skip to main content
For the complete documentation index for agents and LLMs, see llms.txt.

Fork a Service's Pipeline into Builder

When you push a pipeline written as a Python script to the platform with the SDK, the platform creates a service for it, and the service is active right away. Your callers can use it immediately. The pipeline doesn't appear on the Pipelines page, so you can't open it in Builder yet.

To visualize the pipeline and keep working on it in Builder, fork the revision. Forking creates a new pipeline from that revision on the Pipelines page. Your service and the revision it serves stay as they are, so callers aren't affected.

Forking works for revisions that have a pipeline definition you can preview. It isn't available for revisions that run a code bundle, for example when you push a whole project directory instead of a single script.

Prerequisites​

  • You must have write permission to pipelines. Without it, the Fork button is disabled. For details, see User Roles and Permissions.

Fork a Revision​

  1. Open the service. Click Gateway in the navigation and click the service name.
  2. On Overview, in the Pipeline card, click View pipeline. To fork an earlier revision, click its View pipeline action in the Deployment history list instead.
  3. In the preview, click Fork.
  4. In the Fork this revision dialog, check the Name field. By default, the name is the service name, the revision's config hash, and the -fork suffix. For a revision published from a Builder pipeline, it's the pipeline name, the version, and -fork. You can't change the name after you create the pipeline.
  5. Optional: Edit the Tags. The pipeline gets the forked tag by default.
  6. Click Fork.

A notification confirms the fork. Click the pipeline name in it to open the new pipeline in Builder. You can also find it on the Pipelines page. If the name is already taken, the dialog asks you to choose another one.

In Builder, a notice at the top shows which service the pipeline was forked from. You can edit the pipeline, test it in the Playground, and publish it as usual. To serve your changes, publish the new version to the service. For steps, see Publish a New Pipeline Version.