MaeVae is coming to the Microsoft Store.
From launch, the Microsoft Store is the one way to get MaeVae: it installs the app and keeps it up to date. Windows 11 already has the WebView2 Runtime that draws MaeVae’s window; a Windows 10 PC may need it installed, and at launch MaeVae tells you if it does.
MaeVae is in early access. The plans and prices are on the pricing page. Early-access users hear first when selling starts. The Store listing is not public yet; the Store button already points to it.
MaeVae drives the command-line tools you already have; it bundles none.
- Claude Code
- Codex CLI
- Gemini CLI
- Qwen Code
- aider
- Grok CLI
- Plain shell
What you need, and why
Three things on your PC, and an account with the vendor of each agent you use.
MaeVae runs on your PC and drives tools you install yourself. The Store brings MaeVae; each agent you use brings its own command-line tool, and your own account with that agent’s vendor.
To check that a tool is on your PATH, open a terminal and run its version command: claude --version, codex --version, gemini --version, qwen --version, aider --version or grok --version.
| What you need | Why |
|---|---|
| Windows 10 or 11, 64-bitThe 64-bit edition of Windows 11 or of Windows 10. | MaeVae is a Windows desktop app, and every pane in it is a real Windows terminal. The agent in a pane is the same program you would start in any console on your PC. |
| Microsoft Edge WebView2It is built into Windows 11. A Windows 10 PC may need it installed. | WebView2 draws MaeVae’s window: the rail of profiles, the panes, the HUD and every panel. At launch, the Store package does not carry it. On a PC without it, MaeVae shows one box at start that says it needs the Microsoft Edge WebView2 Runtime and names Microsoft’s WebView2 page, then closes. Install the Runtime from there, then start MaeVae again. |
| An agent’s own command-line toolAt least one, installed and on your PATH. | The agent’s tool is what MaeVae drives. MaeVae bundles none of them: each pane starts the tool you installed, under its profile’s own configuration. It drives Claude Code, Codex, Gemini CLI, Qwen Code, aider and Grok, and a profile can also be a plain shell with no agent. |
| An account with each agent’s vendorYour own, signed in inside the pane. | MaeVae holds no agent account of its own. A profile signs in with the agent’s own login inside its pane, or uses an API key you set in the profile. aider has no login: its API key is its account. A Codex, aider, Qwen Code or Grok profile has an Endpoint field, which can point it at a model server you choose instead, on your own PC or with a provider such as Groq or OpenRouter. |
First start, in four steps
At first start the rail is empty. Four steps later a pane is open, and the agent in it is setting itself up.
Its own config dir; you'll log in on first launch. Use my existing Claude login Account label me@example.com
The MaeVae window just after a first profile was made. The rail shows the name MaeVae, the heading Claude Code with the profile Docs and its account me@example.com, and the button Quick settings. The top bar reads 1 open, with the three layout buttons, panic and the window's own buttons. The pane Docs runs Claude Code, with Isolation, review, Redraw and close in its header. In the pane the agent greets you and asks its first setup question, which text style to use: four options with Dark selected, then Light and the two with more contrast, a short preview of how code will look, and a hint to press Enter to choose. The names and lines are examples. Where motion is allowed, a short rendered scene plays once and ends on this frame: the empty window says No profiles yet, + Add profile is clicked, New profile opens over the window and goes through Step 1 Agent, Step 2 Account and Step 3 Project, Create & open is clicked, and the pane opens.
-
Start a new profile
The rail says No profiles yet. Click + Add profile, there or in Quick settings, and New profile opens over the window.
-
Name the profile and pick its agent
Give the profile a short name and pick the agent it runs. A tool that is not on your PATH is marked “(not installed)”.
-
Choose the account
For Claude Code, choose Fresh isolated account for a login of its own, or Use my existing Claude login to share the one you already use. Codex, Gemini CLI, Qwen Code and Grok each get their own isolated configuration. Codex and Grok sign in inside the pane on first launch, or use an API key you add in the profile’s editor. Gemini CLI uses a Gemini API key from Google AI Studio, set in the profile; Google’s own sign-in inside the pane works only with a Workspace Code Assist license. Qwen Code needs an API key, an Endpoint and a Model set in the profile, or its own
/authinside the pane. aider has no login: its API key, set in the profile, is its account. -
Set the project folder and open the pane
Pick the project folder the agent works in. For Claude Code, Codex and Gemini CLI, also pick its Capability: Trusted, with full access, or Restricted, a guardrail that keeps the agent to the project folder and needs a real folder. A CLI launcher, with a Windows Terminal tab where Windows Terminal is installed, is ticked to start with. Create & open makes the profile and opens its pane.
Then the agent sets itself up
The first time a pane opens, the agent runs its own one-time setup in it. For Claude Code that is a theme picker, a prompt to trust the folder, then a sign-in in your browser. Complete it once; from then on the pane starts the agent straight away.
A new pane that seems to wait on a theme list or a trust prompt is this setup, not a fault.
The guide goes on from here: signing in, working side by side, the attention queue, Restricted mode, Isolation and the rest.
If an agent’s tool is not installed, MaeVae says so.
MaeVae looks for each agent’s tool on your PATH. An agent whose tool it cannot find shows “(not installed)” next to its name, and MaeVae cannot start a pane for it.
In the first step of a new profile, the Agent list marks the missing tool, and the step offers Copy install command. It puts the agent’s own install command on the clipboard and opens the agent’s documentation page. Install the tool, check it with its version command, then reopen MaeVae.
Also in Quick settings. Under Update agents, a missing agent has an Install button that runs its own install command. At launch, in the Store release, Grok CLI’s Install shows its command with Copy instead, for you to run in PowerShell yourself. A tool that lands in a new folder is seen after MaeVae restarts.
Guide: When something looks wrong
The MaeVae window with two panes, Client work running Claude Code and Research running Gemini CLI, dimmed behind the New profile panel. The panel shows Step 1 of 3, Agent: the Name box holds Side project, and the Agent list shows Qwen Code (not installed). Under the list the panel says Qwen Code isn't on PATH, with the button Copy install command, then its note on picking the agent. At the foot are Advanced (all fields) and Next. The names and lines are examples. Where motion is allowed, a short rendered scene plays once and ends on this frame: New profile opens over the window, the Agent list changes from Gemini CLI to Qwen Code, and the line about the missing tool appears.
Where to read more before you install
For anything else, write to support@maevae.com, or see the Support page.
The guide walks through the same ground in full: what you need, the install from the Microsoft Store and the first start.
The FAQ answers the common questions, and the features page sets out each part of the app with its limits.