Lumbridge Workspace
Gated · opens on November 13, 2026Lumbridge App is a desktop app for terminals and coding agents. You keep work in spaces, see which agents need you, and leave terminals running when you close the window. Its whole interface is files, so a person or an agent can change it.
Tour
Layouts
Drag a divider to resize. Move a pane by its grip. Collapse the sidebar or open the changes panel. Then switch the whole window to a layout of your own.
Personal layouts
Two layouts written for this demo. Switching between them does not stop a terminal: Core keeps running them.
Themes
The default layout with the changes panel open, in both themes.
01 · What it does
A space holds work on one machine, usually in one repo. Each space has tabs, and a tab splits into panes that show terminals or mod panels side by side.
The sidebar brings agents from all your spaces into one list, including workers started by another agent. Each shows as working, blocked, done or idle. Click one to see it; a worker without a pane opens in a peek over your tab.
Add an SSH machine in Settings and its spaces run their terminals there. Each machine keeps its spaces, tabs and splits in its own Core, so remote work continues when your laptop sleeps.
A layout arranges the window. Mods are small JavaScript programs that draw its panels, menus and dialogs. Save a file and the window reloads it; a broken edit keeps the last good version and reports the error.
lumbridge-app ls and status inspect the open window. lumbridge-app do runs any action in it, from making a space to splitting a pane, with named flags or one JSON object.
The App has no updater, no usage telemetry and no feedback upload. It opens no connection itself; remote terminals go through Core over SSH. Settings shows the App and Core versions.
02 · How it works
The App owns the window and nothing else. Terminals, their history and the shape of your work live in Core.
The App finds lumbridge-core on your machine and connects to it. Closing the window leaves terminals running; closing a pane or tab ends its terminals. After a reboot, kept panes get fresh shells in their last folders.
Spaces, tabs and splits are stored in a document in each machine’s Core. Every connected screen sees the same structure and live terminals, and keeps its own focus and zoom.
Which agents you have looked at and which are pinned are labels on the Core terminal. Look at an agent on one client and it stops showing as done on the others.
Settings, keys, layouts and mods are files in the app home. On every start the App writes an agent guide and API type files beside them, so an agent asked to change the window works from the current API.
03 · Use it
The same commands work from a shell, a script or an agent. lumbridge-app --skill prints the agent guide.
lumbridge-app do prints the IDs it created. lumbridge-app commands works without an open window.lumbridge-app
lumbridge-app ls
lumbridge-app status
lumbridge-app do space.new --name api --machine build-1 --folder /srv/api
lumbridge-app do tab.new --name "fix login" --argv '["claude"]' --task "Look at the login bug"
lumbridge-app do pane.split --direction right
lumbridge-app do layout.switch --name terminals
lumbridge-app commands
lumbridge-app check ~/.config/lumbridge-app/mods/my-panel
lumbridge-app shot window.png
04 · Docs
These pages are in the repository and open with it. Until then, the Guide covers the same ground and is readable now.
Build from source with Rust and Zig, then run the Linux or macOS install script.
How work is arranged, what each agent status means, and peeking at a worker.
Adding an SSH machine and what runs where.
Every window action and its arguments, generated from the App.
The guide to layouts, settings, overlays, mod code and the App API.
The keys.json format and how to rebind any command.
The seen and pinned labels that every Lumbridge client reads and writes.
What a mod can do, what stays on disk, and the local control socket.
Read the Guide chapter: The workspaceRequest access to the repository
05 · Works with
Not yet
Questions
Yes. Core, the App and the TUI began as forks of an open-source project for running coding agents, also under Apache-2.0, and we stay on that license. The project is named and linked in the credits on the Open source and Community pages. Compare says where it is ahead of us today: it is released, and we are not.
Linux and macOS, built from source. It draws with the GPU through GPUI and needs Lumbridge Core installed on the same machine.
No. The App never checks for updates, downloads anything or sends usage data. Mods are the exception: a mod you install can fetch URLs and run programs, so read it first.
An agent uses lbc to run and coordinate programs, and lumbridge-app to change what you see. lumbridge-app do goes through a local control socket in the app home.
Any program that runs in a terminal. The new-terminal menu ships entries for coding agents such as Claude Code and Codex, and you add your own in programs.json. Status shows for agents that report it.
Apache-2.0. The repository is private today and opens on November 13, 2026.
Self-host it, or talk to us about setting it up with you.