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

WritingAugust 13, 2026

Cheap per call, expensive per hour

Every individual model call looks too small to matter. An afternoon of four agents does not. The gap between those two facts is where budgets quietly go.

5 min read

Why the spend is invisible until it is large#

Per call, an agent is trivially cheap — small enough that nobody checks. Per hour, with several agents each re-reading files, retrying, and carrying long context, it is not. Neither number is hidden, exactly; they are just kept somewhere you never look, in units that do not add up to a question you would ask. "Was this week expensive?" is not answerable from a list of API calls.

The provider dashboard does not close the gap either. It knows what your account spent; it does not know which agent, which repository, or which session spent it. When the bill is higher than expected, that is precisely the breakdown you need — and precisely the one nobody has.

One ledger, on your machine#

Because every model call already passes through a local proxy, it can be written down where it happens. Mirasim keeps one ledger of every call — tokens, cache hits, estimated cost — decoded and computed on your machine and nowhere else. Pick a window (today, 7, 30 or 90 days) and it leads with the numbers that answer the question directly.

  • Calls, total tokens, output tokens, cache hit rate and estimated cost — each shown against the previous period, so "more than usual" is a fact rather than a feeling.
  • The same window broken down by agent, model, account, workspace and session. This is the part a provider dashboard cannot give you.
  • How much of the work went through the quota fallback instead of your own subscription. If that share is high, the bottleneck is your plan, not your prompts.

What it changes in practice#

The useful outcome is not frugality, it is attribution. Once spend is broken down by model and by session, the expensive habits become visible and specific: one long-context loop that re-reads the same tree every turn; a reasoning level left high on a task that never needed it; a cache hit rate that dropped because a prompt now changes every call.

It also makes model choice an empirical decision rather than a vibe. Sessions carry their own model and reasoning level, so the cheaper option is one switch away — and after a week you can look at the ledger and see whether the cheaper one actually cost you anything in results.