v6.9.0

This release focuses on improvements to Invoke's Model Manager. The changes are mostly internal, with one significant user-facing change and a data migration.

On first run after installing this release, Invoke will do some data migrations:

• Run-of-the mill database updates.
• Update some model records to work with internal Model Manager changes, described below.
• Restructure the Invoke-managed models directory into a flat directory structure, where each model gets its own folder named by the model's UUID. Models outside the Invoke-managed models directory are not moved.

If you see any errors or run into any problems, please create a GH issue or ask for help in the #new-release-discussion channel of the Invoke discord.

Model Installation Improvements

Invoke analyzes models during install to attempt to identify them, recording their attributes in the database. This includes the type of model, its base architecture, its file format, and so on. This release includes a number of improvements to that process, both user-facing and internal.

Unknown Models

Previously, when this identification fails, we gave up on that model. If you had downloaded the model via Invoke, we would delete the downloaded file.

As of this release, if we cannot identify a model, we will install it as an Unknown model. If you know what kind of model it is, you can try editing the model via the Model Manager UI to set its type, base, format, and so on. Invoke may be able to run the model after this.

If the model still doesn't work, please create a GH issue linking to the model so we can improve model support. The internal changes in this release are focused on making it easier for contributors to support new models.

Invoke-managed Models Directory

Previously, as a relic of times long past, Invoke's internal model storage was organized in nested folders: <models_dir>/<type>/<base>/model.safetensors. Many moons ago, we didn't have a database, and models were identified by putting them into the right folder. This has not been the case for a long time.

As of this release, Invoke's internal model storage has a normalized, flat directory structure. Each model gets its own folder, named its unique key: <models_dir>/<model_key_uuid>/model.safetensors.

On first startup of this release, Invoke will move model files into the new flat structure. Your non-Invoke-managed models (i.e. models outside the Invoke-managed models directory) won't be touched.

We understand this change may seem user-unfriendly at first, but there are good reasons for it:

• This structure eliminates the possibility of model name conflicts, which have caused of numerous hard-to-fix bugs and errors.
• It reinforces that the internal models directory is Invoke-managed:
  • Adding models to this directory manually does not add them to Invoke. With the previous structure, users often dropped models into a folder and expected them to work.
  • Deleting models from this directory or moving them in the directory causes the database to lose track of the models.
• It obviates the need to move models around when changing their type and base.

Refactored Model Identification system

Several months ago, we started working on a new API to improve model identification (aka "probing" or "classification"). This process involves analyzing model files to determine what kind of model it is.

As of this release, the new API is complete and all legacy model identification logic has been ported to it. Along with the changes in #8577, the process of adding new models to Invoke is much simpler.

Model Identification Test Suite

Besides the business logic improvements, model identification is now fully testable!

When we find a model that is not identified correctly, we can add that model to the test suite, which currently has test cases for 70 models.

Models can be many GB in size and are thus not particularly well-suited to be stored in a git repo. We can work around this by creating lightweight representations of models. Model identification typically relies on analyzing model config files or state dict keys and shapes, but we do not need the tensors themselves for this process.

This allows us to strip out the weights from model files, leaving only the model's "skeleton" as a test case. The 70-model test suite is currently about 115MB but represents hundreds of GB of models.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• refactor: model manager v3 by @psychedelicious in #8607
• tidy: docs and some tidying by @psychedelicious in #8614
• chore: prep for v6.9.0rc1 by @psychedelicious in #8615
• feat: reidentify model by @psychedelicious in #8618
• fix(ui): generator nodes by @psychedelicious in #8619
• chore(ui): point ui lib dep at gh repo by @psychedelicious in #8620

Full Changelog: v6.8.1...v6.9.0

v6.9.0rc3

This release focuses on improvements to Invoke's Model Manager. The changes are mostly internal, with one significant user-facing change and a data migration.

On first run after installing this release, Invoke will do some data migrations:

