Run a Daily Check from AI Partners

Checking every AI partner one by one becomes slow as the team grows. AI Partners brings roles, runtime states, recent activity, channels, tasks, and skills into one view, so you can run a quick check before starting the day.

This check has one finish line. Find the partner that needs attention most, complete the matching action, and confirm that it can continue working.

Before you start

Open AI Partners from the MotiClaw sidebar and wait for the list and runtime states to load. When a partner is running important work, inspect recent activity first. Do not use a health check or duplicate submission as a progress reminder.

1. Scan the team in Patrol mode

Choose Patrol and review the counts for Working, Idle, Offline, and Error. Start with errors and unexpected offline states. Review recent activity for working partners, and keep idle partners available for new work.

Runtime state is an operating signal. It helps you decide who to inspect first, while the original task, file, or channel remains the place where you verify the result.

2. Narrow the list with search and filters

Search by partner name, ID, or role, or filter by runtime platform. With a larger team, narrow the view to the roles you will use today instead of inspecting everyone.

For a new handoff, start with a matching role, then check its runtime state, channels, and skills. Switch to Manage only when you need to change order, persona, or custom status names.

3. Open one partner and choose the next action

Choose one action from what the card shows.

• Idle with setup ready Open the workspace, or use a verified default channel to hand over one clearly scoped task.
• Working Review recent activity and the original task. Keep waiting while progress continues. Run a health check only when activity has stopped for an unexpected amount of time.
• Channel needs setup or confirmation Open channel management, finish the remaining step, then send one low-risk test message.
• Offline or Error Open Health Check and review the framework, model, channel message path, and recent reply results. Then fix the relevant setup, run a repair, or choose another partner.

A health check reports the current condition. Review the impact scope before repair because other partners may share the same runtime.

4. Complete one corrective action

Handle only the issue you selected. Finish the channel when setup is incomplete, prepare the model when it is unavailable, or wait and choose another partner when the original task is still running. When several issues appear, begin with the one blocking the current task.

Keep the check result when a repair is needed and follow the action shown on the page. If the page says that the repair affects the same framework or several partners, confirm that no important task is running first.

5. Verify the result where the work happens

After the action finishes, review the partner state again and run a small verification in the matching workspace, file, or channel.

• After connecting a channel, confirm that a test message can be sent and received.
• After recovering an error, run Health Check again and complete one low-risk task.
• After handing over new work, inspect the real result in the agreed location. A Working state does not replace acceptance.

Done when

You found one partner that needed attention today, completed one explicit action, and verified the result where the work belongs. Notices that do not affect current work can wait for another check. You do not need to clear every item at once.

Troubleshooting

• A partner stays Working Inspect recent activity and the original task result. Keep waiting while updates continue. Run a health check when activity has stopped and no result appears, and avoid duplicate submissions.
• A partner is Idle but cannot start Check its model, channel, skills, and input. Idle only means that no task is running.
• The partner still shows Error after repair Run the check again and keep the failed item. Stop repeating the repair when its scope is unclear or it fails more than once, then use another partner for urgent work.
• The list is difficult to scan Search by role and filter by platform. Use Manage to save a long-term order when needed.

Related pages

See Check AI Partner Status and Choose the Next Step for runtime decisions, Connect and Manage Channels for an AI Partner for channel setup, Choose the Right AI Partner for a Task for ownership decisions, and Check and Recover an AI Partner After a Problem for recovery.

Data boundary

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