Leon
CODING AGENTSv0.16.25 Nov 2026

The native workspace for
coding agents. Fast by default

Run Claude Code, Codex, OpenCode or any agent in parallel across projects, worktrees and machines, from one native workspace.

[ BUILT ]Rust, GPU-rendered UI
[ SIZE ]24 to 30 MB download
[ RUNS ]macOS, Linux, Windows
[ REMOTE ]Pair with a code, end-to-end encrypted.
[ LICENCE ]Apache-2.0, open source
Built byZavu
Backed byGlobal
Used by engineers at
The Leon window on its home screen: the sidebar with two projects, a prompt field, and the recent sessions of the demo workspace.
DEFINITION

ADE

n. agentic development environment

An IDE is built around the file you edit. An ADE is built around the agents you run.

You still write code, review it and ship it. The difference is where your attention goes: to several agents, on several projects, at once. An ADE gives that work a home.

RUN01

Start the agents you already use

Claude Code, Codex, opencode and more, in Leon's own conversation view or in real terminals, on this computer or another one.

ORGANISE02

Keep them in one sidebar

Machines, projects, git worktrees and sessions. Leon finds them in your agents' history, so you set nothing up by hand.

RECALL03

Pick any of them back up

Every session is in one searchable history, and each one resumes in its own agent.

01 CHAT

See what the agent does, in plain words.

Leon draws the conversation with Claude Code, Codex, opencode and ACP agents itself, so each of them looks and works the same. A tool call is one line in plain words, not a raw call, and an edit shows its diff where it happens.

[ CHANGES ]A turn that changed files ends with a card listing them. A click opens a panel of diffs beside the conversation. The foot shows the branch and a GIT button to commit, push and open the pull request.
[ REWIND ]Leon snapshots the worktree before each turn, so the card counts what that turn did. Edit from an earlier message to go back to that point.
[ PLAN ]The agent's todos and plans are cards. Find in the conversation, walk your earlier prompts with Up and Down, queue a message or send it into the running turn.
[ SWITCH ]Change agent in the middle of a conversation. The new one starts in the same folder with the context handed off.
[ LINKS ]A file path in an answer is a link: text opens in Leon's editor, anything else in the system's program.
[ LIMITS ]Leon's own interface is still marked experimental (Settings, Experimental). An agent it cannot drive starts in its own terminal program.
A conversation with Claude Code in Leon: each tool call folded into one plain line, an edit shown as a diff, and a card listing the files the turn changed.
02 ORCHESTRATOR

One agent that runs the others.

The Orchestrator is one agent that answers for every project Leon knows. Ask it how something works or what to build next. It answers short questions itself and gives long investigations and changes of code to workers: other agents, each in a worktree and a branch of its own, on the agent and model that cost least for the job.

[ VIEW ]The same conversation view as the chat. Each worker has its own conversation, its changed files with their diffs, and a git footer.
[ CHECKS ]Before a pull request it runs the project's own check on the worker's last commit, opens the pull request only if it passed, then watches CI and has the worker fix what fails.
[ SAFE ]It never merges, never pushes to a default branch and never forces a push. A question it cannot settle reaches you as a card.
[ SERVICE ]It runs as a background service, so it and its workers keep going with the window closed. macOS and Linux; not on Windows yet.
[ PHONE ]Follow it from the phone app: read its conversation, answer its questions, stop a worker.
The Orchestrator view: one prompt for every project, and a workers panel where the agents it starts show up, each in a worktree of its own.
04 OFFICE

Every session is a lion at work.

Open the Office and each live session is a lion at a desk. It works while its agent edits and runs commands, dozes when it has been quiet, and waits on the yellow rug when it needs you.