• Run-of-the mill database updates.
• Update some model records to work with internal Model Manager changes, described below.
• Restructure the Invoke-managed models directory into a flat directory structure, where each model gets its own folder named by the model's UUID. Models outside the Invoke-managed models directory are not moved.

If you see any errors or run into any problems, please create a GH issue or ask for help in the #new-release-discussion channel of the Invoke discord.

Model Installation Improvements

Invoke analyzes models during install to attempt to identify them, recording their attributes in the database. This includes the type of model, its base architecture, its file format, and so on. This release includes a number of improvements to that process, both user-facing and internal.

Unknown Models

Previously, when this identification fails, we gave up on that model. If you had downloaded the model via Invoke, we would delete the downloaded file.

As of this release, if we cannot identify a model, we will install it as an Unknown model. If you know what kind of model it is, you can try editing the model via the Model Manager UI to set its type, base, format, and so on. Invoke may be able to run the model after this.

If the model still doesn't work, please create a GH issue linking to the model so we can improve model support. The internal changes in this release are focused on making it easier for contributors to support new models.

Invoke-managed Models Directory

Previously, as a relic of times long past, Invoke's internal model storage was organized in nested folders: <models_dir>/<type>/<base>/model.safetensors. Many moons ago, we didn't have a database, and models were identified by putting them into the right folder. This has not been the case for a long time.

As of this release, Invoke's internal model storage has a normalized, flat directory structure. Each model gets its own folder, named its unique key: <models_dir>/<model_key_uuid>/model.safetensors.

On first startup of this release, Invoke will move model files into the new flat structure. Your non-Invoke-managed models (i.e. models outside the Invoke-managed models directory) won't be touched.

We understand this change may seem user-unfriendly at first, but there are good reasons for it:

• This structure eliminates the possibility of model name conflicts, which have caused of numerous hard-to-fix bugs and errors.
• It reinforces that the internal models directory is Invoke-managed:
  • Adding models to this directory manually does not add them to Invoke. With the previous structure, users often dropped models into a folder and expected them to work.
  • Deleting models from this directory or moving them in the directory causes the database to lose track of the models.
• It obviates the need to move models around when changing their type and base.

Refactored Model Identification system

Several months ago, we started working on a new API to improve model identification (aka "probing" or "classification"). This process involves analyzing model files to determine what kind of model it is.

As of this release, the new API is complete and all legacy model identification logic has been ported to it. Along with the changes in #8577, the process of adding new models to Invoke is much simpler.

Model Identification Test Suite

Besides the business logic improvements, model identification is now fully testable!

When we find a model that is not identified correctly, we can add that model to the test suite, which currently has test cases for 70 models.

Models can be many GB in size and are thus not particularly well-suited to be stored in a git repo. We can work around this by creating lightweight representations of models. Model identification typically relies on analyzing model config files or state dict keys and shapes, but we do not need the tensors themselves for this process.

This allows us to strip out the weights from model files, leaving only the model's "skeleton" as a test case. The 70-model test suite is currently about 115MB but represents hundreds of GB of models.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• chore: v6.8.1 by @psychedelicious in #8610
• refactor: model manager v3 by @psychedelicious in #8607
• tidy: docs and some tidying by @psychedelicious in #8614
• chore: prep for v6.9.0rc1 by @psychedelicious in #8615

Full Changelog: v6.8.1...v6.9.0rc3

v6.9.0rc2

This release focuses on improvements to Invoke's Model Manager. The changes are mostly internal, with one significant user-facing change and a data migration.

On first run after installing this release, Invoke will do some data migrations:

• Run-of-the mill database updates.
• Update some model records to work with internal Model Manager changes, described below.
• Restructure the Invoke-managed models directory into a flat directory structure, where each model gets its own folder named by the model's UUID. Models outside the Invoke-managed models directory are not moved.

If you see any errors or run into any problems, please create a GH issue or ask for help in the #new-release-discussion channel of the Invoke discord.

Model Installation Improvements

