MaeVae is in early access.
The plans and prices are on the pricing page. Early-access users hear first when selling starts.
At launch
Launch . Available on the Microsoft Store first.
What you get
- Features: every part in full, with renderings
- Guide: step by step, from the Store to everyday use
- FAQ: short answers, in groups
Twelve parts of the app, each in a few sentences, with its limit where it has one.
The two that keep agents apart come first: Restricted mode keeps an agent to its project folder, and Isolation checks that every profile is still its own. The other ten follow in the order you meet them at work, and each one ends on the chapter of the guide that walks through it.
-
Restricted mode
For a Claude Code, Codex or Gemini CLI profile with a real project folder, it keeps the agent to that folder and keeps push and deploy commands from running on their own, in the way each agent allows. Codex asks before a push and can still read outside the folder.
Limit. Restricted mode works by a per-profile folder box and a deny list of command names, not by a sandbox. A deny list is a speed bump: a determined shell can reach the same binaries by another path. Every pane runs as the same Windows user, so the credential stores on the machine, such as git credential helpers, SSH keys and the tokens of hosting tools, are shared across panes. Treat it as a strong guardrail for cooperative agents, not as a security boundary against hostile code.
-
Isolation: check, seal, enforce
Every agent’s pane carries an Isolation badge, in one of four colors, and a report. The report checks the profile’s folders, what points outside them, the vendor’s account channel and anything you never approved. Seal profile applies the safe fixes, and Check all profiles asks whether one profile reaches into another.
Limit. The check knows the channels of the vendor versions it was measured against; a vendor can add a new channel between releases.
-
A profile for each account
A profile is one agent, one account and one project folder, with its own isolated configuration (an aider profile has its own API key instead); the agent is Claude Code, Codex, Gemini CLI, Qwen Code, aider or Grok, or the profile is a plain shell.
Limit. Every pane runs as the same Windows user, so the credential stores on the machine, such as git credential helpers, SSH keys and the tokens of hosting tools, are shared across panes.
-
The HUD and the usage dashboard
Every pane can carry a live strip with the model, cost, session time, tokens, quota and context, as far as each agent reports them, and the usage dashboard shows the same for each profile.
Limit. The figures are measured from the agent’s own files on disk; they are not a bill. Agents report different figures, and a missing one is grayed.
-
The attention queue and the tray
When an agent needs an approval or finishes a turn, its pane lights up, the tray icon is badged and a notification and a chime can follow. While the agent waits you can approve or deny from the pane’s header, and closing the window keeps every session running in the tray.
Limit. Codex and Gemini CLI need a one-time trust step inside the agent before the pane lights up, and Windows decides whether a notification is delivered. An agent started outside MaeVae, in a Windows Terminal tab, does not chime.
-
Layouts, keys and Panic stop
Columns, rows or a grid with draggable dividers, Alt+1 to Alt+9 to focus a pane, the command palette on Ctrl+K, a Broadcast line to every pane, Redraw, and Panic stop, which stops every agent running in MaeVae. At launch, one pane can also fill the window, and Show all brings every pane back.
Limit. Broadcast sends its line to every open pane, Restricted ones included.
-
More than one Claude account
One Claude profile can keep more than one saved login, and you switch between them from the profile’s editor.
Limit. It works for Claude profiles that sign in with a login, not for API-key profiles. It is opt-in, and it keeps a copy of the login token.
-
Windows Terminal tabs and launchers
A profile gets a launcher and, where Windows Terminal is installed, a Windows Terminal tab of its own, with its own icon. Both clear other agents’ credential variables first and pin the profile’s own configuration. The box that makes them is ticked to start with when you add a profile.
Limit. A launcher for a profile that uses an API key carries no key: it falls back to the login its configuration holds. Use the pane in MaeVae, which adds the saved key; aider’s launcher reads its key when it runs.
-
Backup and restore
Quick settings writes a zip or a folder of your MaeVae data and restores it, also on another machine, with account logins and API keys only if you tick them.
Limit. There is no cancel once a backup starts.
-
Updating the agents
Quick settings runs each agent’s own updater from inside MaeVae, checks the agent afterwards, and offers Install for an agent that is missing.
Limit. One update runs at a time, and each updater gets five minutes before MaeVae stops it. At launch, in the Store release, Grok’s Install button shows you the command to run in PowerShell yourself instead of running it.
-
Local and other models
A Codex, aider, Qwen Code or Grok profile has an Endpoint field for a model server on your own PC or a provider such as Groq or OpenRouter. In a Codex, aider or Qwen Code profile, MaeVae asks that server which models it serves only when you click List models or, at launch, when you paste an address into the Endpoint section. At launch, you can paste a key or an address there and MaeVae fills in the profile.
Limit. Qwen Code uses an endpoint only when the key, the endpoint and the model are all set.
-
Themes, pets, chimes and the status line
Built-in light and dark themes and a custom-theme editor, a pane theme and an icon per profile, notification chimes, optional pets that react when an agent needs you, and a status line you can arrange.
Before you install
Two short answers. The FAQ has the rest in groups, and the Support page says what to send when something looks wrong.
What your PC needs, the agent’s own command-line tool and the account it signs in with, and the first start in four steps: What you need, and the first start, on the Download page.
How does MaeVae earn money?
MaeVae earns from its plans for the app and, later, from the MaeVae compute plans. It never resells Claude, GPT or Gemini usage. Each AI vendor’s rules are respected.
Who can I ask?
Write to support@maevae.com, or see the Support page and the FAQ.
One place to get it: the Microsoft Store.
From launch, the Store installs MaeVae and keeps it up to date. Your PC needs 64-bit Windows 10 or 11, Microsoft Edge WebView2 and at least one agent’s own command-line tool on your PATH.
WebView2 is built into Windows 11; some Windows 10 PCs do not have it. At launch, MaeVae says so when it starts and names Microsoft’s WebView2 page, where you can get it.
The Store listing is not public yet; the Store button already points to it.