> For the complete documentation index, see [llms.txt](https://wirebox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wirebox.ortusbooks.com/readme/introduction/whats-new-with-8.3.0.md).

# What's New With 8.3.0

October 13, 2026

You can read the complete ecosystem changes in the [ColdBox 8.3.0 release notes](https://coldbox.ortusbooks.com/readme/release-history/whats-new-with-8.3.0).

## Release Notes

{% tabs %}
{% tab title="WireBox" %}

### Changed

The `CFScopes` scope class was renamed to `EngineScopes` (`coldbox.system.ioc.scopes.EngineScopes`). Scope names are unchanged, but there is no alias for the old class path ([#715](https://github.com/ColdBox/coldbox-platform/pull/715)).

### Fixed

[COLDBOX-1455](https://ortussolutions.atlassian.net/browse/COLDBOX-1455) Singleton, engine (application, session, server) and CacheBox scopes no longer hand objects to other threads before dependency wiring completes. Other threads wait for wiring to finish, while the wiring thread can still resolve circular dependencies ([#715](https://github.com/ColdBox/coldbox-platform/pull/715)).

A circular dependency partner remains marked as wiring until the outermost object build completes, across all scopes ([#718](https://github.com/ColdBox/coldbox-platform/pull/718)).
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wirebox.ortusbooks.com/readme/introduction/whats-new-with-8.3.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.