Hand Over an AI Partner Task the Client Can Repeat

Start a MotiClaw handover with one small task the client repeats each week. Have the client run it on their own computer. By the end, they should know where to submit the input, where to check the result, and whom to contact when something fails.

When to use this guide

This guide is for AI consultants, forward-deployed engineers, and people setting up MotiClaw for a client. Keep the first handover to one task, such as turning meeting notes into follow-up items for review. Agree on owners and approval rules separately when the work needs several people or formal approvals.

Before you start

Install MotiClaw on the client's computer and complete Quickstart. Ask the client to prepare material they permit for this task and choose someone who can judge the result. Agree on actions that require approval, such as sending messages, changing official files, or starting further work.

1. Define the task being handed over

Use an ordinary document to record the input, expected output, result location, and reviewer. For example, turn meeting notes into a follow-up list with owners and deadlines. Mark missing information for confirmation and do not send the list to anyone yet.

Leave this task brief with the client. On later runs, replace the input while keeping the requirements available for reuse.

2. Confirm the partner and entry point together

Open AI Partners from the sidebar and find the partner whose role fits the task. Have the client note its name. Check its state, recent activity, and channels. Review progress before interrupting existing work, and investigate an Offline or Error state before continuing.

The cards bring roles, states, and channels together. During handover, ask the client to identify the card responsible for this task and find the agreed conversation entry point. If a channel still needs setup, finish the channel-management steps and verify that a test message can be sent and answered.

3. Review one result together

Submit the task brief and input through the agreed conversation. When the result arrives, have the client compare it with the source, check omissions and unresolved items, and save the accepted result in the agreed location.

If the output misses a requirement, record the specific difference and refine the task brief. Keep an accepted result as a reference for later runs. A reply alone does not establish that the work is complete.

4. Have the client repeat the task independently

Choose different input of a similar scope. Ask the client to find the partner, submit the task, and review the result without taking over for them. Observe where they get stuck and add the missing instruction to the handover notes.

If a key action still requires the delivery person, improve the instructions or setup and repeat the check. Confirm the handover when the client can complete this kind of task independently.

5. Leave maintenance and support instructions

Keep the partner name, entry point, task brief, accepted-result location, and maintenance contact in one handover document. Record the acceptance date and the actions that need client approval. Do not put passwords or secret keys in these notes.

Ask the client to show how they return to the partner card to check its state. After a failure, keep the message shown, inspect the state and original task result, and follow the repair page when needed. Stop repeated attempts and contact the maintainer if repair keeps failing or its impact is unclear.

Done when

The client has independently completed the task with different input, found an acceptable result in the agreed location, and identified the support route to use after a failure. Record the outcome and unresolved issues. Resolve issues that prevent everyday use before confirming handover.

Troubleshooting

• The demonstration works, but the client's run fails Compare the partner, entry point, and input used in both runs. Resolve the first difference before trying again.
• The partner is Idle, but the task fails Check the input, model setup, channel readiness, and failure message. Idle alone does not establish readiness for this task.
• The client wants many tasks at once Finish independent acceptance of the current task, then add tasks one at a time with a separate accepted result for each.
• The client is concerned about data leaving the device Explain the channels and models actually used before starting, select permitted input, and do not promise fully offline operation.

Related pages

Use Quickstart for initial setup and claiming a partner. Consult Connect and Manage Channels for an AI Partner for connection issues, or Check and Recover an AI Partner After a Problem for runtime failures.

What changed

Added independent client repetition, handover notes, and support steps. Removed promises of maintenance-free operation and automatic resolution of every problem.

Data boundary

Work data stays on your device by default; only channels you connect and model calls go online as the task requires.