Edit in New Task

​

What it is

• Continue work in a clean task. The original task has a long history, and you want to start the next round of changes with a short, focused context.
• Edit one website in several tasks at the same time. For example, one task updates styles, a second task updates page content and a third task adds a feature.

​

How Edit in New Task differs from Make a Copy

​

How to use it

​

Open a website in a new task

1. Open the website dashboard.
2. Click More (the … icon) in the dashboard header.
3. Click Edit in new task.

1. Go to your Library.
2. Find the website or app.
3. Open the three-dot menu on the item.
4. Click Edit in new task.

1. Open the Project that contains the website.
2. Find the website card.
3. Open the menu on the card and click Edit in new task.

​

Describe the change and send

1. In the new task, describe the change that this task must make. Give a self-contained brief, because the new task does not see the chat history of the original task.
2. Send the message.

Update the pricing page only.
Change the Pro plan to $24/month and add a yearly option at $240/year.
Do not change the header, the footer or other pages.

​

Start a parallel task from a suggestion

• Click Start in new task to open the same project in a new task.
• Click Not now to continue in the current task.

​

Get the latest changes from other tasks

You’re viewing an older version. This site has new changes in [task name] — sync to update this preview.

1. Click Sync to load the latest version into this task.
2. To see which task made the change, click the task name in the message.
3. If you click Dismiss, you can sync later from Version history.

​

What you need to know

• All tasks edit one project. Changes from every task go into one version history. Each saved version records the task that created it.
• Code changes merge automatically. Before each edit, Manus loads the latest code. Before each saved version, Manus places its changes on top of the newest version. If two tasks change the same lines, the agent resolves the conflict. Manus does not overwrite another task’s work.
• Changes from other tasks are intended. The agent treats changes that it did not make as edits from another task. It does not undo them.
• The database is shared and has no conflict protection. Code conflicts are handled, but data is not. If two tasks change the same data or the same tables at the same time, one change can overwrite the other.
• Publishing applies to the whole website. If you publish from one task, the website is live for all tasks. You do not need to publish again from each task.
• One task can edit one website. If you attach more than one website to a task, only one opens for editing. The others open as read-only references, and Manus does not save changes to them.
• Only the website owner can use Edit in New Task. Project collaborators who are not the owner see the message “Only the project owner can edit.”
• The new task does not see the original chat history. Put the context that the task needs in your message or in the Project.
• Each task uses credits. Several tasks on one website can use more credits than one task.

​

Tips

• Give each task a different goal. For example, one task for styles, one for content and one for a single feature. Separate areas cause fewer conflicts in the same files.
• Change the database from one task at a time. Plan schema changes and data imports in one task. Tell the other tasks not to change the database.
• Sync before you review. Click Sync before you check the preview, so that you see the changes from all tasks.
• Use a Project for shared rules. Start Edit in New Task from the Project website card. Then every task follows the same brand, copy and code rules.
• Use the main task to coordinate. Ask the main task to check which tasks are finished and to review the combined result. For more information, see Parallel Tasks.
• Use Make a Copy for risky experiments. If you do not want a change to reach the live website, make a copy instead.

​

FAQ