Model Lifecycle

AI model providers regularly release new models and retire older ones. Seclai tracks these lifecycle changes automatically and keeps you informed — through in-app alerts, email notifications, and actionable replacement recommendations — so your agents always run on supported models.

Overview

Every prompt model in Seclai has a lifecycle managed by its provider (Anthropic, OpenAI, Google, etc.). When a provider deprecates or sunsets a model, Seclai:

1. Detects the change — checks model lifecycle status daily at 00:15 UTC
2. Creates in-app alerts — for every affected agent on your account
3. Sends email notifications — once per account per model (at 00:45 UTC)
4. Suggests replacements — successor, upgrade, and alternative models

You can monitor everything from the Agents page, individual agent detail pages, and via the API or MCP.

Lifecycle Stages

Models move through three stages:

Active

The model is fully supported and functioning normally. No action required.

Deprecated

The provider has announced the model will be removed in the future. The model still works but you should plan a migration to a replacement model.

Sunset

The model has been fully removed by the provider and no longer works. Any agent step using a sunset model will fail at runtime. Immediate action is required.

Model Alerts

Seclai generates three types of model lifecycle alerts:

Model Deprecated

Created when a model used by one of your agents is deprecated by the provider. The alert message includes the affected agent name, step names, and the model's sunset date (if known).

Model Sunset

Created when a model used by one of your agents has been fully sunset. This is a critical alert — the affected agent steps will no longer function.

Newer Model Available

Created when a newer model in the same family is released (e.g., Claude Opus 4.6 when you're using Claude Opus 4). This is an informational alert — your current model still works fine.

Alert Banner

The Model Lifecycle Alerts banner appears at the top of:

• Agents list page — shows all unread model alerts across the account
• Agent detail page — shows alerts specific to that agent

Each alert can be individually dismissed, or you can dismiss all at once. The banner polls for new alerts every 5 minutes.

Model Recommendations

When a model is deprecated or sunset, Seclai recommends replacement models based on capability compatibility.

Recommendation Types

Recommendations are grouped into three categories:

Each recommendation includes the model's capabilities (tool use, thinking, structured output), context window size, and a human-readable reason for the suggestion.

Capability Filters

You can filter recommendations to match your requirements:

Recommendation Panel

When editing a prompt call step that uses a deprecated or sunset model, the Model Recommendations panel appears alongside the model selector. It shows the available replacements grouped by type and includes a Use button to switch models with one click.

Email Notifications

Seclai sends email notifications for model deprecation and sunset events:

• One email per account per model — you won't receive duplicate notices
• Includes affected agents — the email lists every agent and step using the model
• Sent at 00:45 UTC daily — shortly after the lifecycle check at 00:15 UTC
• Only for deprecated and sunset models — "newer available" alerts are in-app only

Opting Out

To stop receiving email notifications for a specific model alert type:

1. Go to Agent → Alerts tab (or the account-wide alerts settings)
2. Find the Model Deprecated or Model Sunset alert type
3. Toggle it off

When an alert type is disabled at the account level, both the in-app alert and the email notification are suppressed. Per-agent overrides can be configured for fine-grained control.

Configuring Model Alerts

Model lifecycle alerts appear alongside the standard agent alert types in the Alerts tab. Unlike threshold-based alerts (like Consecutive Failures), model alerts have no configurable thresholds — they fire automatically when the condition is met.

You can:

• Enable/disable each model alert type independently
• Configure per-agent overrides that take precedence over account-wide settings
• Set notification recipients using the same distribution options as other alerts

By default, Model Deprecated and Model Sunset alerts are enabled for all accounts. Newer Model Available is disabled by default and must be opted in.

Automatic Model Upgrades

Instead of waiting for a manual model migration, you can configure agents to automatically adopt successor models when one becomes available. This is controlled by the auto-upgrade strategy set at the agent level (or overridden per step).

Upgrade Strategies

The strategy can be set at two levels:

• Agent level (prompt_model_auto_upgrade_strategy) — applies to all Prompt Call and Insight steps that do not set a step-level override.
• Step level (auto_upgrade_strategy in the step definition) — overrides the agent-level setting for that step only.

Auto Rollback

When an auto-upgraded model is in use, Seclai can automatically roll back to the previous model configuration if it detects quality or compliance regressions. Rollback creates a new agent branch commit reverting the step's model to the last known-good version.

Enable rollback at the agent level with prompt_model_auto_rollback_enabled: true. Like the upgrade strategy, this can be overridden per step with auto_rollback_enabled.

On a successful rollback, Seclai:

1. Creates a new branch commit restoring the prior model selection
2. Sends a model_rollback_success email notification
3. Emits a PROMPT_MODEL_AUTO_ROLLBACK_SUCCEEDED activity event

If no valid prior configuration is found, a PROMPT_MODEL_AUTO_ROLLBACK_FAILED event is emitted instead.

Rollback Triggers

You can specify which failure signals trigger a rollback via prompt_model_auto_rollback_triggers (agent level) or auto_rollback_triggers (step level). When the field is null, the system defaults apply.

Default triggers (when prompt_model_auto_rollback_triggers is null): agent_eval_fail, governance_block, agent_run_failed.

Configuring Auto Upgrade

Via the App: Open the agent, go to Settings → Model Lifecycle, and choose an upgrade strategy and rollback preferences.

Via the API:

# Enable cautious auto-upgrade with rollback on eval failures and governance blocks
curl -X PUT "https://api.seclai.com/api/agents/$AGENT_ID" \
  -H "X-API-Key: $SECLAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt_model_auto_upgrade_strategy": "cautious_adopter",
    "prompt_model_auto_rollback_enabled": true,
    "prompt_model_auto_rollback_triggers": ["agent_eval_fail", "governance_block"]
  }'

