A fast, themeable, cross-platform desktop GUI for Lore β Epic Games' next-generation version control for source code and giant binary assets. Stage, branch, merge, diff, and lock files without touching the command line. Agent-native, with a built-in MCP server.
Community project. Not affiliated with or endorsed by Epic Games. "Lore" is a trademark of Epic Games, Inc. Licensed under MIT.
Agents: read
.claude/skills/loregui/SKILL.mdβ it's the single entry point to install, set up the MCP, configure, and drive LoreGUI.
LoreGUI drives Lore's complete native API in-process β it binds the lore Rust crate directly, with no CLI shelling and no background daemon. Every operation runs at native speed in the same process: status, staging, commits, branches, merge/diff, file locking, and the full operation surface across 14 domains.
It's built for the way modern game and film pipelines actually work β content-addressed storage, sparse on-demand hydration of multi-terabyte repos, and exclusive locks for binaries that can't be merged β all in one signed installer with nothing to babysit.
LoreGUI is also agent-native: it ships an MCP server that exposes lore operations as tools so AI coding assistants can drive your repository directly.
- Universal command palette β every lore op is reachable by name from one keystroke, with typed inputs and inline help (palette parity is a CI gate).
- Rich per-domain panels β branches, history, locks, storage, dependencies, and more, each a first-class view.
- Visual branch, merge & diff β read the commit DAG at a glance, compare any two revisions, resolve merges in a focused three-way view.
- File locking for binaries β claim exclusive locks, see who holds what in real time, release with one click.
- Host or connect β first launch offers Choose Your Setup Mode (connect to a server or host your own). Returning users without a validated repository see a four-action hub: Open existing, Create local, Connect, or Host β with repository validation, native Browse, and no-auth support. The Host flow has a guided config surface: a one-field Basic mode for a local server, and an Expert mode exposing all 54 lore-server options (network/QUIC/gRPC/HTTP, storage, topology & mTLS replication, telemetry, runtime, notifications, features, timeouts). LoreGUI generates the
loreserverTOML for you β view it with one click; you never hand-edit config. - Fully themeable β semantic surface tokens drive a light/dark/custom theme system; the whole UI re-themes.
- MCP support β a built-in MCP server lets AI agents drive lore, one tool per operation.
- Signed, multi-platform releases β single installer per platform, published to GitHub Releases (Windows & Linux now, macOS soon).
Verified end-to-end on a clean Windows 11 install β the app installs, launches straight to onboarding, and hosts a local lore:// server with no errors.
![]() First run β a fresh install launches to Choose Your Setup Mode |
![]() Hosting β stand up your own lore:// server in a couple of clicks
|
Quick install β download the latest signed installer from GitHub Releases and run it (Windows & Linux now, macOS soon).
Build from source β with Rust (stable, edition-2024-capable), Node 20+, and the Tauri v2 system deps for your platform:
npm --prefix frontend install && cargo tauri build # β platform installerFor hot-reload development: cargo tauri dev (from src-tauri/).
π Full docs and downloads: loregui.com Β· loregui.com/docs
LoreGUI ships an MCP server so AI agents can drive lore directly β it registers one MCP tool per operation (status, history, diff, commit, branch, stage/unstage, locks, β¦) plus a lore_repo_summary aggregate. The tool catalog is generated from LoreGUI's command-palette manifests, so the agent surface stays in lock-step with the GUI.
Register it with your agent's mcpServers config:
{
"mcpServers": {
"lore": {
"command": "/path/to/loregui/lore-mcp/venv/bin/python",
"args": ["/path/to/loregui/lore-mcp/server.py"],
"env": {
"LORE_REPO": "/path/to/your/lore/repo",
"LOREVM_BIN": "/path/to/loregui/target/release/lorevm",
"LORE_OFFLINE": "1"
}
}
}
}Full setup, the tool list, and configuration: lore-mcp/README.md. Pair it with the .claude/skills/lore skill for the git/p4 β lore mental model.
| Path | What |
|---|---|
crates/lore-vm/ |
Reusable, GUI-agnostic core. Binds the lore crate; one file per operation. |
src-tauri/ |
Tauri v2 desktop shell. One command per operation. |
frontend/ |
The GUI (Vite + React + TypeScript). Per-domain panels + universal command palette. |
lore-mcp/ |
MCP server exposing lore ops as agent tools (one tool per op). |
website/ |
Marketing landing site (Next.js) for loregui.com. |
docs/IMPLEMENTATION-PLAN.md |
Full-parity build plan and ticket tree. |
lore-vm is intentionally decoupled from the GUI so it can also be embedded in larger tooling.
Pre-1.0, under active development against a pinned upstream lore revision. See docs/IMPLEMENTATION-PLAN.md for the parity roadmap and contribution workflow.
LoreGUI is MIT-licensed (see LICENSE). The distributed binary bundles the upstream Lore crate, the loreserver sidecar, and many open-source Rust/npm dependencies β all permissive. Generated attribution bundles: THIRD-PARTY-LICENSES.md (index), NOTICE, and the in-app Settings β About & third-party licenses view. Regenerate with bash scripts/gen-licenses.sh; CI (licenses.yml) verifies they don't drift.
Open tools for creative production
Created by BizaNator
loregui.com | BrainDeadGuild.com | BrainDead.TV | GitHub | Discord
Building tools for the BrainDeadGuild community
A Biloxi Studios Inc. Production
Β© 2026 Biloxi Studios Inc.








