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

Build the tools that help ideas meet reality.

We are a small team looking for unusually thoughtful builders who care equally about technical depth, product taste, and the people their work reaches. Show us something you shipped and tell us what you would change about it now.

Introduce yourself
InternshipOpen now

Product engineering intern

Build real features on the product, end to end. Product judgement expected, not ticket-taking.

What you'd do

  • Ship features in the build space itself: the agent panes, the editor, the artifact and task systems.
  • Take a rough goal, work out what it should actually be, and build it. The specification is part of the job.
  • Use Mirasim to build Mirasim, and bring back what got in your way. The friction you hit is the roadmap.
  • Put your own work in front of simulated users and act on the evidence that comes back.

What we're looking for

  • Strong engineering fundamentals. You can read an unfamiliar codebase and make it do something new.
  • Real product taste: you can say why one version is better than another, not only that it is.
  • Students and early-career builders welcome; a portfolio of things you actually shipped counts far more than credentials.
  • Comfortable working with coding agents daily, and sceptical enough to check what they produce.
Apply for this role
Full-time

Agent systems builders

Orchestration, tools, context and worktrees: the machinery that lets many agents work as one without stepping on each other.

What you'd do

  • Design how work is split across parallel agents, and how their results merge back safely.
  • Build the tool layer agents call: file systems, terminals, browsers, virtual machines.
  • Make long-running agent work observable: what it did, what it cost, where it went wrong.

What we're looking for

  • Systems depth: concurrency, process isolation, git internals, failure recovery.
  • Judgement about when to constrain a model and when to get out of its way.
Apply for this role
Full-time

Product engineers

Desktop, web and mobile, plus the work that makes hours-long agent runs feel immediate.

What you'd do

  • Own features across the desktop app, the companion apps and the chat surfaces.
  • Make slow work feel responsive: streaming, optimistic state, progress that tells the truth.

What we're looking for

  • You build the whole thing, interface through storage, and you care how it feels.
  • A high bar for detail under real conditions: slow networks, long sessions, big repositories.
Apply for this role
Full-time

Simulation researchers

Human behaviour, evaluation methodology, and evidence systems that keep product teams honest.

What you'd do

  • Design personas and scenarios that produce signal instead of flattery.
  • Build rubrics and scoring that can be wrong, and check them against held-out runs.
  • Separate genuine product findings from failures of our own execution.

What we're looking for

  • Grounding in behavioural or evaluation methodology, and the discipline to distrust a good-looking number.
  • Enough engineering to run your own experiments end to end.
Apply for this role
How we work

Small teams, direct ownership, ambitious prototypes, honest evidence, and a bias toward making the real thing. If none of the roles above is quite you but you think you should be here, write to support@mirasim.ai anyway.