MaeVaeMaeVae

One console. Every agent in its place.

MaeVae is a desktop console that runs your AI coding agents side by side and keeps each one in a pane and a profile of its own. Sign in once per profile, and nothing crosses between them: not the login, not the bill, not the memory.

Coming to the Microsoft Store Early access
Every picture of the app on this page is a rendering, not a screenshot, and the names, lines, figures and commands in them are examples. Three profiles are open: two Claude Code profiles with separate accounts, and one Gemini CLI profile that is waiting for an approval. The marks 1 to 5 tie the window to the details rendered below. In this rendering, amber marks an agent that is waiting for you, and nothing else, and the badges are rendered without their colors. The app grays a figure an agent does not report; this rendering writes n/a.

Launch . Available on the Microsoft Store first.

MaeVae drives the command-line tools you already have; it bundles none.

  • Claude Code
  • Codex
  • Gemini CLI
  • Qwen Code
  • aider
  • Grok
  • Plain shell

In one minute

For Windows 11 and Windows 10, 64-bit, from the Microsoft Store.

A live HUD shows each agent’s model, cost, tokens and context, and an attention queue tells you when an agent needs you.

Every feature, on the features page.

  • 6 agents

    Claude Code, Codex, Gemini CLI, Qwen Code, aider and Grok, and a plain shell with no agent in it.

  • 3 agents in Restricted mode

    Claude Code, Codex and Gemini CLI: mark a profile Restricted and MaeVae boxes its agent to its project folder.

  • 4 badge colors

    on every agent pane’s Isolation dot: green, amber, red or gray, for whether the profile is still its own world.

  • 0 open ports

    MaeVae’s window talks to its core through local calls, not a network server.

Restricted mode keeps an agent inside its project folder.

Mark a Claude Code, Codex or Gemini CLI profile Restricted and MaeVae boxes that agent to the one folder it is meant to work in. It is one choice per profile, made when you create it or later in its editor.

What it does

  • Claude Code is denied reading or editing the folders beside the project folder and the configuration of every other profile, and is denied git push, wrangler, deploy and publish.
  • Gemini CLI asks before every tool call, keeps its file tools to the project folder and is denied push and deploy; a shell it runs can still read outside the folder.
  • Codex keeps its writes to the project folder with its network off, and asks before a push or a deploy; it can still read anywhere.
  • For Claude Code it also switches off the option that skips permission checks, so starting the agent with that flag cannot undo the box.
  • It needs a real project folder: an existing folder that is not your Windows home folder.
  • If the box cannot be written when you save, for example because the settings file is locked, MaeVae saves the profile as Trusted and tells you which file to fix.

Restricted mode on the features page. Restricted mode, step by step, in the guide.

New profile sets Capability to Restricted; later the agent refuses git push itself, because its own settings now deny it. This page marks that refusal Blocked.

Where it stops. 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.

Container mode: an agent in a container of its own. in development

Container mode is not in the app today, and it has no date.

An agent will run inside a container you choose, Podman, Docker or another, with only its project folder mounted.

Restricted mode keeps an agent inside its folder by rules; Container mode will run it inside a container.

  • It is being built to work with the container tool you pick, Podman and Docker Desktop first, through one Docker-compatible driver.
  • Only the agent’s project folder will be mounted in the container; no other folder of yours will be.
  • Inside that folder the agent will be able to change every file, as it can in its project folder today.
  • Each profile will have a login folder of its own for the agent in its container.
  • It will need a container tool, such as Podman or Docker Desktop, installed on your computer.

How much of your computer stays out of the container’s reach on Windows is being measured, and this page will say it plainly when it is known.

Container mode on the features page.

Every profile is its own world. MaeVae checks that it stays one.

A profile’s configuration folder and project folder belong to it alone. MaeVae checks that nothing inside them points outside, that nothing arrives through the vendor’s account channel without your click, and that nothing appeared that you never approved. When something is off, Seal profile puts right what it safely can and tells you what to do about the rest.

The badge

Every agent pane’s header carries an Isolation button with a dot. Click it and the report opens in the pane’s place; the profile editor’s Isolation section shows the same report.

  • Isolation Isolated, green: no rule failed or warned, and nothing is installed that you have not approved.
  • Isolation Drift, amber: something you never approved appeared, or a rule warned.
  • Isolation Breach, red: a Boundary, Reference or Inbound rule failed.
  • Isolation Unchecked, gray: never checked, or no approved set yet.

A plain shell profile runs no agent, so its pane has no badge.