Invoke analyzes models during install to attempt to identify them, recording their attributes in the database. This includes the type of model, its base architecture, its file format, and so on. This release includes a number of improvements to that process, both user-facing and internal.

Unknown Models

Previously, when this identification fails, we gave up on that model. If you had downloaded the model via Invoke, we would delete the downloaded file.

As of this release, if we cannot identify a model, we will install it as an Unknown model. If you know what kind of model it is, you can try editing the model via the Model Manager UI to set its type, base, format, and so on. Invoke may be able to run the model after this.

If the model still doesn't work, please create a GH issue linking to the model so we can improve model support. The internal changes in this release are focused on making it easier for contributors to support new models.

Invoke-managed Models Directory

Previously, as a relic of times long past, Invoke's internal model storage was organized in nested folders: <models_dir>/<type>/<base>/model.safetensors. Many moons ago, we didn't have a database, and models were identified by putting them into the right folder. This has not been the case for a long time.

As of this release, Invoke's internal model storage has a normalized, flat directory structure. Each model gets its own folder, named its unique key: <models_dir>/<model_key_uuid>/model.safetensors.

On first startup of this release, Invoke will move model files into the new flat structure. Your non-Invoke-managed models (i.e. models outside the Invoke-managed models directory) won't be touched.

We understand this change may seem user-unfriendly at first, but there are good reasons for it:

• This structure eliminates the possibility of model name conflicts, which have caused of numerous hard-to-fix bugs and errors.
• It reinforces that the internal models directory is Invoke-managed:
  • Adding models to this directory manually does not add them to Invoke. With the previous structure, users often dropped models into a folder and expected them to work.
  • Deleting models from this directory or moving them in the directory causes the database to lose track of the models.
• It obviates the need to move models around when changing their type and base.

Refactored Model Identification system

Several months ago, we started working on a new API to improve model identification (aka "probing" or "classification"). This process involves analyzing model files to determine what kind of model it is.

As of this release, the new API is complete and all legacy model identification logic has been ported to it. Along with the changes in #8577, the process of adding new models to Invoke is much simpler.

Model Identification Test Suite

Besides the business logic improvements, model identification is now fully testable!

When we find a model that is not identified correctly, we can add that model to the test suite, which currently has test cases for 70 models.

Models can be many GB in size and are thus not particularly well-suited to be stored in a git repo. We can work around this by creating lightweight representations of models. Model identification typically relies on analyzing model config files or state dict keys and shapes, but we do not need the tensors themselves for this process.

This allows us to strip out the weights from model files, leaving only the model's "skeleton" as a test case. The 70-model test suite is currently about 115MB but represents hundreds of GB of models.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• chore: v6.8.1 by @psychedelicious in #8610
• refactor: model manager v3 by @psychedelicious in #8607
• tidy: docs and some tidying by @psychedelicious in #8614

Full Changelog: v6.8.1...v6.9.0rc2

v6.9.0rc1

This release focuses on improvements to Invoke's Model Manager. The changes are mostly internal, with one significant user-facing change and a data migration.

On first run after installing this release, Invoke will do some data migrations:

• Run-of-the mill database updates.
• Update some model records to work with internal Model Manager changes, described below.
• Restructure the Invoke-managed models directory into a flat directory structure, where each model gets its own folder named by the model's UUID. Models outside the Invoke-managed models directory are not moved.

If you see any errors or run into any problems, please create a GH issue or ask for help in the #new-release-discussion channel of the Invoke discord.

Model Installation Improvements

Invoke analyzes models during install to attempt to identify them, recording their attributes in the database. This includes the type of model, its base architecture, its file format, and so on. This release includes a number of improvements to that process, both user-facing and internal.

Unknown Models

Previously, when this identification fails, we gave up on that model. If you had downloaded the model via Invoke, we would delete the downloaded file.

As of this release, if we cannot identify a model, we will install it as an Unknown model. If you know what kind of model it is, you can try editing the model via the Model Manager UI to set its type, base, format, and so on. Invoke may be able to run the model after this.

