README files
The first thing a developer reads in a project. Indexed as a primary source so quickstart and install instructions land in answers.
Connect a GitLab project once and Biel turns READMEs, docs folders, and code into source-cited answers for your customers and your team. gitlab.com or self-managed. Auto-sync via CI/CD.
Used by teams that take their documentation seriously
The first thing a developer reads in a project. Indexed as a primary source so quickstart and install instructions land in answers.
Markdown, MyST, reStructuredText. Whatever lives in your docs folder, indexed at the file level so citations link to the right anchor.
Any file in the repo can be indexed: docstrings, code comments, JSON schemas, even raw source. Configure include / exclude patterns per project.
If your project publishes a docs site to *.gitlab.io or a custom domain, point Biel at the live URL and it crawls the rendered HTML β Jekyll, Hugo, MkDocs, any builder.
read_repository scope. Biel reads the default branch and crawls files matching your include patterns..gitlab-ci.yml job that calls the sync API when docs change, scoped with rules:changes so unrelated commits donβt trigger crawls. Or run it manually from the dashboard.read_repository scope and Biel.ai connects to gitlab.com or any self-managed instance reachable from the public internet. Air-gapped instances can use the deploy upload path instead..gitlab-ci.yml job that calls the sync API on push. Use rules:changes to scope to docs/** so unrelated commits do not trigger crawls..gitlab-ci.yml.