Isolation on the features page. Isolation, step by step, in the guide.

A click on the badge opens the report in the pane’s place; Check isolation finds a plugin you never approved, and the report turns to Drift.

Seal, approve, check all

  • Seal profile

    Applies every safe fix at once and reports the rest with what to do. Every write stays inside the profile’s own configuration folder, and Seal never approves anything.

  • Approve current set

    Makes what is installed now the approved set, for a plugin you installed on purpose. A new profile reads Unchecked until you approve its set once.

  • Check all profiles

    In Quick settings, checks every profile inside its own walls, then whether a path in one profile reaches into another profile’s configuration folder.

Where it stops. The check reads the manifests and channels MaeVae knows for the vendor versions it was measured against. A vendor can add a new channel between releases, and an Inbound row is only as current as that measurement.

Each pane is pinned to its own profile.

A profile is one identity: one agent, one account, one project folder. MaeVae gives each profile its own isolated configuration folder, so logins, billing and memory never mix.

You sign in inside the pane, in the agent’s own login, once per profile. The rail groups your profiles by agent and shows each one’s account label under its name, so two accounts of the same agent read apart at a glance.

For Claude Code, Codex and Gemini CLI, MaeVae checks the account label against the account the pane is really signed in to. A pane whose login differs shows a banner with a one-click Use this login as the label.

aider has no login of its own: its API key is the account, and you set it in the profile.

More than one Claude account on one profile

One Claude profile can hold more than one saved login. In the profile’s editor, Save this login keeps the current one, Add another account signs you out so you can log in as someone else while the old login stays saved, and Switch brings a saved one back. Add another account and Switch close the profile’s open panes, swap the stored login, then reopen a pane for you.

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. Removing a saved account takes two clicks and deletes that stored token for good.

MaeVae closes only its own panes. If a Windows Terminal tab or a launcher of that account was active recently, it warns you before it swaps the login, so you can close that session first.

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.

Profiles and the account switcher on the features page. A second account of one agent, in the guide.

With the profile’s pane running, Switch asks Restart pane? first; the second click swaps the stored login and the pane restarts on the other account.

A live HUD for every pane.

Each pane can carry a live strip with the model, cost, session time, tokens, quota and context, as far as each agent reports them; one tick in Quick settings turns it on. The pane header mirrors it, and a usage dashboard shows the same for each profile.

Limit. The figures are read from each agent’s own files on disk, and Claude Code’s quota from the vendor’s usage endpoint; they are not a bill.

The HUD and the usage dashboard on the features page. The HUD, step by step, in the guide.

Claude Code reports every figure; the header and the strip count up to them as the pane works.

Where the figures come from

  • Claude Code

    The hud button on the profile’s rail entry turns the HUD and the attention queue on. MaeVae registers itself as that profile’s status line and hook commands, merged into the profile’s own settings without overwriting anything you added.

  • Claude’s quota

    The 5-hour and weekly quotas are read with the profile’s own login from the vendor’s usage endpoint, which is not an official one. They are cached for about a minute, and the reading stops quietly if the endpoint fails.

  • The other agents

    Codex, Gemini CLI, Qwen Code and Grok need no setup: MaeVae reads the session files each agent already writes in its own profile folder, read-only, from the first turn. aider is read from the chat history it writes in the project folder.

  • The gauge and the strip

    The context gauge in the header turns amber above 65 percent and red above 85. In Quick settings the strip’s tick is named Chrome HUD, and its figures can be arranged per profile. The renderings here show the strip on.

What each agent reports

Claude Code reports every figure; Codex, Gemini CLI, Qwen Code, Grok and aider each leave out some of the cost, the quota and the context gauge. What each agent reports, side by side, on MaeVae and the AI vendors.

In the app a figure an agent does not report is grayed, and hovering it says why: the agent reports no such figure, the pane has written nothing fresh yet, or MaeVae has no data source for that kind of pane. The renderings on this page write n/a. Why a HUD figure is missing, in the FAQ.

When an agent needs you, its pane lights up.

When an agent needs an approval or finishes a turn, MaeVae lights its pane, badges the tray icon, and can raise a Windows notification and a chime. While the agent is waiting, you can approve or deny from the pane’s header.

approve sends Enter to the pane, which picks the option the agent has highlighted; deny sends Esc. A request for approval lights the pane amber and a finished turn lights it green, and the profile’s light in the rail does the same.

For Claude Code, Gemini CLI, Grok and Qwen Code, the buttons appear on the exact pane that asked. Codex’s requests are matched to the profile rather than to one pane.

