Skip to main content

Clave An Antasphere tool

Your coding agents, side by side.

Every agent session is a terminal. Clave gives the terminals a home: tabs, groups and whole workspaces you launch in one click, whichever agent you run. And Claude Code, inside a tab, can arrange the window around its own work.

  • Free and open source
  • Claude Code, Codex, Antigravity, Pi
  • macOS, and Windows early
The Clave window: the Checkout group open in the sidebar, and four of its tabs side by side: a Claude Code conversation, a Codex review waiting for an answer, a dev server and a test watcher.

How it works

Terminals, grouped the way the work is.

  1. 01 Sessions

    Every agent session is a terminal. Clave gives it a tab.

    Claude Code, Codex, Antigravity, Pi, or a plain shell: each runs in its own tab, with the agent’s state on the tab, so you see who is working, who is waiting for you, and who is done. Select several tabs and they tile side by side. Claude Code and Codex can also open in a chat view, with the answers rendered and the permission requests above the composer.

  2. 02 Groups and workspaces

    Tabs group by project, and a project raises in one click.

    A group remembers its sessions, their folders, its saved terminals (a dev server, a board) and the prompt each session opens on. A workspace is a folder with a small .clave file; Clave finds every project’s file underneath it and offers each as a template. A teammate keeps their own copy and never touches yours.

  3. 03 The agent drives the app

    The window arranges itself around the work.

    Every Claude Code tab is connected to an MCP server inside Clave, in the terminal and in the chat view. The agent can open a sibling session with a prompt, launch a whole group, pin a live page to it, open a file or a document beside itself, message another tab, and ask you for a secret it never gets to see. Our own tools drive Clave this way; yours can too.

  4. 04 What the agent never sees

    The agent asks for the key. You are the one who types it.

    A secret is pasted by you into a masked field and injected for one action, or written straight to the file it belongs in. The value never passes through the transcript, and the agent never reads it back. The same discipline holds over SSH, where a machine elsewhere is just one more location in the sidebar.

The workbench

One window: your projects on the left, your agents side by side, and the page they are building right there.

And because every Claude Code tab is connected to the app through MCP, the agent inside one of them can open the next tab, pin the live page beside it, and hand the work on.

Groups Atelier Website Exos Sessions Lane A Lane B Verifier MCP: the agent opens the next tab The view One folder, one .clave file, and the whole project raises in one click

For agents

The agent in a tab can reach the window around it.

Clave runs an MCP server, and every Claude Code session it starts is connected to it. Twenty-three tools let the agent open, move and message tabs, launch groups, pin live pages, open files and documents beside itself, and ask you for a secret. The clave plugin adds the skills that write a workspace file and bring lost sessions back.

the plugin, then the agent at work
npx plugins add antasphere/clave

# inside a tab, the agent calls the app
clave_open_session  --prompt "verify lane A"
clave_set_group_view  http://localhost:4720
clave_request_secret  STRIPE_KEY → .env
  • Tabs and groups. Open a session with a prompt and a model, launch a pinned group, move, rename, focus or close a tab.
  • Pages beside the work. Pin a dashboard or a preview to a group or a tab, open a file, edit a document or an email in the side panel.
  • Tabs that talk. Send a message to another tab, read its recent output, report back to the tab that opened yours.
How agents use Clave

What it does

The whole of it, as it ships today.

  • The bench

    The window itself: tabs, groups, and the pages that belong beside them.

    • Bring your own agent Claude Code, Codex, Antigravity and Pi, plain terminals, and remote agents over OpenClaw.
    • Terminal or chat Claude Code and Codex in their terminal, or in a chat view with rendered answers, grouped tool calls, attachments and a model menu.
    • Groups and templates One group per project, remembered sessions and servers, a primed prompt, and every nested .clave file discovered as a template.
    • Live views Pin a page to a group or a tab: a dashboard, a preview, a board. If its server is down, the view starts it.
  • Driven from inside

    What a person can do to the window, the agent in a Claude Code tab can do too.

    • The MCP surface Twenty-three tools the agent inside a Claude Code tab can call, and the clave plugin with its skills, so the app is scriptable from within.
    • The side panel A file tree with editors, an HTML preview, a Markdown and email editor beside the session that wrote it, and a git panel with diffs, history and one-click sync.
  • Yours, and local

    No account and no cloud backend: your agents talk to their own providers, and Clave stays on your machine.

    • Secrets, kept from the agent A secret is pasted by you into a masked field and injected for one action. The agent asks; it never reads the value.
    • Remote work Sessions and files over SSH and SFTP, so a machine elsewhere is one more location in the sidebar.
    • History and accounts Past sessions searchable in one place, usage per account, and a tab moved to another Claude or Codex account without losing it.

With Exos

Clave is where the work happens. Exos is the rail it runs on.

In our own workspace, one Exos project is one Clave group, and the group’s view is the project’s board. A delivery lane is a Clave tab; a wave is one coordinator tab opening one tab per lane and talking to them. Exos owns the tasks and the record; Clave knows nothing about Exos and is driven from outside. Either half works without the other.

Who it is for

Developers

Several agents, one workbench

If you already run more than one coding agent at a time, locally or over SSH, Clave is the window you were missing.

Teams

One file per project, yours to override

A default .clave in the repository gives everyone the same groups; a personal copy lets each person diverge without touching the others.

Builders of agent tooling

A desktop host you can drive

The MCP surface our own products use to open tabs, attach pages and hand work between agents is the same one yours get.

Where it came from

A plain observation, and what followed.

Clave began as a plain observation: every agent session is a terminal, and terminals deserve a better home than a window you lose.

So Clave is a desktop app that hosts terminals. Your agents, whichever you already use: Claude Code, Codex, Antigravity, Pi. Sessions group by project, whole workspaces launch in one click, and a live page can sit right beside the sessions producing it.

We work inside it all day, on everything, in the Antasphere Labs in Brussels. It is open source, and deliberately unaware of anything else we build: our own tools drive it from the outside, and yours can do the same.

A photogram of typewriter keycaps, a coiled cord and four glass slides side by side, toned bottle green.
The photogram Keys, a cord, four windows.

From the journal

What shipped lately, with the reasoning left in.

  • A sidebar of grouped tabs with a side panel open, in deep reef green. agents

    Agents that drive the window

    Every Claude Code tab Clave starts is connected to the app over MCP. The agent in it can open tabs, show a file, pin a page, talk to another tab, and ask for a secret it never reads.

    Luca Derumier

  • A chat transcript and a terminal side by side, in reef green. release

    Clave 2.0: a chat view beside the terminal

    Clave 2.0.0, released on 30 September, opens Claude Code and Codex in a native chat view, holds several accounts per agent, and runs plugins that shape the app.

    Luca Derumier

  • An installer window on a pale reef green ground. windows

    Clave on Windows, early

    Since v1.89.0 every Clave release carries a Windows installer. What works on Windows today, what does not yet, and what the first install looks like.

    Luca Derumier

Open source, all of it

Not a free tier around a paid core.

The entire app is open source under the MIT License, with no account, no cloud backend and no wrapper around the model. Switching agents never means switching homes.