Skip to content

Model deprecation / sunset warnings #5452

@kshitijk4poor

Description

@kshitijk4poor

Problem

When a model is deprecated or approaching sunset, users get no warning from Hermes. They discover it only when the API starts returning errors. The models.dev integration already has a status field that can be "deprecated" but nothing reads it for warnings.

Proposed Solution

In the model capability pre-flight (if merged) or during AIAgent init, check the models.dev status field. If the model is marked deprecated, emit a warning via _vprint. Low effort — the data source already exists.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low — cosmetic, nice to havecomp/agentCore agent loop, run_agent.py, prompt buildertype/featureNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions