Your computers. One shared model.

Lumabri connects your computers into a private household cluster using Colibri. Choose a model, select the computers that may help, and ask their owners to approve the allocation. The interface and runtime are written in C.

Start here

Build from source with a compatible Colibri checkout:

make ENGINE=/path/to/colibri/c
./lumabri

After launch, use arrow keys and Enter. Press / for workspace actions and Esc to go back. Use a terminal at least 60 columns by 28 rows.

1. On one computer, open / → /create. Keep Lumabri running.
2. On your other computers, open / → /join. Select the household found on your LAN, compare its identity with /create on the owner computer, then enter the household key. Manual address entry remains available. Only share that key with your household.
3. Open /settings to set the maximum RAM you offer. Choose Share resources on each computer that may participate.
4. On the requesting computer, set /settings to the folder containing your existing Colibri model directories.
5. Open Your computers. Press Enter to select donors; none is selected automatically. Tab switches to Models.
6. Choose a model and review its plan. Enter requests approval from the participating donors. Chat starts only after all approve and the complete chain is ready.

The creating computer saves its key and restarts its household when Lumabri reopens. The tracker uses TCP 47300, household services use TCP 47301–47315, and LAN discovery uses UDP 47300. Restarting does not require opening another random port. If the fixed range is occupied, Lumabri reports the conflict instead of silently choosing ports outside it.

The computers still need direct LAN connectivity. On Windows with mirrored WSL networking, open /network on the Windows computer: after your explicit approval and the Windows administrator prompt, it allows only those ports from the detected private subnet. The firewall stays enabled. The same action can remove Lumabri's rules. Keep the tools folder beside the built binary. Other systems use their normal firewall permissions. Guest Wi-Fi isolation, VPN routing and WSL NAT mode can still prevent direct discovery or connections; the helper does not reconfigure those networks. If your LAN address changes, use /join to rediscover the household rather than guessing an address.

For an advanced multi-interface setup (for example, a VPN or Tailscale), start the household owner with LUMABRI_ADVERTISE=100.101.102.103 ./lumabri, replacing the example with that computer's reachable IPv4 address. Use the same override on later starts; Lumabri saves the announced tracker endpoint in home.conf. Join that exact endpoint on the other computers. The value is an IPv4 address without a port, not a hostname. This does not configure VPNs or firewall rules. An address mismatch is rejected explicitly; it does not bypass household authentication or donor approval. Reopened TUIs restore their saved household key.

Apple Terminal uses a compatible 256-colour palette with a contrasting selection background. Other terminals use detected colour support. For diagnostics, LUMABRI_COLOR=16, 256, truecolor or none overrides detection; NO_COLOR=1 disables the canvas colours. Normal use needs no colour command.

A plan before a download

The catalogue reads the model folders and the household inventory. It shows offered RAM, detected hardware, placement and missing resources. Not calibrated means there is no matching speed measurement—not zero speed. A detected GPU is not a promise that this execution path uses it.

For an optional short measurement, select your computers and model, open / actions → /calibrate, then review and confirm. Donors still approve the plan. Lumabri generates at most 8 test tokens, with a 20-second inference limit, saves the observed speed and releases the plan. Transferring and loading missing weights happens first and can take much longer. This is a short-run indication, not a guarantee for long conversations.

Each participating computer currently admits one CPU, resident Segment plan with verified model sizing and source weights on the requesting computer. It distributes contiguous layer ranges, not isolated experts. Each donor keeps the state for its layers; the chosen chat host receives the conversation text. The chat connection itself does not mount or download a checkpoint. Separate donor groups can run independent chats at the same time, provided each group can hold its model. An occupied computer returns BUSY; it does not replace its existing request or chat. Sharing one donor between sessions and automatic recovery after a donor failure are not implemented yet.

The donor queries its installed Segment runtime before sharing. A runtime built without OpenMP uses one execution thread; CPU core count is not a promise of engine parallelism. The default system RAM reserve is one quarter of physical RAM, bounded to 1–4 GiB (2 GiB on an 8 GiB computer). The sharing limit is an additional cap, not permission to consume the system reserve.

Adding computers can make a model fit when it would not fit on one machine. It does not automatically make each chat faster.

Sharing is your decision

A request shows the model, layer range, RAM budget, disk headroom and whether the computer also hosts chat. Decline is selected initially. Move to Accept and press Enter only when you agree.

No model is loaded until every participating donor accepts. Rejection or cancellation releases the plan. Esc stops sharing; closing chat releases its allocations.

Inside chat, your messages and the streamed answers stay in the transcript. Type / for command suggestions, use arrows to choose and Tab to complete. /help, /debug, /reset and /quit provide help, diagnostics, a new conversation and exit.

Household chat also shows the approved layer allocation. /plan displays each compute donor, its layer range, reserved RAM and the Edge/chat host. /experts queries activity on the same household tracker. Serving checkpoint files is not the same as executing model layers; a chat process runs no layers, even when a separate approved donor runs on that computer. The allocation is a READY-time snapshot, not a live utilization or speed measurement.

What has actually been checked?

• Linux-environment build with warnings treated as errors.
• A real encrypted tracker, two donor TUIs, Colibri Segment engines and hosted generation using a tiny synthetic OLMoE checkpoint on loopback.
• Arrow/Enter navigation, all-party approval, rejection, slash completion, terminal restoration and resource release.
• The images above are frames from that integration test, not performance claims for a large model or a multi-computer LAN.

Native macOS Intel and Apple Silicon CI covers the real Tiny household flow. A user-operated Windows/WSL-to-macOS 12.6 Intel trial also completed two Tiny responses with all model computation on the Mac and source weights on the PC. This is a smoke test, not a performance or large-model certification.

Not yet certified: general physical-LAN reliability, native Windows, GPU household execution, all model families, multi-session household use, or transparent recovery after losing a donor. WSL testing is not native Windows certification.

Adapter registration is broader than tested household execution. A checkpoint appearing in the catalogue does not make its sizing or backend supported. There are no promised tok/s or automatic “best model” recommendations.

Native runtime build

Build the complete runtime with make household ENGINE=/path/to/colibri/c. Building only lumabri does not install the model services. macOS builds use Homebrew libomp when available and work single-threaded without it. Changing OpenMP flags invalidates the generated engine build automatically. CI pins Colibri to 12a5c464b5c1f8292d578c62458706bc32d6ac95 for reproducibility.

Discovery and outbound reporting do not prove inbound connectivity. Before indexing, Lumabri checks each selected donor's address and identity. Keep the household owner's window open; it owns the tracker. Allow the installed lumabri and segment_node executables through the donor's application firewall rather than disabling the firewall. Rebuilding an unsigned executable may require reviewing its application permission again.

Development and diagnostics

make test ENGINE=/path/to/colibri/c
python3 tests/integration/home_flow_test.py --models-dir /path/to/tiny-model-folder

The second command starts a loopback integration test with real engines; it requires a compatible small OLMoE checkpoint. Normal household use stays in the TUI.

See repository layout, Segment engineering and release checks for developer details. Expert/Hybrid, public-network protocols and advanced CLI tools remain available for development; they are not extra steps in the household interface.