Operations

Sprite operations

Check runtime health, inspect logs, resync Sprite Services, upgrade binaries, verify the proxy origin, and diagnose older installs.

Status

Check the installed Sprite services:

zodex sprite status --sprite dev-sprite

The expected services are zodexd and zodex-prd.

The status command also has the alias:

zodex sprite services-status --sprite dev-sprite

Read service logs from the operator machine:

zodex sprite logs --sprite dev-sprite --service zodexd --lines 100
zodex sprite logs --sprite dev-sprite --service zodex-prd --lines 100

Use --duration when investigating a time window:

zodex sprite logs --sprite dev-sprite --service zodexd --duration 30m

The logs command also has the alias:

zodex sprite service-logs --sprite dev-sprite --service zodexd --lines 100

Check runtime health through the Sprite path:

zodex sprite health --sprite dev-sprite

You can also verify the public origin and proxy:

zodex proxy verify-origin --sprite dev-sprite
curl https://dev-zodex.example.net/health

A healthy daemon returns:

{"status":"ok"}

After changing service definitions or runtime configuration:

zodex sprite sync --sprite dev-sprite --force-recreate

To avoid stopping detached services during a targeted sync:

zodex sprite sync --sprite dev-sprite --skip-stop-detached

Upgrade an installed runtime:

zodex sprite upgrade --sprite dev-sprite --version latest

To upgrade while also updating repo or URL auth behavior:

zodex sprite upgrade   --sprite dev-sprite   --version v0.2.10   --repo amxv/zodex   --url-auth sprite

After an upgrade, verify service status, logs, proxy origin, reader-backed clone, and one short command execution through MCP.

For older pre-zodex Sprites, check these before debugging the new runtime: