Skip to main content
In Multitask mode the agent you are chatting with acts as an orchestrator. It hands each piece of work to a subagent, keeps its own context lean, and stays free for your next message. Multitask mode is available when Replicas enables it for your organization.

​
How to use

  1. Start your message with /multitask, or click Multitask in the prompt.
  2. Send anything you want done. For each request the agent spawns a new subagent, messages one that is already working, or reuses one that has finished.
  3. Keep sending requests. Each subagent’s result arrives in the chat when it finishes.

​
Subagents

Each subagent is its own workspace with its own sandbox, built from the same environment as its parent. It receives only the task the orchestrator writes for it, and it does not see uncommitted changes in the parent workspace. Subagents stay out of the workspace list. Click the Subagents button in the parent’s header to see each one’s state and pull requests, then pick one to open it in the right pane. There you can follow its work, message it directly, or open its full workspace. Replies to your own messages stay in the subagent’s workspace. A workspace can hold up to 10 subagents that are not archived. The orchestrator archives a subagent once its pull requests are merged or closed, and messaging an archived subagent restores it. Subagents cannot spawn their own subagents.

​
Pull request follow-through

A subagent 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 subagent’s workspace, and the orchestrator tracks them instead of calling the work finished. Once activity settles, the orchestrator gets one report per subagent:
  • 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 orchestrator messages the subagent or asks you.
  • Merged or closed: the subagent’s task is done, and the orchestrator archives it.
When every subagent’s pull request is ready, the orchestrator gives you one consolidated summary.

​
Tools

The orchestrator manages subagents with these tools from the Replicas MCP server. Workspaces get the server when they are created, so Multitask mode works in workspaces created after it was enabled. It is not available in Cursor chats.