Templates

What this means

A template is a saved starting point for the New Pipeline form. It captures the task description, type, engine, repo, and budget cap. Picking a template prefills the form so you don't retype the same fields every time.

Templates do not run on their own. They are presets you apply to the New Pipeline form. The user can still edit any field before dispatching.

When to use it

• A task you run on a schedule, like a weekly dependency bump.
• A common bug pattern your team triages the same way.
• A frontend smoke test you re-run after every release.
• Any task with a similar shape across multiple weeks.

Before you start

• A product and at least one repository must already exist.
• Creating, editing, or deleting templates requires the admin or owner role. Developer and viewer roles can use templates but cannot manage them.
• A template locks the engine to a concrete value - Auto is not allowed. Templates created from a New Pipeline form set to Auto fall back to Claude Sonnet.

Where to find them

• Pipelines → Templates in the sidebar - the templates list, where you create, use, and delete templates.
• The Template picker bar at the top of the New Pipeline form, when at least one template exists.
• The Save as template button on the New Pipeline form - captures the current form values.

Steps

Create a template from scratch

1. Go to Pipelines → Templates.
2. Click New template (admin only).
3. Fill in the fields below.
4. Click Save template.

Save the New Pipeline form as a template

1. Open Pipelines → New and fill in the fields you want to reuse.
2. Click Save as template.
3. Give it a short name.
4. Click Save.

The button is disabled while Let Bilbis pick is on, since templates lock to a single repo.

Use a template

1. Open Pipelines → New.
2. Pick the template from the Template picker bar at the top of the form.
3. The form prefills. Adjust any field if you need to.
4. Click Dispatch pipeline.

Or open a deep link: /[orgSlug]/pipelines/new?template=<id>. The form auto-applies the template on load. The Use button on the templates list opens this URL for you.

Delete a template

1. Go to Pipelines → Templates.
2. Click the trash icon on the template's row.
3. Confirm in the dialog.

Pipelines launched from a deleted template stay intact. Only the preset is removed.

Field reference

What happens next

• The template appears in the templates list and in the Template picker on the New Pipeline form.
• Picking it prefills the form. The user can still change any field, including engine and budget.
• Dispatching from the form creates a pipeline as usual. The pipeline has no link back to the template - past pipelines are not affected by template edits or deletes.

Problems and fixes

Related pages

• Create a pipeline - every form field the template prefills.
• Budgets and dry runs - budget caps in detail.
• Pipeline states - what to expect once you dispatch.