Create a Mothership
- Click + next to Motherships in the left sidebar and pick an environment. The Mothership is created right away and opens.
- Rename it from its header. Until you do, your first message names it.
- Send it work in any of its chats. It replies right away with what it delegated, then acts on each result as it arrives.
create_replica MCP tool, set kind to mothership and use a personal API key.
Convert a workspace
To turn one of your own workspaces into a Mothership, right-click it in the sidebar and choose More → Make Mothership, or press and hold it in the mobile app and tap Make Mothership. You can also use the API or themake_mothership MCP tool.
- It keeps its chats, sandbox and history. Its next turn in every chat runs as the Mothership; a turn already running finishes as it started.
- Ships, archived workspaces and environment setup workspaces can’t be converted.
- A
delete_when_doneorarchive_when_doneworkspace switches to the default lifecycle so it isn’t removed after its next turn. - It can’t be turned back into a regular workspace.
Ship updates
After delegating, the Mothership replies and ends its turn. News from its ships starts a new turn, or reaches it mid-turn if it’s still working: a finished turn, or pull requests that are ready or need attention.Board
The Ships tab opens on the board, a live status page the Mothership keeps with every ship, pull request, Linear ticket, blocker and decision, grouped under Questions (only decisions it can’t make itself, with its recommendation), Ready to review, Working and Done. It handles ship updates by updating the board instead of writing in chat. Ships, pull requests and tickets on it stay current on their own. Click a choice or button to answer the Mothership, message a ship, merge a pull request or open a link. The item leaves the board right away, and the Mothership adds it back only if it still needs you. The derived list of ships and pull requests stays under All ships and pull requests, below the board.Chat
The chat shows only your messages and the Mothership’s final replies: answers, decisions only you can make, and links to finished work. To see its tool calls and ship updates, turn on Show activity in the new chat menu, or in the chat menu in the mobile app. A Mothership doesn’t write code itself, so it has no Files or Desktop pane, diffs, previews or editor and branch actions. Open a ship for those.Sidebar
The Motherships section lists your Motherships with their status: needs attention, working (the Mothership or any of its ships is working or following up pull requests), ready, or idle. Drag a Mothership to reorder the section, the same way as Pinned; the order syncs across your devices, and new Motherships join at the bottom. Motherships always stay in this section, so they can’t be pinned or moved to another one. Each Mothership gets its own icon when it’s created. To change it, click the icon in its header and pick another icon or choose Upload image (JPG, PNG, WebP or GIF under 5 MB). Remove image switches it back to an icon from the set.Slack
Give a Mothership its own Slack channel from the Slack button in its header, or with theadd_mothership_slack_channel MCP tool. Mention @Replicas in that channel to message it, and it replies under its own name and icon. See Mothership channels.
Linear
Send Linear tickets to a Mothership by telling it which ones you want, like “send me support-labeled tickets in the current REP cycle”, or from the Linear button in its header. Pick a team and, optionally, the current cycle, labels, a project and an assignee; a ticket must match all of them, and have at least one of the labels. New tickets that match, and tickets that start matching later (moved into the cycle, labeled, assigned), arrive once each with their description and the reason they matched. Finished tickets and tickets already delegated to an agent are skipped. If two of your Motherships match a ticket, the one linked first gets it.Sharing
Share a Mothership to run it together. Teammates you share it with see it in their Motherships section with its ships, get its notifications, and can reach its ships from the API and CLI. Ships still run as the Mothership’s creator.Notes
A Mothership keeps notes on its domain, ongoing work and decisions in~/.replicas/canvas/mothership-notes.md. It reads them at the start of each turn and updates them when something durable changes. The file survives the workspace sleeping, and you can read it in the Canvas.
Ships
Each ship is its own workspace with its own sandbox, built from its Mothership’s environment. To change that environment, open the Mothership’s info panel and click Change next to Environment. Ships you spawn afterwards use the new environment; existing ships keep theirs, and the Mothership’s own sandbox keeps the repositories it started with. A Mothership can also start a ship in another environment its owner can use, such as a backend-only one for a backend task: ask it to, or it picks one whose repositories and services fit the task. To send a kind of work to the same environment every time, add the rule to the system prompt of the Mothership’s environment, like “Start ships for mobile work in the mobile-ios environment.” Set it before you create the Mothership: an existing Mothership keeps the system prompt it started with. The Ships pane shows a ship’s environment on hover when it isn’t the Mothership’s. It receives only the task the Mothership writes for it, and it does not see uncommitted changes in the Mothership. In the sidebar, ships with open work are listed under their Mothership with their state (working, ready for review, or blocked) and open pull requests. A pull request is ready for review once its ship finishes its turn, even while CI runs; its checks show next to it. Click a pull request to review it. The Mothership’s row shows when a pull request is ready for review. A blocked ship is the Mothership’s to handle: the Mothership’s row only needs you when the Mothership itself asks you something. Under All ships and pull requests on the board, ships and their pull requests are grouped under Needs you, Ready to merge, Ready to review, Ships working, and Shipping (merged and deploying); hover a pull request to see its checks. Click a ship’s name to open it in the right pane, where you can follow its work, message it directly, or open its full workspace. On smaller screens, use the Ships button in the header. Replies to your own messages stay in the ship’s workspace. A Mothership can hold up to 20 ships that are not archived. The Mothership archives a ship once its pull requests are merged or closed, and messaging an archived ship restores it. Ships cannot spawn their own ships.Pull request follow-through
A ship that opens a pull request is not done until the pull request is ready. CI failures and review comments are still fixed automatically in the ship’s workspace, and the Mothership tracks them instead of calling the work finished. Once activity settles, the Mothership gets one report per ship:- Ready: CI passes, automatic fixes are done, and nothing but a human review or branch protection blocks the merge. The report summarizes what was fixed along the way.
- Needs attention: CI still fails with no fix running, the pull request is a draft, has conflicts or another merge blocker such as requested changes, or fixes have not settled within an hour. The Mothership messages the ship or asks you.
- Merged or closed: the ship’s task is done, and the Mothership archives it. The Mothership acts on it only when other work waits on it, such as starting the next task once a pull request merges.