Create a pipeline

What this means

A pipeline is one task you hand to Bilbis. You describe the work in plain language, pick a repository, and Bilbis dispatches a team of agents to plan it, write the code, run tests, push a branch, and open a merge request.

The form on this page is the only thing you fill in. Every other moving part - the agents, CI checks, the review pass - runs on its own.

When to use it

• A small feature you can describe in a paragraph.
• A bug fix where you can point at the symptom.
• A repetitive change across one repo.
• A frontend tweak that follows an existing design.
• A test or documentation update.

If a task spans many repositories, see the Let Bilbis pick option below.

Before you start

You need all four of these in your organization, or the form will refuse to render:

• An LLM credential - Anthropic or OpenAI.
• A Git credential - GitLab or GitHub.
• A product.
• At least one repository inside that product.

Bilbis also surfaces this as the setup checklist on your dashboard. If anything is missing, the form replaces itself with the checklist and a deep link to the right page.

A Jira credential is optional. Without it, the Jira ticket field is disabled and shows a link to add one.

Steps

1. Go to Pipelines → New in the sidebar.
2. Type the task into the Task field. Be specific. Mention file paths, function names, expected behavior. The agents read this verbatim.
3. Pick a Repository, or turn on Let Bilbis pick to give the agents a shortlist.
4. Pick a Type - see the field reference below.
5. Leave Engine on Auto unless you have a reason to override it. Bilbis will recommend one based on past results for that repo and task type.
6. Set the Budget cap in dollars. The run halts if cost exceeds this.
7. Tick Dry run if you want a plan + code without a push or MR.
8. Optionally open Advanced options to add a ticket id, Jira ticket, Figma URL, branch overrides, or a queue priority.
9. Click Dispatch pipeline. You land on the pipeline detail page so you can watch it run.

Field reference

Main fields

Type values

Engine values

If a recommendation appears next to one of these options, that's the engine Bilbis suggests based on past runs for this repo and task type. You can still override it.

Advanced options

What happens next

After you click Dispatch pipeline:

1. You're redirected to the pipeline detail page.
2. The state badge cycles through routing, coding, testing, pushing, CI, and reviewing.
3. When the agents finish, the pipeline either reaches Done with an MR link, Failed, or pauses on a question (Awaiting clarification or Awaiting approval).
4. The pipeline appears in your Pipelines list and feeds the dashboard KPIs and analytics.

If you ticked Dry run, the pipeline stops after the coding step. No branch is pushed, no MR is opened.

Templates

If you find yourself filling in the same task type, repo, engine, and budget repeatedly, save the form as a template:

1. Fill in the fields you want to reuse.
2. Click Save as template.
3. Give it a short name like "Weekly dep bump" or "Frontend smoke test".

Templates lock to a concrete engine. If you saved with Auto, the template stores Claude Sonnet instead.

Apply a template later from the Template picker at the top of the form, or open the form via ?template=<id> to auto-apply.

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

Problems and fixes

Related pages

• Pipeline states - what each state badge means.
• Review results - what to do once a pipeline finishes.
• Troubleshooting - recovery for stuck or failed runs.