If the model still doesn't work, please create a GH issue linking to the model so we can improve model support. The internal changes in this release are focused on making it easier for contributors to support new models.

Invoke-managed Models Directory

Previously, as a relic of times long past, Invoke's internal model storage was organized in nested folders: <models_dir>/<type>/<base>/model.safetensors. Many moons ago, we didn't have a database, and models were identified by putting them into the right folder. This has not been the case for a long time.

As of this release, Invoke's internal model storage has a normalized, flat directory structure. Each model gets its own folder, named its unique key: <models_dir>/<model_key_uuid>/model.safetensors.

On first startup of this release, Invoke will move model files into the new flat structure. Your non-Invoke-managed models (i.e. models outside the Invoke-managed models directory) won't be touched.

We understand this change may seem user-unfriendly at first, but there are good reasons for it:

• This structure eliminates the possibility of model name conflicts, which have caused of numerous hard-to-fix bugs and errors.
• It reinforces that the internal models directory is Invoke-managed:
  • Adding models to this directory manually does not add them to Invoke. With the previous structure, users often dropped models into a folder and expected them to work.
  • Deleting models from this directory or moving them in the directory causes the database to lose track of the models.
• It obviates the need to move models around when changing their type and base.

Refactored Model Identification system

Several months ago, we started working on a new API to improve model identification (aka "probing" or "classification"). This process involves analyzing model files to determine what kind of model it is.

As of this release, the new API is complete and all legacy model identification logic has been ported to it. Along with the changes in #8577, the process of adding new models to Invoke is much simpler.

Model Identification Test Suite

Besides the business logic improvements, model identification is now fully testable!

When we find a model that is not identified correctly, we can add that model to the test suite, which currently has test cases for 70 models.

Models can be many GB in size and are thus not particularly well-suited to be stored in a git repo. We can work around this by creating lightweight representations of models. Model identification typically relies on analyzing model config files or state dict keys and shapes, but we do not need the tensors themselves for this process.

This allows us to strip out the weights from model files, leaving only the model's "skeleton" as a test case. The 70-model test suite is currently about 115MB but represents hundreds of GB of models.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• chore: v6.8.1 by @psychedelicious in #8610
• refactor: model manager v3 by @psychedelicious in #8607
• tidy: docs and some tidying by @psychedelicious in #8614

Full Changelog: v6.8.1...v6.9.0rc1

v6.8.1

This patch release fixes the Exception in ASGI application startup error that prevents Invoke from starting.

The error was introduced by an upstream dependency (fastapi). We've pinned the fastapi dependency to the last known working version.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• Fix(nodes): color correct invocation by @dunkeroni in #8605

Full Changelog: v6.8.0...v6.8.1

v6.8.0

This minor release includes a handful of fixes and enhancements.

Fixes

• When accepting raster layer adjustments, the opacity of the layer was "baked" in.
• Corrected help text for non-in-place model installation. Previously, the help text said that a non-in-place model install would copy the model files. This is incorrect; it moves them into the Invoke-managed models dir.
• Failure to queue generations with an error like Failed to Queue Batch / Unknown Error.

Enhancements

• Added a crop tool. For now, it is only enabled for Global Ref Images.
  • Click the crop icon on the Ref Image preview to open the tool.
  • Adjust the crop box and click apply to save the cropped image for that ref image.
  • To revert, open the crop tool, click Reset, then Apply to revert to the original image.
  • We'll explore integrating this new tool elsewhere in the app in a future update.
• Improved Model Manager tab UI. Thanks @joshistoast!
• Keyboard shortcuts to navigate prompt history. Use alt/option+up/down to move through history.
• Support for the NOOB-IPA-MARK1 IP Adapter. Thanks @Iq1pl!

Internal

