●Change8

Migrating to InvokeAI v6.9.0

Version v6.9.0 introduces 2 breaking changes. This guide details how to update your code.

Released: 10/17/2025

2
Breaking Changes
3
Migration Steps
2
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

Model ManagerModel identification logic

Breaking Changes

●Issue #1

The internal model storage directory structure for Invoke-managed models has changed from nested folders (<models_dir>/<type>/<base>/model.safetensors) to a flat structure where each model resides in its own UUID-named folder (<models_dir>/<model_key_uuid>/model.safetensors). This requires a data migration on first run.

●Issue #2

Manually adding models to the Invoke-managed models directory or moving/deleting them within that directory will now cause the database to lose track of them, as the structure is strictly managed by Invoke.

Migration Steps

  1. 1
    On first run after installing this release, Invoke will perform automatic data migrations, including updating the database and restructuring the Invoke-managed models directory.
  2. 2
    If you encounter errors during migration, create a GH issue or seek help in the #new-release-discussion channel on Discord.
  3. 3
    Users on older GPUs (20xx and 10xx series) may experience issues installing/updating due to recent torch updates; manual downgrading of torch has been reported as a potential workaround.

Release Summary

This release significantly improves Invoke's Model Manager by refactoring model identification logic and normalizing the internal model storage directory structure. A key user-facing change is that previously unidentifiable models are now installed as 'Unknown' rather than being deleted.

Need More Details?

View the full release notes and all changes for InvokeAI v6.9.0.

View Full Changelog