Metal AgentandClaude Opus 5
b6dc70f9fa
The adapter is only worth having if the call sites exist, so this wires the ten elements `UX_VERTICAL_SLICE.md` actually names and stops there. The shell root is an application; the sidebar, its row list and the workspace are named regions; every workspace panel is a pane carrying its label, its execution target, its waiting state and whether it owns the keyboard; every live terminal surface is a terminal; the command palette and the add-panel chooser are dialogs; the footer's usage strip is a status. Seven elements gained a stable GPUI id along the way, because an element worth naming to a screen reader is an element worth keeping state on. The other 137 divs are left alone deliberately. Fixed-width slots, meters, chips, borders and painted terminal cell runs have no identity to hang a node on, and publishing 80x24 nodes a frame would be a tree nobody can navigate and a cost on every repaint. No new strings were invented for the screen reader where the model already had one. `describe()` labels each sidebar row -- that is its caller, so its `#[allow(dead_code)]` is deleted rather than carried, as decision 0023 requires. The three words in a pane header's corner and the three words its description leads with now come from one function. The two lines a pane header prints about where it runs and what its process is doing moved out of `pane_context` into `pane_header_lines`, because the pane's semantic node is built one level up in `workspace_panel` and recomputing them there would have meant two expressions that agree today and disagree after the first edit. The add-panel chooser's heading and its accessible name are one constant. Four labels are new strings, because nothing on screen names these areas: "Lumbridge", "Workspace", "Sidebar" and "Harness usage". Each is the name the code and the docs already use for the thing it labels. The scorecard's accessibility row now reads fail rather than a hedge. The call sites are wired; the semantics are absent, because the adapter no-ops. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SPYebLiN2w4TqnHUYGdECq
Lumbridge
Lumbridge is a fast, local-first workspace and terminal multiplexer for agentic engineers. It will run coding harnesses side by side, preserve their sessions, connect rich agents through ACP, and show trustworthy account and usage context without forcing users into one model vendor.
The first supported desktop platforms are:
- macOS (Apple Silicon first, Intel when CI capacity is available)
- Ubuntu Linux
- Omarchy and compatible Arch Linux systems
Lumbridge is free and open source under Apache-2.0. Releases will be published as installable binaries; building from source will remain supported.
Status
This repository is in architecture and vertical-slice phase. The installable binary is still a scaffold, while the isolated native UI spikes now exercise an interactive 20/60/20 workspace backed by six live comparison surfaces, and the root workspace contains the first bounded local PTY, runtime actor, VT engine, and capability-gated workspace command boundaries. The GPUI slice shows a responsive one-, three-, or five-panel workspace—five on a 3440 px ultrawide— where every panel owns its own context, work surface, and decision shelf. One panel contains a styled actor-owned VT session and five comparison surfaces remain deterministic. Retained-history navigation is wired. The usage footer is a live strip over an append-only ledger with provenance, fed by two real adapters: Codex's documented quota surface and Claude Code's session transcripts. A harness with no adapter renders an explicit gap rather than a zero. We are still validating terminal text selection and mouse input, standalone runtime IPC/durability, ACP integration, and packaging before a large implementation.
Product shape
- A native desktop shell with tabs, panes, workspaces, worktrees, diffs, and an agent-aware footer.
- A Rust session runtime that survives UI restarts and can later run headless.
- ACP-native integrations where available, with supervised PTYs as the universal fallback for any CLI harness.
- First-class harnesses for Claude Code, Codex, DeepSeek Harness, Pi, Hermes, OpenClaw, Goose, Gemini CLI, and OpenCode.
- Subscription login owned by the upstream harness, plus separate BYOK provider profiles for OpenAI, Anthropic, Gemini, Groq, Cerebras, DeepSeek, and more.
- Usage history, burn rate, reset windows, and forecasts with visible data provenance instead of invented precision.
- Optional first-class Buzz channels, messages, agents, and confirmed redacted pane sharing without making Buzz a requirement.
- An optional Lumbridge Harness that can suggest, coordinate, and—with explicit execution capability—manage agents through the same audited command plane as the human UI. Lumbridge remains useful without it.
Start with the product spec, architecture, research map, and captured upstream revisions. The native UI choice is intentionally open; see the measured decision plan.
Scaffold
bacon # continuous check; t tests, c lints, v runs the full gate
cargo xtest # fast isolated tests with nextest
./scripts/ci.sh # format + strict Clippy + tests + doctests
cargo run -p lumbridge
See the testing strategy for fake harnesses, ACP replay, terminal conformance, UI driving, recovery, performance, and packaging tests.
The accepted local/remote boundary is recorded in
decision 0003. The two
native shell candidates live in spikes/, with results tracked in
the UI scorecard.
The signed-protocol and pane-sharing boundary is in
the Buzz integration design.
Brand masters, platform-ready raster exports, and usage rules are in
assets/brand/ and the brand guide.