• Support for dynamic model drop-downs in Workflow Editor. This change greatly reduces the amount of frontend code changes needed to support a new model type. Node authors may need to update their nodes to prevent warnings from being displayed. However, there are no breakages expected. See #8577 for more details.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• fix(ui): do not reset params state on studio init nav to generate tab by @psychedelicious in #8572
• feat(model manager): 💄 refactor model manager ui by @joshistoast in #8564
• Prompt history shortcuts by @hipsterusername in #8571
• feat(ui): crop tool by @psychedelicious in #8562
• chore: prep for v6.8.0rc1 by @psychedelicious in #8574
• fix(ui): allow scrolling in ModelPane by @joshistoast in #8580
• added support for NOOB-IPA-MARK1 by @Iq1pl in #8576
• feat: dynamic model fields in workflow editor by @psychedelicious in #8577
• ui: translations update from weblate by @weblate in #8575
• fix(ui): ref images for flux kontext not parsed correctly by @psychedelicious in #8587
• feat(nodes): better ui_type deprecations by @psychedelicious in #8586
• restore list_queue_items method by @maryhipp in #8583
• fix(ui): do not bake opacity when rasterizing layer adjustments by @psychedelicious in #8592
• fix(ui): correct the in-place install verbiage, add tooltip by @psychedelicious in #8593
• docs: add BiRefNet and Image Export to communityNodes.md by @veeliks in #8602
• chore: prep for v6.8.0rc2 by @psychedelicious in #8581
• chore: prep for v6.8.0 by @psychedelicious in #8604

New Contributors

• @Iq1pl made their first contribution in #8576
• @veeliks made their first contribution in #8602

Full Changelog: v6.7.0...v6.8.0

v6.8.0rc2

This minor release includes a handful of fixes and enhancements.

Fixes

• When accepting raster layer adjustments, the opacity of the layer was "baked" in.
• Corrected help text for non-in-place model installation. Previously, the help text said that a non-in-place model install would copy the model files. This is incorrect; it moves them into the Invoke-managed models dir.

Enhancements

• Added a crop tool. For now, it is only enabled for Global Ref Images.
  • Click the crop icon on the Ref Image preview to open the tool.
  • Adjust the crop box and click apply to save the cropped image for that ref image.
  • To revert, open the crop tool, click Reset, then Apply to revert to the original image.
  • We'll explore integrating this new tool elsewhere in the app in a future update.
• Improved Model Manager tab UI. Thanks @joshistoast!
• Keyboard shortcuts to navigate prompt history. Use alt/option+up/down to move through history.
• Support for the NOOB-IPA-MARK1 IP Adapter. Thanks @Iq1pl!

Internal

• Support for dynamic model drop-downs in Workflow Editor. This change greatly reduces the amount of frontend code changes needed to support a new model type. Node authors may need to update their nodes to prevent warnings from being displayed. However, there are no breakages expected. See #8577 for more details.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• fix(ui): do not reset params state on studio init nav to generate tab by @psychedelicious in #8572
• feat(model manager): 💄 refactor model manager ui by @joshistoast in #8564
• Prompt history shortcuts by @hipsterusername in #8571
• feat(ui): crop tool by @psychedelicious in #8562
• chore: prep for v6.8.0rc1 by @psychedelicious in #8574
• fix(ui): allow scrolling in ModelPane by @joshistoast in #8580
• added support for NOOB-IPA-MARK1 by @Iq1pl in #8576
• feat: dynamic model fields in workflow editor by @psychedelicious in #8577
• ui: translations update from weblate by @weblate in #8575
• fix(ui): ref images for flux kontext not parsed correctly by @psychedelicious in #8587
• feat(nodes): better ui_type deprecations by @psychedelicious in #8586
• restore list_queue_items method by @maryhipp in #8583
• fix(ui): do not bake opacity when rasterizing layer adjustments by @psychedelicious in #8592
• fix(ui): correct the in-place install verbiage, add tooltip by @psychedelicious in #8593
• docs: add BiRefNet and Image Export to communityNodes.md by @veeliks in #8602
• chore: prep for v6.8.0rc2 by @psychedelicious in #8581

New Contributors

