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
Clave An Antasphere tool
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.
Terminals, grouped the way the work is.
01 Sessions
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.
02 Groups and workspaces
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.
03 The agent drives the app
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.
04 What the agent never sees
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
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.
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.
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 The whole of it, as it ships today.
The window itself: tabs, groups, and the pages that belong beside them.
What a person can do to the window, the agent in a Claude Code tab can do too.
No account and no cloud backend: your agents talk to their own providers, and Clave stays on your machine.
Free, on your Mac today, and early on Windows.
No account and no sign-up. Clave updates itself from its releases on GitHub. You bring your own agents: install at least one of them and sign in to it as you normally would.
macOS
Windows, early
Version 2.0.0. Requirements, updates and what Clave sends.
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.
Developers
If you already run more than one coding agent at a time, locally or over SSH, Clave is the window you were missing.
Teams
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
The MCP surface our own products use to open tabs, attach pages and hand work between agents is the same one yours get.
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.
What shipped lately, with the reasoning left in.
agents 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
release 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
windows 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
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.