boucle

Great ideas deserve to ship.

From a ticket in your forge to a feature in production. Boucle works so you can live. You decide at the key moments, nothing else. 👍👎

Get startedHow it works

How boucle works

boucle lives in your forge. GitHub, GitLab. No external tool, no dashboard.

  • GitLab

Drop your idea in an issue

Create an issue in your forge with a title and a description. It's just a normal ticket.

Why boucle

Harness made for human, made by an indie product builder for product builders.

Lives in your forge

A new tool to learn, a dashboard to babysit.

boucle lives in your forge (GitHub/GitLab). No external tool, no separate dashboard. Everything happens where you already work.

Deterministic and reliable

An agent that decides everything, with no human review.

Deterministic, therefore reliable. You intervene at the right moment, at the decision points.

Works while you sleep

A daemon to babysit, a laptop left on all night.

The agent works overnight for you. You intervene only when it matters.

No UI, No CLI

A new interface to learn, a command line to master.

No interface to learn, no command line to master. You interact through your forge: issues, comments, labels.

Self-healing, self-learning loop

A static tool that never improves.

A loop that learns from its mistakes, self-updates, and adapts to your codebase as your project advances.

Quick start

One command, and the loop takes over.

curl -fsSL https://raw.githubusercontent.com/ankaboot-source/boucle/main/install.sh | bash
Install boucle on this GitLab/GitHub repository. Execute these steps and report
back what you did:

1. If you are not already inside the target repository — the one whose
   origin remote points to your GitLab host — ask the user for its URL,
   clone it, and work from the clone.
2. git submodule add https://github.com/ankaboot-source/boucle .boucle
3. Run setup in non-interactive mode. It auto-detects the GitLab host and
   project from `git remote get-url origin`, so no value needs to be
   replaced: .boucle/bin/setup --non-interactive
4. Do NOT include an API key anywhere. The API key must never appear in
   this conversation. If setup tells you the key is missing, that's
   expected — it is configured manually in the GitLab UI afterwards.
5. git add .gitmodules .boucle .gitlab-ci.yml && git commit -m "chore: install boucle engine"
6. Show me the URL bin/setup printed for configuring the masked API key,
   and any next steps it listed.
Next

Create an issue in your forge and tag it boucle:triage — the loop starts.

View the docs →