• @Iq1pl made their first contribution in #8576
• @veeliks made their first contribution in #8602

Full Changelog: v6.7.0...v6.8.0rc2

v6.8.0rc1

This minor release includes a few QoL enhancements.

Enhancements

• Added a crop tool. For now, it is only enabled for Global Ref Images.
  • Click the crop icon on the Ref Image preview to open the tool.
  • Adjust the crop box and click apply to save the cropped image for that ref image.
  • To revert, open the crop tool, click Reset, then Apply to revert to the original image.
  • We'll explore integrating this new tool elsewhere in the app in a future update.
• Improved Model Manager tab UI. Thanks @joshistoast!
• Keyboard shortcuts to navigate prompt history. Use alt/option+up/down to move through history.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• fix(ui): do not reset params state on studio init nav to generate tab by @psychedelicious in #8572
• feat(model manager): 💄 refactor model manager ui by @joshistoast in #8564
• Prompt history shortcuts by @hipsterusername in #8571
• feat(ui): crop tool by @psychedelicious in #8562
• chore: prep for v6.8.0rc1 by @psychedelicious in #8574

Full Changelog: v6.7.0...v6.8.0rc1

v6.7.0

This minor release includes improved object selection on Canvas, layer adjustments, prompt history and a handful of other enhancements and fixes.

Select Object v2

We've made some major improvements to object selection.

• Segment Anything v2 is now supported. You can choose between SAM1 and SAM2. We've found that SAM2 is much faster than SAM1, but often does not perform as well, so we left SAM1 as an option.
• You may now draw a box around the target object. The box doesn't need to be exact - sometimes, you can get better results by making it a bit smaller than the target object. Points are still supported and can be used independently or as a refinement for a box.
• Holding shift while clicking creates an exclude point if you have include selected. If you have selected exclude, holding shift will instead create an include point.
• You can now provide a text prompt instead of a box and points. Use very simple language for best results. Internally, this uses Grounding DINO to identify the target.

Raster Layer Adjustments

Right click a Raster Layer to add adjustments. Adjustments are non-destructive, though you can accept them to bake them into the layer.

You can adjust brightness, contrast, saturation, temperature, tint, and sharpness, or use the curves editor to adjust each channel independently.

Thanks @dunkeroni for implementing this very useful feature.

Prompt History

There's a new button in the Positive Prompt box for prompt history. Your last 100 unique prompts are stored for easy recall. You can search them, delete individual prompts, or clear the whole list.

Enhancements

• Improved object selection on Canvas.
• Raster layer adjustments. Thanks @dunkeroni!
• Support for mathematical expressions in number input fields. Currently, these are only enabled for fields in the Workflow Editor (including Builder Forms). Thanks @csehatt741!
• Prompt history for Positive Prompt.
• Queue list now sorts with newest on top. You can reverse the sort if you want, to restore the previous sorting. Thanks @csehatt741!
• Updated translations. Thanks @Harvester62 @Linos1391!

Fixes

• Fixed an issue that prevented you from using LoRA weights outside the range -1 to 2.
• Fixed an issue where LoRA settings could be lost on refresh.
• Fixed an issue where LoRAs with weights outside the range -1 to 2 were not able to be recalled from metadata.
• Fixed an issue where popovers like the Canvas Settings popover were obscured by other UI elements.
• Fixed a path traversal vulnerability affecting the bulk downloads API.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• feat(ui): reverse queue list by @csehatt741 in #8488
• fix(ui): route metadata to gemini node by @psychedelicious in #8547
• fix(ui): LoRA number input min/max restored by @csehatt741 in #8542
• fix(app): path traversal via bulk downloads paths by @psychedelicious in #8548
• feat(ui): maths enabled on numeric input fields in workflow editor by @csehatt741 in #8549
• feat(ui): SAM2 Node & Integration by @hipsterusername in #8526
• queue list: remove completed_at, restore field values by @maryhipp in #8555
• ai(ui): add CLAUDE.md to frontend by @psychedelicious in #8556
• feat(ui): Raster Layer Color Adjusters by @dunkeroni in #8420
• ui: translations update from weblate by @weblate in #8545
• chore: prep for v6.7.0rc1 by @psychedelicious in #8557
• fix(ui): extend lora weight schema to accept full range of weights by @psychedelicious in #8559
• feat(ui): simple prompt history by @psychedelicious in #8561
• fix(ui): render popovers in portals to ensure they are on top of other ui elements by @psychedelicious in #8568
• fix(ui): dedupe prompt history by @psychedelicious in #8567
• ui: translations update from weblate by @weblate in #8563
• chore: prep for v6.7.0 by @psychedelicious in #8569

