Invite codes no longer gate your own accounts. Bring-your-own-account use is free for everyone; cloud Pro stays invite-only.Read the announcement
AnnouncementAugust 9, 2026

To everyone who's been following or using Mirasim:

Over the past few days, Mirasim ended up in front of a much bigger audience much earlier than we'd planned. We were still in private beta and, honestly, nowhere near ready for a wider launch.

Invite codes spread far beyond the small beta group we had planned for. In a very short window, we saw a flood of visits and test requests, along with some unusually aggressive, probing request patterns. Our capacity, reliability, and security systems weren't ready for that volume. Some of you ran into slow loading, failed requests, or Pro benefits that never showed up.

We're genuinely sorry for the rough experience. Whatever the source of the traffic, we should have been better prepared. That's on us, and our users shouldn't have to pay for it.

At the same time, you sent us a huge amount of honest, detailed feedback. A lot of issues that probably wouldn't have surfaced until a public launch showed up early. Thank you to everyone who took the time to try Mirasim, patiently share feedback, or report security issues responsibly.

Here's how access to Mirasim will work from here

Invite codes no longer limit connecting your own accounts to Mirasim — they only limit the cloud Pro service that Mirasim pays for.

Connecting and using your own accounts locally will be free for everyone. You'll be able to connect the Claude Code, Codex, and other model accounts or services you already use, then work across multiple models, Agents, and sessions in Mirasim. Mirasim won't charge for any of this. Third-party subscription or API fees will still follow each provider's own terms.

Cloud Pro access — where Mirasim covers the model usage costs to make things cheaper for users — will remain invite-only and roll out in batches as capacity allows. We'll keep sharing our progress and what opens next, so the rules stay as clear and transparent as possible.

A note on Pro benefits

  • The 1,000 beta users covered by our original promise will still receive one full year of Mirasim Pro. That promise has not changed.
  • Anyone who successfully registered during this wave after we had already passed the original 1,000-user limit will receive one month of Mirasim Pro. This is both to make up for the unstable experience and to thank you for trying Mirasim before it was fully ready.
  • If you've already registered or activated your access but your Pro benefits still aren't showing up, please don't try again. We have the records. We'll verify eligibility and apply the benefits in batches, then share the timing and start-date details.

How the rollout will work from here

Over the next week or two, we'll focus on adding capacity, fixing the entitlement system, tightening security, and working through your feedback one issue at a time. Mirasim remains open. Registration and local, bring-your-own-account access will stay available, while cloud Pro access will roll out in batches as capacity allows.

We're not trying to build yet another model aggregator. We want Mirasim to be an Agent workspace you can keep building in for the long run. Wherever the next leap in Agent capability comes from, you should be able to plug it into the same workflow, switch seamlessly, and use different Agents together. Once you've built something, you can put it in front of simulated users in a real environment and let evidence — not guesswork — tell you what to do next.

We want every leap in what Agents can do to become real leverage for everyone — so you spend less time chasing tools and more time building what you actually care about.

Models will change. You shouldn't have to start over.

Thank you for showing up before Mirasim was fully ready. From here, we'll put these promises into every fix and every update, and work to earn your trust by making Mirasim more stable and more reliable.

— The Mirasim team

Mirasim
Get helpGet Mirasim

Mirasim Documentation

Chapter 02

The workbench

One window, seven places. Step through the real interface and see which chapter covers each part.

Every part of the window

Mirasim opens as one window and everything happens inside it — no separate terminal, no second app for the code. Step through the figure below to see what each region is. Every stop links to the chapter that covers it, so this doubles as a table of contents you can point at.

The workbench, region by region
The Mirasim workbench, with seven regions highlighted in turn: the whole pane stage, the group strip, the session sidebar, the prompt composer, the model picker, the Git panel entry, and the tasks entry.

The windowSessions and workspaces down the left, the pane stage in the middle, the prompt box along the bottom, and the code surfaces on the right.Core concepts — this control is not on the captured screen.

The buttons in this panel work — click them to look around.

The code side hangs off the title bar

The panels on the right are not separate windows — they are toggles in the title bar. Git, Files, Artifacts and Tasks are four views of one right-hand dock, so opening one closes whichever was showing, and each opens against the workspace the current session belongs to. Press the same button again to put the panel away.

Left to right along the title bar
Search ⌘K
The command palette: jump to any session, workspace, file or command by name. It sits on the left, next to the version readout.
Sidebar ⌘B
Collapse or bring back the session sidebar on the left.
Usage
How much of your subscriptions and of the mirasim cloud quota is used. Click the cloud one to pin the account and usage card.
Git
Diffs, staging, commits and branches for this workspace.
Files ⇧⌘E
The file tree, with Git status shown on each row.
Artifacts
What runs produced: builds, screenshots, logs, exports and evaluation reports.
Tasks
Two pages: what is waiting on you, and the prompts that run on a clock. The badge is the count of the first.
Controlled browser
A live view of the browsers and emulators mirasim drives — still while idle, breathing while an agent works one.
Host
Which machine actually runs the agents — this Mac, another on your network, or a Linux box over SSH.
Appearance
Theme, language, density and window mode.

Something wrong or missing on this page? Tell us