Openclaw Face Follow

curl --noproxy "*" -X POST http://127.0.0.1:8010/api/v1/session/connect \
  -H 'Content-Type: application/json' \
  -d '{"prefer_real":true,"allow_sim_fallback":false}'

3. Start follow.

Use this by default for demos. It enables attention mode: track a face when one is visible, briefly hold when the target disappears, then switch into idle scan fallback.

curl --noproxy "*" -X POST http://127.0.0.1:8010/api/v1/follow/start \
  -H 'Content-Type: application/json' \
  -d '{"target_kind":"face","enable_idle_scan_fallback":true}'

If the user explicitly wants pure face follow without idle behavior, disable fallback:

curl --noproxy "*" -X POST http://127.0.0.1:8010/api/v1/follow/start \
  -H 'Content-Type: application/json' \
  -d '{"target_kind":"face","enable_idle_scan_fallback":false}'

4. Inspect status when needed.

curl --noproxy "*" http://127.0.0.1:8010/api/v1/follow/status

Important fields:

• data.control_mode: attention means face follow with idle-scan fallback; follow means pure follow.
• data.follow.mode: commonly tracking, hold, or scanning.
• data.follow.target_visible: whether a target is currently visible.
• data.follow.last_error: backend-side follow error, if any.
• data.follow.last_result_status: latest status from the /latest observation source.

5. Stop follow when the user asks to stop tracking.

curl --noproxy "*" -X POST http://127.0.0.1:8010/api/v1/follow/stop

Decision Rules

• Use this skill when the user asks for face follow, person follow, subject tracking, 主播跟随, or “keep the person in frame”.
• Prefer target_kind="face" unless the caller explicitly asks for person or generic target tracking.
• Prefer enable_idle_scan_fallback=true for demo mode because it avoids a dead still camera when nobody is in frame.
• If the user only wants standby cruise and not tracking, use openclaw-idle-scan instead.

Notes

• follow/start automatically replaces any currently running follow or idle-scan worker.
• The backend already has tuned defaults, so a small JSON payload is usually enough.
• If the follow request fails with NOT_CONNECTED, connect the session first.
• If the worker is running but the arm is not reacting, inspect data.follow.last_error and data.follow.last_result_status.