[OPS] Model tag health check -- validate all configured models before loop start #116

Closed
opened 2026-04-04 11:55:14 +00:00 by Timmy · 1 comment
Owner

Problem

claude-haiku-4-20250414 and claude-3-5-sonnet-latest were retired by Anthropic, causing 404 errors across cron jobs and Ezra. Failures were silent until manually discovered.

Solution

Add a pre-flight model validation step to deploy.sh and loop startup:

  1. For each model tag in config.yaml, make a minimal API call to verify the model exists
  2. If any model returns 404, log a warning and suggest the correct current tag
  3. Block loop startup if the primary model is dead

Acceptance

  • deploy.sh --validate checks all model tags
  • Prints clear pass/fail for each model
  • Known-good model tag list maintained in timmy-config
## Problem claude-haiku-4-20250414 and claude-3-5-sonnet-latest were retired by Anthropic, causing 404 errors across cron jobs and Ezra. Failures were silent until manually discovered. ## Solution Add a pre-flight model validation step to deploy.sh and loop startup: 1. For each model tag in config.yaml, make a minimal API call to verify the model exists 2. If any model returns 404, log a warning and suggest the correct current tag 3. Block loop startup if the primary model is dead ## Acceptance - deploy.sh --validate checks all model tags - Prints clear pass/fail for each model - Known-good model tag list maintained in timmy-config
Timmy self-assigned this 2026-04-04 11:55:14 +00:00
Timmy closed this issue 2026-04-04 16:00:08 +00:00
Author
Owner

Delivered in commit 3cf9f0d on main. Tested locally. Closing.

Delivered in commit 3cf9f0d on main. Tested locally. Closing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#116