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 Documentation

Chapter 18

Reference

The keyboard map, the whole ui-cli catalog, the config tree, ports, paths and platform requirements — in one place to look things up.

Keyboard map

Navigating

  • KCommand palette — sessions, commands, and full-text transcript search
  • NNew session pane
  • 1…⌘9 — open the Nth session as a pane, ordered by what needs you
  • 1…⌥6 — focus pane N in the current group
  • Cycle pane focus (⌘⌥→ forwards)
  • 1…⌥6 — focus the Nth pane on the stage
  • FFind in the transcript — with next, previous and a match count

Arranging

  • DNew pane, splitting right
  • DNew pane, splitting down
  • WClose the focused document, then its tile, then the pane
  • Zoom the focused pane, and back
  • TNew group
  • TNew tab inside the focused pane
  • Cycle groups (⌃⇧⇥ backwards)
  • Cycle groups, the other chord (⌥⌘← backwards)

Code and terminals

  • EThe files and Git surface for this pane's workspace
  • `Flip the focused pane between chat and the agent's terminal UI
  • `New standalone terminal pane
  • clickGo to definition in the editor

ui-cli command catalog

`mirasim ui-cli help` prints the authoritative catalog; this is the shape of it. Read-only commands are safe to run at any time; the acting ones have the same effect as clicking in the UI.

Read
CommandWhat it returns
stateHost bootstrap: version, working directory, platform
agents · clis · cli-toolsInstalled agents and their default; agent CLI versions; dev CLIs on PATH and their auth
sessions · history · queueSession rows; a session's settled turns; its queued prompts
catalog · commands · modelsComposer options for an agent; its slash commands; the BYOK provider/profile/binding layer
accounts · usage · relayStored accounts with quota; per-agent quota snapshots; relay sign-in and fallback state
workspaces · workspace gitRegistered folders; one folder's live Git status
mcp list · connectors list · skill listTool inventory at each scope
traffic stats · calls · metaThe local usage ledger, and its footprint plus export disclosure
system · permissions · resourcesHost telemetry; macOS permission states; a resource baseline
Act
CommandWhat it does
prompt · send · watch · stopStart or continue a run (blocks until the turn settles), stream snapshots, interrupt
answerAnswer an agent's interactive prompt — the scriptable “click Allow”
queue steer | jump | recall | moveHand a queued prompt to the running turn, cut the line, take it back, reorder
session new | open | rename | delete | resumeSession lifecycle, including printing the native resume command
workspace add | update | removeRegister, edit, unregister a workspace folder
account use | add | rename | token | removeMulti-account management; login / logout for the relay
provider · profile · model bind · model testThe BYOK layers, and one real round-trip to prove it
local probe | start | pull | pulls | deleteLocal inference backends and models
mcp add | remove | toggle | healthMCP servers at workspace or global scope
skill install | create | update | removeSkills at workspace or global scope
connectors install | enable | validate | auth | search | uninstallConnector lifecycle, including the official registry
im validate · codex-reset · restartCheck a channel's credentials; redeem a Codex limit reset; restart the host
Config and shell
CommandWhat it does
config get | set | applyRead the whole settings tree, set dot-paths, or converge onto a desired tree (--dry-run shows the diff)
screenshot · shellA PNG of the real app window; window and app facts
navigate · ui · dom · click · press · type · readRoute the UI, run a semantic UI command, list actionable controls, and drive them by text or selector
rawPost any protocol frame verbatim — total coverage escape hatch

The settings tree

`config get` returns one JSON tree covering every persisted setting. Secrets are deliberately not in it.

defaultAgent
The agent new sessions start with.
agents.<agent>.{model,effort,accessMode}
Per-agent default model, reasoning level, and whether it runs on a subscription or an API key.
relay.{enabled,threshold,on5h,on7d,reactive,always}
Quota-fallback behavior: whether it is on, at what usage fraction, per window, on refusal, or unconditionally.
computerUse.{browserEnabled,browserHeadless,peekabooEnabled}
Browser and screen automation toggles.
preventDisplaySleep · agentAutoUpdate
Keep the screen awake while the app runs; keep agent CLIs up to date.
workdir · workspaces[]
The default working directory and the registered workspace folders.
im.<channel credentials>
IM channel configuration, applied hot.

Paths, ports and requirements

On disk
PathHolds
~/.mirasim/setting.jsonHost settings — what the Settings UI and `config set` write
~/.mirasim/recordingsRaw model request/response recordings, subject to retention
~/.mirasim/capture.offCreate this file to disable recording from the next launch
~/.mirasim/tui/Live agent status Mirasim publishes into each agent's own status surface
<workspace>/.mirasim/schedules.jsonThis workspace's scheduled prompts
<workspace>/.mirasim/Workspace-scoped skills and configuration that belong in your repo
Ports ui-cli connects to
PortInstance
4970The installed desktop app's server
4950A development desktop instance's server
4939A server started by `mirasim serve` — its default port
(none)Spawn a private throwaway server for one command
Platform requirements
SurfaceRequires
DesktopApple Silicon Mac, macOS 13 Ventura or later — or Linux via AppImage / .deb (x86_64, arm64)
AndroidAndroid 8.0 or later
iPhoneiOS 15 or later, TestFlight beta
CLI / TUImacOS on Apple Silicon (darwin-arm64 archive)
Useful environment variables
MIRASIM_RECORD=0            # disable raw recording for this launch
MIRASIM_ANALYTICS=0         # collect and emit nothing at all — no product analytics
PI_GUI_CDP_URL=…            # attach browser automation to an external Chrome

Something wrong or missing on this page? Tell us