How a pane signals is yours to set in Quick settings, or per profile: a steady or pulsing ring, a flash, a corner dot, a tint, a blink, or nothing; a color per state; and a Windows notification per state if you want one.

The attention queue and the tray on the features page. When an agent needs you and Close to the tray, Quit, Panic stop, in the guide.

Gemini CLI asks to run npm install: the pane lights amber, and approve and deny appear in its header.

One step inside Codex and Gemini CLI

MaeVae writes its hook into the profile’s own configuration, but both agents guard their hooks. In Codex, type /hooks in the pane and trust MaeVae’s two hooks; Codex asks again whenever the hook text changes, for example after a MaeVae update. Gemini CLI lists them under /hooks panel, enabled by default, and loads them once you have trusted the project folder it opened in. Close and reopen the pane after turning the glow on.

Grok and Qwen Code need no such step. aider lights only green, when it is back at its prompt after a reply; it never asks for an approval through MaeVae.

Limit. Until the one-time trust step is done inside Codex or Gemini CLI, that profile’s pane never lights or chimes.

Close the window. The sessions keep running.

  • To the tray

    Closing the window hides MaeVae to the tray, and the agents keep working. When one needs you, the tray icon takes an amber dot and, while the window is not in front, MaeVae can raise a Windows notification.

  • A chime

    A chime, chosen per profile, sounds once per event through Windows audio, even with the window in the tray; one switch in Quick settings mutes them all.

  • Quit

    Quit in the tray menu ends the sessions. Launching MaeVae again brings the window that is already running to the front.

Limits. Windows decides whether a notification is delivered. With the window in the tray, a chime can arrive up to about a minute late. An agent started outside MaeVae, in a Windows Terminal tab, does not chime; its profile’s pane can mirror its state with an “· outside” mark, without approve and deny.

With the window in the tray, the tray icon takes an amber dot and Windows shows MaeVae’s notification.

One working session, start to finish.

Three agents in one window, in under forty seconds. Every step but one is something the app does today; one pane filling the window is new at launch. The chapter marks under the rendering jump to any step.

Layouts and keys on the features page. Work side by side, in the guide.

One session: three profiles open, an approval, a refused push, a plugin found and approved, the grid, one pane filling the window, and the window to the tray and back with the agents still at work.

What happens in it

  1. Three profiles open. A click on a profile in the rail opens its pane, and a second and a third follow, each on its own account and folder. The top bar counts them. On a wide screen the panes stand side by side and, once two are running, the Broadcast box appears; on a phone the rendering stacks the panes and leaves the rail out.
  2. The HUD counts. Each header and each strip fills with that agent’s own figures.
  3. An approval. Research asks to run npm install. Its pane lights, its rail light turns amber and the tray icon takes a dot; approve, in the pane’s header, answers it.
  4. A blocked push. Side project is Restricted, so its agent refuses git push.
  5. Drift. Client work installs a plugin. A click on its Isolation badge opens the report, and Check isolation finds the plugin: the report turns to Drift, and once the report is closed the badge in the pane’s header is amber. A second click opens the report again; Approve current set accepts the plugin, and the badge is green again.
  6. Grid. On a wide screen the grid button in the top bar sets the panes two by two, with the third across the row; on a phone the rendering keeps them stacked.
  7. One pane fills the window. New at launch: the fill button in Client work’s header hides the other panes without closing them, and Show all (3) in the top bar brings them back.
  8. To the tray and back. The window’s close button hides MaeVae to the tray while the agents keep working; Show MaeVae in the tray menu brings the window back with their work moved on.

