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 17

Data, recording and privacy

Local-first is not network-free. Exactly what is stored, what can leave, and the two switches that stop it.

What lives where

The selected host owns your project files, Git worktrees, session history, local usage data, and most state under `~/.mirasim`; workspace-scoped configuration lives under `<workspace>/.mirasim`. Mirasim is local-first in the sense that your work is anchored to your host — and it is not network-free, because it talks to the model providers and channels you connect.

  • Your code goes to the model providers you configured, under your own accounts — and to any IM channels you enabled, which necessarily pass through their platforms.
  • Local models keep everything on the machine.
  • Provider and connector secrets use the OS keychain where one is available, with a sealed fallback where it is not. Some subscription-account and relay state stays in local Mirasim configuration, so protect your user account and ~/.mirasim.

Raw recording, on by default

On supported native passthrough routes, Mirasim records raw model requests and responses to `~/.mirasim/recordings`. This is the material the usage ledger is decoded from, and it is enabled by default — so it is worth knowing precisely, rather than discovering later.

What is stored
HTTP-layer facts plus the raw request and response bodies. With the default header redaction on, request headers are reduced to a safe whitelist; turning that off may retain credential-bearing headers.
What it never does
Block, mutate or break a live session. The recorder is off the hot path — if its bounded queue fills, it drops data and counts the drops rather than slowing the agent.
Coverage limits
Codex native capture requires OpenSSL. Profile-injected Claude and Codex turns currently stand down from capture, and some compatibility paths translate provider wires. Built-in and direct native-wire routes can still be captured.
Turn recording off
# for one launch
MIRASIM_RECORD=0 mirasim

# persistently, from the next launch
touch ~/.mirasim/capture.off
# …then relaunch. Remove the file to enable recording again.

Retention and the sweep

A recording-enabled host sweeps on startup and every 30 minutes thereafter. Raw upload is conditional on an authenticated export destination being configured at all.

What gets reclaimed, and when
DataRemoved after
Uploaded, complete recordings24 hours of inactivity
Recordings that were never uploaded30 days
Derived usage ledger entries90 days

Direct CLI-only use does not run that sweep; cleanup resumes the next time a recording-enabled host runs. The traffic monitor tells you the ledger's footprint and the current export disclosure, and can reveal both the ledger and the recordings in Finder — so "what is actually on my disk" is something you can look at rather than infer.

Remote hosts and pairings

  • A keyed Android pairing uses application-layer end-to-end encryption when the pairing code carries the host's E2E public key. Legacy or keyless pairings do not — re-pair them.
  • Manual remote desktop entries authenticate with a bearer token and carry no pairing E2E key. Use HTTPS/WSS, or a network you trust.
  • A connection code contains the access token. Treat it like a credential.
  • Selecting a remote host does not migrate the local host's pairings, IM configuration or schedules.

Something wrong or missing on this page? Tell us