Metal AgentandClaude Opus 5
d7560d4b8b
Lumbridge will build and open-source lumbridge-toolkit and ship on it, the same arrangement Zed has with GPUI and for the same reason: nothing existing is built for a terminal-grid-and-agent-panels product. GPUI stays as the backend until parity, then goes. What changed is not appetite. Writing a toolkit used to mean writing a GPU renderer, a shaping and layout engine, and an accessibility layer from scratch; vello, parley, accesskit, kurbo, peniko, winit and taffy now do that under a permissive licence. Measured at ce48461e the GPUI family is 129,110 lines across nine crates, and the large majority of it is those primitives. What is left -- the element model, layout composition, the paint pipeline, input routing, and the terminal grid -- is what this project actually has to write. Two claims justify building rather than adopting, and no other Rust toolkit makes them. Accessibility is a crate the element model is built on rather than an adapter added later, which matters because both candidates Lumbridge evaluated failed that hard gate and 0017 shipped knowing it. And the terminal grid is a first-class widget rather than an embedding problem, which matters because this repository has already got cell measurement wrong twice. M0 is a gate with its thresholds written before the run, so the result cannot be rationalised afterwards: five panels of 200x60 styled cells no worse than the GPUI baseline on frame p95 and key-to-present, an IME round trip that does not split UTF-8, and an AccessKit tree driven by Orca and VoiceOver -- a passing TreeUpdate unit test explicitly does not count. Failing it means staying on pinned GPUI and superseding this record. The failure mode being guarded against is a year with neither a finished toolkit nor a finished product, so Phase 1's exit criterion is not deferred for toolkit work, and no GPUI capability is removed before its replacement passes the same gate. 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.