Start here

Lumbridge is a set of programs you install on Ubuntu and run on your own machines. It is mostly Rust and licensed Apache-2.0. Together the parts give you terminals that stay alive, a desktop app and a terminal workspace for coding agents, notes, a library, mail, speech, a software factory, and a way to serve open models on your own GPU box. This guide walks through them in the order you would set them up.

Light

Dark

The stack in one picture

• Bare metal: machines you own or rent. A laptop or desk machine, a build server, and later a GPU box if you want your own models.
• Ubuntu: a current LTS release on each machine. Lumbridge is not a distribution. It installs into your home directory on top of the Ubuntu you already run.
• Lumbridge: Core runs the terminals on every machine. The App, the TUI and the phone app are ways to see and steer them. Notes, Library, Mail, Voice, Speak, the Factory and Computer are separate programs you add when you need them.

What you need

• A C toolchain and git, from Ubuntu’s own packages.
• Rust, installed with rustup. Core is built with Rust 1.97.1, and the TUI pins its own version in rust-toolchain.toml, which rustup fetches for you.
• Zig 0.16.0, for the terminal emulation library that Core, the App and the TUI vendor. Ubuntu does not package this version, so install it from the Zig project and put zig on your PATH.
• just, a small command runner that Core and the App use for their build recipes.

$ sudo apt update
$ sudo apt install build-essential git
$ rustc --version
$ zig version
0.16.0
$ cargo install just
$ just --version

How the release works

All twelve parts open on November 13, 2026. Each part lives in its own repository at github.com/lumbridge-corp/<repo>, for example lumbridge-core. You clone a part and build it. Until then the repositories are private, and the clone commands in this guide will fail for you.

The order of this guide

1. CoreBuild the terminal runtime and run a program that outlives your session.
2. WorkspacePut a window on it with the App, or work in a terminal with the TUI.
3. AgentsRun a coding agent, let it start another, and take over when it needs you.
4. MachinesAdd a second machine over SSH and run work there from the first.
5. WorkNotes, Library and Mail: plain files and commands that agents can call.
6. VoiceDictate and listen, with a speech model you run yourself.
7. Factory and modelsLet agents build from issues behind gates, and choose where your models run.

The next chapter builds and installs Core, starts it, and runs your first program in a terminal that keeps going after you leave.