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 15

Phone, chat and remote hosts

The Android companion, seven IM channels, and pointing the desktop at another machine.

Every surface Mirasim ships

Your desktop is normally the host and the source of truth. Everything else is a way into that host: paired Android clients and configured IM channels enter through their own transports, and the desktop can instead point at a self-hosted macOS or Linux server.

What each surface is for
Desktop
The primary multi-agent workbench and local host. Apple Silicon macOS DMG (macOS 13+), or Linux as an AppImage or .deb (x86_64 and arm64).
Android
Paired companion for sessions, prompts, decisions, notifications and transcript images. Signed APK, Android 8.0+.
iPhone
The same companion on iOS, distributed through TestFlight, Apple's beta channel, rather than the App Store: install TestFlight first, then open the invite from the download page. iOS 15+.
CLI / TUI
Built-in agent, transparent Claude/Codex launches, host control, accounts, diagnostics, automation. Standalone darwin-arm64 archive.
IM channels
Remote prompts, live progress, human-in-the-loop decisions and artifact replies: Telegram, Feishu, Slack, Discord, DingTalk, WeCom, Weixin.

The Android companion

Install the signed APK, pair it with your host, and you can read sessions, send prompts, answer the decisions that are blocking work, and get notified when something needs you — from wherever you are. Pairing is keyed: when the pairing code carries the host's end-to-end public key, the connection uses application-layer end-to-end encryption.

  1. Enable remote access on the host

    In Settings, Connection: this machine can stay local, be reachable on your LAN, or be reachable over the internet through a relay address. If the machine has a public address, enter it and clients connect directly instead.

  2. Pair the phone

    Scan the host's code from the app, or paste the connection code. The code contains the access token — share it only with people you trust.

  3. Use it as a companion, not a second workbench

    The phone is built for the moves that are worth making one-handed: read what happened, answer a question, queue the next prompt, unblock a decision.

Settings on the phone has a Run account row: which subscription account the conversations on that machine run under, each identity shown with its usage. Switching takes effect from the next turn — the turn already running keeps the account it started on. Adding an account means pasting a credential, which is a job for the computer; the phone only picks between the accounts you already have.

The phone can also update the computer it is paired with, which is worth knowing when the machine is at home and you are not. It asks before doing it, because applying an update restarts the app on that desk and drops this connection — the reconnect is how you know it worked.

A pairing is meant to outlast the network it was made on. The phone dials the LAN first when both are on it and falls back to the relay address elsewhere, and the host finds that address itself rather than asking you to configure one. When the phone temporarily cannot reach the machine, the panel says so and the link reconnects on its own — you do not pair again. The credentials behind it are stored encrypted and signed against the device they were issued to, so a copied credential does not work somewhere else.

IM channels

Connect a chat platform and your workspace becomes reachable from a conversation: send a prompt, watch progress, answer a decision, get artifacts back. Every supported channel uses a long-lived connection mode, so none of them needs a public IP or an inbound webhook.

Seven channels, each with its own credential shape
The Mirasim IM settings screen listing the supported chat channels and what each one still needs configured.

All sevenEach row states plainly whether it is connected and what is still missing — so a half-configured channel is visible rather than mysteriously silent. — this control is not on the captured screen.

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

What each channel needs
ChannelWhat you provide
TelegramA bot token from @BotFather; optionally a list of allowed chat IDs to restrict who can use it.
FeishuAn app's App ID and secret, the bot capability enabled, the IM scopes imported, and events plus callbacks both set to long-lived connection mode.
SlackSocket Mode enabled with an app-level token, plus a bot token and the message and mention event subscriptions.
DiscordA bot token with the message content intent enabled, and the bot invited to a server.
DingTalkClient ID and secret from an internal or chatbot app, with the chatbot capability on and events on Stream Mode.
WeComA Smart Bot's ID and one-time secret from the admin console; the channel then holds a long-lived WebSocket open.
WeixinA QR sign-in confirmed on your phone; the channel enables only after validation succeeds.

Each channel's setup panel walks its own steps in order and validates the credentials before it enables anything, so a mistyped secret fails at setup rather than three days later. You can also validate a channel at any time from the CLI.

Configure and check a channel headlessly
mirasim ui-cli --port 4970 im validate --channel feishu
mirasim ui-cli --port 4970 config set im.feishuAppId=cli_xxx im.feishuAppSecret=yyy

Using another machine as the host

The Connection page decides which machine this console controls: this computer, another on your LAN by address, or a remote one by connection code. The same page can also share this machine — enable server access, then hand the connection code to someone you trust.

You do not have to take the connection code apart yourself. Paste it into either field — address or token — and it splits into the two halves it carries. If it turns out to hold no directly reachable address, only the token is filled in and the page says which half is missing. Sharing a machine offers the token on its own as well, next to the code, because another desktop connecting in wants just that.

  • Remote entries authenticate with a bearer token and do not carry an Android pairing's E2E key — use HTTPS/WSS or a trusted network.
  • Selecting a remote host does not migrate the local host's pairings, IM configuration or schedules; those belong to the host that holds them.
  • Work follows the host: files, Git worktrees, session history, artifacts, recordings and usage data live where the host lives.

A Linux box over SSH

A Linux machine does not need Mirasim installed beforehand. Give the Connection page an SSH target and Mirasim probes the machine, copies the server build over, starts it there and tunnels it back — no ports opened on the remote side. Close the window and the agents on that machine keep running.

  • Sign in with your SSH agent, a password, or a private key. The agent option reuses your ssh-agent and ~/.ssh/config, so it behaves exactly like typing ssh in a terminal. A password is stored only on this computer, encrypted by the system keychain.
  • Hosts already in your SSH config are listed for you, so you do not have to retype names this computer already knows.
  • A bastion host and per-machine environment variables are available under the advanced options — the environment variables are passed when the server starts on that machine.
The same thing from a terminal
mirasim ssh ubuntu@dev.example.com   # connect, tunnel, stay in the foreground
mirasim ssh list                     # saved machines and their status
mirasim ssh stop dev.example.com     # stop the server on that machine

Something wrong or missing on this page? Tell us