Guide · Chapter 3

  1. Chapter 1: Start here
  2. Chapter 2: Install Core
  3. Chapter 3: A workspace: the App and the TUI
  4. Chapter 4: Agents
  5. Chapter 5: A second machine
  6. Chapter 6: Notes, Library and Mail
  7. Chapter 7: Voice and Speak
  8. Chapter 8: The Factory and models

A workspace: the App and the TUI

Build the desktop App and the terminal TUI, open them for the first time, and learn spaces, tabs and agent status.

Chapter 3 of 83 min read21 commands

You need

  • Core installed and on your PATH (chapter 2)
  • For the App: a desktop session on X11 or Wayland with a working Vulkan driver
  • Access to lumbridge-app and lumbridge-tui (the TUI also pulls in lumbridge-notes)

There are two ways to look at your work. The App is a desktop window for a machine with a screen. The TUI is a workspace that runs inside any terminal, which suits SSH. You can install one or both. They do not depend on each other.

Lumbridge App
Lumbridge App at work: an agent edits code in one pane, the pane splits for a test run and a diff, another agent asks to deploy, and a person answers it from the agents list.Lumbridge App at work: an agent edits code in one pane, the pane splits for a test run and a diff, another agent asks to deploy, and a person answers it from the agents list.
Three spaces, three agents. Split a pane, run the tests, answer the agent that needs you.Open full sizeOpen full size

Build and install the App

The install script copies the release binary under ~/.local and adds a launcher entry.
git clone https://github.com/lumbridge-corp/lumbridge-app
cd lumbridge-app
git submodule update --init --depth 1
cargo build --release --locked
just install
lumbridge-app

First launch: spaces, tabs and panes

The App finds lumbridge-core on your PATH and connects to it. A space holds work on one machine, usually in one repository. Each space has tabs, and a tab splits into panes that show terminals side by side. Closing the window leaves every terminal running. Closing a pane or a tab ends its terminals. Ctrl+Shift+P shows every command and its key.

  • Working: the agent is busy.
  • Blocked: the agent is waiting for you. This is the one to answer first.
  • Done: it finished while you were looking elsewhere.
  • Idle: it is not working, or it finished and you have looked at it.

The sidebar gathers the agents from all your spaces into one list with these four states, including workers that another agent started. A space and a tab show the most urgent state of the agents inside them, so a blocked agent is visible from anywhere. Click an agent to go to it.

Lumbridge App
Lumbridge App changing shape: a divider is dragged, a pane is moved by its grip, the sidebar collapses, a changes panel opens, and two personal layouts are applied.Lumbridge App changing shape: a divider is dragged, a pane is moved by its grip, the sidebar collapses, a changes panel opens, and two personal layouts are applied.
Resize, move and rearrange. Then switch the whole window to a layout of your own.Open full sizeOpen full size
Lumbridge App in a personal layout: a file tree on the left, terminal panes in the middle, spaces and agents on the right.Lumbridge App in a personal layout: a file tree on the left, terminal panes in the middle, spaces and agents on the right.
A personal layout: files on the left, sidebar on the right.Open full sizeOpen full size
Lumbridge App in a personal layout: a narrow agents list on the left and the changes panel as a drawer under the terminal panes.Lumbridge App in a personal layout: a narrow agents list on the left and the changes panel as a drawer under the terminal panes.
A personal layout: agents only, with changes in a drawer below.Open full sizeOpen full size
Everything you can click is also a command, for scripts and for agents.
lumbridge-app ls
lumbridge-app status
lumbridge-app do space.new --name api --folder ~/acme/api
lumbridge-app do tab.new --name "fix login"
lumbridge-app do pane.split --direction right
lumbridge-app commands

Build and install the TUI

One binary is the server, the client and the command line.
git clone --recurse-submodules https://github.com/lumbridge-corp/lumbridge-tui
cd lumbridge-tui
cargo build --release
install -m 755 target/release/lumbridge-tui ~/.local/bin/
lumbridge-tui --version
lumbridge-tui
# ctrl+b then q detaches. Run lumbridge-tui again to come back.
lumbridge-tui workspace create --cwd ~/acme/api --label api
lumbridge-tui agent list
lumbridge-tui server stop

The first lumbridge-tui starts a background server and attaches to it. A workspace is a project, with tabs and panes inside. The mouse works everywhere. For the keyboard, press ctrl+b and then a key: v splits right, - splits down, c makes a tab, w moves between workspaces, q detaches and ? lists every binding. The sidebar shows each agent as working, blocked, done or idle.

Lumbridge TUI
Lumbridge TUI in a terminal: the sidebar lists three workspaces and their agents, the view moves between them, then the palette opens the notebook drawer with a list of notes and a preview.Lumbridge TUI in a terminal: the sidebar lists three workspaces and their agents, the view moves between them, then the palette opens the notebook drawer with a list of notes and a preview.
Move between workspaces, then open the notebook from the palette.Open full sizeOpen full size

The next chapter runs a coding agent in a Core terminal, lets it hand work to a second agent, and shows how you step in.

Parts in this chapter Lumbridge App · Lumbridge TUI · Lumbridge Core