Quickstart
Take a new Bilbis organization from empty setup to the first pipeline.
What this means
This is the shortest path to a first successful pipeline.
Use it when you are setting up Bilbis for a new organization and want to get from "nothing connected" to "Bilbis can work in a repository."
Before you start
You need:
- Owner or admin access in Bilbis.
- An Anthropic or OpenAI API key.
- A GitLab or GitHub token with access to the repository.
- A product or service you want Bilbis to work on.
- A small first task that is safe to review.
If you were invited to an existing organization, accept the invite first. If you have no organization yet, create one from the workspace picker.
Step 1: Add an LLM provider
Bilbis needs an LLM provider before agents can plan and write code.
- Open Settings -> Integrations.
- Select Add credential.
- Choose Anthropic or OpenAI.
- Add a clear label.
- Paste the API key.
- Save the credential.
See LLM providers for details.
Step 2: Connect a Git provider
Bilbis needs Git access before it can read code, push branches, and open an MR/PR.
- Open Settings -> Integrations.
- Select Add credential.
- Choose GitLab or GitHub.
- Add a clear label.
- Paste the token.
- Save the credential.
See Git providers for details.
Step 3: Create a product
A product groups repositories under shared automation settings.
- Open Products.
- Select New product.
- Enter a name.
- Review the generated product id.
- Keep the defaults unless you already know you need custom branch, label, engine, or approval settings.
- Create the product.
See Products for the field reference.
Step 4: Add a repository
A repository is the codebase Bilbis can work in.
- Open the product you just created.
- Select Add repo.
- Pick a discovered repository if available, or enter the repo path manually.
- Confirm the provider and default branch.
- Add test, lint, build, or structure hints if you know them.
- Save the repository.
See Repositories for the field reference.
Step 5: Create a first pipeline
Start with a small task that is easy to review.
Examples:
- "Add a short README section explaining local setup."
- "Add a health check endpoint that returns status ok."
- "Fix the typo in the settings empty state."
Then:
- Open Pipelines.
- Select New pipeline.
- Describe the task clearly.
- Choose the repository.
- Keep Engine set to Auto unless you have a specific reason to choose one.
- Keep the first budget modest.
- Dispatch the pipeline.
See Create a pipeline for the full guide.
What happens next
Bilbis opens the pipeline detail page. From there you can watch status, timeline events, CI results, clarifications, approvals, learnings, diffs, and diagnostics.
If the pipeline asks a question, answer it before expecting the work to continue. If the pipeline fails, open the troubleshooting page and check the state, diagnostics, and linked MR/PR.
Problems and fixes
| Problem | What to check |
|---|---|
| New pipeline form is blocked | Complete all four setup checklist items: LLM provider, Git provider, product, repository. |
| Repository picker is empty | Add a repository under Products first. |
| Git provider is missing while adding a repo | Add the matching GitLab or GitHub credential. |
| Pipeline fails immediately | Check provider credentials, repo access, and product/repo configuration. |
| First task is too broad | Try a smaller task so the first run is easy to review. |