Automatically pull and start a new version of Clayde as it becomes available

[max-tet]

Right now, for every new clayde version, a script on the server must be executed. This should go automatically. For example, there is the watchtower sidecar that monitors and updates the image. That could be used. But I am open to other option. Update should be fast, at most a few minutes, not 24h. Balance update latency and the risk of hitting rate limits.

[ClaydeCode]

Preliminary Plan

Approach

Add a Watchtower sidecar service to docker-compose.yml. Watchtower polls the container registry, detects image updates, and restarts the container automatically — no server-side scripts needed.

Key configuration choices:

• Poll interval: 5 minutes (--interval 300) — fast enough for prompt updates, low registry API pressure
• Scope: monitor only the clayde service via label filter (com.centurylinklabs.watchtower.enable=true) — future-proofs against adding other services
• Registry auth: not needed, image is public
• Cleanup: remove old images after update
• Notifications: none

This is a small, self-contained change to docker-compose.yml only.

---

This looks like a small issue. React with 👍 to approve this preliminary plan and proceed directly to implementation.

[max-tet]

• Access to the image is public.
• Clayde is the only service on the host, but label filter is good regardless, to be future-proof.
• No update notification needed.

[ClaydeCode]

Plan updated. All three questions answered: image is public (no credentials needed), label filter will be used for future-proofing even though Clayde is the only service, and no notifications required. The approach is confirmed — small change to docker-compose.yml only.

[ClaydeCode]

Implementation complete — PR opened: #61