Lumbridge Workspace
Gated · opens on November 13, 2026Lumbridge Mods is the set of mods, layouts and key bindings we run on top of the App: fleet health, a factories board, tabs inside panes, a notes panel and more. It is also a working method for building mods with several agents in parallel. Teams use it as a starting point for their own.
Tour
Layouts
The Terminals layout has no sidebar. One mod draws the tab bar across the top. Another draws a small header on each pane.
Pane tabs
An agent, a test run and a diff as tabs of one pane. Shown in both themes.
01 · What it does
A sidebar panel with one row per machine: load, memory, disk, service dots and alerts grouped by name. Click a machine for details and actions. It reads the lumbridge-fleet feeder, which queries Prometheus and Alertmanager.
The lumbridge-tabs layout gives every pane its own tab strip. Add a shell or pick an agent from a menu, rename a tab with a double-click, and move between tabs with keys.
One board shows every factory: busy slots and workflows grouped by what needs a person, what is stuck, running or done. Another lists CI runs, failing first. Both are read-only.
Star a terminal and it moves to a Favorites space; unstar it and it goes home. The right-click menu adds Move to. After a reboot, the restore mod offers to put each pane’s Claude Code session back, using labels set by a hook.
One key opens a fuzzy list of your own actions, such as a machine’s journal or failed units. The notebook panel lists a folder of Markdown notes and opens one in lumbridge-notes in a split.
Scripts scaffold a mod, check it, install it on this screen or another, and merge a wave of builder branches. Written rules keep parallel builders out of each other’s folders.
02 · How it works
There is no build step. A mod is a folder with main.js and mod.json, and the App runs it.
Every mod is named lumbridge-something and never shadows a mod the App ships. The App refuses imports from outside a mod’s folder, so shared helpers live in one kit file that a script copies into each mod; the check fails on a stale copy.
Our layout is generated from the App’s shipped layout by a script, so it picks up changes when the App updates. Key bindings and menu entries are merged into your own files: added where free, conflicts reported, a backup kept.
Mods read files and run commands with the App’s API, on this computer or on a connected machine. Panels poll gently, every 15 seconds for live health and slower for the rest, and keep the last good data when a machine is offline.
Mods that look at factories, CI, services or alerts only read. Anything that changes a machine needs its own spec section and a confirm dialog before it ships.
03 · Use it
Run these from a checkout of the repo, with lumbridge-app on your PATH.
scripts/new-mod.sh standup "Standup"
scripts/check.sh lumbridge-standup
scripts/install.sh lumbridge-standup
lumbridge-app do mod.open --name lumbridge-standup
lumbridge-app status
scripts/shot.sh standup
scripts/install.sh
scripts/install.sh --host desk
lumbridge-app do layout.switch --name lumbridge
scripts/ci.sh
04 · Docs
These pages are in the repository and open with it. Until then, the Guide covers the same ground and is readable now.
Check, install and switch to the layout, and how to undo it.
Naming, one owner per folder, copies not symlinks, read-only by default, gentle polling, no secrets.
The skill an agent follows: orient, scaffold, build against the spec, check, look at it live.
One spec per mod with its status, data sources, interface and done-when.
How a wave runs: one spec per builder, one worktree each, one integrator who merges.
A numbered list of things that went wrong while building mods, with the fix for each.
What check.sh and ci.sh verify, and the logic tests that run without a window.
Read the Guide chapter: The workspaceRequest access to the repository
05 · Works with
Not yet
Questions
No. The App ships its own layouts and mods for spaces, agents, tabs, files and menus. This repo adds ours on top and shows how to write your own.
JavaScript that describes native interface elements. There is no HTML, CSS or web view. The App writes type files for its API on every start, and those are the reference.
The repo has no telemetry. A mod can fetch URLs and run programs, so each one talks to what its code names: your monitoring, your code host, your machines. Read a mod before you install it.
Agents build the mods. The repo carries the rules and a skill file, lumbridge-app check verifies a mod without a window, and every click path is also a command, so an agent can drive it with lumbridge-app do.
Apache-2.0, the same as the App. The repository is private today and opens on November 13, 2026.
Self-host it, or talk to us about setting it up with you.