Team spaces

What a team space is

A team space is an environment Mirasim hosts for you. Its workspaces, sessions, terminals and files live there, so sessions keep running when you close your laptop, lose the network or switch devices, and every device sees the same thing.

Getting a team space

Team spaces come with Collaboration: Basic, Lite, Standard and Pro run in our cloud and come with credits, and the plan on your own computer is free (chapter 12 covers attaching it). Prices are on the Pricing page (mirasim.ai/pricing).

Your account has a team space allowance: how many of each spec you can create. Without one, “New collaboration space” under “Add a space” says “Your account has no cloud spaces available”; once all are in use it says “All available cloud spaces are in use”. For more members or more spaces, write to support@mirasim.ai.

Create one

1. Open the space menu

   Click the space name at the top of the sidebar. “All spaces” in the menu lists this computer, your team spaces, and any space or computer shared with you.

2. All spaces › Add a space › New collaboration space

   “Add a space” asks where it comes from. “New collaboration space” is the one we host for your team; it shows how many you have left.

3. Pick a spec

   “Collaboration space” or “Collaboration space · Mac”. A spec your account does not include says “Not enabled”. Once it is assigned, the team space appears in your space list.

4. Set up its environment

   Once it is ready, this window opens its Space settings › Environment & sync: its spec and runtime components, Agents and sign-ins, and its workspaces. You can come back to it from the space's settings at any time.

Under “Bring over from this computer”, “Sync” copies a local workspace up: its files, its sessions and the agents' memory. It is a one-time copy; the two sides do not sync afterwards, so move code between them with git. Credentials, ~/.ssh and ~/.aws are not copied.

Opening it

Click the space name at the top of the sidebar, then click a team space under “Recent” or on the “All spaces” page. It opens in its own window, or that window comes forward if it is already open. The window you clicked from stays as it was. The top of the sidebar shows which space a window is on.

If the connection drops, the window reconnects by itself and the space menu shows when it will retry; “Reconnect now” tries at once. The team space keeps running while you are disconnected.

Working in a team space

A team space window is the same workbench as on your own computer — sessions, panes, files, Git, terminals — only everything runs in the team space. A few things are specific to it:

• Coding agents such as Claude Code and Codex are already installed. Project toolchains are yours to install, from the team space's terminal.
• Running pages: when an agent or your terminal starts a dev server, its localhost port is listed under “Running pages” on the tool rail at the right of the window — click to open it in the preview. A localhost link in a conversation opens in the preview too.
• Remote desktop: “Remote desktop” on the same tool rail shows the team space's screen, for example for a browser sign-in inside the space.

Pushing code as yourself

Settings › Connections › Code hosting connects GitHub and GitLab. After that, agents and terminals in team spaces clone, pull and push as you. Each person connects their own account, and every git operation runs as whoever started it.

Models and credits

The team can use two kinds of models in the same space:

Setting up agents, keys and credits for the team is covered in chapter 11.

Where your data is

• Workspaces, sessions and the team's chat are stored in the team space.
• When a team space is reclaimed, everything in it is erased. Push code you want to keep to a remote repository.