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 08

Panes, groups and windows

Split the stage, keep several scenes on tap, put documents and terminals beside your agents, and drive it all from the keyboard.

Splitting the stage

The stage is a split tree, the way a terminal multiplexer is: split right, split down, and every leaf is one of four things — a session, a terminal, the workspace shell, or a document. Drag any divider to resize; double-click it to even the split out again.

  • ⌘DNew pane, splitting right
  • ⇧⌘DNew pane, splitting down
  • ⌘WClose the focused document; when it was the last one, the tile; then the pane
  • ⇧⌘⏎Zoom the focused pane to the whole stage, and back
  • ⌃`Flip the focused pane between chat and its agent's terminal UI
  • ⌃⇧`Open a fresh standalone terminal pane

Groups: several scenes, switched instantly

One split tree is not enough for real work, because real work has more than one shape. Groups are complete scenes — each with its own layout — switched from the strip in the title bar. Nothing is torn down when you switch, so a group is a set of views, never a container of processes.

  • A session can appear in as many groups as you like. Watch the same agent from the review scene and the debugging scene at once.
  • Closing a group closes the view only. Its sessions keep running and stay in the sidebar — Mirasim says so before it closes.
  • Each group tab shows what it contains, and pulses when something inside is running or waiting on you.
The group strip
The title-bar group strip with several scenes, the switch and new-group controls, and the pane stage below it.

The stripOne tab per scene. Each holds its own layout, and each tells you what is inside it. — this control is not on the captured screen.

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

  • ⌘TNew group
  • ⌃⇥Cycle groups (⌃⇧⇥ backwards)
  • ⌥⌘→Cycle groups with the other hand (⌥⌘← backwards)

Documents and terminals on the same stage

Files, diffs and terminals are tiles, peers of your sessions — so reading a file never hides the agent that wrote it.

A pane can hold more than one thing, switched by a tab bar in its own header — ⇧⌘T adds a tab, and drag reorders them. What makes this safe for sessions is that a tab you are not looking at keeps running: its live updates, transcript, scroll position and half-typed message are all still there, it still holds its row in the sidebar, and it still counts toward its group's badge. Switching tabs uncovers a session rather than reopening it.

Double-click a tab, or press F2, to rename it in place. Renaming a session's tab renames the session itself, so the new name follows it into the sidebar and everywhere else; a terminal or blank tab keeps its name on the tab. A terminal names itself after the first command you run in it.

When you open a document and the stage is already full, Mirasim asks rather than guessing: stack it into a document tile, or start a new group for it.

Terminals are first-class too. A session pane can flip to the agent's own terminal UI — the real TUIs of Claude, Codex and Pi GUI, preserved exactly, with their own authentication and their own rendering. A standalone terminal pane is just a shell in your workspace, for the commands you want to run yourself.

Drag a file or folder onto any terminal pane and its path is typed in for you, quoted so spaces do not break it — the same move you would make in a real terminal, and it works whether the pane holds an agent's TUI or a plain shell.

More than one window

One stage is not always enough screen. The workspace surface — file explorer, search, source control, artifacts and terminal — opens as its own window on the desktop, so you can put code on a second display while the agents keep the first. Artifact previews can do the same.

  • ⇧⌘EOpen the files and Git surface for the focused pane's workspace
  • ⌘FFind within the transcript you are reading — next, previous, and a match count

The command palette

⌘K opens one search box over three things at once: your sessions, the workbench's own commands, and the full text of every recorded transcript. It is the fastest path to almost anything, and the only navigation you need to memorize.

  • Sessions — ranked by recency, opened as a pane on ⏎.
  • Commands — new session, split right, split down, close pane, zoom pane, theme, language, settings, the files surface.
  • Full-text matches — every transcript scanned as you type, with progress while it runs and a hit count when it finishes. Space splits terms; "quotes" match exactly.
The palette, open over the workbench
The Mirasim command palette open above the workbench, with its input and result list highlighted.

The paletteOne box over three things at once: your sessions, the workbench's own commands, and the full text of every recorded transcript. — this control is not on the captured screen.

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

  • ⌘KOpen or close the palette
  • ↑↓Move through results
  • ⏎Open the selected result
  • ⎋Close

Something wrong or missing on this page? Tell us