> For the complete documentation index, see [llms.txt](https://commandbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commandbox.ortusbooks.com/5.8.0/release-history/4.x-versions/whats-new-in-4.6.0.md).

# What's New in 4.6.0

## Release Notes

### Bug

* \[[COMMANDBOX-934](https://ortussolutions.atlassian.net/browse/COMMANDBOX-934)] - Server commands can have huge delay on Windows
* \[[COMMANDBOX-937](https://ortussolutions.atlassian.net/browse/COMMANDBOX-937)] - List artifacts alphabetically.
* \[[COMMANDBOX-939](https://ortussolutions.atlassian.net/browse/COMMANDBOX-939)] - /usr/bin/open on Linux
* \[[COMMANDBOX-942](https://ortussolutions.atlassian.net/browse/COMMANDBOX-942)] - Errors in command CFCs can cause box to exit completely during tab complete
* \[[COMMANDBOX-949](https://ortussolutions.atlassian.net/browse/COMMANDBOX-949)] - Running native binary that returns lots of text can perform poorly
* \[[COMMANDBOX-950](https://ortussolutions.atlassian.net/browse/COMMANDBOX-950)] - Interceptor service blows up if you register a module with an interceptor not matching any current states
* \[[COMMANDBOX-951](https://ortussolutions.atlassian.net/browse/COMMANDBOX-951)] - Allow modules to register an interceptor with no currently valid states
* \[[COMMANDBOX-953](https://ortussolutions.atlassian.net/browse/COMMANDBOX-953)] - Catch errors from desktop.isDesktopSupported()

### New Feature

* \[[COMMANDBOX-930](https://ortussolutions.atlassian.net/browse/COMMANDBOX-930)] - Allow system setting (env var) expansions in REPL
* \[[COMMANDBOX-932](https://ortussolutions.atlassian.net/browse/COMMANDBOX-932)] - Improve task DSL to allow access to exit code
* \[[COMMANDBOX-944](https://ortussolutions.atlassian.net/browse/COMMANDBOX-944)] - Add config setting to debug raw native command being used in the "run" command

### Improvement

* \[[COMMANDBOX-249](https://ortussolutions.atlassian.net/browse/COMMANDBOX-249)] - Enforce correct casing conventions on scaffolding commands
* \[[COMMANDBOX-927](https://ortussolutions.atlassian.net/browse/COMMANDBOX-927)] - Update propertyFile core module
* \[[COMMANDBOX-928](https://ortussolutions.atlassian.net/browse/COMMANDBOX-928)] - Improve default ignores in box.json from init command.
* \[[COMMANDBOX-929](https://ortussolutions.atlassian.net/browse/COMMANDBOX-929)] - Disable ping to time server host by default
* \[[COMMANDBOX-931](https://ortussolutions.atlassian.net/browse/COMMANDBOX-931)] - Allow exit code to be returned via "return" keyword
* \[[COMMANDBOX-935](https://ortussolutions.atlassian.net/browse/COMMANDBOX-935)] - Improve syntax highlighting in REPL
* \[[COMMANDBOX-938](https://ortussolutions.atlassian.net/browse/COMMANDBOX-938)] - Checking interrupted status from inside a thread doesn't end the task/command
* \[[COMMANDBOX-943](https://ortussolutions.atlassian.net/browse/COMMANDBOX-943)] - Remove hint from default CFC in Lucee for CommandBox CFCs with no hint of their own
* \[[COMMANDBOX-945](https://ortussolutions.atlassian.net/browse/COMMANDBOX-945)] - Endpoint URL shows incorrectly for forgebox endpoints
* \[[COMMANDBOX-948](https://ortussolutions.atlassian.net/browse/COMMANDBOX-948)] - Enhance tab complete for private slugs


---

# 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://commandbox.ortusbooks.com/5.8.0/release-history/4.x-versions/whats-new-in-4.6.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.