$ open source · local-first · no telemetry NEW what's new →

Your terminal,
wherever you go.

An open-source terminal with command blocks, inline AI and split panes — plus a QR code that turns your phone into the same session. No account, no telemetry.

RustTauri 2SolidJSxterm.jsnot Electronnot a fork
01 REMOTE CONTROL

The terminal you left running is in your pocket.

Every other terminal stops at the edge of your desk. Scan the code once, and the same live session is in your hand — same panes, same scrollback, same shell. Or open it from your laptop, in another Lume.

Lume on the desktop showing the pairing QR code and one connected device, and a phone running the same live session
paired, not shared

The QR code is single-use and pairs one device. Each device gets its own key and shows up in a list you can revoke from — there's no link to leak.

end-to-end encrypted

On your Wi-Fi or through the optional cloudflared tunnel, the network only ever sees ciphertext. Nothing stays open behind your back.

Lume ↔ Lume

Open your desktop's terminals from your laptop, in a pane that reconnects by itself after a Wi-Fi switch or a restart.

# how pairing, encryption and the tunnel actually work → Control your terminal from your phone

02 FEATURES

Everything a terminal should be.

A terminal emulator with blocks, panes and palettes — powerful where it counts, invisible where it shouldn't get in the way.

~/lume $ lume --features
[01]

Command blocks

Each command and its output is an isolated block. Jump between them, copy, re-run — no scrolling through a wall of text.

[02]

Inline AI

Explain a block, or turn plain English into a command. Bring your own Claude, Codex, OpenAI or Ollama — keys stay local.

[03]

Panes & tabs

Split, tab, rearrange by drag-and-drop. Panes, sizes, folders and recent blocks survive a restart — and each tab shows its git branch.

[04]

Command palette

Every action, workspace, SSH host, workflow and theme in one search. ! digs through your history, ? asks the AI.

[05]

Workspaces

Save a project's tabs once — folders, splits, npm run dev and the queue worker — and reopen the whole setup in one click.

[06]

Rich history

Every command with its folder, exit code, duration and git branch. failed, here, branch:main — find it in a keystroke, secrets left out.

[07]

Autocomplete

Inline suggestions from your history, the files around you, your aliases and your PATH.

[08]

File tree sidebar

Follows the active pane's directory instead of fighting it. Right-click actions are yours to define.

[09]

SSH manager

Your ~/.ssh/config hosts (Includes too), favorites first. Re-attach tmux or use mosh, and reconnect in one click when the link drops.

[10]

Workflows

The commands you can never remember, saved as snippets with named arguments — recalled from the palette, not from a stale gist.

[11]

Themes, fonts & 14 languages

10 themes, custom fonts, Nerd Font support, remappable keys — and a UI translated into 14 languages, not just English.

[12]

Local & self-updating

Everything runs on your machine — no account, no telemetry — with signature-verified auto-updates.

03 WHY LUME

Warp is open-source now. So why not just fork it?

Fair question. Lume is the alternative that isn't a fork — and that changes three things.

~/lume $ git log --oneline | tail -1 › initial commit — from nothing
[01]

A fork inherits the weight

Forking gets you the features and the mass that came with them. Lume started from nothing, so there was never anything to strip out — 3.6 to 9 MB, depending on your OS.

[02]

A fork inherits the licence

Lume is MIT. Fork it, rebrand it, sell it, ship it across your company — no conversation with legal. Copyleft forks stay copyleft; MIT hands the choice back to you.

[03]

A fork inherits upstream

Every fork spends its life rebasing onto someone else's roadmap. Lume answers to nobody — which is how a feature like phone control gets built at all.

3.6 MBWINDOWS .EXE
5.4 MB.DEB / .RPM
9.0 MBMACOS .DMG
MITLICENCE

# sizes measured on the v1.5.0 artefacts. Lume shares no code with Warp and is not affiliated with it. Want Warp's exact feature set? Use Warp — this is a smaller bet.

04 SHOWCASE

See it in action.

Real screenshots of the app, not mockups.

inline ai

An assistant in your prompt, not in charge of it.

Ask what a block did, or describe what you want and get the command — inserted, never auto-run. A deliberate choice: you keep the last keystroke.

Inline AI in Lume
panes & themes

Lay it out the way you think.

A CLI agent in one pane, your dev server in another — and the whole layout comes back exactly as you left it tomorrow.

Panes and themes in Lume
settings

Configurable to the last detail.

Appearance, shell, AI providers, shortcuts, language — one panel. Export and import the whole config as JSON.

Settings in Lume
05 FAQ

Questions, answered.

? Warp is open-source now — why use Lume?+

Because a fork inherits everything: the codebase, the licence, and the job of chasing upstream forever. Lume shares no code with Warp — it's an independent open-source terminal, and it does one thing no Warp build does: it follows you to your phone.

? Is Lume a fork of Warp?+

No. Written from scratch in Rust with Tauri 2, SolidJS and xterm.js — no shared code, no lineage, no trademark. The block-based workflow is a convention, not a codebase.

? How does remote control work?+

Lume serves a small page from your own machine. Scan its QR code once to pair your phone — or paste the link into another Lume — and the device reconnects on its own from then on; revoke it any time. Everything is end-to-end encrypted, on your network or through the optional cloudflared tunnel.

? Does Lume send my data anywhere?+

No. No account, no telemetry, no cloud. AI is off until you configure it, and your API keys stay local — they're even excluded from config export.

? Which AI providers can I use?+

Claude and Codex through their local CLIs, or OpenAI, DeepSeek, Ollama and any OpenAI-compatible endpoint with your own key. Opt-in, picked in Settings.

? Why MIT and not AGPL?+

So you can actually use it: fork Lume, rebrand it, ship it in a commercial product, with no conversation with legal. Copyleft licences stay copyleft — MIT leaves the choice to you.

? Why are the macOS & Windows builds unsigned?+

Certificates cost money, so early releases ship unsigned — a one-time prompt to bypass. Each release has a signature file and the source is public, so you can verify or rebuild.

? What is Lume built with?+

Rust + Tauri 2 + SolidJS + xterm.js. A native binary: 3.6 MB on Windows, 5.4 MB on Debian, 9 MB on macOS. Not Electron.

06 DOWNLOAD

Get Lume.

Free, MIT, no sign-up form between you and a working terminal.

~ $ lume install › detecting os…

macOS

Universal — Intel & Apple Silicon · 9.0 MB

↓ .dmg

Unsigned for now: on first launch, right-click → Open.

Windows

Windows 10 & 11 (x64) · 3.6 MB

↓ .exe

SmartScreen may warn: More info → Run anyway.

Linux

AppImage · .deb · .rpm · AUR · 5.4 MB

all downloads

# prefer a package manager? yay -S lume-bin on Arch. Every release auto-updates in-app.