[ CARD ]Point at a lion and its card says where the session left off: what the agent last said, then what you last asked.
[ ACT ]Select a lion to message its agent, interrupt it, rename it or send it home. A message waits in a queue while the agent works.
[ WORKERS ]The Orchestrator's workers are lions too, and sessions running in another terminal show up as well.
[ THEME ]The room is drawn in your theme's colours, light or dark.
Office13 lions
    05 MACHINES

    Your laptop, your servers, your phone.

    Run agents wherever the machine is and drive them from the window in front of you. Usage of each agent, accounts and updates come along.

    [ SSH OR CODE ]

    Other computers sit next to this one

    Add a server over SSH, or pair a computer with a code. Its projects and sessions show up in the same sidebar. How the code works.

    [ NO PORTS ]

    Nothing to open, end-to-end encrypted

    Both computers dial out to a relay that only sees ciphertext. One key per device, revocable.

    [ PHONE ]

    Leon for iPhone and Android

    Pairs with a shared computer by the same code. Chat with an agent there and follow the Orchestrator. It lives in the repository's mobile folder, not in the desktop downloads.

    [ HOST ]

    A computer that stays reachable

    Install leon host as a background service and it keeps sharing with no window open. Linux and macOS.

    RELAY · ONLINE

    The relay service at relay.getleon.dev is online, and "With a code" works across networks. The feature has had no independent security review yet.

    06 SPEED

    Native, so it answers when you ask.

    Leon is written in Rust and draws its own window on the GPU. Search, terminals and the sidebar run in one process, on your machine, with nothing to boot behind them.

    1–2ms

    Full-text history search

    Across about 14,700 messages.

    ~5ms

    Re-import with nothing new

    About 1 s the first time, for 132 agent sessions.

    25–31MB

    Download

    Native Rust, with no browser engine inside.

    The search and import times were measured by the developer on one M1 Pro, on real agent history, with the 0.1.0 code. The size is that of the 0.15.0 downloads. Your machine and your history will differ. These are Leon's own numbers and say nothing about any other product.

    ALSO IN LEON

    The rest of the workspace.

    Smaller features that save a trip to another tool.

    [ TASKS ]

    One board for you and your agents

    Drag cards in the window, or use leon task and its MCP server. A card can make a worktree and start an agent on it. Issues sync with GitHub through your gh login.

    [ MEMORY ]

    What one agent learns, the next can read

    Decisions saved by any agent, and a memory file each agent reads before it starts. Off until you turn it on for a project.

    [ CHANGES ]

    Read the diff, open the pull request

    Commit, push and open the pull request from the Changes tab or the conversation. No force push, amend, reset or discard.

    [ TERMINALS ]

    Real terminals, split your way

    GPU-rendered terminals with splits and tabs, for the agents you prefer in their own program. Keep local sessions running lets them outlive the window.

    [ EDITOR ]

    An editor beside the agents

    Text files open in a tab with highlighting, search and replace and a file tree with git marks. Markdown and SVG preview, and a picture viewer.

    [ KEYBOARD ]

    Every action has a shortcut

    ⌘P goes anywhere, ⇧⌘P runs any command, ⌥⇧⌘K opens the Orchestrator and ⌥⇧⌘L the Office. Ctrl replaces ⌘ on Linux and Windows.

    [ USAGE ]

    Limits, tokens and cost

    How much of each agent's limits you have used, and tokens per agent, model and day with a cost estimated at API list prices. Several accounts of one agent are fine.

    [ DICTATE ]

    Say it instead of typing it

    A speech model that runs on your computer writes what you say into the field. Nothing is downloaded until you choose a model, and no sound leaves the machine.

    [ THEMES ]

    A theme is a TOML file

    Leon and Zavu ship built in, light and dark. Yours extends one and reloads as you save.

    [ NOTIFY ]

    Told when an agent needs you

    A banner in the window and a system notification when an agent finishes, asks or fails. You choose which events.

    [ PROJECT FILE ]

    Scripts and setup in leon.toml

    Name the commands of a project, give each a shortcut, and run a setup command in every new worktree. Leon asks before the first run.

    [ UPDATES ]

    Updates that wait for you

    Leon checks the GitHub releases, verifies the download against the checksums and installs it at your next restart.

    ROADMAP

    What is next.

    Planned, not shipped. Nothing here is available today unless it says so.

    [ NOW ]

    Public releases

    RELEASED

    Chat with agents

    RELEASED

    Orchestrator

    RELEASED

    + 10 more

    [ NEXT ]

    Linear

    PLANNED

    Annotate a diff for the agent

    PLANNED

    Independent security review

    PLANNED

    + 1 more

    [ LATER ]

    Compare agent results

    PLANNED

    Live remote sessions after a restart

    PLANNED

    Remote history import

    PLANNED

    + 1 more