Bitloom: follow, diagnose and ship Yocto builds from a web dashboard or a terminal cockpit.

Your build stays yours.

Describe how the project builds once: the guided setup proposes the profile from the project folder. From then on builds, logs, the image explorer, SBOM checks, Studio and the migration assistant work the same, whatever runs BitBake.

A launcher script needs to forward shell -c "<command>", keep standard input open and keep the build folder on the machine. Bitloom runs next to your build, or inside your build container with bitloom.pyz: one file to mount, no image to rebuild. Where your build runs →

Your builds, one browser tab away.

bitloom --web opens the dashboard on the build service. Close the tab, open it on another machine through an SSH tunnel, or switch to the terminal: the queue, the history and the running build stay where they are.

Follow and diagnose

Live output with search and an errors-only view, progress and ETA, then a Toaster-style summary, sstate reuse, warnings, timings and a comparison with the previous run. A failed build starts with the diagnosis of its real cause.

What is in the image, and why

Browse what you built, file by file, with the package and recipe behind each one and what pulls it in, see what starts at boot, what listens on the network and where the space goes, and read the board's device tree. Which recipe installs… answers for any file; Change it opens the append, starting from the file as it is on the device.

Pick an image, press b

The target field lists the image recipes in your layers, the kas target and what is already built first. Any recipe, or several, can still be typed.

Recipes by layer

Every layer with its counts, folders that open on demand, filters for recipes, images, appends, classes and kas files, and a search that keeps the structure.

SBOM, CVEs and the CRA

SBOM quality gauges, vulnerabilities from sbom-cve-check, cve-check and Grype with Markdown, HTML, CSV, JSON and SARIF exports, release support and CRA readiness.

Studio, step by step

Pick what to create, then walk through it: every option says what it means, the preview shows where the files go and what they contain, the review lists exactly what Create will do, and the last screen offers what comes next.

Scarthgap → Wrynose, guided

Every rule of the official migration guides checked on your files, the mechanical changes applied with a diff and undo, and the new kas file written next to the old one with its own profile. The current build keeps working while you try the new one.

Write BitBake without guessing

Completion from your own layers (variables with their documentation, classes, overrides, recipes, features), and the mistakes a parse would hit shown as you type. bitloom --lint does the same in CI.

Best practices, your rules

See how far your layers follow the Yocto advice, where they do not and how to fix it. Switch rules off, change their weight, add your company's own, and fail CI with bitloom --practices.

Any project, set up in a minute

Point it at a folder: kas files, Poky checkouts and YML=… ./run_kas.sh build launcher scripts become profiles, one per product, with the build folder found for you.

Inspired by the idea of yoctui.

Bitloom is inspired by the idea behind yoctui: bringing everyday Yocto and BitBake work into a terminal interface. Thank you to 0xbadcaffe, the author of yoctui, for the inspiration and for sharing the project with the community. Bitloom has its own implementation and interface.

From a recipe to a release.

Browse metadata, queue work and inspect evidence without losing the context of your build profile.

No matching capability. Try a broader term.

A complete manual testbook.

Build and launch Bitloom, configure kas-container, create layers and recipes, develop with devtool and verify every implemented command. Each case lists prerequisites, inputs and expected evidence; optional hardware and classes are identified explicitly.

Open the testbook

Follow a change from source to image.

Sixteen connected views implement all fourteen researched workflows: variable origins, recipe and container files, rebuild signatures, task failures, IDE SDKs, image regressions, measured performance, kas/multiconfig, offline checks, CVE/SPDX, kernel and upgrade review, boards and shutdown evidence.

Preview complete licensed CMake, Meson, Make, Python or Rust fixtures, create and register a layer, clone a profile, capture a baseline and compare after rebuilding. Optional tasks are checked against the selected release. Real device operations retain job/transcript evidence; missing equipment and reports remain unavailable.

Open the Developer guide Run all fourteen experiments → Research and sources →

Install Bitloom.

Download your version from GitHub Releases. Debian and Ubuntu users can install the .deb with bundled Python dependencies; other Linux distributions and WSL2 can use the source archive or wheel. Python 3.10+ is required.

sudo apt install ./bitloom_1.2.3_all.deb
bitloom --demo

Source archive, wheel, checksum verification and removal instructions

One small profile per setup.

{
  "name": "host",
  "root": "/work/poky",
  "build_dir": "build-qemu",
  "mode": "host",
  "init_script": "oe-init-build-env"
}

Full schema and path rules: user guide · Copy-ready profiles: profile examples

Create recipes without leaving the terminal.

New file opens an editor with recipe and .bbappend templates in the selected host or container runtime. Parent directories are created, and existing files are preserved. Local metadata changes refresh every five seconds; open runtime directory listings refresh every fifteen seconds while idle.

File creation and refresh guide

Work through the problem.

Ask why. Keep the evidence.

Explain rebuild signatures, trace an image file to its recipe and packagegroup, inspect runtime preflight, compare build snapshots and export redacted reproducibility references. Review source changes before devtool finish/reset. Advisory locks coordinate cooperating cache users; unproven references never trigger automatic removal.

Read inputs, workflow details and practical limits

Fourteen themes. One workspace.

Press F7 to preview Bitloom, Soft Slate, Linen, Nord, Dracula, Tokyo Night, Catppuccin Mocha, Gruvbox, Solarized Dark, Ocean, Forest, Ember, Paper or High Contrast. Save restores the palette next session; Cancel restores your previous choice. Light and dark themes adapt tables, dialogs, logs and editor backgrounds.

Theme controls and persistence

A tour of the terminal.

These captures come from the running Textual app using its Pilot driver. They show a sample workspace, not a claimed successful image build. Click a screenshot to enlarge.

Everything, written down.

Task-oriented guides with screenshots, a generated command and keyboard reference, and the evidence of real builds. Every page has search (/), a table of contents and light and dark themes.