Also in the app

  • Layouts

    Columns, rows or a grid from the top bar, with gutters you drag to resize; new at launch, one pane can fill the window and Show all brings the others back. More on layouts

  • The command palette

    Ctrl+K opens a searchable list of actions: open a profile, jump to a pane, change the layout or the theme, open the usage dashboard. More on the command palette

  • Broadcast

    With two or more panes running, the Broadcast box sends one line to every open pane at once, Restricted ones included. More on Broadcast

  • Alt keys

    Alt+1 to Alt+9 move keyboard focus to a pane; new at launch, Alt+0 makes the focused pane fill the window. More on the keys

  • Windows Terminal tabs and launchers

    A launcher and a Windows Terminal tab for each profile, pinned to its own configuration, that clear other agents’ credential variables first. More on tabs and launchers

  • Backups

    Quick settings backs up your MaeVae data to a zip or a folder and restores it, on another computer too; logins, usage history and API keys only if you tick them. More on backup and restore

  • Updating the agents

    An update button for each installed agent and Update all installed, each running the agent’s own updater, one at a time. More on updating the agents

  • The Endpoint field and List models

    Codex, aider, Qwen Code and Grok profiles have an Endpoint field for a model server on your PC or a provider. For Codex, aider and Qwen Code, List models asks that server which models it serves, only when you click it or, at launch, when you paste an address. More on local and other models

  • Themes, pets and chimes

    Light and dark themes and a theme editor; a pane theme, icon, color and chime per profile; and optional pets that react to the agent. More on themes, pets and chimes

  • Panic stop and Close all

    Panic stop, in the top bar and the tray menu, stops every agent in MaeVae’s own panes at once; Close all asks first and says how many panes go. More on the tray and Panic stop

  • Redraw

    If a resize leaves stray characters on screen, the Redraw button in the pane’s header nudges the program to repaint. More on Redraw

  • The usage dashboard

    One table of every profile’s model, cost, tokens, context and quota figures, with a total row, measured from the agents’ own files. More on the usage dashboard

From install to the first pane

  1. Install an agent’s own tool

    Install the command-line tool of at least one agent, as its vendor publishes it, and check that it answers in a terminal: claude --version, for example. MaeVae marks an agent it cannot find on your PATH “(not installed)” and cannot start a pane for it until the tool is installed and MaeVae is reopened. More in the guide: What you need.

    Later, in MaeVae’s New profile, an agent whose tool is not on your PATH is marked (not installed), with its install command one click away.

  2. Install MaeVae and add a profile

    Install MaeVae from the Microsoft Store once the listing is public; the Store installs it and keeps it updated. Then + Add profile asks three things: an agent and a name, an account, and a project folder. MaeVae gives the profile its own isolated configuration folder. More in the guide: Make your first profile.

    Three short steps, an agent and a name, an account, a project folder; Create & open starts the pane.

  3. Sign in inside the pane

    The first start runs the agent’s own one-time setup in the pane. For Claude Code that is a theme, a question whether to trust the folder, then its sign-in in your browser. After that, the pane starts the agent straight away. Add more profiles and arrange them side by side. More in the guide: Sign in inside the pane.

    The first start runs the agent’s own setup in the pane, once: a theme, a folder-trust question, then its sign-in.

What it never does

  • It holds no agent account of its own. Each profile uses your own account with the agent’s vendor, and you sign in inside the pane.
  • This website sets no cookie. It runs no tracking script.

Coming next

One more thing is in development. It is not in the app today, and it has no date.

  • macOS and Linux in development

    MaeVae runs on Windows 10 and 11 today. Versions for macOS and for Linux are next.

Questions people ask

Two questions this page leaves open, in short. Each links to its full answer.

What leaves my computer?

The traffic comes from things you start or switch on. The agents talk to their vendors. The HUD’s quota reader asks the vendor’s usage endpoint with the profile’s own login. List models asks the endpoint you typed, when you click it, and updating or installing an agent runs that agent’s own updater or install command.

At launch, pasting an address into a profile’s Endpoint section also asks that server for its models, and Grok’s Install button shows its command for you to run instead of running it.

The FAQ’s full answer on what leaves your computer. The app’s network activity, on the privacy 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.

The FAQ’s full answer on how MaeVae earns. The statement on MaeVae and the AI vendors

All questions and answers

The FAQ’s ten groups:

MaeVae is coming to the Microsoft Store.

Launch . Available on the Microsoft Store first.

At launch

  • Claude Code, Codex, Gemini CLI, Qwen Code, aider and Grok side by side in real terminal panes, each pane on its own isolated profile.
  • Restricted mode for Claude Code, Codex and Gemini CLI: a guardrail that keeps an agent to its project folder.
  • The Isolation check, with its badge on every agent pane.
  • A live HUD with each agent’s model, cost, tokens, quota and context, as far as the agent reports them, and the attention queue for an agent that needs you.
  • No telemetry and no open ports.
  • New at launch: your panes come back where they were after a restart, and wait for one click to start.
  • New at launch: quota warnings at a line you set, 85 percent by default, and a notice when a spent quota renews.
  • New at launch: in a profile’s Endpoint section, paste a key or an address and MaeVae fills in the profile.

See the plans and prices

MaeVae is in early access. The plans and prices are on the pricing page. Early-access users hear first when selling starts.

Coming to the Microsoft Store Early access

The Store listing is not public yet; the Store button already points to it.