Full Changelog: v6.6.0...v6.7.0

v6.7.0rc1

This minor release includes improved object selection on Canvas, layer adjustments, math evaluation in Workflow Editor number fields, and a handful of other enhancements and fixes.

Select Object v2

We've made some major improvements to object selection.

• Segment Anything v2 is now supported. You can choose between SAM1 and SAM2. We've found that SAM2 is much faster than SAM1, but often does not perform as well, so we left SAM1 as an option.
• You may now draw a box around the target object. The box doesn't need to be exact - sometimes, you can get better results by making it a bit smaller than the target object. Points are still supported and can be used independently or as a refinement for a box.
• Holding shift while clicking creates an exclude point if you have include selected. If you have selected exclude, holding shift will instead create an include point.
• You can now provide a text prompt instead of a box and points. Use very simple language for best results. Internally, this uses Grounding DINO to identify the target.

Raster Layer Adjustments

Right click a Raster Layer to add adjustments. Adjustments are non-destructive, though you can accept them to bake them into the layer.

You can adjust brightness, contrast, saturation, temperature, tint, and sharpness, or use the curves editor to adjust each channel independently.

Thanks @dunkeroni for implementing this very useful feature.

Enhancements

• Improved object selection on Canvas.
• Raster layer adjustments. Thanks @dunkeroni!
• Support for mathematical expressions in number input fields. Currently, these are only enabled for fields in the Workflow Editor (including Builder Forms). Thanks @csehatt741!
• Queue list now sorts with newest on top. You can reverse the sort if you want, to restore the previous sorting. Thanks @csehatt741!
• Updated translations. Thanks @Harvester62 @Linos1391!

Fixes

• Fixed an issue that prevented you from using LoRA weights outside the range -1 to 2.
• Fixed a path traversal vulnerability affecting the bulk downloads API.

Installing and Updating

The Invoke Launcher is the recommended way to install, update and run Invoke. It takes care of a lot of details for you - like installing the right version of python - and runs Invoke as a desktop application.

Note: With recent updates to torch, users on older GPUs (20xx and 10xx series) will likely run into issues with installing/updating. We are still evaluating how we can support older GPUs, but in the meantime users have found success manually downgrading torch. Head over to discord if you need help.

Follow the Quick Start guide to get started with the launcher.

If you don't want to use the launcher, or need a headless install, you can follow the manual install guide.

What's Changed

• feat(ui): reverse queue list by @csehatt741 in #8488
• fix(ui): route metadata to gemini node by @psychedelicious in #8547
• fix(ui): LoRA number input min/max restored by @csehatt741 in #8542
• fix(app): path traversal via bulk downloads paths by @psychedelicious in #8548
• feat(ui): maths enabled on numeric input fields in workflow editor by @csehatt741 in #8549
• feat(ui): SAM2 Node & Integration by @hipsterusername in #8526
• queue list: remove completed_at, restore field values by @maryhipp in #8555
• ai(ui): add CLAUDE.md to frontend by @psychedelicious in #8556
• feat(ui): Raster Layer Color Adjusters by @dunkeroni in #8420
• ui: translations update from weblate by @weblate in #8545
• chore: prep for v6.7.0rc1 by @psychedelicious in #8557

Full Changelog: v6.6.0...v6.7.0rc1