MoviePilot Update

Use this skill for MoviePilot restart and upgrade operations.

Use the built-in moviepilot_api tool only. The host selects fixed API routes, authenticates with the trusted Agent identity, and applies administrator and confirmation policy. Never request or pass an API token, URL, HTTP method, shell command, or legacy helper script.

Operations

Check versions

{"operation_id":"system.versions","path_params":{},"query":{},"body":{}}

This read-only operation lists available MoviePilot releases.

Restart MoviePilot

{"operation_id":"system.restart","path_params":{},"query":{},"body":{}}

Restart requires explicit confirmation and interrupts the current Agent session.

Release update

Check for the highest stable V3 Release and inspect current progress. A manual check may replace an older prepared target with a newer version; failed checks preserve downloaded packages:

{"operation_id":"system.update.check","path_params":{},"query":{},"body":{}}
{"operation_id":"system.update.status","path_params":{},"query":{},"body":{}}

When supports_batch_update=true, prepare the latest backend, matching frontend, and site resources together. This does not restart MoviePilot:

{"operation_id":"system.update.download","path_params":{},"query":{},"body":{"target":"all"}}

After every non-idle item in updates reports state=ready and no item has a check error, installation requires a separate explicit confirmation:

{"operation_id":"system.update.install","path_params":{},"query":{},"body":{"target":"all"}}

install writes one verified install intent and restarts MoviePilot once. Do not call it until the user explicitly confirms the restart. Use target=application or target=resources for a specifically requested single-target update. On older hosts without supports_batch_update, retain the single-target flow; an omitted target defaults to application.