01 / Choose one useful first assignment
Start with something as small as turning supplied project notes into tomorrow's work plan. A bounded task gives you a way to see what Muse understood before expanding its responsibilities.
This guide refers to Meta's personal agent Muse. It is an original manual handoff method based on documentation checked on October 5, 2026. We have not tested it in a signed-in account or verified a complete cross-platform memory importer. The templates below do not claim that such an importer exists.
02 / Confirm what your account can actually do
Meta describes connected apps, background work, and action approvals as Muse capabilities. That does not establish which accounts you have connected or what your current session can access. Check the functions shown in your own account.
Choose a familiar deliverable: an action list from meeting notes, a project summary, or an email draft from messages you supply. Specify what the result should contain and when work should stop. ‘Manage all my work’ leaves too many decisions unresolved for an informative first check.
Meta: Muse capabilities, permissions, and background tasks ↗
03 / Send your preferences and project context separately
First provide your communication habits, time zone, and action boundaries. Then provide the project's goal, current state, materials, and unanswered questions. Use the personal brief and project card from the first guide.
‘Do not invent missing information’ is a general working preference. ‘This client's budget is unconfirmed’ is a project fact that can change. Keeping the two distinct makes future corrections easier.
If your interface supports file uploads, attach the relevant material. Otherwise paste a focused excerpt. A reference to a filename or a path on your computer is not proof that a cloud assistant can read it.
04 / Copy this first-handoff request
Replace the fictional project details with your own. Read Muse's first response for what it knows, what it lacks, and what it proposes to do. If you have not supplied the draft, it should not claim to have evaluated a particular page.
Help me prepare the Orange Leaf workshop proposal.
I will provide my personal brief, project card, and relevant materials.
For this first round:
1. Separate the lasting preferences from this project's requirements.
2. List the materials you can actually access and those you cannot.
3. Draft up to three useful next actions from the supplied evidence.
Current state: Six pages are needed; the first four are drafted.
Budget: Unconfirmed.
Acceptance: Each action names its evidence and any input needed from me.
Scope: Analyze and draft only. Do not send messages or edit external data.
Do not create recurring jobs in this round.
If something needs a feature or permission enabled, explain its purpose.
Say explicitly if you cannot confirm that information was saved for later.05 / Connect an app when the task needs it
A task based entirely on pasted notes may need no email connection. When you want Muse to retrieve a project's updates itself, inspect the connection and authorization options your account offers.
Record the account, the data required, and whether the work involves reading or writing. Use narrower options when available. If the offered access is broader than you want, continue supplying selected material manually.
Meta documents connection permissions and activity review. Match those actual controls to your intended scope. A sentence in a prompt is not an access-control setting.
Meta: Muse capabilities, permissions, and background tasks ↗
06 / Check a small result before extending the scope
Provide one confirmed fact and one explicitly unknown item, then ask for a short client-update draft. Check the structure and tone, the latest project state, whether the budget remains unknown, and whether it identifies inaccessible materials. Confirm that it stayed within drafting permission.
If it invents a budget, correct that particular problem and try a similar task. Changing many requirements at once makes it harder to know which adjustment helped.
If you want preferences to apply across conversations, repeat a suitable task in a new ordinary chat without supplying the same answers. Correct behavior in the first handoff only establishes what happened in that conversation.
07 / Specify recurring work before creating it
Meta says Muse can continue background work after the app closes. Before setting up a monitor, define its scope, cadence, notification conditions, and end date.
Treat this template as a proposed task specification. Ask which parts are supported, then verify creation through the actual task record. Sending the text alone is not evidence that a schedule exists. If a condition is unsupported, narrow the workflow or use the controls that are available.
Meta: Muse capabilities, permissions, and background tasks ↗
PROPOSED PROJECT FOLLOW-UP
Scope: Updates about the Orange Leaf proposal only.
Check: Weekdays at 09:00, Asia/Shanghai.
End date: [actual date]; stop after that date.
Notify when: A deadline changes, key material is missing,
or a decision from me is needed.
No material change: No routine progress notification.
Duplicates: Notify once per change unless its status changes again.
Allowed actions: Summarize; sending externally still needs my review.
First explain the supported plan and limitations; do not claim creation.
After I confirm creation, show the task name, status, and next run
so I can verify the actual configuration.08 / Close the loop with your previous assistant
List the reminders and monitors still active in the old tool. Compare them with the new task records, then decide which to keep, move, or pause. Two assistants should not independently send the same routine message.
A completed first handoff leaves three things you can inspect: approved background material, a small result that meets your criteria, and an explicit record of permissions and task state. Keep the previous setup available as a return path while you resolve gaps. The next guide explains how to adjust notification frequency and stop repetitive updates.