# Disable auto-upgrade
curl -X PUT "https://api.seclai.com/api/agents/$AGENT_ID" \
  -H "X-API-Key: $SECLAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prompt_model_auto_upgrade_strategy": "none"}'

Via MCP: Use the update_agent tool with prompt_model_auto_upgrade_strategy, prompt_model_auto_rollback_enabled, and prompt_model_auto_rollback_triggers parameters.

For step-level overrides, set auto_upgrade_strategy, auto_rollback_enabled, and auto_rollback_triggers directly in the step definition via update_agent_definition. See Agent Steps: Model Lifecycle Controls for field details.

API Access

All model lifecycle features are available via the REST API with API key authentication:

# Get replacement recommendations for a model
curl "https://api.seclai.com/api/models/{model_id}/recommendations" \
  -H "X-API-Key: $SECLAI_API_KEY"

# Get recommendations with capability filters
curl "https://api.seclai.com/api/models/{model_id}/recommendations?require_tool_use=true&min_context_tokens=100000" \
  -H "X-API-Key: $SECLAI_API_KEY"

# List model lifecycle alerts
curl "https://api.seclai.com/api/models/alerts" \
  -H "X-API-Key: $SECLAI_API_KEY"

# List unread alerts for a specific agent
curl "https://api.seclai.com/api/models/alerts?agent_id=$AGENT_ID&unread_only=true" \
  -H "X-API-Key: $SECLAI_API_KEY"

# Get unread alert count
curl "https://api.seclai.com/api/models/alerts/unread-count" \
  -H "X-API-Key: $SECLAI_API_KEY"

# Dismiss a single alert
curl -X PATCH "https://api.seclai.com/api/models/alerts/$ALERT_ID/read" \
  -H "X-API-Key: $SECLAI_API_KEY"

# Dismiss all alerts
curl -X POST "https://api.seclai.com/api/models/alerts/mark-all-read" \
  -H "X-API-Key: $SECLAI_API_KEY"

MCP Access

Model lifecycle tools are available through the MCP (Model Context Protocol) server for use with agentic coding tools:

These tools use the same API key authentication as all other MCP tools.

Next Steps

• Alerts — Configure all alert types including model lifecycle alerts
• Agents — Learn about creating and configuring agents
• API Examples — More API usage examples
• Dashboard — Monitor aggregated metrics for your account